How scrum works
Download as PPTX, PDF0 likes249 views
Scrum is a lightweight framework for managing complex work. It consists of a Scrum Team including a Product Owner, Development Team, and Scrum Master. The work occurs in Sprints which include planning, daily standups, development work, a review, and retrospective. The Product Owner prioritizes requirements in the Product Backlog. The team pulls items into the Sprint Backlog for a Sprint. They create an increment of work to demonstrate at the Sprint Review.
How scrum works
- 1. A Quick Overview of Scrum framework By: Annu Rana
- 2. Description A framework within which people can address complex adaptive problems, delivering products of the highest possible value, scrum is Lightweight Simple to manage Simple to understand Scrum is not a process or a technique for building products; rather, it is a framework within which you can employ various processes and techniques.
- 3. The Scrum Team Product Owner: The Product Owner is responsible for understanding the requirements and maximizing the value of the product and the work of the Development Team The Development Team: The Development Team consists of professionals who work on product backlog items delivering a potentially releasable increment of product at the end of each Sprint. The Scrum Master : The Scrum Master is responsible for ensuring Scrum is understood clearly. Scrum Masters acts as intermediate between product owner and development this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules.
- 4. Scrum Events The Sprint: is the duration in which the useable, and potentially releasable product Increment is created. Sprints consists of Sprint Planning Daily Scrums Development work Sprint Review Sprint Retrospective
- 5. Sprint Planning The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team. Development team , product owner and scrum master together contribute to finalize the items to be taken for that sprint and the Acceptance criteria for that task in order to consider the same as completed
- 6. Daily Scrum The Daily Scrum is a 15-minute meeting for the Development Team to synchronize activities and create a plan for upcoming working day. It must be precise and each member must explain what I have done yesterday What I will be doing today Any impediments till date
- 7. Sprint Review A Sprint Review occurs at the end of the Sprint to inspect the Increment and change the Product Backlog if needed. During the Sprint Review, the Scrum Team and stakeholders collaborate on what was done in the Sprint. This is an informal meeting, unlike status meeting, and the presentation of the Increment is intended to feedback
- 8. Sprint Retrospective The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements for upcoming Sprint. It focus on how the last Sprint went with regards to people, relationships, process and tools Identify the positive and negative things occur during sprint Creation of a plan to implement improvements to the way the Scrum Team does its work.
- 9. Scrum Artifacts Product Backlog : baseline requirements prioritized in order from Product Owner to the Scrum Team Sprint Backlog : The Sprint Backlog is a subset of the Product Backlog that the team pulls into the sprint to work on Increment : potentially shippable product increment at end of each sprint by development team
- 10. Thanks