Agile Teams and Collaboration: What's New About Agile?

1,806 views

Published on

Before you transition to agile, you are accustomed to functional roles, people who “owned the code,” and time to bake quality in. In agile we have cross-functional teams, collective code and quality ownership, and a collective notion of “done.” It sounds like we magically become a big happy family, doesn’t it?

Teams don’t just become self-organized cross-functional happy teams. They have to work to get that way. In this talk, Johanna will help you understand some of the challenges teams face, and how agile practices help. She’ll also help you understand some of the practices that don’t help, such as multitasking and distributed teams.
We’ll talk about some models for scaling agile, such as Scrum of Scrums, and a network model of scaling. No matter what problems you encounter on your agile team, retrospectives are the one way the team can help itself solve its own problems.

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

No Downloads
Views
Total views
1,806
On SlideShare
0
From Embeds
0
Number of Embeds
11
Actions
Shares
0
Downloads
31
Comments
0
Likes
8
Embeds 0
No embeds

No notes for slide

Agile Teams and Collaboration: What's New About Agile?

  1. 1. AgileTeams and Collaboration: What’s New About Agile? Johanna Rothman New: Hiring GeeksThat Fit @johannarothman www.jrothman.com jr@jrothman.com 781-641-4046
  2. 2. © 2013 Johanna Rothman Johanna’s General Agile Picture 2
  3. 3. © 2013 Johanna Rothman AgileTeams 3 Contain all the roles required 5-7 people is the sweet spot Delivers value every iteration
  4. 4. © 2013 Johanna Rothman Who AreTheseTeams? 4
  5. 5. © 2013 Johanna Rothman HowTeamsWork Working agreements “How we do things here” What “done” means to us What our values are Social contract among members of the team Behaviors, not practices 5
  6. 6. © 2013 Johanna Rothman Areas for Discussion forTeam Working Agreements Values: Sustainable pace We have core hours and we respect them Working agreements What done means Timebox everything Respect the timebox Ground rules: One person talking Group norms: How we treat meeting times 6
  7. 7. © 2013 Johanna Rothman Team Chartering Project charters for the project Vision: brief and compelling:Where are we headed? Release criteria: What does done mean for the project? 7
  8. 8. © 2013 Johanna Rothman Teams Mature overTime Two significant models of teams to know about: Tuckman Hackman 8
  9. 9. © 2013 Johanna Rothman Tuckman’s Model Forming Storming Norming Performing 9
  10. 10. © 2013 Johanna Rothman KeepTeamsTogether Once the Project is Complete Agile team members learn how to collaborate with each other.That learning is expensive. Don’t waste the investment. Flow work through the teams 10
  11. 11. © 2013 Johanna Rothman The Journey to Self-Organizing 11 Who is Responsible for Manager led teams Self-directed teams Self-managing teams Self-governing teams Set overall direction Manager Manager Manager Team Design the team and its organizational context Manager Manager Team Team Monitor and manage work process & progress Manager Team, with the exception of hiring/firing Team Team Execute team task Team Team Team Team Adapted from Hackman’s Leading Teams: Setting the Stage for Great Performances, Harvard Business Press
  12. 12. © 2013 Johanna Rothman Hackman Teams evolve from manager-led to self- organizing teams Very few teams start as self- managing teams 12
  13. 13. © 2013 Johanna Rothman No Multitasking in Agile People work on one project at a time People work on one feature at at time People work on one task at a time 13
  14. 14. © 2013 Johanna Rothman Approaches to Manage Interruptions or High Priority Requests Leave room in the iteration; don’t fill up on features Urgent queue 14
  15. 15. © 2013 Johanna Rothman High Emphasis on Collaboration Team works together Swarming: everyone works together to move one feature forward to done 15
  16. 16. © 2013 Johanna Rothman High Emphasis on Facilitation We facilitate each other’s work with feedback and coaching, meta-feedback and meta-coaching Not a manager’s job 16
  17. 17. © 2013 Johanna Rothman Feedback and Meta-Feedback Not evaluation or praise; feedback When you use a peer-to-peer feedback approach: Create an opening Describe behavior or results State the impact Make a request 17
  18. 18. © 2013 Johanna Rothman Coaching and Meta-Coaching Coaching is much more than teaching Offering options with support Example: Rule of Three 18
  19. 19. © 2013 Johanna Rothman Many Ideas About How to Scale Agile Scrum-of-Scrums SAFe My ideas: Small world networks Choose what fits your context 19
  20. 20. © 2013 Johanna Rothman Inspect & Adapt with Retrospectives Periodically review the team’s process At the end of an iteration At the end of a significant deliverable Often! 20
  21. 21. © 2013 Johanna Rothman Re-evaluate the Projects Periodically 21
  22. 22. © 2013 Johanna Rothman Distributed vs Co-located Want co-located cross- functional teams Can manage with distributed cross- functional teams Be wary of trying to do agile with anything else 22
  23. 23. © 2013 Johanna Rothman Johanna’s General Agile Picture 23
  24. 24. © 2013 Johanna Rothman What Questions DoYou Have? or, What challenges do you see where you work? 24
  25. 25. © 2013 Johanna Rothman Let’s Stay inTouch... Pragmatic Manager: www.jrothman.com/pragmaticmanager Please link with me on LinkedIn 25

×