WHAT IS THE SCRUM MASTERS ROLE IN SPRINT RETROSPECTIVE?
- Ensure the meeting is positive and productive.
- The scrum master teaches all to keep it within 3hrs.
- Scrum master makes sure the events take place and attendants understand the purpose.
What is the Scrum Masters Role in Sprint Retrospective?
- Encourages the team to improve within:
- the scrum process framework
- Its development process
- And practices
To make it more enjoyable for the next sprint.
What is purpose of the sprint retrospective?
- Inspect how the last sprint went with regards to people, relationships, process, and tools
- Identify and order the major items that went well and potential improvements
- Create a plan for implementing improvements to the way the scrum team does its work.
During the sprint retro what should happen?
The scrum team PLANS WAYS TO INCREASE PRODUCT QUALITY BY IMPROVING WORK PROCESSES OR ADAPTING THE DEFINITION OF “DONE”, if appropriate and not in conflict with product or organizational standards.
How should a Sprint retro conclude?
- Scrum team should have identified improvements that it will implement in the next sprint.
THIS IS THE ADAPTATION TO THE INSPECTION OF THE SCRUM TEAM ITSELF!
- Sprint retro provides a formal opportunity to focus on inspection and adaptation.
What are scrum artifacts?
Represent work or value to provide transparency and opportunities for inspection and adaptation.
DONE SO EVERYONE HAS THE SAME UNDERSTANDING OF AN ARTIFACT!!!
Name the Scrum Artifacts:
- Product Backlog
- Sprint Backlog
- Increment
What is a Product Backlog? Pt 1
- An ORDERED LIST OF EVERYTHING that is known to be needed in the product.
- 1 Considered a LIVING artifact
- 2 Single source of requirements for any changes to be made to the product.
What is a Product Backlog? Pt 2
- Evolves as the product and work environment evolves.
- Its dynamic, constantly changing to identify what the product needs to be appropriate, competitive, and useful.
- If a product exists so does a product backlog
Who is responsible for it?
What does the earliest development of it contain?
- Product owner is responsible for it all; content, availability and ordering.
- Lays out the initially known and best understood requirements.
What does a product backlog list?
- Features
- Functions
- ReQs
- Enhancements
- And fixes.
That constitute changes to be made to the product in future releases.
What attributes do product backlog items have?
- Description,
- Order
- Estimate
- Value.
Once the increment has been introduced to the market how does this effect the product backlog list?
- The product backlog list grows with the feedback from the marketplace.
- Changes in business requirements, market conditions or tech may cause changes in the product backlog.
Can multiple scrum teams work together on the same product? If yes how?
- . Yes.
2. One product backlog is used to describe the upcoming work on the product.
What is Product backlog refinement?
- The act of adding detail, estimates, and order to items in the product backlog.
- It’s an ongoing process whereby the product owner and the dev team collab on the details of the product backlog items.
- Review and revision of product backlog happens here.
Who decides how and when refinement is done?
What capacity of the dev team is taken up during refinement?
How often can items be updated?
- The scrum team decides how and when refinement is done.
- Refinement usually consumes no more than 10% of the capacity of the dev team.
- At any time by the product owner.
What is the difference between a higher ordered item and a lower ordered item?
Clarity and detail; there is more in the higher ordered items.
Which product backlog items occupy the dev team on the upcoming sprint?
- Refined items that can be reasonably “done” within the sprint timebox (usually one month).
- These items are deemed “ready” for selection in a sprint planning.
- The dev team is responsible for the estimates.
How often can total work remaining to reach a goal be summed?
Who tracks the total work remaining?
How frequently are the checks?
- Whenever.
- Product owner
- Atleast every sprint review
What does the person do to assess progress?
Who can know of the assessment?
- A comparison of work remaining at previous sprint reviews to assess progress toward completing project work by the desired time for the goal.
- All stakeholders.
What is a Sprint Backlog?
The SET OF PRODUCT BACKLOG ITEMS selected for the sprint, plus a plan for delivering the product increment and realizing the sprint goal!
A forecast by the dev team about what functionality will be in the next increment and the work needed to deliver it into a “done” increment.
How does the dev team ensure continuous improvement?
How detailed is a sprint backlog?
- By including at least one high priority process improvement identified in the previous retrospective meeting.
- A plan with enough detail that changes in progress can be understood in the daily scrum.
Who modifies the sprint backlog and how often is it modified?
When does the sprint backlog emerge?
- The dev team makes changes throughout the sprint.
4. During the sprint.
How is sprint progress monitored, who is responsible for it and how do they do it?
At any time during the sprint the total work remaining in the sprint backlog can be summed.
The dev team tracks this work at least for every daily scrum to project likelihood of achieving sprint goal.
By tracking remaining work throughout the sprint the dev team manages its progress.
