Back to Course

Product Owner 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 - A Journey Through the Agile Lifecycle
  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 8 – Generalizing Specialist
  14. Agile Team – Part 9 – The Agile Business Analyst (BA)
  15. Agile Team – Part 12 – Agile Sponsors & Stakeholders
  16. Agile Team – Part 13 – Agile Executives and Leaders
  17. Agile Team – Part 14 – Real World Agile Role Challenges
  18. Agile Team – Part 17 – Distributed Teams
  19. Week 3 - Visioning
    Agile Simulation - Part 1 Meet the Agile Team
  20. Agile Simulation - Part 2 Agile Lifecycle Overview
  21. Agile Simulation - Part 3 Purpose, Agenda, Team Norms
  22. Agile Simulation - Part 5 Visioning II
  23. Agile Simulation - Part 6 Stakeholder Analysis
  24. Agile Simulation - Part 7 User Personas
  25. Agile Simulation - Part 8 Use Case Diagrams
  26. Agile Simulation - Part 9 Process Diagram and UI Flow
  27. Project-Release & Visioning Meeting – Part 3 – Facilitating the Top 10 Agile Meetings
  28. Sample Project Visioning Meeting – Part 4 – Facilitating the Top 10 Agile Meetings
  29. Project Kickoff Meeting - Real World Tips – Part 5 – Facilitating the Top 10 Agile Meetings
  30. Week 4 - Team Level Release Planning & Cross-Team PI Planning
    Introduction to Release Planning
  31. Agile Simulation - Part 15 Release Planning
  32. Agile Simulation – Part 16 Iteration Pre- Planning | Backlog Refinement
  33. Release Planning Meeting – Part 9 – Facilitating the Top 10 Agile Meetings
  34. Release Planning Meeting Real World Tips – Part 10 – Facilitating the Top 10 Agile Meetings
  35. Iteration Zero Planning Meeting – Part 13 – Facilitating the Top 10 Agile Meetings
  36. PI Planning - Feature Readiness
  37. PI Planning - Backlog, Alignment and Event Space Readiness
  38. PI Planning - Keeping the Program Board Active
  39. PI Planning - Anti-Patterns and Positive Patterns
  40. Preparing for PI Execution
  41. Week 5 - Story Writing, Backlog Prioritization and Refinement
    Agile Simulation - Part 10 Building the Backlog | Writing User Stories
  42. Agile Simulation - Part 11 Story Slicing
  43. Agile Simulation - Part 12 Non-Functional Foundation Stories
  44. Agile Simulation - Part 13 Prioritization | Ranking
  45. Backlog Prioritization - MoSCoW & Kano methods
  46. Backlog/Story Writing Meeting – Part 6 – Facilitating the Top 10 Agile Meetings
  47. Story Writing Meeting Real World Tips – Part 7 – Facilitating the Top 10 Agile Meetings
  48. Story Writing Meeting Demo – Part 8 – Facilitating the Top 10 Agile Meetings
  49. Story Elaboration Pre-Planning Meeting – Part 14 – Facilitating the Top 10 Agile Meetings
  50. Backlog Refinement Meeting – Part 18 – Facilitating the Top 10 Agile Meetings
  51. Week 6 - Sprint Execution
    Release Planning Rapid Sizing Method – Part 11 – Facilitating the Top 10 Agile Meetings
  52. Release Planning Story Sizing Demo – Part 12 – Facilitating the Top 10 Agile Meetings
  53. Agile Simulation - Part 17 Sprint Planning Meeting
  54. Agile Simulation - Part 19 Team Interruption During Iteration
  55. Iteration Planning Meeting – Part 15 – Facilitating the Top 10 Agile Meetings
  56. Daily Standup Meeting – Part 16 – Facilitating the Top 10 Agile Meetings
  57. Daily Standup Meeting Real World Tips – Part 17 – Facilitating the Top 10 Agile Meetings
  58. Agile Simulation - Part 21 The Dysfunctional Daily Standup
  59. Agile Simulation - Part 22 Demo
  60. Sprint Review Meeting Demo – Part 19 – Facilitating the Top 10 Agile Meetings
  61. Agile Simulation - Part 23 Sprint Retrospective
  62. Sprint Retrospective Meeting – Part 20 – Facilitating the Top 10 Agile Meetings
  63. Week 7 - Intro to Kanban
    Introduction to Kanban
  64. Visualize Your Workflow
  65. Limit Your Work In Process (WIP)
  66. Measure and Optimize Flow
  67. Make Process Policies Explicit
  68. Sample Kanban Board: Reports Team
  69. Sample Kanban Board: Marketing Team
  70. Sample Kanban Board: Support Team
  71. Sample Kanban Board: Claims Management Board
  72. Week 8 - Agile/Servant Leadership and High Performance Culture
    High Performing Teams – Part 1 – Foundations of High Performing Teams
  73. High Performing Teams – Part 2 – Team Maturity Stages
  74. High Performing Teams – Part 3 – Servant Leadership
  75. High Performing Teams – Part 4 – Shifting Towards Servant Leadership
  76. High Performing Teams – Part 5 – Self-Organizing Teams
  77. High Performing Teams – Part 6 – Understanding Team Motivators
  78. High Performing Teams – Part 7 – Team Forming Stage
  79. High Performing Teams – Part 8 – Team Norms & Agreements
  80. High Performing Teams – Part 9 – Team Storming Stage
  81. High Performing Teams – Part 10 – One-on-One Coaching Tips
  82. High Performing Teams – Part 11 – Emotional Intelligence
  83. High Performing Teams – Part 12 – Correcting Dysfunctional Team Member Behavior
  84. High Performing Teams – Part 13 – Resolving One-on-One Conflict
  85. Weeks 9 - Effective Facilitation Skills
    Effective Facilitation - Part 1 Introduction to the video series “Delivering Effective Agile and Non-Agile Meetings
  86. Effective Facilitation - Part 3 Top 10 Must Haves for Effective Meetings Part 1
  87. Effective Facilitation - Part 4 Top 10 Must Haves for Effective Meetings Part 2
  88. Effective Facilitation - Part 6 Questioning Skills
  89. Effective Facilitation - Part 7 Non-Verbal Communication
  90. Effective Facilitation - Part 14 DYSFUNCTION - “I’m Your Boss”
  91. Effective Facilitation - Part 15 DYSFUNCTION - Live Demo
Lesson 10 of 91
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.