Your SlideShare is downloading. ×

Growing Agile Team Behaviors

396
views

Published on

The +15FLIGHTPLAN agile team behaviors, used to support and guide agile teams in developing a growth plan for long-term sustainable agility. Presented at Agile2012, in Dallas, Texas.

The +15FLIGHTPLAN agile team behaviors, used to support and guide agile teams in developing a growth plan for long-term sustainable agility. Presented at Agile2012, in Dallas, Texas.

Published in: Technology, Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
396
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
12
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Specialized skill and knowledgeis actively being shared anddistributed within and acrossteams to reducesingle point failure Predictabilityrisk Automation Quality Collaboration TransparencyDevelopment work on committedStories is guided by executableacceptance tests (ATDD) Predictability Automation Quality Collaboration Transparency
  • 2. Only non-critical issues andexploratory testing are manuallyverified Predictability Automation Quality Collaboration TransparencyAll non-functional requirementsare automated Predictability Automation Quality Collaboration Transparency
  • 3. There are multiple, thrivingchannels to grow expertise whileTeams remain cross functionale.g. Communities ofPractice Predictability Automation Quality Collaboration TransparencyWe have one shared Definitionof Done across our group/organization Predictability Automation Quality Collaboration Transparency
  • 4. We can create stable andverifiable builds of our producton demand and fromindependent sources Predictability Automation Quality Collaboration TransparencyCross cutting concerns arecollectively managed by avirtual expert group drawn fromthe teams (for examplearchitecture or Predictabilitycontinuous Automation Qualitydelivery) Collaboration Transparency
  • 5. The entire Team works todeliver the release during therelease sprint Predictability Automation Quality Collaboration TransparencyThe Team takes ownership ofexternal dependencies to ensurecommitted value gets delivered Predictability Automation Quality Collaboration Transparency
  • 6. The Team mostly swarms oncommitted Stories in the sprintto ensure items are delivered Predictability Automation Quality Collaboration TransparencyThe Team has a visible measureof end user value from ourreleases Predictability Automation Quality Collaboration Transparency
  • 7. Business Value drives all Teamwork (even ‘technical’ tasks andresearch) Predictability Automation Quality Collaboration TransparencyAll our Definition of Done testsper Story (inc acceptance tests)are fully automated Predictability Automation Quality Collaboration Transparency
  • 8. We continuously anddemonstrably strive to improveour engineering capabilities forexample by havingregular code dojos Predictability Automation Quality Collaboration TransparencyThe Team actively works toreduce technical debt it hasidentified, and is focussed onnot creating new debt Predictability Automation Quality Collaboration Transparency
  • 9. Release Planning is guided bythe Team’s ability to deliver(their velocity) Predictability Automation Quality Collaboration TransparencyThe team takes responsibility forits tool and environments totake Stories to ‘Done’ Predictability Automation Quality Collaboration Transparency
  • 10. Each team member hasexperienced the Scrum Masterrole for at least one sprint Predictability Automation Quality Collaboration TransparencyThe Team typically works on thecommitted Sprint backlog in thesame priority order as theProduct Backlog Predictability Automation Quality Collaboration Transparency
  • 11. The Business Value attached toStories is understood by theTeam Predictability Automation Quality Collaboration TransparencyAll Teams have a commonRelease Definition of Done Predictability Automation Quality Collaboration Transparency
  • 12. Retrospectives are producing 1-3actionable improvement actionsevery sprint which the Teamworks on and reviews at thenext retrospective Predictability Automation Quality Collaboration TransparencyThe Team actively works to fixexisting defects (bugs) Predictability Automation Quality Collaboration Transparency
  • 13. The actively identifies TechnicalDebt and makes it visible Predictability Automation Quality Collaboration TransparencyShared code ownership isactively pursued by the team, forexample shared codeconventions or trunk isin a constantly Predictabilitybuildable state Automation Quality Collaboration Transparency
  • 14. During the Sprint, the Teamreviews Stories with the ProductOwner as they are completed Predictability Automation Quality Collaboration TransparencyThe team delivers on itscommitment with at least 90%predictability (ratio of acceptedto committed estimation points) Predictability Automation Quality Collaboration Transparency
  • 15. The team takes from the top ofthe backlog at least 6-10 Storiesof about the same size intoevery 1-2 week sprint Predictability Automation Quality Collaboration TransparencyThere is a product vision,expressed as an elevator pitch,and a list of SMARTrequirements prioritized bybusiness value and it Predictabilityis visible to all Automation Quality Collaboration Transparency
  • 16. At the end of every sprint theteam delivers a potentiallyshippable product, that can bereleased or usedinternally Predictability Automation Quality Collaboration TransparencyThe Team has a clear, agreedand visible Definition of Readywhich has been communicated tothe Product Owner Predictability Automation Quality Collaboration Transparency
  • 17. The Team works to a clear,agreed and visible Definition ofDone. All ‘Done’ Stories meet thisstandard Predictability Automation Quality Collaboration TransparencyThe team is continuouslyimproving quality and theprocess, using the ActiveLearning Cycle during theretrospective Predictability Automation Quality Collaboration Transparency
  • 18. There is an impediment backlogmanaged by the ScrumMaster.Impediments are quicklyresolved by the team or theScrumMaster Predictability Automation Quality Collaboration TransparencyThere is a product backlog withenough Stories to fill 1-2 sprints,that all meet the Definition ofReady Predictability Automation Quality Collaboration Transparency
  • 19. The Team has a clear andpublished Working Agreementthat is agreed to by all itsmembers Predictability Automation Quality Collaboration TransparencyDuring the sprint, the teamworks on at most 2-3 Stories atany one time until the Story isdone Predictability Automation Quality Collaboration Transparency
  • 20. There is a sprint burndown thatuses estimation points and isupdated daily. Points only burndown when Stories aredone Predictability Automation Quality Collaboration TransparencyThe team and Product Ownermeet regularly to groomStories. Everyone in thedevelopment team estimatesStories before Predictabilitycommitting to Automation Qualitythem Collaboration Transparency
  • 21. Stories are broken down intotasks that are small enough tobe completed in 1-2 days,tracked on the teams taskboard Predictability Automation Quality Collaboration TransparencyThe team meets every dayaround the task board, for ashort (max 15 min) standup toupdate each other and plan thedays activities Predictability Automation Quality Collaboration Transparency
  • 22. The Product Owner has visibilityof the Team’s sprint capacity andadjusts expectations accordingly Predictability Automation Quality Collaboration TransparencyThe development team has 7+/-2people and is cross-functional,with all the skills necessary todeliver a Story inside a sprint Predictability Automation Quality Collaboration Transparency
  • 23. PredictabilityAutomation Quality Collaboration Transparency PredictabilityAutomation Quality Collaboration Transparency
  • 24. PredictabilityAutomation Quality Collaboration Transparency PredictabilityAutomation Quality Collaboration Transparency
  • 25. PredictabilityAutomation Quality Collaboration Transparency PredictabilityAutomation Quality Collaboration Transparency
  • 26. PredictabilityAutomation Quality Collaboration Transparency PredictabilityAutomation Quality Collaboration Transparency
  • 27. PredictabilityAutomation Quality Collaboration Transparency PredictabilityAutomation Quality Collaboration Transparency
  • 28. PredictabilityAutomation Quality Collaboration Transparency PredictabilityAutomation Quality Collaboration Transparency