When solving complex problems at scale, we use epics, features, and stories to align, focus, and coordinate the work of multiple teams to achieve the objectives of our organizations. An epic represents the investment decision to solve a tangible problem; a collection of epics together represent a broader investment decision […]
Agile / Product Management
Posted on:
The Potential of Agile
The pop-culture concept of a silver bullet – a simple solution to a hard problem – is a dangerous idea. It can be used to over-promise, and doom a team to under-delivery. When an executive, too far removed from what makes creating products hard thinks of “agile” as a silver […]
Agile / Prioritization / Product Management / Product Strategy / Project Management / Requirements / Requirements Models / Software development / User Stories
Posted on:
Agile at Scale – Outcome Driven (or Broken)
An organization attempting to use agile processes at scale must be outcome driven – without intentionality the system of delivery breaks down and operates no better than waterfall.
Agile / Kano Analysis / Prioritization / Product Management / Product Strategy / Requirements / Requirements Models / Software development
Posted on:
Good Enough
We hear a lot about building products which are “good enough” or “just barely good enough.” How do we know what “good enough” means for our customers? No one really tells us.
Agile / Product Management
Posted on:
Agile Through a Matrix Lens
“Agile” is something most teams do wrong*, without realizing they’re doing it wrong. A good 2×2 matrix acts as a lens, helping to convert information into insight. Let’s apply this lens to agile as applied within a company, and see if it helps people decide to do things differently.
Agile / Product Management
Posted on:
Agile Cadabra
Agile is not magical. Changing from a waterfall process to an agile process changes how your team works, and helps eliminate inefficiencies. Adopting an agile process does not let you magically have a more successful product. What makes agile powerful is also makes it dangerous.
Agile / Communication / Prioritization / Product Management / Product Strategy / Requirements gathering / Software development
Posted on:
Whole Product Game
How can Theodore Levitt’s classic Whole Product approach help with defining a product roadmap? I’ve been revisiting his concepts and their use recently, thinking about how to revise them for some exercises I’ve been doing with product teams.
Uncategorized
Posted on:
Is Agile Really Cheaper?
There are several ways to answer the question “is agile cheaper than waterfall?” Here are two of my favorites: “It depends. Agile done well is cheaper, as long as you measure correctly.” “You’re asking the wrong question. The right question is: is agile better?”
Interaction design / Interface Design / Ishikawa Diagram / Kano Analysis / Prioritization / Product Management / Requirements / Requirements Models / ROI / Software development / UX
Posted on:
Why Do Products Fail? – Forgetting that Users Learn
Next up in the series on the root causes of product failure – products that fail because you have ignored the user’s level of experience. The first time someone uses your product, they don’t know anything about it. Did you design your interfaces for new users? After they’ve used it […]