What Scrum Masters Need to Learn & What the Team Needs to Learn-Not the Same

March 16, 2018 — Posted by Al Shalloway

Part of the reason Net Objectives broke w/the Scrum Alliance 10+ yrs ago was our wanting to provide team training to new Scrum teams instead of Scrum Master training. These 2 roles are quite different. I’d suggest that the Product Owner role is closer to the development team role than the SM because they define the “what” for the team & engages with them in building it.

Here’s a list of what these 3 roles need to be trained in:

PO, SM, Team

  • The values &core rules of Scrum
  • The events &artifacts of Scrum
  • The responsibilities of the roles in Scrum

PO & Team. How to identify value & decompose stories. The POs specify the ‘what’ while the team does the ‘how’. Since the development team has design, code & testing responsibilities, these two roles comprise the ATDD Triad of customer, developer (non-Scrum use of the team) & tester.

Team - How to design, code and test the stories.

ScrumMaster – how to coach a team and fulfill the ScrumMaster role It is best if all three roles are in the same training – this teaches collaboration and an appreciation of each role. But note that 

ScrumMaster training is not needed for POs or the team. ATDD should be included since it's the best decomposition method

 

If you're looking for help for your Scrum teams please drop me a line.

Al Shalloway

See our new breakthrough training for Scrum teams and Scrum Masters.

Subscribe to our blog Net Objectives Thoughts Blog

Share this:

About the author | Al Shalloway

Al Shalloway is the founder and CEO of Net Objectives. With 45 years of experience, Al is an industry thought leader in Lean, Kanban, product portfolio management, Scrum and agile design. He helps companies transition to Lean and Agile methods enterprise-wide as well teaches courses in these areas.



        

Blog Authors

Al Shalloway
Business, Operations, Process, Sales, Agile Design and Patterns, Personal Development, Agile, Lean, SAFe, Kanban, Kanban Method, Scrum, Scrumban, XP
Cory Foy
Change Management, Innovation Games, Team Agility, Transitioning to Agile
Guy Beaver
Business and Strategy Development, Executive Management, Management, Operations, DevOps, Planning/Estimation, Change Management, Lean Implementation, Transitioning to Agile, Lean-Agile, Lean, SAFe, Kanban, Scrum
Israel Gat
Business and Strategy Development, DevOps, Lean Implementation, Agile, Lean, Kanban, Scrum
Jim Trott
Business and Strategy Development, Analysis and Design Methods, Change Management, Knowledge Management, Lean Implementation, Team Agility, Transitioning to Agile, Workflow, Technical Writing, Certifications, Coaching, Mentoring, Online Training, Professional Development, Agile, Lean-Agile, SAFe, Kanban
Ken Pugh
Agile Design and Patterns, Software Design, Design Patterns, C++, C#, Java, Technical Writing, TDD, ATDD, Certifications, Coaching, Mentoring, Professional Development, Agile, Lean-Agile, Lean, SAFe, Kanban, Kanban Method, Scrum, Scrumban, XP
Marc Danziger
Business and Strategy Development, Change Management, Team Agility, Online Communities, Promotional Initiatives, Sales and Marketing Collateral
Max Guernsey
Analysis and Design Methods, Planning/Estimation, Database Agility, Design Patterns, TDD, TDD Databases, ATDD, Lean-Agile, Scrum
Scott Bain
Analysis and Design Methods, Agile Design and Patterns, Software Design, Design Patterns, Technical Writing, TDD, Coaching, Mentoring, Online Training, Professional Development, Agile
Steve Thomas
Business and Strategy Development, Change Management, Lean Implementation, Team Agility, Transitioning to Agile
Tom Grant
Business and Strategy Development, Executive Management, Management, DevOps, Analyst, Analysis and Design Methods, Planning/Estimation, Innovation Games, Lean Implementation, Agile, Lean-Agile, Lean, Kanban