Agile 2

Question 1

Structure of Scrum:

Answer 1

Product backlog
Sprint backlog
Daily standup
Sprint cycle, executing task
Product increment- outcome

Question 2

Product Backlog:

Answer 2

• Project to do list
• updated when changes are needed or new tasks
• product owner, to produce product backlog

Question 3

Sprint backlog:

Answer 3

-Cycle where some of the tasks are executed
- Event to plan the sprint, quarterly planning event
- tasks from product backlog move to sprint backlog
- tasks are completed in the sprint cycle

Question 4

Sprint planning

Answer 4

What will take place during the sprint
After planning, then execution can start…

Daily scrum or daily standup:
To discuss what they did yesterday today and issues they are facing

Question 5

Sprint review:

Answer 5

When the sprint ends, we show accomplishments and walkthrough on outcome of the sprint

Whole team will participate

Only the tasks that are completed are what’s presented:
Contributes to future planning
Better decisions and lessons learned for the next sprint and stakeholder feedback

Question 6

Daily scrum

Answer 6

Development team
Scrum master- product manager or team leader
Enacting scrum values and that they practice Agile methodologies

Question 7

Sprint retrospective:

Answer 7

-1 hour per week after sprint review
- managed by the scrum master
- brain storming sailboat and post it

Question 8

What is sailboat:

Answer 8

What is pushing us forward?

What is holding is back?

What are the risks?

What is the goal we are working towards

Question 9

Sprint retrospective(post it)

Answer 9

What went well?

What could be improved?

Actions for the future?

Question 10

Agile tool (kanban)

Answer 10

Effective if the team is committed

Question 11

Scrum vs Kanban

Answer 11

Origin: Scrum started in software and kanban started in vehicle manufacturing

Ideology: scum you learn from experiences and prioritising kanban is working on visuals to improve work in progress

Approach: scrum regular fixed length sprints typically 1-4 weeks and kanban has a continuous flow

Practices: sprint planning, sprint, daily scrum, sprint review sprint retrospective and for kanban visualise workflow incorporate feedback loops

Roles: product owner scrum master and development team
No required roles in Kanban