I recently read the book Being Mortal by Dr. Atul Gawande about empowering people to make end of life decisions. Now you might be wondering, what does that have to do with scrum? Well it turns out the same questions we might ask a dying person to help facilitate their end of life in an empowering way are the same ones we might ask a client to empower their scrum practice or agile transformation. Read the full article…
One of our clients recently reached out to us asking for advice about how to manage their organization’s scaled scrum adoption. They wanted to know if they could use scrum to manage the adoption of scrum in the organization. The short answer is yes.
Guiding an organization’s adoption of scrum is a big project. It’s a project that will require a cross-functional team. It’s a project where the full scope of work can’t be known when the work starts. It’s complex, exactly the kind of endeavor that you want to use scrum to implement. When I’m working with organizations that are adopting scrum at scale, I always start by recommending that they create a scrum adoption team, and that this team use scrum to do the work of rolling scrum out to the organization. Read the full article…
World Café is a fun, flexible, and scalable technique for group conversations that leads to creative solutions to complex problems. World Café has some similarities to Open Space Technology: both techniques work for groups ranging from a few people to a few thousand; both are frameworks that support individuals and interactions. World Café is useful for generating and communicating ideas, making decisions, and even doing hands-on work. We’ll be teaching product owners how to use it in our upcoming Advanced Certified Scrum Product Owner (A-CSPO) workshop.
How It Works
The facilitator breaks the room into groups, then sets them to explore a set of related topics, one per table. Each table has a host whose job is to stay with the table and provide continuity while the groups discuss the topic. The other participants rotate between tables on a regular schedule, perhaps every 15-30 minutes. The idea is that those who travel between tables will cross-pollinate ideas between the topics and bring fresh perspectives. By participating in each topic, the participants come to have a holistic understanding of the main issue, and are able to understand each sub-issue within this context. In the last round, people have the option of returning to a previous table so there is opportunity for closure and continuity. Read the full article…
One of the highlights of this interactive workshop is the half-day product road mapping session. Participants will be guided through the creation of a series of minimal viable product (MVP) releases for their product, and learn how to adjust their MVP and their roadmap as market conditions and business needs change.
Another highlight is the use of the World Cafe framework to dive deeply into the skills a product owner needs to communicate effectively with the stakeholders and development team.
The workshop includes several topics taken from the world of lean product development, including the creation and testing of product hypotheses as well as creating a Lean Startup Canvas.
Additional topics covered include: defining and validating business value, crafting a product strategy and vision, how scaling impacts the product owner role, product backlog refinement, avoiding cognitive bias, and much more.
The course includes about 4 hours of self-paced pre-work, followed by a 2-day in-person workshop. In order to take the workshop, you will need to already hold a CSPO from the Scrum Alliance. In order to complete the A-CSPO certification process, you will need to self-report at least one year of product owner experience. Details can be found here on the Scrum Alliance website.
A scrum team’s definition of done is an important tool that helps the team add new functionality while keeping the product in a releasable state. Here is one way of facilitating the creation and evolution of your scrum team’s definition of done.
Identify The Work Needed To Release Something
Have the development team identify all of the work items (often called tasks) needed to release a high quality product backlog item (often called a user story) to production. Each piece of work goes on a sticky note. Be as specific as possible. If a team member says “testing” get specific about what that entails and write specific sticky notes:
Each acceptance criteria has an automated regression test
A scrum master wears many hats including teacher, mentor, coach, and facilitator. Each is a different stance the scrum master might take when interacting with the scrum team, or others in the organization. Part of the art of being an excellent scrum master is being able to select an appropriate stance for a given situation. We also need to be able to flow between them, inspecting and adapting based on the situation and the needs of the people involved.
This is the act of showing or explaining something to someone so that they acquire new knowledge. The scrum master is an expert in scrum and related agile practices. The scrum master spreads this knowledge throughout the organization, enabling people to engage in their work more effectively. Read the full article…
The big news from the Dublin Scrum Gathering is that Cathy Simpson has become a certified scrum trainer. This is a monumental accomplishment. She is one of less than 250 people in the world, and less than 30 women, who hold this certification. We have had the privilege of working with Cathy over the past 3+ years and supporting her as she climbed this mountain. It’s been inspiring to see her do all of the work required. We couldn’t be more proud of her.
David Marquet was about to become a submarine commander. He spent a year learning everything about the boat he was going to command. Two weeks before he was to assume command he was given a different sub, and the only thing he knew was that it has the reputation for being the worst in the Navy. He made it the best. Here’s how.
Product team is starting to assign business values to epics so we can, along with effort estimates, set correct priorities. However, we also have quarterly goals. Once we reach the end of a quarter, if an epic is not completely done (all stories under it), how do we get partial credit?
I recommend rolling the value down from the epics into the stories themselves. This way, you can see what you delivered in the quarter. Keep in mind that value estimates, just like effort estimates, are really just a tool to help with planning and decision making. At the end of the quarter, I’d like to see you focusing on the awesome stuff you delivered and what your customers’ reactions were to that new functionality.