Understanding your users is critical to developing good products. A “complete” understanding is sometimes required, and always comes at a cost. A contextualized understanding is valuable but less so, and costly but less so. Even a shallow understanding of your users provides value by preventing some dysfunctional behaviors. You do not always need to develop personas before developing products.
Continue reading Progressively Elaborated Users
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 bullet it becomes difficult to manage expectations.
Continue reading The Potential of Agile
Taking agile, a process otherwise optimized for small, cross-functional, collaborative teams and making it work at scale is fascinating. You have to change some elements, and retain others, as you redefine the context. Being outcome driven, is one element you must retain – or even elevate in importance, or you fundamentally break the system of delivery
Continue reading Agile at Scale – Outcome Driven (or Broken)
Product owners and product managers. Two roles, often done by one person. Together, the product people need to take an organization’s strategy, figure out the appropriate product strategy, and convert that into actionable work for the delivery teams to create the right product. What does the product manager own, and for what is the product owner responsible?
Continue reading Product Owner Manager – Alone Together
Product owners are likely to find themselves alone in the organizational wilderness. Their organizations expect them to connect the towers of long-term strategic planning with the frontiers of great new products. Iterative and incremental development of solutions can bring these two worlds together. There’s always a gap between strategy and execution – and product owners are ideally positioned to help fill that gap.
What we need is a survival guide – a set of principles, tools, and techniques; learned and applied in a two-day “camp” with industry-leading experts in agile product management and product ownership.
Continue reading Product Owner Survival Camp
Last month, Mike Smart of Egress Solutions and I gave a webinar for Pragmatic Marketing on product roadmapping when working in agile environments. We had a great turnout of over 1500 people in the session – with not nearly enough time to answer all of the questions.
One attendee asked, “Please explain how a prioritized list of features is not a roadmap?”
A fantastic question, which we did not see in time to answer during the call.
Continue reading Features do not a Product Roadmap Make
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.
Continue reading Good Enough
Your product roadmap is a view of what you are building right now, in the near future, and in the more distant future. Or is your roadmap a view of why you are building whatever you’re building right now, in the near future, and in the more distant future?
Your roadmap is both – but one is more important than the other – and product managers need to be able to view the roadmap both ways.
Continue reading Opposite Views of a Product Roadmap
“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.
Continue reading Agile Through a Matrix Lens
Agile is not magical. Changing from a waterfall process to an agile process changes how your team works, and helps eliminate inefficiencies. . What makes agile powerful is also makes it dangerous.
Continue reading Agile Cadabra