1
Q
What are Scrum Artifacts
A
- Product Backlog
- Monitoring Progress toward Goals
- Sprint Backlog (select use stories from product backlog)
- Monitoring Sprint Progress
- Increments
- Definition of Done / Acceptance Criteria
2
Q
What are the purpose of Scrum Artifacts
A
- 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
3
Q
What are the characters of Product Backlog
A
- 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.
4
Q
How Scrum master can help Product backlog
A
- SM has responsibility to help PO to groom and maintain the Product Backlog.
5
Q
Who decide the estimate to complete a user story
A
Development Team
6
Q
Waht informations are included in a user story
A
- 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
7
Q
What is work breakdown structure
A
A structure or a principle to break down the work that can not be break down anymore
8
Q
What is a Daily Scrum
A
- 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.
9
Q
What are the three questions that all member of the Scrum Team should answer (yes, every day)
A
- 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.
10
Q
What are the responsibility of SM and Scrum Team
A
- 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.
11
Q
What Daily Scrum improve (what are the benefits)
A
- Communication
- Eliminate other meetings
- Identify impediments for removal
- Hightlight and promote quick decision-making
- Improve the Scrum Team’s level of knowledge.
12
Q
What is a Sprint Review
A
- 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.
13
Q
What is the suggest time box for Sprint Review for a 4 weeks Sprint
A
4 hrs. ( 1 hrs. every week) For shorter Sprint, it is shorter.
14
Q
Who is respobsible for everyone understand the Sprint Review event and keep the event in the time box
A
SM
15
Q
What is the flow of Sprint Review
A
- 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.
16
Q
What is a Sprint Retrospective Review
A
- Occurs after the Sprint Review and prior to the next Sprint Planning.
- It is an opportunity for the team to inspect itself and create a plan for improvements that can be enhanced during the next Sprint.
- The advised time box is 3 hrs. fro an 4 week Sprints.
- SM facilitate the meeting and the team to understand the purpose.
- SM ensure the meeting is productive and positive.
- SM is responsible to keep the time-box.
17
Q
Waht are the principle of the Sprint Retrospective Event
A
- Always look for ways to improve; do not matter how little, there should be improvements.
- The purpose is to
- Inspect how the last Sprint went regarding to people, 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 it work.
18
Q
Ho the PO monitor the progress towards the goal
A
- At any time, work can be summerized.
- PO tracks work at every sprint review.
- PO compare work remining in pervious sprint to access progress towards the goal.
- The information should made available to all stakeholders.
- Empirical processes ?? are used in situations where it is difficult to have consistent processes.
- Use Burn-Down Chart to visulized the progress ; how many remaining work vs. Time, one Char for one Sprint.
19
Q
What is the Sprint Backlog
A
- It is created during the Sprint Planning event.
- All Screm Team member collaborate to create it
- The backlog includes
- a number of items selected from the top of Product backlog, based on the estimated work and capacity.
- The Sprint Gaol will help to describe the real meaning of the items and direct the effort.
- It shows as a detailed plan for item delivery and Sprint gaol realization during the Sprint.
- The Sprint Backlog is frozen after the Sprint Planning; meaning the stories can not be added or removed diring the Sprint.
- If items need to be re-negociate, justify or clear, the PO yake the respobsbility.
- The details will become more complete as the Sprints are continue.
20
Q
Monitoring Sprint Progress
A
- The responsibility of the Scream Team at least once per Daily Scrum.
- The information is used to calculate the likelihood of achieveing the Sprint Goal and completing all items of the Sprint Backlog.
- Use Burn-down Chart and make it a part of the Sprint board that everyone can see.
21
Q
What is the “Increment” in a Sprint
A
- The Increment is the total of all the product Backlog items at the end of Sprint.
- The Increment must be “Done; meaning it is in useable condition and meet Scrum Team’s definition of “Done”.
- It is a step toward a project vision.
- PO can decide whether to release it or not.
22
Q
What is the priciple of “ Definition of Done”
A
- Every Scrum Team member need to have consistent understanding of whqat “Done” means.
- Transparency helps with the understanding.
- It is used to access when the work is completed on the product increment.
- It is a guide for Scrum Team in knowing how many Baclog items can be selected during the Sprint Planning.
- Check point of increments deliveries. ex: elements are consistent and integratable.
Agile Scrum
flashcards
Decks in class (14)
# Cards
