Rules to create value in a fast way, how to be agile.

1. Scrum Rules
For successful projects

2. Events
Scrum prescribes 4 events inside a Sprint for Inspection and Adaptation:
● Sprint Planning
● Daily Scrum
● Sprint Review
● Retrospective

3. Sprint
● Time-boxed of one month or shorter
● A new sprints start immediately after the conclusion of previous
● No changes are made that would endanger the Sprint goal
● Quality goals do not decrease
● Scope may be renegotiated between PO and Dev Team
● Limit risk to one calendar month of cost.

4. Sprint Planning
● Time-boxed to a maximun of 8 hours for a 1 month sprint, for shorter sprints, the events is shorter.
● Inputs: PB, Product Increment, Capacity and Past Performance of Dev Team
● Answer the following:
★ What can be done in this sprint
➔ Product Owner Present the Product Backlog
➔ The Product Backlog items are only selected by the Dev. Team
➔ Scrum Team craft the Sprint Goal
★ How will the chosen work get done
➔ Development Team decides how to build this functionality into a “Done”
➔ Enough work is planned for Dev team and decomposed in units of one day or less.
➔ The PBI selected and the Plan for delivering them is called Sprint Backlog
➔ If the Dev Team determines it has too much or too little work, it may renegotiate PBI.
➔ Dev Team self-organizes to undertake the work in the Sprint Backlog

5. Daily Scrum
● Time-Boxed to 15 minutes
● Development Team create a plan for the next 24 hours
● Is held at same time and place to reduce complexity
● Dev Team inspect progress toward the Sprint Goal
● Dev Team inspect progress toward completing the work
● Dev Team is responsible for conducting the daily scrum
● The Scrum Master enforces the rule that only Dev Team participate
● This is a key inspect and adapt meeting

6. Sprint Review
● Time-boxed to 4 hours for 1 month sprints. For shorter sprints, the event is usually shorter.
● Scrum Team and stakeholders collaborate about what was done in the sprint and on the next things
that could be done to optimize value.
● The Dev Team demonstrate the work that it has “Done” and answers questions about the increment.
● The entire group collaborates on what to do next.
● Review the timeline, budget, capabilities and marketplace for the next anticipated release of the
product.
● The result of the SR is a revised PB the defines the probable PBI for the next Sprint.
● The PB may also be adjusted to meet new opportunities.

7. Retrospective
● Time-boxed to 3 hours for 1 month sprints. For shorter sprints, the event is usually shorter.
● Inspect how the last sprint went with regards to people, relationship, 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 its works
● The Scrum Team plans ways to increase product quality by adapting the DoD as appropiate
● Improvements in the next Sprint is the adaptation to the inspection of the Scrum Team itself

8. Scrum Roles

9. Product Owner
● Responsible for maximizing the value of the product and the work of the
Dev Team.
● Is one person responsible for managing the Product Backlog
★ Clearly expressing PBI
★ Ordering Items of PB
★ Ensuring Dev Team understand items in PB
★ Shows what the Scrum Team will work
★ The entire organization must respect his or her decisions

10. Development Team
● Professionals who do the work of delivering a potentially releasable increment of “Done”
product.
● Are structured and empowered by the organization to organize and manage their own work.
● They are self-organizing, cross-functional, with all the skills necesary.
● Scrum recognizes no titles for Dev Team members other than Developer, regardless of the
work being performed by the person
● Scrum recognizes no sub-teams, regardless of particular domains like testing or business
analysis
● Optimal development team size to gain productivity is between 3 and 9 members.

11. Scrum Master
● Is responsible for ensuring Scrum is understood and scrum team adheres to theory,
practices and rules.
● Scrum Master is a servant-leader.
● The scrum master helps everyone to understand which of their interactions are helpful
and which aren’t to maximize value.
● Helps to Product Owner to finding techniques for effective PB management.
● Coaching the Dev Team in self-organization and cross-functionality
● Facilitating Scrum events
● Removing impediments
● Causing change that increases the productivity of the scrum team

12. Artifacts

13. Product Backlog
● Ordered list of everything that might be needed in the product
● The PB evolves as the product and the environment in which it will be used. The PB is dynamic.
● Is a list of features, functions, requirements, enhancements and fixes.
● Have the attributes of description, order, estimate and value
● PB refinement is the act of adding detail, estimates and order to items
● Product Owner and Dev Team Collaborates in refinement
● Refinement usually consumes no more than 10% of the capacity of the Dev. Team.
● PB items can be updated any time by the PO
● Product Backlog Items that can be “Done” by the Dev Team are deemed “Ready” for selection in
the Sprint Planning.

14. Sprint Backlog
● Is the set of Product Backlog Items selected for the sprint, plus a plan for delivering
the product increment.
● Is the forecast by the Dev. Team about what functionality will be in the next increment
and the work needed to deliver that functionality.
● Is the work the Dev. Team identifies to meet the Sprint Goal.
● Only the Dev. Team can modify the Sprint Backlog throughout the sprint.
● As work is completed the estimated work remaining is updated.

15. Product Increment
● Is the sum of all the Product Backlog items completed during a Sprint and
the value of the increments of all previous Sprints.
● The increment must be “Done” at the end of a Sprint
● The increment must be in useable condition.

16. The End