There’s really only one way to travel down a waterfall – in a barrel. A lot of people died this way, but some survived. Software projects have been predominantly waterfall projects since the start of software projects. And stakeholders rode down those projects, basically in a barrel. The people riding […]
Business Analysis / Product Management
Posted on:
Inspired By Your Customers
Should your products be designed by your customers, or inspired by your customers?
Agile / Product Management / Software development
Posted on:
ProductCamp Austin Winter 2009
The second productcamp for Austin is just around the corner! Are you going to be there? You should.
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.
Product Management
Posted on:
Keeping up With Change
How quickly is your market changing? Bet it’s faster than you thought.
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 / Prioritization / Product Management / Requirements / ROI / Software development
Posted on:
Plan Your Next Sprint By ROI: Part 1
You’ve got a giant backlog of user stories and product capabilities. How do you determine which stories to implement right now? By the estimated value of each story? Pick the ones the developers want to build next? How about picking the stories that maximize the ROI of the sprint? To […]
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, […]