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 / 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.
Interaction design / Interviews / Prioritization / Product Management / Requirements / Requirements gathering / Uncategorized / UX
Posted on:
20/20 Vision – Innovation Game in Action
Having an outside-in bias as a product manager is important – you need to understand how your customers (or your customer’s customers) would value capabilities you might build into your product. When running a workshop to collect that information, playing some “serious games” is a great way to get more […]
Agile / Kano Analysis / Product Management / Requirements Models / Software development
Posted on:
The One Idea of Your Product
“For what one idea do you want your product to stand in the mind of your customer?” I heard Roger Cauvin ask that question at the most recent ProductCamp Austin [correction – he said it here – thanks Roger], and the quote has been jumping to the front of my […]
Kano Analysis / Marketing / Product Management / Requirements / Requirements Models
Posted on:
Minimum Market Acceptance
April Dunford just presented Startup Marketing 101 at DemoCamp Toronto. Great ideas from the ‘marketing and your startup’ point of view. I’ve often said that product managers and product marketers care about much of the same market data, they just do different things with it. The idea of minimal feature […]
Agile / Business Analysis / Business Rules / Communication / Consulting / Product Management / Software development
Posted on:
Simple Agile Model Example
A picture is worth a thousand words. Agile values working software over comprehensive documentation, and it values customer collaboration over contract negotiation. With that in mind, how much is a picture of a model worth? Check out a simple example, how it helped, and what we didn’t do.
Agile / Product Management / Requirements / Software development
Posted on:
Satisficing Sprints
Satisficing probably makes more sense than perfecting your product. Can? Open. Worms? Everywhere. Are we really saying “don’t make it perfect?” Yup.
Agile / Prioritization / Product Management / Requirements / ROI / Software development
Posted on:
Plan Your Next Sprint By Bang For The Buck: Part 2
Planning by ROI. Hmmm. Isn’t that impractical? In an econometric way, yes. But you can still estimate the relative value of the capabilities / stories you’re planning for your scrum sprints. The point is – don’t look only at value – also look at costs. While “ROI” may be a […]
Agile / Ishikawa Diagram / Product Management / Requirements / Requirements Models / Software development
Posted on:
Agile Product Management: Providing Context
Agile development methodologies succeed because they help development teams be as effective as possible. Development teams do not, however, work in complete isolation. The company they work for has a strategy. The company manages a portfolio of products, and targets a particular product at specific market problems. Within that context, […]