Scrum writeup - Agile
Download as DOCX, PDF0 likes482 views
The document discusses Scrum, an agile framework for managing product development. It describes key Scrum roles like the Product Owner who prioritizes features and the Scrum Master who facilitates the process. User stories are collected in a product backlog to plan releases. The team estimates stories in story points or hours. Sprints are short, timed periods used to tackle parts of the backlog and make the product shippable. Daily stand-up meetings and sprint retrospectives help monitor progress visualized in burndown charts and velocity metrics.
![3.
4.
5.
6.
Developer : builds the product
Tester : to ensure the product meets the requirement
Customer : User
Executives :
Release Planning
TO plan a release , team starts with < Product Backlog> , identify < user stories > they want to consider ,
these <user stories> forms a part of Release Planning .
Estimation of time for the Release planning , breaking down user stories to estimated time
Collection of all rough estimated provides
Estimates
Story points –
Best technique – Hrs
Time Boxing
Sprints [ 2 – 30 days ]: Short duration milestones that all the team to
the project and make it ship ready.
tackle a manageable chuck of](https://image.slidesharecdn.com/scrumwriteup-140107170904-phpapp01/85/Scrum-writeup-Agile-2-320.jpg)
Scrum writeup - Agile
- 1. SCRUM writeup Products contains inputs from users , executives … In SCRUM , the functions are written from user perspective User Stories : Collection of User Stories is Product backlog ( also known as wish list ) Which user stories need to go Key roles 1. Product owner : which feature would be included in the product 2. Scrum Master : to ensure the project is progressing smoothly and every member should get their job done , setup the meeting , monitors the work and facilitate release planning ,
- 2. 3. 4. 5. 6. Developer : builds the product Tester : to ensure the product meets the requirement Customer : User Executives : Release Planning TO plan a release , team starts with < Product Backlog> , identify < user stories > they want to consider , these <user stories> forms a part of Release Planning . Estimation of time for the Release planning , breaking down user stories to estimated time Collection of all rough estimated provides Estimates Story points – Best technique – Hrs Time Boxing Sprints [ 2 – 30 days ]: Short duration milestones that all the team to the project and make it ship ready. tackle a manageable chuck of
- 3. Goal of Sprint The goal of each sprint is to get a subset of the release backlog to a ship ready state. So at end of the all the sprint you should have full tested product with all the feature Progress Burndown Chart – project visibility tool .. and one of the reason why scrum is so popular Velocity = Rate of productivity
- 4. Execution of
- 5. SCRUM Daily Scrum Meeting : fast paced meeting .. Meeting daily all Sprint Retrospective meeting Tools - Ontime , Who is working on what …