My highlight of the conference was a session that Molly and I convened called, “How to create more love”. We've been pondering current events and wondering how to foster more love in the world. A thoughtful group of participants joined the conversation, and we hit upon some important themes:
Hannes Horn writes about his experience in my half-day class on Medium. He describes the Core Protocols as a way to "speed up the 'Forming to Norming phases of Tuckman’s Team Development Process”. Hannes concludes:
Best of all, taking the Study of Google (The five keys to a successful Google team) the core protocol approach really matters regarding the first key of the study: psychological safety. Developing a team which stops behavior like judging and defending will lead to trust, awareness and openness to each other and that´s the basement of psychological safety.Peter Antman writes about my one-hour presentation on Crisp’s Blog. He finds utility in the culture-as-a-protocol-stack model that I shared: "I knew about the Core Protocols since before, but clustering them in a stack made it so much easier to understand and apply the protocols.” Peter also connects the Core Protocols to Google’s work:
Given the recent published studies from Google on successful teams (members are good at “social sensivity”) the next protocol level is like the perfect match: doing a Check-in by telling how you are actually feeling right now. You learn to acknowledge your self and you learn to accept that we have feelings and that we carry them with us in the meetings.Thank you, Hannes and Peter! I am grateful you both for sharing your thoughts and for connecting this work with the Tuckman Model and Google's ideas on psychological safety. I notice that there’s a lot of research on team characteristics correlating to high performance, but there’s very little published on how teams can learn and embody these attributes. The Core Protocols are just the thing for teams that want high performance!
"Experience Agile" is the activity I use to close my my two-day Agile class. Students learn Agile by doing Agile and by teaching Agile to each other. The assignment:
Design, implement, and deliver courseware that teaches you everything you need to know about Agile.The activity leads them through every step of the Agile product development life span, from product vision and team inception, through delivering the first version of their product. It works!
Download it here. Enjoy!
Want to live in greatness? This book is your guide. The Core Protocols show you how to discover and obtain what you want, on your own, with your friends and family, and with the people you work with. Follow these easy recipes to understand and articulate your personal alignment, to connect and align with others, to share vision together, and to make the abundant goodness of the universe yours. Based on the work of Jim McCarthy and Michele McCarthy, this book is your concise guide to understanding what you want, connecting with others who support you, and living in greatness.Here’s a review:
The Core Protocols are a life-changing experience in logical relationships and work. I use them all the time. I teach them. I share them.
Destined to be a classic of intra and interpersonal interaction that is maybe slightly ahead of its time, those that embrace their simplicity reap massive rewards.
I'm in.Want a copy? You can buy it on Amazon.
Manifesto for Greatness
Here’s a great Scrum scaling pattern based on the pattern that one of my clients uses. They use this pattern to scale their 500 people into a very successfully business unit of a huge technology company.
For each Product Backlog, there is one Product Owner (PO), one Scrum Master (SM), and up to four Development Teams. Each Development Team, plus the PO and SM, are a proper Scrum Team. The four Scrum Teams collaborate together on the single Product Backlog, ensuring that they are working on a single cohesive value stream.
Step 1: Form teams
The group’s manager creates a roster template on the wall. The roster template includes a column for each team and empty slots for team members. Rows indicate the desired mix of skills on each team: programmers, testers, UX specialists, DBAs, Op’s, etc.
Everyone in the group writes their name on a Post-It.
The manager explains the goal to the team. Group members fill the empty roster slots with their names. Talking and collaborating are encouraged! When all roster spots are filled, teams formation is complete.
Though not officially part of the scaling pattern, for great teams in just a few days, send them to a Core Protocols one-day workshop or five-day BootCamp.
Step 2: Scrum!
Here are recipes for your scaled Scrum events:
Sprint: All teams’ Sprints are synchronized, starting and ending at the same time.
Part 1—What: The whole group gathers in their shared work area. The PO re-acquaints the group with the contents of the Product Backlog. Each Development Team selects the subset of Product Backlog Items (PBIs) that they think they can get Done during the sprint.
Part 2—How: Each Development Team creates their individual Sprint Backlog. They carefully note dependencies and other collaboration needs with their cousin Dev Teams.
Part 3—Align: The whole group gathers again. Each Dev Team shares their Sprint Backlog with the group. Dev Teams share collaboration needs. They inspect and adapt, adjusting as needed. They agree on their Sprint Goal. (Did you notice the Diverge-Converge pattern? You'll see it again in the Daily Scrum and Sprint Retrospective.)
Each team holds its own Daily Scrum. Daily Scrums are staggered so the SM and PO can attend all of them.
Daily Scrum of Scrums: Representatives of each Dev Team meet to share their progress toward their individual and joint Sprint Goal. They inspect and adapt and adjust their plans.
The group meets all together, along with stakeholders invited by the PO, for their Sprint Review.
Part 1—Teams: Each team holds their own Sprint Retrospective. They create a concrete plan to improve their team during the next sprint. They also identify ideas for improving the whole group. This meeting lasts about one hour.
Part 2—Group: The whole group meets to inspect and adapt as a team-of-teams. They create a concrete plan to improve the whole group during the next sprint.
Product Backlog Refinement
Refinement with volunteer leaders: The PO and volunteer leaders from the group meet to refine the Product Backlog regularly, usually 1-2 times per sprint. The purpose of this meeting is to get the backlog more Ready for the whole group, so we don’t waste people’s time with PBIs that aren’t Ready enough for the group to estimate together. For great collaboration, the size of this volunteer group is around 8 people. (“More than eight, no collaborate.” -Luke Hohmann) This subgroup may provide *initial* estimates for backlog items, to help the PO with initial forecasting. These estimates are not final, though, because estimating is the Development Team’s responsibility. Consider not sharing these estimates with the members of the Dev Team to prevent anchoring. Consider using this Product Backlog Refinement Workshop.
Refinement with whole group: The whole group convenes to refine the Product Backlog. The purpose of this meeting is to get the Product Backlog ready, with 1-2 sprints worth of PBIs totally Ready, and up to 6 months of backlog estimated—with the whole Development Team estimating backlog items together.
Scaling to 500 people
Each group is around 40 people. The pattern scales horizontally, up to 10 Product Backlogs and 40 Scrum Teams. For every five POs, there is a PO Manager. When there are two PO Managers, there is a PO Director above them.
Scrum Masters form a community of practice, perhaps with a manager handling their career development and HR needs. Programmers, testers, and other specialists do the same.
All together there are around 500 people in the business unit, including managers and support staff.
- Get the Product Backlog Ready for the next Sprint Planning meeting
- Get 6 months of Product Backlog Items estimated so the Product Owner (PO) can forecast well
- Same time and place, every week: so everyone knows and everyone can participate
- 2-hour time box
- Preferred place is the team’s everyday workspace.
- Input: The input to the workshop is the Product Backlog in its current state.
- Output: The output is a Product Backlog that is more Ready
- In 30-minute cycles,
- The PO presents the next PBIs that aren’t Ready to the team. (up to 5 minutes)
- The Development Team decomposes into sub-teams of 3-4 people.
- Each sub-team selects one of the next PBIs and gets it Ready. (15-20 minutes)
- Use User Stories, 3 Cs, INVEST, your Definition of Ready, etc. to guide you.
- If Readiness is blocked by an impediment outside the Scrum team, the sub-team makes a concrete plan for what they will do to get the PBI Ready before the next Sprint Planning or Backlog Refinement meeting.
- Merge back into whole group, the full Scrum team.
- Sub-teams present their work to the whole group. (5-10 minutes)
- Take a break (5 minutes)