1. 3 Roles
1.1. Product Owner
1.1.1. Maximize the value of the product resulting
1.1.2. Manage the product backlog
1.1.2.1. Clearly express the product backlog items
1.1.2.2. Oder the product backlog
1.1.2.3. The product backlog is visible, transparent, clear to all.
1.1.2.4. Optimize the value of work the development team performs
1.1.2.5. Ensure the development team understand items in the product backlog.
1.2. Development Team
1.2.1. Team size from 3 to 9 members
1.2.2. 5 Characteristics
1.2.2.1. Self organization
1.2.2.2. Cross functional
1.2.2.3. No Titles
1.2.2.4. No Sub-Teams
1.2.2.5. Committed to achieving the Sprint Goal and delivering a high quality increment.
1.3. Scrum Master Service
1.3.1. Product Owner
1.3.1.1. Ensuring that goals, scope and product domain are understanded by everyone on Scrum Team.
1.3.1.2. Finding techniques for effective Product Backlog management
1.3.1.3. Heling the Scrum Team understand the need for clear and concise Product Backlog items.
1.3.1.4. Helpoing the Product Owner in understanding product planning in an empirical environment.
1.3.1.5. Ensruing the Product Owner how to arrange the Product Backlog to maximize value.
1.3.1.6. Helping Product Owner in Understanding and practicing agility
1.3.1.7. Facilitating Scrum Events as requested or needed.
1.3.2. Development Team
1.3.2.1. Coaching the Development Team in Self-Organization and Cross-Functionality.
1.3.2.2. Helping the Development Team to create high-value products.
1.3.2.3. Removing impediments to the Development Team’s progress.
1.3.2.4. Facilitating Scrum events as requested or needed.
1.3.2.5. Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood.
1.3.3. Organization
1.3.3.1. Leading and Coaching the organization in applying Scrum.
1.3.3.2. Planning Scrum implementations within the organization.
1.3.3.3. Helping employees and stakeholders understand and enact Scrum and empirical product development.
1.3.3.4. Causing change that increases the productivity of the Scrum Team;
1.3.3.5. Working with other Scrum Masters to increase the effectiveness of the Scrum application in the organization
2. 5 Events
2.1. The Sprint
2.1.1. Time-box is from 2 to 4 weeks
2.1.2. No changes in the sprint
2.1.3. Keep quality goals
2.1.4. Scope may be clarified and re-negotiated between Product Owner and Development Team
2.1.5. Cancelling a Sprint
2.1.5.1. By Product Owner and may be under influence from Stakeholders, Development Team, Scrum Master.
2.1.5.2. - If The Sprint Goal becomes obsolete, - If the company changes direction - If market or technology conditions change - If no longer makes sense given the circumstances
2.1.5.3. - Any completed and "Done" Product Backlog items are reviewed. - All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog.
2.2. Sprint Planning
2.2.1. Time-box is maximum to 8 hours for one-month sprint.
2.2.2. Purpose 1: - What can be delivered in the upcoming sprint? -- Input: Product Backlog Items -- Output: Sprint Goal.
2.2.3. Purpose 2: - How to achieve the work need to deliver the Incremental? (Sprint backlog) -- Select Product Backlog Items. -- Plan for delivering( discuss, forecast, decide, decompose, estimate, re-negotiate)
2.2.4. The Sprint Goal is an objective set. - Created in the sprint planning - Provide the great reason to build it. - Re-negotiation between Product Owner and Development Team if it's different from the development team expectation.
2.2.5. The duration of a Sprint is fixed and cannot be shortened or lengthened.
2.3. Daily Scrum
2.3.1. Time-Box is 15 minutes
2.3.2. Occur every day of sprint on the same time and place. And answer 3 questions: - What did you do yesterday? - What will you do today? - Do you see any impediment to you or the team?
2.3.3. Purpose: - Optimize Team Collaboration and Performance. - Improve Communications and eliminate other meetings. - Identify impediments, highlight and promote make decision making quickly. - Improve Development team knowledge. - Inspect progress of completing work in the sprint backlog. - Inspect progress toward the Sprint Goal.
2.3.4. - This meeting is a key inspection and adaptation meeting.
2.4. Sprint Review
2.4.1. Happen on end of the sprint, informal meeting and not a status meeting.
2.4.2. Time-box is 4 hours for one-month sprint.
2.4.3. Elements of Sprint Review
2.4.3.1. Attendees include the Scrum Team and key stakeholders invited by the Product Owner.
2.4.3.2. The Product Owner explains what Product Backlog items have been "Done" and what has not been "Done".
2.4.3.3. The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved.
2.4.3.4. The Development Team demonstrates the work that it has "Done" and answers questions about the Increment.
2.4.3.5. The Product Owner discusses the Product Backlog as it stands. Product Owner projects likely target and delivery dates based on progress to date (if needed);
2.4.3.6. The Sprint Review provides valuable input to the next Sprint Planning.
2.4.3.7. Review of how the marketplace or the most potential use value of the product to do next.
2.4.3.8. Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated releases of functionality or capability of the product.
2.5. Sprint Retrospective
2.5.1. Occurs after the Sprint Review and before the next Sprint Planning.
2.5.2. Time-box is 3 hours for one-month Sprints
2.5.3. Ensuring positive and productive
2.5.4. Provides a formal opportunity to focus on inspection and adaptation
2.5.5. The participants: Development Team, Product Owner
2.5.6. Purpose:
2.5.6.1. Inspect how the last Sprint went with regards to people, relationships, process, and tools.
2.5.6.2. Identify and order the major items that went well and potential improvements.
2.5.6.3. Create a plan for implementing improvements to the way the Scrum Team does its work.
2.5.7. Objectives
2.5.7.1. make Scrum Development process and practices more effective and enjoyable for the next Sprint
2.5.7.2. Increase product quality by improving work processes or adapting the definition of "Done"
3. 3 Artifacts
3.1. Purpose: - Present work or value to provide transparency and opportunities for inspection and adaptation. - To maximize transparency of key information.
3.2. Product Backlog
3.2.1. The single source of requirements.
3.2.2. Content, availability, and ordering of Product Backlog is presented by Product Owner
3.2.3. A Product Backlog is never completed. If a product exists, its Product Backlog also exists.
3.2.4. Including: features, functions, requirements, enhancements, fixes.
3.2.5. Attributes like a description, order, estimate, value and test descriptions.
3.2.6. It constantly changes to identify what the product needs to be appropriate, competitive, and useful.
3.2.7. Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog
3.2.8. Higher ordered product backlog items are more details and clearer. And Lower ordered is less detail.
3.2.9. The Development Team is responsible for all estimates
3.2.10. Monitoring Progress Toward Goals
3.2.10.1. Tracked by Product Owner at least every Sprint Review
3.2.10.2. Assess progress toward completing projected work by comparing the total remaining work of current sprint review and previous sprint review
3.2.10.3. This information is made transparent to all stakeholders.
3.2.10.4. Ways are used to forecast progress like burn-downs, burn-ups, or cumulative flows
3.3. Sprint Backlog
3.3.1. is the set of Product Backlog items selected, plus the delivery plan and the sprint goal for the Sprint.
3.3.2. It belongs solely to the Development Team. And only the Development Team can change its Sprint Backlog during a Sprint.
3.3.3. Monitoring Sprint Progress
3.3.3.1. Tracked by Development Team at least for every Daily Scrum to forecast the ability to achieve the Sprint Goal.
3.4. Increment
3.4.1. Is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints
3.4.2. Is a step toward a vision or goal
3.5. A Scrum Master can detect incomplete transparency by: - inspecting the artifacts, - sensing patterns, - listening closely to what is being said, - and detecting differences between expected and real results.
4. 5 Values
4.1. Commitment
4.2. Encourage
4.3. Focus
4.4. Respect
4.5. Openess
5. Other
5.1. Definition of "Done"
5.1.1. is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum.
5.1.2. New Definition doesn't apply for the work in the previously "Done" sprints.