Building High Performing AgileTeamsIncrementally…Presented byNaveed KhawajaCarl Bruiners                     Copyright © M...
www.morphilibrium.com                                                                                              N      ...
Bio – Carl Bruiners                      Originally a techie who became a                       frustrated Development Ma...
Where we want to be…                  Maturity Unconscious     Conscious                  Conscious               Unconsci...
The basics                 Copyright © Morphilibrium             Presented at Agile Cambridge 2012
Waterfall                                                http://scalingsoftwareagilityblog.com                Copyright © ...
Customer focused…User Story Lifecycle                           Copyright © Morphilibrium                       Presented ...
The perfection lament          If you wait until you do        everything for everybody                 instead of        ...
Values, Principles and Practices                     Values    BEING                 Principles                  Practices...
Activity 1Duration: 10-12 minutes         The Tower Project               [Iteration 1]                        Copyright ©...
Agile Manifesto   We are uncovering better ways of developing software by doing it and helping             others do it. T...
Transformation – Poorly plannedOrganisational change                  Copyright © Morphilibrium              Presented at ...
The heartbeat - Ceremonies                              • Show & Tell        • Pre-Sprint Planning • Sprint Retrospective ...
Create a trusting environment     Empower teams to help guide product direction     Trust team estimations     Continue...
Communication and Collaboration is key   Ideally co-located teams   Enabling teams to keep in constant contact by utiliz...
What is a high performing team                  Copyright © Morphilibrium              Presented at Agile Cambridge 2012
Disciplined execution vs continuousinnovation                  Copyright © Morphilibrium              Presented at Agile C...
What a good (Agile) team looks like   Constant business engagement   Customer delivery focused   Diverse   Flexible  ...
Challenge = Opportunity             Responsibility                     Obligation       You                               ...
Agile Improvements                                            Quarterly  Everything      Quarterly Pseudo                 ...
Agile Improvements                                                 Colocation with BA &                                   ...
Activity 2Duration: 10-12 minutes         The Tower Project               [Iteration 2]                        Copyright ©...
Tips to helping you become a highperforming team                    Copyright © Morphilibrium                Presented at ...
Embrace Continuous Improvement   Change of pace should be    measured – a steady    cadence can lead to    disappointment...
No two teams are equal Don’t compare, instead play to their  strengths Move your team members around to  create your str...
Visual to reality                                                                                       Iteration 1       ...
Is limiting what my partner can buy a badthing? – PO ManagementBe sensible limit the PO’s choices– if you say you can theo...
Sprint 34 End                                                           Sprint 35 End                                     ...
Backlog management -MMFS / MVPAlways create a Minimal Viable Product / Minimal MarketableFeature Set                      ...
Managing your task board (& don’t forgetyour WIPs).                    Copyright © Morphilibrium                Presented ...
Have you kicked off your story yet?                  Copyright © Morphilibrium              Presented at Agile Cambridge 2...
A streamline kick off…                                      BA             UX                                             ...
In Sprint test debt / avoid mini-waterfall                      Copyright © Morphilibrium                  Presented at Ag...
Continuous Delivery… Its easy… but   Continuous Integration?   Test Automation?   Software Configuration?   Automated ...
Defects                                                   TDD & BDD Earlier               Defects,                        ...
Using class of serviceStandard service classClasses should be dictated by the business costs     Various class types shou...
Stop escaping defectsDo not use average defect throughput as a stick to beat yourteams withDefects discovered that are not...
How the cost of removing defectsincreases over time                  Copyright © Morphilibrium              Presented at A...
“Done is better than perfect!”•   Gauge multi-tasking•   Manage comfort level•   Systems impact visibility•   Propose time...
Fail fast and learn from the mistakes                   Copyright © Morphilibrium               Presented at Agile Cambrid...
Embrace TDD / BDD sooner rather thanlater Retro-fitting TDD / BDD into your work process is far more  painful than the in...
Lean everything out…   Constantly seek ways to    improve your processes   Waste is not always    obvious – Don’t be afr...
Agile is not an Arm’s Race Simple Agile = Beautiful Agile Don’t run before you can walk Embrace Pragmatic Continuous Im...
This presentation was delivered    at Agile Cambridge 2012    Held at Churchill College, Cambridge            from Sep 27-...
@morphilibrium                                                @cbruinersslideshare.net/morphilibriumblogs.morphilibrium.co...
This presentation was inspired by the works of many people, and we cannotpossibly list them all. Though we did our very be...
Upcoming SlideShare
Loading in …5
×

