effective agile teams
DESCRIPTION
In the deck I share some nifty secrets on building effective Agile teams,scaling teams for large, distributed projects and delivering business value leveraging the team synergy. As they - you are as good as your team!TRANSCRIPT
![Page 1: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/1.jpg)
Effective Agile Teams
![Page 2: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/2.jpg)
Self – Organizing Teams
“ Agile processes employ self-organizing teams to handle the complexity inherent in systems development projects. A team of individuals is formed. They organize themselves into a team in response to the pressure of a deadline, reminding me of the saying, "Nothing focuses the mind like a noose!" (Schwaber 2001)
![Page 3: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/3.jpg)
Key Characteristics of an Agile Team• Whole, Self-Contained.
Does not require external experts
• Generalizing Specialists. Cross-functional
• Stable. Change your mind! Do not change the team!
![Page 4: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/4.jpg)
Agile Teams Are…..
• Autonomous
• Adaptive
• Accountable
And they have loads of FUN ……………………..Well Almost Always
![Page 5: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/5.jpg)
Team Composition
![Page 6: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/6.jpg)
Agile Teams – The Core Supporting Pattern
Technical ExpertDomain Expert
Independent Tester
Scrum MasterTeam
Product Owner
![Page 7: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/7.jpg)
Large Teams – Work within a universe
Scrum MasterTeam
Product Owner
![Page 8: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/8.jpg)
Managing Large/ Distributed Teams
![Page 9: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/9.jpg)
The ‘Ideal’ Team
• Co-located
• Between 3 and 10 people
• Cross-functional, Self-Contained
• Reporting to a single Product Owner
![Page 10: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/10.jpg)
The Realities• In real world you work
with a larger eco-system
• Geographically dispersed
• Multiple Component Teams
![Page 11: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/11.jpg)
Team A Team B Team C Team D Team E
Product Backlog
Scaling ScrumProduct Owner
![Page 12: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/12.jpg)
Chief Product Owner
PO PO POPO PO
Scaling Scrum
Team A Team B Team C Team D Team E
![Page 13: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/13.jpg)
Integration Management• Product architecture identifying
interfaces and dependencies
• User stories explicitly recognizing dependencies- Example new ordering system should interface with X billing system
• Synchronize iterations through consolidated release planning
• Scrum of Scrums
• Integration testing13
Continuous Integration
Team A Team B Team C
Release Backlog
![Page 14: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/14.jpg)
Distributed teams• Communication Technology – video conferencing, chat tools
• Establish communities of practice, wiki, blogs – shared knowledge
• Deploy local scrum masters – Scrum of scrums to synchronize global teams
• Move from a verification based approach to a result driven, value based approach
14
![Page 15: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/15.jpg)
Scaling the Scrum Rituals• Daily Scrum: Each team has a daily scrum. Updates posted
to common dashboard
• Iteration Planning: Shared understanding of highlevel stories
• Each team does first level of planning. Joint review to validate dependencies
• Release planning: Essential to get atleast all the scrum masters and lead developers together. Rest of team on-phone support
15
![Page 16: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/16.jpg)
Collaborating across teams• Distribute coherent set of
functionalities based on location
• Each team has needed skills. Self-sufficient and self-
organising
• Teams in different locations work independently but collaborate to coordinate their work
16
![Page 17: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/17.jpg)
Scaling Agile – Best practices• Shared code repositories
• Wikis/ blogs to replace physical white boards
• Online communities of practice
• Disciplined approach to continuous integration. Plan for an integration environment
• For complex projects allow for a follow-on end to end test sprint
17
![Page 18: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/18.jpg)
People Management
![Page 19: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/19.jpg)
Agile People Management: Key Role
• Plan Staffing – Resource Mobilization
• Manage Staffing
• Guide Careers
• Plan Succession
![Page 20: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/20.jpg)
Agile Resource Management Challenges
• Recruiting specializing generalists
• Sensitizing HR to the Agile Culture. Less Reshuffle
• Agile is highly challenging. Only the most motivated will stay on
• How do you fit in trainings, knowledge sharing sessions
• Half-baked Agile practices can cause dissatisfaction. Watch Out!
![Page 21: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/21.jpg)
Servant Leadership - The Invisible Leaders
• Managers recede to the back-ground
• Move away from allocating tasks to people. Tasks choose people
• Team members decide who and what
• Protect the team. Be the guiding angel. Servant Leader
![Page 22: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/22.jpg)
Secret Recipe for Great Teams• Trust. Inspire trust. Promote trust among the team
• Communicate often. And without fear
• Make it a fun place. Decorated work places. Fancy titles. Chief Imagination Officer, Managing Dreamer, Bug-Seeker
• Reward. Agile Stars. Badges of Honor.
• Nurture. Give everyone a pet project. Guide careers. Promote growthAnd the best team award goes to….
![Page 23: Effective Agile Teams](https://reader033.vdocuments.net/reader033/viewer/2022052410/554c448ab4c90570648b5137/html5/thumbnails/23.jpg)
Thank You
http://in.linkedin.com/in/rimjhimray