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 poor choice of terms, “bang for the buck” is not.
Category Archives: Prioritization
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 do that, you need to estimate both value and cost. While remaining agile.
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 3 of your presentation to a venture capitalist should not say “And then we get lucky!”
Improved Prioritization And Market Segmentation
Prioritization is about maximizing the value you provide to your customers. When you have multiple sets of customers with different priorities, what do you do? You could try and find the lowest-common-denominator, and please everyone a little bit. But that would be the wrong thing to do – by trying to please everyone, you fail to delight anyone.
Plan For Today, And Plan Correctly For Tomorrow
Instead of
Prioritize the present when planning your product. Neglecting the future is almost as bad as over-emphasizing it. The key is to incorporate your plans for the future correctly by making them play second fiddle to the present needs of your market. Serve both today and tomorrow – but prioritize today.
Read the rest of the article …
Is Your Product Improving?
Do you recognize this early logo from Amazon.com? Future Now has a great article detailing how Amazon evolved their “add to shopping cart” implementation. From reviewing this summary of the evolution of one feature, we can see that Amazon decided there was value in reinvention. The improved the way their product did something over time. Have you?
Use Case Management is a Tough Balancing Act
Learning how to write use cases can be tough, but it is simple compared to the balancing act of determining which use cases to write and how to manage the expectations of all the stakeholders that are involved. It can be a difficult balancing act to prioritize use cases to assure that you meet the goals of the business while satisfying the needs of the users.
Posted in Business Analysis, Interaction design, Prioritization, Product Management, ROI, Requirements, Requirements Models, Software development, UX, Use Cases
Tagged business goals, corporate goals, end users, goal directed use cases, goal-driven use cases, Interaction design, managing data, personas, principal stakeholders, principle stakeholders, structured requirements, two tier, two tier requirements, two tier sales requirements, two-tier business model, ux
3 Comments
Stakeholder Value-Delivery Matrix
Roger Burlton, of the Process Renewal Group, gave an excellent presentation Monday morning at the 10th annual International Business Rules Group: Developing a Business Process Architecture and Program of Change. A lot of good stuff about how to define, develop, and manage processes. One idea in his presentation was particularly compelling – that of driving process improvement strategy based on stakeholders. This approach looks at how much benefit the stakeholders can get from the improvement, and how much pain the current process causes them. A very compelling strategic prioritization tool.
Posted in Business Analysis, Prioritization, Requirements
Tagged managing data, Prioritization, prioritizing, prioritizing processes, process improvement, process prioritization, process re-engineering, process reengineering, re-engineeering processes, re-engineering processes, stake holder, stakeholders
4 Comments
Why Prioritization Matters
I am a big fan of boxes and arrows, but this time, Jeffrey Davidson found a great article by Dan Willis before I did, and told me about it. Thanks Jeffrey! The article is about how to deal with the what and how of requirements and design – and it provides some really sage advice. But what got my attention was the lack of prioritization of requirements in his example.
Fast Follower Product Strategy: Microsoft Zune
Microsoft has a product called Zune that is a competitor to the Apple iPod. They just recently announced their second release – the new version of the Zune. Since Apple already dominates that market, Microsoft qualifies as a follower – how are they approaching the introduction of a new product to compete with an 800 lb. gorilla?
Read the rest of the article …
Latest Articles
Comments on all Articles