Creating High Performing Teams

643 views
549 views

Published on

Published in: Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
643
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
38
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Creating High Performing Teams

  1. 1. Building High Performing AgileTeamsIncrementally…Presented byNaveed KhawajaCarl Bruiners Copyright © Morphilibrium Presented at Agile Cambridge 2012
  2. 2. www.morphilibrium.com N a v e e d K h a w a Assessment Coaching j Strategy a@morphilibrium Copyright © MorphilibriumIn.morphilibrium.com Presented at Agile Cambridge 2012
  3. 3. Bio – Carl Bruiners  Originally a techie who became a frustrated Development Manager  Has been on a Agile education journey  Companies range from SME’s to large Corporations  Strong passion & experience for taking on problem’ projects / teams  Loves automation Agile Coach or Most Valuable Mentor of the Year Agile Player UK
  4. 4. Where we want to be… Maturity Unconscious Conscious Conscious UnconsciousIncompetence Incompetence Competence Competence Maslow Copyright © Morphilibrium Presented at Agile Cambridge 2012
  5. 5. The basics Copyright © Morphilibrium Presented at Agile Cambridge 2012
  6. 6. Waterfall http://scalingsoftwareagilityblog.com Copyright © Morphilibrium Presented at Agile Cambridge 2012
  7. 7. Customer focused…User Story Lifecycle Copyright © Morphilibrium Presented at Agile Cambridge 2012
  8. 8. The perfection lament If you wait until you do everything for everybody instead of something for somebody you will end up not doing anything for anybody ~ Malcom Bane Copyright © Morphilibrium Presented at Agile Cambridge 2012
  9. 9. Values, Principles and Practices Values BEING Principles Practices DOING Copyright © Morphilibrium Presented at Agile Cambridge 2012
  10. 10. Activity 1Duration: 10-12 minutes The Tower Project [Iteration 1] Copyright © Morphilibrium Presented at Agile Cambridge 2012
  11. 11. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals & Working Customer Responding to interactions software collaboration change over over over over processes and comprehensive contract following a plan tools documentation negotiation 𝑾𝒉𝒚 𝑽𝒂𝒍𝒖𝒆 = 𝑯𝒐𝒘 Agile Manifesto with Dude’s Law Copyright © Morphilibrium Presented at Agile Cambridge 2012
  12. 12. Transformation – Poorly plannedOrganisational change Copyright © Morphilibrium Presented at Agile Cambridge 2012
  13. 13. The heartbeat - Ceremonies • Show & Tell • Pre-Sprint Planning • Sprint Retrospective • Sprint Planning defineWed Thu Fri Mon Tue Wed Thu Fri Mon Tue Wed Thu Fri Mon Tue On-going iterative activities throughout the sprint • Story Kick-Offs • Daily Scrum • Backlog Grooming • User Story Writing Copyright © Morphilibrium Presented at Agile Cambridge 2012
  14. 14. Create a trusting environment Empower teams to help guide product direction Trust team estimations Continued trust when a Sprint doesn’t work out sov·er·eign·ty 1. Supremacy of authority or rule as exercised by a sovereign or sovereign state. 2. Royal rank, authority, or power. 3. Complete independence and self-government. 4. A territory existing as an independent state. 5. A group or body of persons or a state having sovereign authority.
  15. 15. Communication and Collaboration is key Ideally co-located teams Enabling teams to keep in constant contact by utilizing any and all communication methods (Face to face, VC, Telephone, Email, IM, Task Walls) Business representation throughout the delivery process Daily updates Copyright © Morphilibrium Presented at Agile Cambridge 2012
  16. 16. What is a high performing team Copyright © Morphilibrium Presented at Agile Cambridge 2012
  17. 17. Disciplined execution vs continuousinnovation Copyright © Morphilibrium Presented at Agile Cambridge 2012
  18. 18. What a good (Agile) team looks like Constant business engagement Customer delivery focused Diverse Flexible Energized Constantly seeks ways to improve Meets their commitments more often than not Copyright © Morphilibrium Presented at Agile Cambridge 2012
  19. 19. Challenge = Opportunity Responsibility Obligation You Others Justify Shame Blame C Avery Copyright © Morphilibrium Presented at Agile Cambridge 2012
  20. 20. Agile Improvements Quarterly Everything Quarterly Pseudo Releases & instead of Releases Continuous something (Mini-Waterfall) Deployment Collaborative Requirements Backlog volatile progression conundrum yet prioritized - WIP Limits - Kick-Offs - Wall of Shame Well controlled/ Value Based negotiated / Portfolio Portfolio prioritized/Prioritization Planning Cost of Delay over Delivery Copyright © Morphilibrium Presented at Agile Cambridge 2012
  21. 21. Agile Improvements Colocation with BA & open casual Pseudo colocation Communication discussion space with without BA dedicated focus timeslots Functional Team 7 plus minus 2 7 plus minus 2 Structure without BA with BA Disciplined Disciplined Prescriptive execution with execution &processes with little value & flexibility Continuous value Innovation Copyright © Morphilibrium Presented at Agile Cambridge 2012
  22. 22. Activity 2Duration: 10-12 minutes The Tower Project [Iteration 2] Copyright © Morphilibrium Presented at Agile Cambridge 2012
  23. 23. Tips to helping you become a highperforming team Copyright © Morphilibrium Presented at Agile Cambridge 2012
  24. 24. Embrace Continuous Improvement Change of pace should be measured – a steady cadence can lead to disappointment Don’t wait for your retrospectives to encourage CI, introduce constant Team Kaizens Copyright © Morphilibrium Presented at Agile Cambridge 2012
  25. 25. No two teams are equal Don’t compare, instead play to their strengths Move your team members around to create your strongest teams Don’t cross compare team velocities Move team members around to cross pollinate Copyright © Morphilibrium Presented at Agile Cambridge 2012
  26. 26. Visual to reality Iteration 1 Iteration 2 Release 1 … Vision Release 2 Iteration n Programme … 1 Iteration 1 Backlog Iteration 2 Release n … Releases Iteration n Portfolio Vision … Release 1 Iteration n Release 2 Programme 2 Iterations … … … Release n Programme Iteration n n Copyright © Morphilibrium Presented at Agile Cambridge 2012
  27. 27. Is limiting what my partner can buy a badthing? – PO ManagementBe sensible limit the PO’s choices– if you say you can theoreticallyput a man on the moon, beprepared to be asked to do so. Copyright © Morphilibrium Presented at Agile Cambridge 2012
  28. 28. Sprint 34 End Sprint 35 End Sprint 36 End Sprint 37 End Sprint 38 EndNumber of ItemsRemaining Legend: Incoming Remaining Completed Date Copyright © Morphilibrium Presented at Agile Cambridge 2012
  29. 29. Backlog management -MMFS / MVPAlways create a Minimal Viable Product / Minimal MarketableFeature Set Copyright © Morphilibrium Presented at Agile Cambridge 2012
  30. 30. Managing your task board (& don’t forgetyour WIPs). Copyright © Morphilibrium Presented at Agile Cambridge 2012
  31. 31. Have you kicked off your story yet? Copyright © Morphilibrium Presented at Agile Cambridge 2012
  32. 32. A streamline kick off… BA UX Dev QA TT…and continuous team effort gets us the gold Copyright © Morphilibrium Presented at Agile Cambridge 2012
  33. 33. In Sprint test debt / avoid mini-waterfall Copyright © Morphilibrium Presented at Agile Cambridge 2012
  34. 34. Continuous Delivery… Its easy… but Continuous Integration? Test Automation? Software Configuration? Automated Deploy? ACDT – Automated Continuous Delivery & Test Copyright © Morphilibrium Presented at Agile Cambridge 2012
  35. 35. Defects TDD & BDD Earlier Defects, Pain -Defect fast tracking Defects TDD earlier -Cycle time controls pain - Class of service (SLAs)" Copyright © Morphilibrium Presented at Agile Cambridge 2012
  36. 36. Using class of serviceStandard service classClasses should be dictated by the business costs Various class types should be created under the standard service class. For example;  A – Under $10000 impact if delayed  B – Under $5000 impact if delayed  C – Under $1000 impact if delayed  D – Under $100 impact if delayed  E – BAU The prioritization of the Stories is driven by the Standard Service Class Types A Story will change service types as it gets closer to its delivery date; i.e. a C type after 5 days would be escalated to a B type and therefore more further up the priority stack. Impact delay would be determined at the point of a story being added to the Task Wall, this will help Stories move up the priority stack as it gets closer to its delivery date. Copyright © Morphilibrium Presented at Agile Cambridge 2012
  37. 37. Stop escaping defectsDo not use average defect throughput as a stick to beat yourteams withDefects discovered that are not legacy deal with within youcurrent Sprint £58 p/d 10 incoming defects p/w 2 days per defect to fix Copyright © Morphilibrium Presented at Agile Cambridge 2012
  38. 38. How the cost of removing defectsincreases over time Copyright © Morphilibrium Presented at Agile Cambridge 2012
  39. 39. “Done is better than perfect!”• Gauge multi-tasking• Manage comfort level• Systems impact visibility• Propose time bound analysis activity• Ask for the definition of value Copyright © Morphilibrium Presented at Agile Cambridge 2012
  40. 40. Fail fast and learn from the mistakes Copyright © Morphilibrium Presented at Agile Cambridge 2012
  41. 41. Embrace TDD / BDD sooner rather thanlater Retro-fitting TDD / BDD into your work process is far more painful than the initial pain of getting setup at the beginning Copyright © Morphilibrium Presented at Agile Cambridge 2012
  42. 42. Lean everything out… Constantly seek ways to improve your processes Waste is not always obvious – Don’t be afraid of change There is no such thing as perfection Copyright © Morphilibrium Presented at Agile Cambridge 2012
  43. 43. Agile is not an Arm’s Race Simple Agile = Beautiful Agile Don’t run before you can walk Embrace Pragmatic Continuous Improvement Copyright © Morphilibrium Presented at Agile Cambridge 2012
  44. 44. This presentation was delivered at Agile Cambridge 2012 Held at Churchill College, Cambridge from Sep 27-28, 2012 Presented by Naveed Khawaja Carl Bruiners Copyright © Morphilibrium Presented at Agile Cambridge 2012
  45. 45. @morphilibrium @cbruinersslideshare.net/morphilibriumblogs.morphilibrium.com blog.carlbruiners.comin.morphilibrium.com in.carlbruiners.com Copyright © Morphilibrium Presented at Agile Cambridge 2012
  46. 46. This presentation was inspired by the works of many people, and we cannotpossibly list them all. Though we did our very best to attribute all authors oftexts and images, and to recognize any copyrights, if you think that anythingin this presentation should be changed, added or removed, please contactme at info@morphilibrium.com http://creativecommons.org/licenses/by-nd/3.0/ Copyright © Morphilibrium Presented at Agile Cambridge 2012

×