Posts Categorized: Blog

Co-create the future state

We are experimenting a lot with simulations and agile games at the #PoDojo. One game we have used over the last two years is a variant of the Lego 4 Scrum by Alexey Krivitsky game that creates consistently a hard leadership challenge. We have got very mixed outcomes from using the game playing around with… Read more »

Is scaling Agile the right focus?

During the registration of a recent Agile conference, browsing the program chock full of Scaled Agile presentations, a friend of mine looked at me and asked, “Is scaling Agile the most important problem for us to help solve in today’s business climate?” By “scaling Agile”, I mean solving a problem involving lots of people, say… Read more »

How to: Doing 5 Whys to help vision a future state

The 5 Whys is a problem-solving technique originally developed by Sakichi Toyoda and used within the Toyota Motor Corporation during the evolution of the Toyota Production System manufacturing methodologies. It’s an iterative question-asking technique used to explore the cause-and-effect relationships of a particular problem, with the primary goal of the technique to determine the root… Read more »

Sharing the vision

Often we see that development begins with someone on the business side of the house sharing a “Product XYZ Strategic Win Charware” presentation with the developers. This presentation is meant to convey the reason for building the product, including statements that are supposed to get folks fired up to begin developing the product. However, many… Read more »

How to: Link User Stories to the Value Proposition Canvas

How do you know that the items in your Product Backlog are about solving a customer’s problem? How can you involve the whole team in working on a plan for validating your assumptions about a problem your customer may have and a possible solution you could build? At the #PoDojo we have experimented with Alexander… Read more »

How to: Empathy Map

My father used to say “in order to please the customer you need to get into the customer’s skin.”  The particular saying being meant to convey that unless you truly see a problem from the customer’s point of view, you can’t respond to the problem or develop any customer insights to be able to answer… Read more »

Line of Respect

For those of you familiar with Scrum, you might be wondering what the dotted line is in this picture, just northeast of the Product Backlog. We call it the “Line of Respect”. I’ve seen a similar line drawn, called the “heat shield”, the “s#$% umbrella”, the “wall”.  We have a few reasons for calling this… Read more »

Why should your Product Owner be a Servant Leader?

Servant leadership is characterized by the desire to serve and empower followers and the belief that the best way to achieve organizational goals is through developing the potential of workers. The primary aim is service to others (Greenleaf: Servant Leadership: a journey into the nature of legitimate power and greatness. 1977). This is a far… Read more »

Back to the Roots into the Future

In their HBR article ‘The New New Product Development Game’ from 1986, Hirotaka Takeuchi and Ikujiro Nonaka wrote the for first time about Scrum as a “rugby” approach for organizations to match increased market complexity with increased internal complexity. This was quite different from Henry Ford who neglected the variability of customer needs in his… Read more »