Scrum Guide

Help you understand Scrum and hopefully help you pass Scrum related exams :D Status: Done

76 flashcards · Other · by claudehsu

1. What is Scrum

   A lightweight framework that helps ppl, teams and orgs generate value through adaptive solutions for complex problems.

2. Upon what is Scrum built? a.) collective intelligence of the ppl using it b.) management team to provide detailed instructions Answer: a

3. Scrum is founded on empiricism lean thinking

   1st blank: knowledge comes from experience and making decisions based on what is observed 2nd blank: reduces waste and focuses on the essentials

4. What are the three pillars of Scrum? Transparency Inspection Adaptation

5. Transparency enables inspection. Inspection with out it is misleading and wasteful.

6. How Scrum, the framework, helps with inspection?

   Scrum provides cadence in the form of its 5 events.

7. Inspection enables adaptation. It is considered pointless if no adaptation follows.

8. When should adjustment/adaptation happen? Why?

   As soon as possible. To minimize further deviation.

9. It's possible that ppl involved are not empowered or self-managing. In that case, what is likely to happen?

   In that case, Adaptation becomes more difficult.

10. What are the Scrum Values? Commitment Courage Focus Openness Respect

    Use CCFOR

11. How to under stand the 5 Scrum Values?

    Commitment: commit to achieving its goals and to supporting each other [Claude: commit to try the very best] Focus: focus on the work of the Sprint to make the best possible progress toward these goals Openness: scrum team and its stakeholders are open about the work and the challenges Respect: Scrum team members respect each other to be capable, independent people Courage: scrum team members have the courage to do the right thing, to work on tough problems

12. The Scrum team consists of one Product Owner one Scrum Master Developers

13. What are the two characteristics of Scrum teams Cross-functional Self-managing

    The members have all the skills necessary to create value each Sprint. They internally decide who does what, when, and how.

14. What is the size of a Scrum team?

    Small enough to remain nimble Large enough to complete significant work within a Sprint Typically 10 or fewer ppl. In general, we have found that smaller teams communicate better and are more productive.

15. If a Scrum Team becomes too large, what should we do?

    Consider re-organizing into multiple cohesive Scrum Teams, each focus on the same product. They share the same Product Goal, Product Backlog, and Product Owner.

16. Who should be accountable for creating a valuable, useful Increment every Sprint?

    The Entire Scrum Team.

17. What are the three specific accountability within the Scrum Team? the Product Owner the Scrum Master the Developers

18. Developers are always accountable for what? Tips: Four points

    Creating a plan for the Sprint, the Sprint Backlog Instilling quality by adhering to a Definition of Done Adapting their plan each day toward Sprint Goal[Claude: Daily Scrum] Holding each other accountable as professionals Mnemonic: Think about the scrum events that developers need to attend scrum planning -> create the plan for the sprint daily scrum -> adapt to better reach the sprint goal scrum review -> increment & scrum retrospective -> review DoD, so -> instilling quality of Increment by…

19. What is Product Owner accountable for?

    Maximizing the value of the product. How this is done may vary widely across organizations, Scrum Teams, and individuals.

20. The Product owner is also accountable for effective Product Backlog management. What are the four key points regarding to Product Backlog management?

    Developing and explicitly communicating the Product Goal Creating and clearly communicating Product Backlog items Ordering Product Backlog items Ensuring that the Product Backlog is transparent, visible and understood. Understanding: it's more than just keep documents clear and transparent. It's also about interaction between PO and other roles. Mnemonic: Action related: communicating two entities product goal product backlog items Doc related: two things Product backlog items to be ordered Ent…

21. Can Product Owner delegate the responsibility(having the duty to take care of) to other ppl?

    Yes, but Product Owner remains accountability(being held responsible for the consequences).

22. Can Product Owner be a committee?

    No, Product Owner is one Person. The Product Owner may represent the needs of many stakeholders in the Product Backlog.

23. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice. Which people are included by saying everyone?

    Both within the Scrum Team and the Organization.

