Student Scrums s Wor orks kshop op Tom Reichlmayr Rochester - PowerPoint PPT Presentation

Student Scrums s Wor orks kshop op Tom Reichlmayr Rochester Institute of Technology Department of Software Engineering tjr@se.rit.edu

The Scrum Framework Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

The Scrum Framework Burndown Charts Chris Noffke: http://www.noffke.com/ Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

The Scrum Framework Burndown Charts Three Scrum Roles Chris Noffke: http://www.noffke.com/ Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Ham-n-Eggs Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

The Scrum Framework THE HE Burndown SCRUM RUM TEAM AM Charts (aka “PIGS”) • Project initiation sprint Chris Noffke: http://www.noffke.com/ Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

The Scrum Framework Burndown Charts Three Scrum Ceremonies Chris Noffke: http://www.noffke.com/ Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

The Scrum Framework Burndown Charts Three ee Scrum um Ar Artif tifact acts Chris Noffke: http://www.noffke.com/ Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

The Scrum Framework Burndown Charts Chris Noffke: http://www.noffke.com/ Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Scrum is not about software… Burndown Charts Chris Noffke: http://www.noffke.com/ Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Scrum is a Project Management FRAMEWORK Burndown Charts Chris Noffke: http://www.noffke.com/ Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Scrum Origins Mike Cohn, Mountain Goat Software Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Scrum is not (always) about software… “Scrum in church? Of course! How else did God create the world in seven days?” Rev. Arline Conan Sutherland , First Paris rish h Lexin xingt gton on - Lexin xingt gton on, MA • 1986 Harvard Business Review Paper* • 1993 Ken Schwaber & Jeff Sutherland • 1995 OOPSLA Presentation • 1996 Extreme Programming (XP) • 2001 Agile Manifesto • “Agile Values & Practices” Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Is Scrum Mainstream? “Perils of Agile, But”, Dottie Acton – Lockheed Martin Senior Fellow, 2010 Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

2010 State of Agile Development Survey Results VersionOne Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Scrum is used at… Microsoft Apple Nielsen Media Yahoo Qualcomm Google Electronic Arts Texas Instruments IBM Salesforce.com Philips John Deere Siemens Lexis Nexis Sabre Nokia Lockheed Martin Oracle Capital One Time Warner BBC Turner Broadcasting Intuit Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Scrum Illuminates Opportunities Scrum works by exposing the impediments in our processes, by shoving them in our face so we have no choice but to do something about them. - Ron Jeffries Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

“War Stories – Fighter Jets and Agile Development at Lockheed Martin”, Agile Journal, 2007 Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Scrum & Agile Practices Agile le Pr Practices actices Scrum is a … FRAMEWORK Time me Boxed ed Iteratio tions Self Organi anizing zing Teams ams Conti tinuous uous Inte tegrati tion on User r Storie ries Test t First/ st/Dri Driven en Develo lopm pment nt (TFD FD/TD /TDD) D) Pair r Prog ogramm amming ing Refactoring toring Retrospec ospectiv tives Scrum Roles … others Scrum Artifacts Practices used in Scrum Ceremonies a Scrum Project Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Scrum & Software Engineering Practices SE SE Pr Practices actices Scrum is a … FRAMEWORK Time me Boxed ed Iteratio tions Self Organi anizing zing Teams ams Conti tinuous uous Inte tegrati tion on User r Storie ries Test t First/ st/Dri Driven en Develo lopm pment nt (TFD FD/TD /TDD) D) Pair r Prog ogramm amming ing Refactoring toring Retrospec ospectiv tives Scrum Roles … others Scrum Artifacts Practices used in Scrum Ceremonies a Scrum Project Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Ideal Scrum Product Backlog “Grooming” throughout project Initial Product Backlog Definition (New stories, refined stories, estimate, prioritize) Initial Architecture / Evolving Architecture/Design throughout project Design Definition (May vary widely based on project/organization) Agile practices per iteration: planning, user story implementation, unit testing, Sprint 1 acceptance test case generation, acceptance testing, product demonstration, team retrospective Preliminary work required to support Sprint 2 the start of Sprint 1 Iteration Number of required sprints (n) = Total Story points/ Velocity Delivery date driven by number Sprint n Sprint Zero of sprints (Iteration Zero) “Release” 2-4 weeks ~2-6 weeks Sprint 2-4 weeks Sprint 1 Start Last “Final” Project Increment Release Start “Potentially Shippable” Releases

(the often overlooked) Sprint Zero • Minimal Backlog to start Sprint 1 • Project initiation sprint • Environment setup / CI Support • Architecture / High Level Design • Team setup / Team norms • Training / Instruction • Define Deliverable Artifacts (DONE!) Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Ideal Scrum Product Backlog “Grooming” throughout project Initial Product Backlog Definition (New stories, refined stories, estimate, prioritize) Initial Architecture / Evolving Architecture/Design throughout project Design Definition (May vary widely based on project/organization) Agile practices per iteration: planning, user story implementation, unit testing, Sprint 1 acceptance test case generation, acceptance testing, product demonstration, team retrospective Preliminary work required to support Sprint 2 the start of Sprint 1 Iteration Number of required sprints (n) = Total Story points/ Velocity Delivery date driven by number Sprint n Sprint Zero of sprints (Iteration Zero) “Release” 2-4 weeks ~2-6 weeks Sprint 2-4 weeks Sprint 1 Start Last “Final” Project Increment Release Start “Potentially Shippable” Releases

Technical Debt • Incurs when project team chooses an approach that’s expedient in the short term but that increases complexity and is more costly in the long term. • Debt can be incurred both intentionally and unintentionally • As in our financial lives, there is “good” and “bad” debt Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Scrum & Technical Debt • A complete description of what it means to be DONE-DONE with a user story – Addresses intentional debt – Conscious decision to complete stuff “later” – Affects credibility of velocity metric • Small work increments (minimal WIP) – Addresses unintentional debt – Defect propagation – Avoid long term hand-offs, work queues Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Done- Done? Did you do… • Performance testing • Stability testing • Refactoring • Integration with the work of the other six teams • Integration testing with the work of the other six teams so the increment is the totality of all seven teams • Release notes • Internationalization to the six cultures where the product will be sold • User acceptance testing • Regression testing Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Creating the Product Backlog Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Product Backlog • Prioritized list of product features as determined by the Product Owner • Reprioritized are the start of each new sprint. • Scru rum m does es not specify ecify the format mat of items ms on the Produc duct t Bac acklog, klog, but typicall ically y they y expresse ressed d as User er Storie ries. • Each User Story also defines the acceptance criteria the Product Owner will use to accept the release at the end of the Sprint - DONE! • Acceptance criteria is expressed as Acceptance (Functional) Test Cases Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Product Backlog Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

User Stories User Stories

What is a “User Story” • Card – Stories are traditionally written on index cards. – Cards may be annotated with notes, estimates, etc. • Conversation – Details behind the story come out during conversations with customer, product owner • Confirmation – Acceptance tests validate the story was correctly implemented in the application Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

The Card As a user, I want to purchase a book. As a user, I want to cancel an order. Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012

Communciating the Details “As a user, I want to cancel an order” • Does the user get a full or partial refund? – Credit card? Site credit? Other? • Is a confirmation provided to the user? – How? • Can you specify a subset of items from an order? Student Scrums Workshop - Tom Reichlmayr, SIGCSE2012