Back to Course

Senior Leader Learning Path

0% Complete
0/0 Steps
  1. Week 1 - Overview of Agile & Scrum and Why Agile

    Scrum 101 - Part 1 | Scrum Basics
  2. Scrum 101 - Part 2 | The Scrum Process
  3. Scrum 101 – Part 3 | Scrum Values
  4. Scrum 101 - Part 4 | Scrum Terms Review
  5. Webinar - Thinking of Agile Adoption? Start HERE
  6. Week 2 - Agile Team Roles and Expectations
    Agile Team – Part 1 – Team Characteristics
  7. Agile Team – Part 2 – The Leadership Triangle
  8. Agile Team – Part 3 – The Product Owner Role
  9. Agile Team – Part 4 – The ScrumMaster Role
  10. Agile Team – Part 5 – The Team
  11. Agile Team – Part 6 – Technical Leadership
  12. Agile Team – Part 7 – Agile Coach
  13. Agile Team – Part 12 – Agile Sponsors & Stakeholders
  14. Agile Team – Part 13 – Agile Executives and Leaders
  15. Agile Team – Part 14 – Real World Agile Role Challenges
  16. Week 3 - Introduction to Business Agility
    Enterprise Business Agility Explainer
  17. Overview of the 7 Pillars
  18. Sally Elatta - Accelerating Your Enterprise Business Agility Journey
  19. Business Agility - Evan Leybourn
  20. The State of Enterprise Business Agility - Evan Leybourn
  21. Week 4 - Leadership and Culture
    Leadership Agility Pillar
  22. BCBS Executive Leadership
  23. High Performing Teams – Part 3 – Servant Leadership
  24. High Performing Teams – Part 4 – Shifting Towards Servant Leadership
  25. How Leadership and Culture Influences Your Transformation - Sheri Reed
  26. Transformative Leadership - Sanjiv Augustine
  27. Assessing your Agility Transformation Readiness - Rupert Schmidtberg
  28. The Role of Managers and Leaders within Agile Transformations - Tiffany Willis
  29. Moving Beyond the Traditional “Command & Control” Culture - Jennifer Bensky
  30. Week 5 - Customer Seat at the Table
    Customer Seat and Lean Product Intro
  31. Product and Discovery Trends - David Bland
  32. How the Customer is Key to Our Culture - Trisha Hall
  33. Product Leadership - Stacey Louie
  34. Experiments - Skip Angel
  35. Week 6 - Lean Portfolio Management
    Lean Portfolio Mgmt Overview
  36. Building Measurable Outcomes with OKRs
  37. Outcomes and OKRs - Part 1 Annual Outcomes
  38. Outcomes and OKRs - Part 2 Quarterly
  39. AgilityHealth Outcomes OKR Demo
  40. Agile/Lean Finance - Evan Campbell
  41. Enterprise Visibility Room Case Study - Sean Barrett
  42. Driving Teams Towards Measurable Business Outcomes
  43. Week 7 - Organization Structure and Design
    Org/Team Design Pillar
  44. Stable Teams - Bryan Tew
  45. Enterprise Agile – Stable Teams, Portfolio Management, and Budgeting
  46. Enterprise Stable Teams - Why Is This So Hard?
  47. Org-Team Design - Demand vs Delivery Portfolios
  48. Week 8 - Agile Business Teams
    Bringing Agile to the Sales Team - Leon Herszon
  49. Sample Kanban Board: Marketing Team
  50. Agile HR – A Game Changer
  51. Transforming Marketing and Design - Russ Peña
  52. Agile Finance and Governance - Evan Leybourn
  53. Creating an Agile Team in an HR Organization - Doc List & Sally Elatta
  54. Business Agility Within A Regulated Utility - Lisa Smith
  55. Agile Talent & HR: Preparing Organizations for the Future of Work
  56. Week 9 - Make It Stick/Sustain
    Make it Stick Pillar Video
  57. Evolving a Continuous Improvement System - Dan Craig
  58. Measuring & Accelerating Enterprise Business Agility - Sally Elatta
  59. Team Health Metrics - Jim Peer
  60. Enabling Agility by Measuring what Matters
  61. Top Challenges with Measuring Team Health
  62. Week 10 - Technical Agility
    Technology Agility Pillar
  63. Technical Agility - David Hussman
  64. Technical Excellence - Richard Kasperowski & Bryan Tew
  65. Technical Lead - Jesse Riley
  66. What does DevOps really mean? - Brian Levy
  67. Unlock Team Potential with DevOps - Daniel Gruesso
  68. Problem Solution - Skip Angel
  69. Assess and Accelerate Your Digital Transformation Webinar
Lesson 10 of 69
In Progress

Agile Team – Part 5 – The Team

Who makes up the Team and what do we expect of them? This video provides a high-level overview of what is needed to form an Agile Team!

Responses

  1. Hi Funke,

    The disadvantages can be:

    • Harder to communicate with one another if larger than 9 Team Members on your Team. You have to make extra effort.
    • Stand ups can go longer than the recommended 15 minutes. Team Members could be disengaged if stand up takes too long.
    • ScrumMaster has to ensure a healthy team; with 15 Team Members and their dysfunctional behavior and correcting that behavior (ie: late for stand up meetings, side conversations, etc.).
    • More coordination for ScrumMaster if Team Members are distributed and getting them all on Webex/Zoom/Bluejean/ etc. for meetings.
    • Harder facilitation for ScrumMaster during Agile meetings with a larger Team.
    • Maybe more difficult in reaching consensus on estimating, team norms, best practices, etc.
    • Small ‘cliques’ may form if teams are too big.
    • Your Sprint planning meetings may take longer since your Team is larger and should have a higher velocity
    • Your Story/Tasks boards could have 20-30 stories and 200-300 tasks. A lot to manage and ensure priority stories are done first. If you have a physical board, it may require a large area.
    • Your Demo could take longer since you have so many Team Members doing so much work.
    • Your Retros could take longer since you have so many Team Members. Some quieter Team Members may not feel comfortable speaking up.
    • It may take longer for your Team to move from Forming to Storming to Norming and then Performing.

    Does that help?

  2. You are right Sally, a big team 15-20 can be a disaster. I was engaged with a team of 18! I knew we were set up for a fail. I struggled for 2 months. I got to understand the project and advised we spilt the team by business theme. Fortunately I had a very collaborative and understanding PO. We got 2 more team members and has 5 members for each business theme. (Inclusive of 2 Solution Architects who were responsible for 2 teams each). Then we had Team Leads who were quite knowledgeable on each theme. We ran 2 sprints each month and sync with the PO at SOS every month before major monthly release. The team was easier to manage as smaller units with focus than as a large group of 20. We were also able to achieve more.