Continuous Health

4,390
-1

Published on

This presentation as given at Agile Australia to around 200 attendees. It is based on a previous presentation that we gave at Agile China 2011..

The core focus of this presentation is to raise the capability level of Agile teams to perform better risk management.

We propose a new positive approach focusing on Healthy teams, a Continuous Risk Manifesto and tools to perform risk management in an Agile manner.

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
4,390
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Risk Management isn’t typically done well- Either its not done at all or pretty poor- Usually left to Project Managers (even in Agile)- Boring, Negative and in ExcelRisk is all about Culture- Healthy Kids and teams
  • Dont be a negative thinkerThis project is too big to failWe all knew it was never going to work, but nobody did anythingIf I raise a problem I will have to fix itIt’s a managers job to monitor risk – let me get one with coding…We jus talk about watermelon reporting here – having a slide for it I think is overkill as it was at AA2012
  • To create a positive, healthy culture, where motivated people create great products and embrace risk
  • To create a positive, healthy culture, where motivated people create great products and embrace risk
  • To create a positive, healthy culture, where motivated people create great products and embrace risk
  • Successful delivery of projects require healthy teams and healthy projects. High performance teams deliver and improve when the health of system is in a good state. Monitoring the health of a team and the project provides a wellness check, a more positive and preventative mechanism that the team can use to track and communicate its own state that can sometimes be missed, misunderstood or not communicated.The two elements of health are the team and the project. Both can be monitored in different ways and should be owned and discussed by the team. The proposed essential elements for health are…
  • Successful delivery of projects require healthy teams and healthy projects. High performance teams deliver and improve when the health of system is in a good state. Monitoring the health of a team and the project provides a wellness check, a more positive and preventative mechanism that the team can use to track and communicate its own state that can sometimes be missed, misunderstood or not communicated.The two elements of health are the team and the project. Both can be monitored in different ways and should be owned and discussed by the team. The proposed essential elements for health are…
  • Successful delivery of projects require healthy teams and healthy projects. High performance teams deliver and improve when the health of system is in a good state. Monitoring the health of a team and the project provides a wellness check, a more positive and preventative mechanism that the team can use to track and communicate its own state that can sometimes be missed, misunderstood or not communicated.The two elements of health are the team and the project. Both can be monitored in different ways and should be owned and discussed by the team. The proposed essential elements for health are…
  • Hand-over to James
  • Agile smells – common term been used… we smell something is wrong – not a pleasant termExplain the rose, rat and fish and what they meanWell we do this but in more with more rigour and transparency
  • We can take the health attributes that we saw earlier which are more softer, intangible attributes and add to them some more tangible and Agile/Technical project and team related attributes
  • We break down health into two groups, tangible and intaigble related to their ease of monitoringMoraleVibe, Mood, Motivation, Engagement etcCollaborationAcross functions, Pairs, swarming etcLeadership SupportHow support are the team by leadership, impediments, guidance, decision making, clarity etcPeak PerformanceWhere do the team think there are in terms of peak performance
  • So how can we use these attributesBVC is an agile conceptWe have build montiorsWhy not health monitors
  • Putting this into practice we use the health dashboardBig screenUpdated every week or iteration or day – you chooseViewable from a distance – a build monitor for your heatlhHealth monitoring should start a conversation, like a user story
  • Build it inMake it normal – do health and risk as part of your normal operationStand-ups etcHold meetings that focus on it or build it into your retrospectives
  • Continuous Health

    1. 1. Continuous Risk Management James Brett @James_Brett Marina Chiovetti @marinagoround jbrett@thoughtworks.com marina@thoughtworks.com
    2. 2. In todays lesson, you will learn….1. Focus on Health and embrace Risk2. Health means Healthy teams and Healthy projects3. An approach and tools to help you monitor health and “manage” risk
    3. 3. The Problem…
    4. 4. Risk = Opportunity
    5. 5. If a project has no riskDON’T DO IT!
    6. 6. Risk is all about culture!
    7. 7. Continuous Risk Management
    8. 8. Continuous Health Monitoring
    9. 9. Health : A state of complete physical, mental, and social well-being and not merely the absence of diseaseWorld Health Organisation
    10. 10. Team One People don’t talk, they are nothonest, they act like a bunch of people doing their own thing.
    11. 11. Team TwoOpen, passionate, engaged, inspired,working together in unison.
    12. 12. Organisational Health… • “Organizations that focused on performance AND health simultaneously were nearly twice as successful as those that focused on health alone, and nearly three times as successful as those that focused on performance alone.”
    13. 13. Health : the ability of a team to align,execute, and renew itself fasterthan the competition so that it cansustain exceptional performanceover time
    14. 14. That’s soft and fluffy! • Minimal Politics • Minimal Confusion • High Morale • High Productivity • Low Turnover
    15. 15. So what do we do?
    16. 16. Health Monitoring is: Noticing the “Agile smells”but in a more consistent and transparent way
    17. 17. The Attributes of Healthon Intangible Tangible
    18. 18. 5 Intangible Health AttributesTeam Morale Team Collaboration Leadership Support Peak Performance Target Confidence
    19. 19. 6 Tangible Health AttributesContinuous Delivery Automation Technical Debt Environment, Tools Capability Quality and Infrastructure
    20. 20. So how can we use these attributes?
    21. 21. Health Health Trend Icon Name 4.0 Confidence Slider Health Value Scale 1-5 Value Color
    22. 22. Health Dashboard 2 issues Capability 4.0 8 risks Morale 4.0 Technical Debt 4.0 Collaboration 2.5 Automation 2.0 Leadership Support 5.0 Quality 3.0 Confidence 3.5 Cont. Delivery 2.0 Peak Performance 1.0 Env Tools + Inf 3.0 Intangible Tangible
    23. 23. Build Healthy Teams that Embrace Risk (in an Agile way)
    24. 24. Continuous Risk Management The manifesto Healthy Teams over Risk Management
    25. 25. Continuous Risk Management The manifesto Team and governance collaboratio over Status Reporting
    26. 26. Continuous Risk Management The manifesto Responding to Risks over Following the Delivery Train
    27. 27. Continuous Risk Management The manifesto Continuous Attention over Scheduled Meetings
    28. 28. Daily Look Health RetrospePlanning Stand- Ahead Review Session ctive ups Planning Make it part of the “normal” iterative process
    29. 29. 4 issues 0 issues Overall 8 risks Project 0 risks 0 issues People 0 issues 2 risks Physical 0 risks1 0 issues 0 issues2 Process 1 risks Culture 2 risks3 Our Mood: 4 issues Tools 3 risks Risk Dashboard
    30. 30. 1. Focus on Health and embrace Risk2. Health means Healthy teams and Healthy projects3. An approach and tools to help you monitor health and “manage” risk
    31. 31. James Brett @james_brettMarina Chiovetti @marinagoround
    32. 32. People Risk Technical Impact Risk Risk Risk RiskLow Low Probability Probability Risk Risk Risk Impact Business Logical
    33. 33. Current IterationRisk Wall Risk/Iteration 25 15 20 10 5 5 5 3 2

    ×