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 / 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, […]
Agile / Product Management / Requirements gathering / ROI / Software development
Posted on:
Market Driven Competitive Advantage
Your strategy should be driven by the needs of the market. Becoming market-driven is critical to intentional product success. But it is not enough to understand your market. You have to sustain your understanding, and take advantage of it, competitively.
Agile / Slightly off-topic
Posted on:
Good Enough For Now
Adam Bullied wrote a really good article about not losing motivation in the face of challenges. His closing quote spun us off on a philosophical tangent about being “good enough.”
Agile / Prioritization / Product Management / Project Management / Requirements / Requirements gathering / ROI / Software development
Posted on:
Successful Products: Lucky or Intentional?
Is your product successful because you were lucky, or because you were methodical and intentional? Do you want to build a plan where you are dependent on good fortune, or do you want to make your own “luck?” Both approaches work, but only one makes sense as an intention. Slide […]
Communication / Consulting / Design / Outsourcing / Software development / Testing
Posted on:
Making Offshore Design Work
When companies first start off-shoring, they usually send the “low level” implementation work overseas first, to work out the process kinks and manage risk. Over time, your valued, domain-aware developers will perceive a lack of career opportunities with this limited role. Naturally, you will want to consider sending design work […]