24. How does Scrum Master serves the Scrum Team?

    Coaching the Scrum team members in self-management and cross-functionality Helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done Causing the removal of impediments to the Scrum Team's progress Ensuring that all Scrum events take place and are positive, productive, and kept within the time-box Mnemonic: starting from the scrum team's characteristic so coach Scrum team cross-functional & self-management Think about the target/purpose of the team what to d…

25. How does Scrum Master serve the Product Owner?

    Helping find techniques for effective Product Goal definition and Product Backlog management Helping the Scrum Team understand the need for clear and concise Product Backlog items Helping establish empirical product planning for a complex environment Facilitating stakeholder collaboration as requested or needed Mnemonic: The core is the Product Backlog, so as a whole: help on effective Product Goal definition and Product Backlog management as the collection of PBIs: help to understand the need…

26. How does Scrum Master serve the organization?

    Leading, training, and coaching the organization in its Scrum adoption Planning and advising Scrum implementations within the organization Helping employees and stakeholders understand and enact an empirical approach for complex work Removing barriers between stakeholders and Scrum Teams. Mnemonic: Think about the level/process of Scrum adoption, from learning basic knowledge to implement, then to understand the theory behind the sense, and finally a particular practice Promote Scrum adoption A…

27. What are formal opportunities to inspect and adapt Scrum artifacts?

    Each Scrum event

28. Events are used in Scrum to create regularity minimize the need for meetings not defined in Scrum

29. Are all events held at the same time and place or only Daily Scrum is required to be that?

    All events are held at the same time and place to reduce complexity

30. What is a container for all other Scrum events? Answer: Sprint

    It's the heartbeat of Scrum.

31. When does a new Sprint start?

    Immediately after the conclusion of the previous Sprint.

32. During the sprint, No changes are made that would endanger the Sprint Goal - T Quality may decrease a little bit - F The Product Backlog is refined as needed - T Scope may be clarified and renegotiated with the Product Owner as more is learned - T

    Fill in the blanks with 'T'(true) or 'F'(false)

33. Compare long Sprint with short Sprint.

    When a Sprint's horizon is too long the Sprint Goal may become invalid, complexity may rise, and risk may increase. Shorter Sprints can be employed to generate more learning cycles and limit risk of cost and effort to a smaller time frame.

34. Can a Sprint be canceled?

    A Sprint could be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to cancel the Sprint.

35. Who should attend the Sprint Planning?

    The plan is created by the collaborative work of the entire Scrum Team. The Scrum Team may also invite other people to attend Sprint Planning to provide advice.

36. The Sprint Planning addresses three topics. What are they?

    Why is this Sprint valuable? What can be Done this Sprint? How will the chosen work get done?

37. Why is the Sprint valuable?

    The Product Owner proposes how the product could increase its value and utility in the current Sprint. The whole Scrum Team then collaborates to define a Sprint Goal that communicates why the Sprint is valuable to stakeholders. The Sprint Goal must be finalized prior to the end of Sprint Planning.

38. What can be done this sprint?

    Through discussion with the Product Owner, the Developers select items from the Product Backlog. The Scrum Team may refine these items to increases understanding and confidence.

39. How will the chosen work get done?

    Often done by decomposing Product Backlog items into smaller work items of one day or less. How this is done is at the sole discretion of the Developers. No one else tells them how to turn Product Backlog items into Increments of value.

40. What are together referred as the Sprint Backlog?

    Sprint Goal PBIs selected for the Sprint Plan for delivering them

41. Sprint Planning is time-boxed to a maximum of 8 hours for a one-month Sprint.

    Fill in Arabic digit.

42. What's the purpose of the Daily Scrum?

    To inspect progress toward the Sprint Goal Adapt the Sprint Backlog as necessary Adjust the upcoming planned work

43. The Daily Scrum is a 15-minute event for the Developers of the Scrum Team

    For the 1st blank fill in Arabic digits

44. To reduce the complexity, when holding Daily Scrum, it should be at same time same place

45. What are the benefit of having Daily Scrum?

    improve communications identify impediments promote quick decision-making consequently eliminate the need for other meetings

