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 ,

3. Developer : builds the product 4. Tester : to ensure the product meets the requirement 5. Customer : User 6. 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 tackle a manageable chuck of the project and make it ship ready.

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

Execution of

SCRUM

Daily Scrum Meeting : fast paced meeting .. Meeting daily all

Sprint Retrospective meeting

Tools - Ontime ,

Who is working on what …