Organize your SMs and POs development
summary
A mentoring framework for developing Scrum Masters and Product Owners uses one-on-one pairs, one-hour weekly sessions, a semi‑formal kickoff to set expectations and set date after 2–3 months to review progress, a pool of mentee‑chosen topics, mutual team visits, confidentiality rules, and concrete action points to try techniques back in the team. Regularity, trust, preparation and follow‑up drive results; the program produces a shared knowledge base and shows measurable skill gains in about three months.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:07Setting up meetings
- 2:13Mutual expectations
- 5:31Topics
- 8:31Feedback
- 10:19Success factors
- 13:06Outcomes
related talks
21mMeaningful Mentorship for Developers
35mBecoming a mentor, why and how?
55mMentorship Panel
33mMentoring, For me or not for me, that is the question
37mPairing with Intention: A Guide for Mentors
19mTwo Examples of Scrum Master Initiatives Supporting the Whole Team in Large-Scale Scrum
20mFacing Our Organization's Philosophy with Scrum
24mHow to be a good mentor