Agile process cheat sheet using scrum

786 views
612 views

Published on

Comparing scrum with RUP style corporate process of a large corporation I worked prior to Cisco.

Published in: Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
786
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Agile process cheat sheet using scrum

  1. 1. Agile process cheat sheet using ScrumInitiation (aka RUP Inception phase) Kickoff meeting- Brainstorming session (Time-boxed) Goal: To define scope/SoW and/or problem statement, leads to Release backlog later.Exploration (aka RUP Inception phase) Explore domain concepts Goal: to develop domain model, helps in creating detailed object and/or data models. Define basic prototype/storyboard/workflow Goal: to define product workflow and/or web navigation. Do informal white-boarding of architecture Goal: feasibility/risk assessment, estimating and sizing the effort involvedPlanning (aka RUP Elaboration phase) Scrum meeting #1a- Release Planning meeting (Time-boxed) Define Release backlog and prioritize USE-CASEs/user-stories for the Release. Goal: to develop release plan and master project plan with sprint-level milestones. Scrum meeting #1b- Spring Planning meeting (Time-boxed) Define sprint backlogs and prioritize USE-CASEs/stories for sprint(s) for the next release Goal: to create the sprint dashboard and the sprint project plan with detailed tasks. Define glossary Goal: everyone in the Scrum teams uses common terminology. Develop system conventions Use sprint 0 for environment setup and/or PoC (Proof of Concept). TDD best practice- use acceptance test scripts as requirement for each use-case/story. Goal: coding standards, check-in/out & unit-test/continuous-integration conventions.Build (aka RUP Construction phase) Scrum meeting #2- Daily Scrum meeting (Time-boxed for 15 minutes stand-up, not sit-down) Each Scrum team-mate talks about status, blocks and pending work. Goal: to update the sprint dashboard.Deployment (aka RUP Transition phase) Scrum meeting #3- Sprint Review meeting (Time-boxed demo) ScrumMaster demos the work “done” for the sprint. “Done” can’t be ambiguous. Goal: to get the sprint burn-down chart and sprint velocity (work done per sprint). Scrum meeting #4- Sprint Retrospective meeting (Time-boxed- lessons learned) PMs analyze the sprint dashboards. Process improvement ideas take shape here. Goal: to use the sprint velocity to update the next sprint backlog.

×