46. Is Daily Scrum the only time Developers are allowed to adjust their plan?

    No, they often meet throughout the day for more detailed discussion about adapting or re-planning.

47. Purpose of Sprint Review?

    inspect the outcome of the Sprint determine further adaptations

48. In Sprint Review, who will present the increment to key stakeholders?

    No mentioned in the guide, but it points out the Scrum Team presents the result of their work to key stakeholders.

49. During the event, what do Scrum Team and stakeholders review?

    what was accomplished in the Sprint what has changed in their environment

50. Is Sprint Review a working session or presentation?

    A working session, and Scrum Team should avoid limiting it to a presentation.

51. Sprint Review is time-boxed to a maximum of 4 hours for a one-month Sprint.

    Fill in Arabic digit

52. What is the purpose of Sprint Retrospective?

    Plan ways to increase quality and effectiveness

53. With regards to what can Scrum Team inspect how the last Sprint went?

    individuals interactions processes tools DoD

54. What do Scrum Teams discuss usually?

    what went well during the Sprint what problems it encountered how those problems were solved

55. What concludes the Sprint? Answer: Sprint Retrospective

56. Scrum's artifacts represent work or value. They are designed to maximize transparency of key information. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: For Product Backlog, it's the Product Goal. For Sprint Backlog, it's the Sprint Goal. For Increment, it's the Definition of Done.

57. What's Product Backlog?

    An emergent ordered list of what is needed to improve the product. It's the single source of work undertaken by the Scrum Team.

58. What's Product Backlog refinement?

    An ongoing activity. It's the act of breaking down and further defining Product Backlog items into smaller more precise items.

59. What do Developers and Product Owner usually do in Product Backlog refinement?

    The Developers are responsible for the sizing and PO may influence the Developers by helping the understand and select trade-offs.

60. What's the commitment of the Product Backlog? Answer: Product Goal

    It's the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next.

61. What's the characteristics of a Product?

    A product is a vehicle to deliver value has a clear boundary known stakeholders well-defined users or customers could be a service a physical product something more abstract

62. The Sprint Backlog is composed of what?

    The Sprint Goal PBIs selected for the Sprint Actionable plan for delivering the Increment

63. Is Sprint Backlog dynamic or fixed in the Sprint?

    It's updated throughout the Sprint as more is learned.

64. Should Sprint Backlog have enough detail?

    Yes, it should have enough detail that they can inspect their progress in the Daily Scrum.

65. What' the commitment of the Sprint Backlog? Answer: Sprint Goal

66. How to understand the Sprint Goal?

    The single object for the Sprint A commitment by the Developers Create coherence and focus, encouraging the Scrum Team to work together rather than on separate initiatives.

67. If the work turns out to be different than Developers expected, what should they do?

    Collaborate with PO to negotiate the scope of the Sprint Backlog within the Sprint without affecting the Sprint Goal.

68. What is Increment?

    A concrete stepping stone toward the Product Goal.

69. Can multiple Increments be created within a Sprint?

    Yes, they can. The sum of the Increments is presented at the Sprint Review.

70. When is an Increment born?

    The moment a Product Backlog item meets the Definition of Done, an Increment is born.

71. Can an Increment be delivered to stakeholders prior to the end of the Sprint?

    Yes, and the Sprint Review should never be considered a gate to releasing value.

72. If an item meets most of the Definition of Done, can it be considered part of an Increment?

    No. The work that doesn't meet the Definition of Done is not part of an Increment.

73. How do we understand DoD?

    The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.

74. If a Product Backlog item doesn't meet DoD, what will usually happen?

    cannot be release or even presented at the Sprint Review returns to the Product Backlog for future consideration

75. If there are multiple Scrum Teams working together on a product, how can they define DoD?

    They must mutually define and comply with the Same DoD. [Claude: think about the Nexus case. A shared DoD, but a team can choose to apply a more rigorous version]

76. Is Scrum framework mutable or immutable?

    Immutable. While implementing only parts of Scrum is possible, the result is not Scrum.