Vacation Stealth Scrum
Upcoming SlideShare
Loading in...5
×
 

Vacation Stealth Scrum

on

  • 2,331 views

Story of how a technical lead was able to introduce Scrum practices incrementally using the iteration and retrospectives as the engine of change. ...

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.

Statistics

Views

Total Views
2,331
Views on SlideShare
2,323
Embed Views
8

Actions

Likes
4
Downloads
17
Comments
0

2 Embeds 8

http://www.slideshare.net 7
http://www.lmodules.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-NonCommercial LicenseCC Attribution-NonCommercial License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • This is from the Hilton @ Bali

Vacation Stealth Scrum Vacation Stealth Scrum Presentation Transcript

  • Stealth Scrum Michael Sahota Senior 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, William.Wake@acm.org, www.xp123.com Free for non-commercial use. 1-25-04 Daily Scrum Hosted by ScrumMaster Attended by all, but Stakeholders don’t speak Same time every day Answer: 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 Backlog List of requirements & issues Owned by Product Owner Anybody can add to it Only Product Owner prioritizes Sprint Goal One-sentence summary Declared by Product Owner Accepted by team Sprint Backlog List of tasks Owned by team Only team modifies it Blocks List List of blocks & unmade decisions Owned by ScrumMaster Updated daily Increment Version of the product Shippable functionality (tested, documented, etc.) Key Meetings Sprint Planning Meeting Hosted by ScrumMaster; ½-1 day In: Product Backlog, existing pro­duct, business & technology conditions 1. Select highest priority items in Product Backlog; declare Sprint Goal 2. Team turns selected items into Sprint Backlog Out:: Sprint Goal, Sprint Backlog Sprint Review Meeting Hosted by ScrumMaster Attended by all Informal, 4-hour, informational Team demos Increment All discuss Hold retrospective Announce 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’
  • Engineering Best Practices © Advanced Development Methods 2003 All Rights Reserved 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”
  • 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 Scrum Scrum White Label Scrum XP 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 Iteration Agree 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.