A high performing agile team
A high performing agile team has 10 key attributes: 1) trusts each other through honesty and sharing personality tests, 2) spends time together to build bonds through a team formation model, 3) has functional conflicts to face the truth and experiment with ideas, 4) keeps team commitments by understanding and agreeing on goals, 5) holds itself accountable by focusing on delivered value and continuous improvement, 6) buys into the shared mission by understanding its purpose, 7) continuously strives for improvement through health checks, 8) keeps its workload and impediments visible through boards, 9) delivers working software incrementally at a sustainable pace through test-driven development and visible build pipelines, and 10) uses various tools like personality tests, model stages,
A high performing agile team
- 1. A High Performing Agile Team by Adnan Aziz
- 2. A High Performing Agile Team Team: A team comprises a group of people linked in a common purpose Performance: The process of carrying out an task Agile: Able to move quickly and easily
- 3. Attribute # 1 Trust each other
- 4. Tools to use • Open yourself to others that demonstrates honesty and humility. • Your team needs to know that you are just like them. • Share your Myers-Briggs Type Indicator (MBTI) scores.
- 5. Attribute # 2 Spent time together to form bonds
- 6. Tools to use Use Tuckman model to build common understanding Storming Forming Norming Performing PersistentTeams Time
- 7. Attribute # 3 Team has functional conflict on how to achieve outcomes
- 8. Tools to use Face the truth • If functional conflict doesn’t occur, then team is afraid of facing the truth • Encourage positive conflict Time boxed experiments • Implement two ideas and agree to have measurement based discussion
- 9. Attribute # 4 Keeps team commitment
- 10. Tool to use • Understand the commitment • Build team agreements around commitment • Create a goal and visualize your commitment
- 11. Attribute # 5 Holds themselves accountable
- 12. Tools to use • Ask what value is getting delivered to the client? • Question how value will be measured? • Holds regular team retrospectives • Retrospective results and action items are visible in the team area
- 13. Attribute # 6 Buys into the mission
- 14. HOW WHY Tools to use WHAT Understand what is the cause behind the mission?
- 15. Attribute # 7 Continuously strive for improvement
- 16. Tools to use Conduct regular team health checks
- 17. Attribute # 8 Team workload is visible in open space
- 18. Tools to use Build workflow boards in your team space
- 19. Attribute # 9 Team impediments are visible
- 20. Tools to use Use impediment board
- 21. Attribute # 10 Deliver working software incrementally at sustainable pace
- 22. Tools to use • Do more of TDD and BDD • Adopt components from IaaS model • Use build lights and information radiators to highlight the status of your build pipeline
- 23. Questions?