Scrum Artifacts Flashcards
What are Scrum Artifacts
- Product Backlog
- Monitoring Progress toward Goals
- Sprint Backlog (select use stories from product backlog)
- Monitoring Sprint Progress
- Increments
- Definition of Done / Acceptance Criteria
What are the purpose of Scrum Artifacts
- Increase level of information / Transparancy
- How to inspect / measure / forcast the project and the product
- What are the rodblocks
- Use information radiator to see how the work is being done and what adption is needed
What are the characters of Product Backlog
- The PO’s responsibility
- It is a ordered list of everything needed for the final product.
- Presented in a simple business language to stakholders.
- Allow dynamically change and improving, thus it’s not about completion.
- Start Sprint prtocess as long as there are user stories with acceptence criteria in the Backlog.
- PO sets factors to determine the value of each item, i.e. ROI.
- Strat the high priority first.
How Scrum master can help Product backlog
- SM has responsibility to help PO to groom and maintain the Product Backlog.
Who decide the estimate to complete a user story
Development Team
Waht informations are included in a user story
- Story Name
- Story Description
- Add Alert ( such as customer alert)
- Due Date
- Change Log
- Complexcity
7.Estimate - Categories
- Assigment
- Tracker
- Additional Fields
- Color for Categorizing Items
- Task
- Attachments
- Comments
What is work breakdown structure
A structure or a principle to break down the work that can not be break down anymore
What is a Daily Scrum
- A 15 minutes time box event for the Scream Team.
- Held everyday . What the Scrum team plans to work for the next 24 hours.
- Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog.
- Optimizes the probability that Scrum Team will meet the Sprint Goal.
- It is not a status meeting for all stakholders. Rather than how to remove road block.
What are the three questions that all member of the Scrum Team should answer (yes, every day)
- What has been accomplished since the last meeting?
- What will be done before the next meeting?
- What obstacles are in the way fro me or the Scrum Team from meeting the Sprint Goal.
What are the responsibility of SM and Scrum Team
- SM ensure the team has the meeting but the ST is responsible for conducting the Daily Scrum
- SM to ensure the meeting is within the 15-mins time box (really important for SM to reduce the noice and keep the flow)
- SM ensure Daily Scrum is held everyday and resolve if there is a dispute.
What Daily Scrum improve (what are the benefits)
- Communication
- Eliminate other meetings
- Identify impediments for removal
- Hightlight and promote quick decision-making
- Improve the Scrum Team’s level of knowledge.
What is a Sprint Review
- It is held at the end of the Sprint to inspect the increments and adapts the product Backlog if needed.
- The Scrum Team and stakeholders are collabrated what was done in the Sprint.
- Any changes to the Product backlog during the Sprint, attendees collabrate on the next step tp optimize values.
4 It is a informal format, the presentation of the increments is intended to elict feedbacks and foster collabration.
What is the suggest time box for Sprint Review for a 4 weeks Sprint
4 hrs. ( 1 hrs. every week) For shorter Sprint, it is shorter.
Who is respobsible for everyone understand the Sprint Review event and keep the event in the time box
SM
What is the flow of Sprint Review
- Scrum Team and stakholders are invited by the product Owner.
- PO explains what Backlog items have been “Done” and what has not. Item will not be presented if it’s not 100% “Done”.
- Scrum Team discuss, in the Sprint, what went well, what was the issue, and how the problem is solved.
- The Scrum Team demo the work that has been “Done” and answer questions about the increment.
- The PO discuss the Product Backlog as it stands. The PO projects the target and deliver estimation based on the current progress.
- The whole team decides the next step, to contribute valueable input to the next Sprint.
- Review how the marketplace or potential use of product might have changed; what is the most valuable things to do next.
- Review timeline, budget, potential capabilities, anticipation for the next release.