Embed Size (px)
DESCRIPTION
Story of how a technical lead was able to introduce Scrum practices incrementally using the iteration and retrospectives as the engine of change. Please email me if you would like a download.
Citation preview
Stealth Scrum
Michael SahotaSenior Principal Consultant
BEA Systems
May, 2005
Agenda
• Review of Scrum• Situation Description• Planning Exercise & Discussion• White Label Scrum & Route Taken
Scrum
• Lightweight Agile process• Empirical Focus: Inspect and Adapt
© Advanced Development Methods 2003 All Rights Reserved
© Copyright 2004, William C. Wake, [email protected], www.xp123.comFree for non-commercial use. 1-25-04
Daily ScrumHosted by ScrumMasterAttended by all, but Stakeholders don’t speakSame time every dayAnswer: 1) What did you do yesterday? 2) What will you do today? 3) What’s in your way?Team updates Sprint Backlog; ScrumMaster updates Blocks List
PO
Product Owner: Set priorities
Roles
SM
ScrumMaster: Manage process,
re move blocks
T
Team: Develop product
SH
Stakeholders: observe &
advise
Key Artifacts
Product BacklogList of requirements & issuesOwned by Product OwnerAnybody can add to itOnly Product Owner prioritizes
Sprint GoalOne-sentence summaryDeclared by Product OwnerAccepted by team
Sprint BacklogList of tasksOwned by teamOnly team modifies it
Blocks ListList of blocks & unmade decisionsOwned by ScrumMasterUpdated daily
IncrementVersion of the productShippable functionality (tested, documented, etc.)
Key Meetings
Sprint Planning MeetingHosted by ScrumMaster; ½-1 dayIn: Product Backlog, existing pro duct, business & technology conditions1. Select highest priority items in Product Backlog; declare Sprint Goal2. Team turns selected items into Sprint BacklogOut:: Sprint Goal, Sprint Backlog
Sprint Review MeetingHosted by ScrumMasterAttended by allInformal, 4-hour, informationalTeam demos IncrementAll discussHold retrospectiveAnnounce next Sprint Planning Meeting
Product Backlog
Development Process
Increment
Sprint Planning Meeting
Daily Scrum
Daily Work
Sprint Goal
Sprint Backlog
Blocks List
Product
Sprint Review Meeting
Sprint: 30 days each
Product Backlog’
Increment’
Capability If not present, insert into Product Backlog the identified non-functional requirements at high priority
Source code management
“Investigate and implement source code management”
Test driven development
“NonFunctional Requirement - Learn and implement test driven development”
Automated builds“Investigate and implement automated build and test capability”
Refactoring “Investigate, learn and implement refactoring”
Coding standards “Devise and implement coding standards”
User development of acceptance tests
“Investigate and implement user development of acceptance tests”
Frequent check-in of code
“Set standards for checking in code”
Shared code “ Investigate and implement code review and sharing practices”
Working environment “Upgrade working environment and tools for teams”
Engineering Best Practices
© Advanced Development Methods 2003 All Rights Reserved
Situation Description
• Small team of developers • Financial Institution• Waterfall process, but project behind
Exercise
• Split into groups.• Discuss possible sequence of
introduction of process/practices.
• Write summary on flip-chart paper.• Present findings to the group.
Stealth Scrum Cookbook
• Talk about iterative and incremental development in general. Do not mention Scrum/XP.
• Use standard terminology; avoid Agile lingo such as Sprint or user stories. See white-label guide (next page).
• Implement processes and practices incrementally.
White Label ScrumScrum White Label
ScrumXP
Product Owner Project Manager Customer
Scrum Master Team Lead/Project Manger
n/a (Coach)
Sprint Iteration Iteration
Sprint * Meeting Iteration * Meeting Standup Meeting, Iteration Planning
Product Backlog Project Tasks User Stories, Release Plan
Sprint Backlog Iteration Tasks Tasks
Incrementally Add Process
Process IterationAgree to do iterative development (Two week iteration) 0
Iteration Planning Meeting - light version 1
Iteration Goal 1
Daily Meeting (RIP weekly status meeting) 1
Mid-point review Meeting 1
Iteration Review Meeting - including demo, retrospective 1
Iteration Tasks 2
Product Backlog, Release Planning 4
Iteration Task Burndown (First mention of Scrum) 5 & 6
Incrementally Add Software Practices
Practices Iteration
Source code management 0
Architecture/Design Diagrams 1
Test driven development (Unit test only) 2
Working environment (Tools only) 2 & 3
Refactoring 4
Coding standards 4
Shared code (Some pair programming) 4
Frequent check-in of code 5
User development of acceptance tests 5
Automated builds (Was on to-do list)
Challenges
• Advantage of using explicit Scrum• Technical Lead vs. Scrum Master
Critical Success Factors
• Timeboxed Iteration!• Inspect and Adapt is the engine of
change. (daily meeting, iteration review, retrospective)
Conclusion
• Many ways to introduce Agile - no right way or wrong – whatever works.
• Stealth Scrum provides a structure for sneaking in Agile process and practices.
