Real World Agile/Scrum Development

Transcription

1 Real World Agile/Scrum Development Ron Wilcom Chief Engineer Next Century Corporation 01 Dec 2009, v35

2 Who am I? Experiences Roles Projects.. a lifetime cynic of software process 01 Dec Nov 2009, 13, 2012 v35-2 -

3 Overview Software Development Models Agile/Scrum Process (crash course!) Why Agile/Scrum is Good and Bad Agile/Scrum in Real Life 01 Dec Nov 2009, 13, 2012 v35-3 -

4 Software Development Models Waterfall UP/RUP - [Rational] Unified Process Spiral Agile / Scrum Kanban 01 Dec Nov 2009, 13, 2012 v35-4 -

5 Agile Manifesto Individuals and interactions over process Working software over documentation Customer collaboration over negotiation Respond to change over following a plan results in Faster delivery times Lower defect rates Improved team morale More satisfied customers Agile becomes a mindset! 01 Dec Nov 2009, 13, 2012 v35-5 -

6 Agile - Notions Problem cannot be understood or defined up front Quick mistakes and successes Simple and self organizing Adjustments made constantly Early and continuous delivery of valuable software The customer can hate it if they want, but they will hate it early. 01 Dec Nov 2009, 13, 2012 v35-6 -

7 Agile Adoption 35% Agile (Scrum, Feature Driven, Test Driven, extreme) 21% Iterative (RUP/Spiral) 13% Waterfall (Waterfall, ISO9000) 30% No Process Percentage of Usage Agile Iterative Waterfall No Process Forrester/Dr. Dobbs Survey Dec Nov 2009, 13, 2012 v35-7 -

8 Agile/Scrum - Not a Process? 01 Dec Nov 2009, 13, 2012 v35-8 -

9 Agile/Scrum Is a Process Collaborative Scrum Team (~8) Product Owners (visionaries/stakeholders, users) Scrum Master (the coach) Team (analysts, UX, developers, QA, DBA) Product Backlog Sprint (2-4 weeks) Sprint Planning Sprint Execution Sprint Review 01 Dec Nov 2009, 13, 2012 v35-9 -

10 Agile/Scrum Sprint Planning Scoring "User Stories" with "Story Points" PostIt notes Express difficulty/time "As a user I want... " - Epic/Theme/Story Planning Poker - collaborative scoring Move stories from backlog to fit in sprint Use velocity of team to guess Prioritize based on need and scores Break down of "User Stories" into tasks Include non-functional tasks: code review, unit tests, etc Best guess at hours per task Immutable commitment 01 Dec Nov 2009, 13, 2012 v

11 Agile/Scrum Sprint Execution Daily "standup Meeting Yesterday / Today / Roadblocks Do not solve problems here Pigs (committed) / Chickens (involved) Task Board Pending / In Progress / Resolved / Complete Burn down Reach 0 within each sprint Shows issues Can help predict velocity and release dates 01 Dec Nov 2009, 13, 2012 v

12 Agile/Scrum Sprint Review Review High Level Results Demonstrate Product Invite all No slides! Technical Debt Accrual Bugs Refactoring Performance fixes Retrospective 01 Dec Nov 2009, 13, 2012 v

13 Agile/Scrum Goodness Results in a tangible product very quickly Customer buy in from early inclusion Biggest advocate for your work is the customer Break bad news early - report it 'up' early Allowed to adjust the idea of product Built in quality No 'crunch time' always a constant pace, not a constant crunch always releasing the software 01 Dec Nov 2009, 13, 2012 v

14 Agile/Scrum - Badness Requires trust in the team to get it done Sometimes considered cowboy development When are you done? Estimate the Final Release date A happy customer is hard to bean count Final product prediction is not possible Long term budgeting difficult Not all surrounding processes match agile Documentation tied to old processes (KPP, LOC) External dependencies slow down delivery Bad member can paralyze the team 01 Dec Nov 2009, 13, 2012 v

15 Daily Standups.. usually Agile/Scrum Realities Need to sit together, not always possible Planning / Review / Retro (same day < 2 hours) Pre-planning a must Not everyone can be there Planning poker.. a novelty Early stories "As a developer... ", "As the CTO..." Catch Up Sprint Extreme/Pair Programming not likely Emotional highs and lows are rare Immutability Difficult Sprint tasks change in the middle sometimes 01 Dec Nov 2009, 13, 2012 v

16 Agile/Scrum Tips/Tricks Strip it down as needed but keep the core values Use Agile tools - not PostIt cards! auto burn down, reporting, release notes, etc Documentation use internal WIKI 01 Dec Nov 2009, 13, 2012 v

17 Agile/Scrum Tips/Tricks Daily Standup out of control? gavel / conch Enemies? Make them product owners! Product owners should perform demonstrations Disparate Team use group chat 01 Dec Nov 2009, 13, 2012 v

18 Questions? Next Century Corporation 7075 Samuel Morse Drive, Suite 250 Columbia, MD Dec 2009, v35