Ad
More Related Content
What's hot (20)
Similar to Scrum framework (20)
Ad
Recently uploaded (20)
Ad
Scrum framework
- 2. About Scrum: It is a framework for managing complex products. It is used for s/w development.
- 3. Scrum Roles Product owner. Scrum Master. Scrum Team.
- 4. Product Owner Define the features of the product.(Based upon the customer requirement Product Owner will define the features of the product.) Prioritize the product backlog.(Suppose the customer given 10 requirements, so the Product Owner will decide which one is priority one). Decide on release date and content.(PO will decide whether the product is working according to customer requirement (or) do we need to do certain changes, so if he is not satisfied he can reject or he will satisfy then he will deliver the product to the customer). Adjust features and priority every iteration, as needed.(Sometimes, initially, we get 10 requirement from the customer and Product owner is responsible for whatever the first features will deliver because we don't deliver all the features to the customer at one time. So we will deliver by version by version. In the first version, we will deliver some features and the second version we will deliver some more features like this). Responsible for the product vision. Person who maintains the product backlog and the responsible person for the same.
- 5. Scrum Master & their responsibilities: Scrum Masters are those who fully understand Scrum, and help the Scrum Team by coaching them, and ensuring that all Scrum processes are implemented correctly. The Scrum Master is a management position, which manages the Scrum process, rather than the Scrum Team. He/she is a servant-leader for the Scrum Team. Facilitator of the Scrum process. Scrum Master also tries to remove impediments to the Development Team, facilitates their events. The Scrum Master also needs to make sure that the development team works based on the core values of Scrum. Responsible for enacting Scrum values and practices Helps resolving any issues / impediments faced by the Scrum team. SM will care about the process how work is going on, Is there any blockers, how we can proceed, what are the challenges how we face and how to overcome those challenges. So all things are taken care of by the Scrum Master.
- 6. Scrum Team & their responsibilities: Should be a self-organizing and cross-functional team (consists of the members with testing, development, business analyst, domain expertise, etc., skills). Should self-manage the tasks among the team. Should resolve people management issues if any among the team and should only take it to Scrum Master if it has gone out of the team’s control. Works with product owner in reprioritizing the product backlog items. Consists of 7+/- 2 members. Responsible to complete the committed task for the sprint.
- 7. Scrum Events
- 8. Sprint SPRINT A sprint is a short, time-boxed period when a scrum team works to complete a set amount of work. Sprint is nothing but, the heart of the scrum. Typical duration is 1–4 week or a calendar month at most. Generally, the duration of a scrum sprint (scrum cycle) depends upon the size of project and team working on it. The team size may vary from 3-9 members. In general, a scrum script complete in 3-4 weeks. A new Sprint can be started immediately, once the previous Sprint ends. Defined period of time in which the specific committed work has to be completed
- 9. Sprint Planning Sprint planning meeting is attended by the product owner, Scrum Master, and the development team. Team selects items from the product backlog they can commit to complete Sprint backlog is created . Tasks are identified and each is estimated (either by hours or story points). Estimate sprint backlog in hours. Sprint planning is an event in scrum that kicks off the sprint. The purpose of sprint planning is to define what can be delivered in the sprint and how that work will be achieved. Sprint planning is done in collaboration with the whole scrum team. This meeting is held every week and lasts for almost 1 hour.
- 10. Sprint Review Before the end of the Sprint, the Development Team presents the outcome of the Sprint to the customer and receives feedback. This meeting is called Sprint Review (also known as Sprint Demo). During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. This meeting lasts at most for 4 hours for a one-month Sprint. The development team presents the results of the Sprint. The Product Owner reviews and accepts the delivered product increment. During the Sprint Review Product Owner, Development Team and stakeholders review what was done.
- 11. Daily Standup In Scrum, on each day of the sprint, the team holds a meeting called the Daily Scrum. Usually this meeting is held at the same location and at the same time every day. This is a strictly time boxed meeting of 15 minutes. In this meeting the following 3 things will be discussed/ answered by each team member. During the daily scrum, each team member answers the following three questions: What did you do yesterday? What will you do today? Are there any impediments in your way? All team members are required to attend, and the product owner and Scrum Master are expected to attend the meeting. Any issues raised in the Daily Scrum becomes the Scrum Master's responsibility to resolve by facilitating another meeting with the appropriate group of people as soon as possible. Daily Scrum meetings are not used for issue discussion and problem-solving. A separate meeting should be held outside Daily Scrum to address any issues.
- 12. Sprint Retrospective After every sprint, the Scrum team schedules an internal meeting that is the last meeting in the sprint, to assess what went wrong and want went well. The entire team, including both the Scrum Master and the product owner should participate The Scrum Master facilitates this meeting by asking everyone to explain their ideas. Attendees: Scrum Master, product owner, Scrum team Duration: Multiply the number of weeks in your sprint by 1 hour.
- 13. Scrum Artifacts
- 14. Product Backlog An ordered list of everything that might be needed in the final product. Typically, a Scrum team and its product owner begin by writing down everything they can think of for agile backlog prioritization. The Product Backlog is an ordered list of user requirements. P.O will make the product owner.
- 15. Sprint Backlog The Sprint backlog is the list of the product backlog item for which the development team commits to deliver as part of that particular sprint. Sprint Backlog is created by the team members during the Sprint Planning meeting. This backlog contains a list of user stories or features that can be implemented during Sprint iterations.
- 16. Sprint Burn down chart The Sprint Burn down Chart makes the work of the Team visible. It is a graphic representation that shows the rate at which work is completed and how much work remains to be done. Progress on a Scrum project can be tracked by means of a release burn down chart. The Scrum Master should update the release burn down chart at the end of each sprint. The horizontal axis of the sprint burn down chart shows the sprints; the vertical axis shows the amount of work remaining at the start of each sprint. Sprint Burn down chart is used to track the progress.