Scrum Artifacts Flashcards

1
Q

What are Scrum Artifacts

A
  1. Product Backlog
  2. Monitoring Progress toward Goals
  3. Sprint Backlog (select use stories from product backlog)
  4. Monitoring Sprint Progress
  5. Increments
  6. Definition of Done / Acceptance Criteria
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the purpose of Scrum Artifacts

A
  1. Increase level of information / Transparancy
  2. How to inspect / measure / forcast the project and the product
  3. What are the rodblocks
  4. Use information radiator to see how the work is being done and what adption is needed
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the characters of Product Backlog

A
  1. The PO’s responsibility
  2. It is a ordered list of everything needed for the final product.
  3. Presented in a simple business language to stakholders.
  4. Allow dynamically change and improving, thus it’s not about completion.
  5. Start Sprint prtocess as long as there are user stories with acceptence criteria in the Backlog.
  6. PO sets factors to determine the value of each item, i.e. ROI.
  7. Strat the high priority first.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

How Scrum master can help Product backlog

A
  1. SM has responsibility to help PO to groom and maintain the Product Backlog.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Who decide the estimate to complete a user story

A

Development Team

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Waht informations are included in a user story

A
  1. Story Name
  2. Story Description
  3. Add Alert ( such as customer alert)
  4. Due Date
  5. Change Log
  6. Complexcity
    7.Estimate
  7. Categories
  8. Assigment
  9. Tracker
  10. Additional Fields
  11. Color for Categorizing Items
  12. Task
  13. Attachments
  14. Comments
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is a Daily Scrum

A
  1. A 15 minutes time box event for the Scream Team.
  2. Held everyday . What the Scrum team plans to work for the next 24 hours.
  3. Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog.
  4. Optimizes the probability that Scrum Team will meet the Sprint Goal.
  5. It is not a status meeting for all stakholders. Rather than how to remove road block.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What are the three questions that all member of the Scrum Team should answer (yes, every day)

A
  1. What has been accomplished since the last meeting?
  2. What will be done before the next meeting?
  3. What obstacles are in the way fro me or the Scrum Team from meeting the Sprint Goal.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What are the responsibility of SM and Scrum Team

A
  1. SM ensure the team has the meeting but the ST is responsible for conducting the Daily Scrum
  2. SM to ensure the meeting is within the 15-mins time box (really important for SM to reduce the noice and keep the flow)
  3. SM ensure Daily Scrum is held everyday and resolve if there is a dispute.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What Daily Scrum improve (what are the benefits)

A
  1. Communication
  2. Eliminate other meetings
  3. Identify impediments for removal
  4. Hightlight and promote quick decision-making
  5. Improve the Scrum Team’s level of knowledge.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is a Sprint Review

A
  1. It is held at the end of the Sprint to inspect the increments and adapts the product Backlog if needed.
  2. The Scrum Team and stakeholders are collabrated what was done in the Sprint.
  3. 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.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Who is respobsible for everyone understand the Sprint Review event and keep the event in the time box

A

SM

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is the flow of Sprint Review

A
  1. Scrum Team and stakholders are invited by the product Owner.
  2. PO explains what Backlog items have been “Done” and what has not. Item will not be presented if it’s not 100% “Done”.
  3. Scrum Team discuss, in the Sprint, what went well, what was the issue, and how the problem is solved.
  4. The Scrum Team demo the work that has been “Done” and answer questions about the increment.
  5. The PO discuss the Product Backlog as it stands. The PO projects the target and deliver estimation based on the current progress.
  6. The whole team decides the next step, to contribute valueable input to the next Sprint.
  7. Review how the marketplace or potential use of product might have changed; what is the most valuable things to do next.
  8. Review timeline, budget, potential capabilities, anticipation for the next release.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is a Sprint Retrospective Review

A
  1. Occurs after the Sprint Review and prior to the next Sprint Planning.
  2. It is an opportunity for the team to inspect itself and create a plan for improvements that can be enhanced during the next Sprint.
  3. The advised time box is 3 hrs. fro an 4 week Sprints.
  4. SM facilitate the meeting and the team to understand the purpose.
  5. SM ensure the meeting is productive and positive.
  6. SM is responsible to keep the time-box.
17
Q

Waht are the principle of the Sprint Retrospective Event

A
  1. Always look for ways to improve; do not matter how little, there should be improvements.
  2. 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
  1. At any time, work can be summerized.
  2. PO tracks work at every sprint review.
  3. PO compare work remining in pervious sprint to access progress towards the goal.
  4. The information should made available to all stakeholders.
  5. Empirical processes ?? are used in situations where it is difficult to have consistent processes.
  6. 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
  1. It is created during the Sprint Planning event.
  2. All Screm Team member collaborate to create it
  3. 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.
  4. The Sprint Backlog is frozen after the Sprint Planning; meaning the stories can not be added or removed diring the Sprint.
  5. If items need to be re-negociate, justify or clear, the PO yake the respobsbility.
  6. The details will become more complete as the Sprints are continue.
20
Q

Monitoring Sprint Progress

A
  1. The responsibility of the Scream Team at least once per Daily Scrum.
  2. The information is used to calculate the likelihood of achieveing the Sprint Goal and completing all items of the Sprint Backlog.
  3. 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
  1. The Increment is the total of all the product Backlog items at the end of Sprint.
  2. The Increment must be “Done; meaning it is in useable condition and meet Scrum Team’s definition of “Done”.
  3. It is a step toward a project vision.
  4. PO can decide whether to release it or not.
22
Q

What is the priciple of “ Definition of Done”

A
  1. Every Scrum Team member need to have consistent understanding of whqat “Done” means.
  2. Transparency helps with the understanding.
  3. It is used to access when the work is completed on the product increment.
  4. It is a guide for Scrum Team in knowing how many Baclog items can be selected during the Sprint Planning.
  5. Check point of increments deliveries. ex: elements are consistent and integratable.