- There may be challenges to overcome
- Consider a different way of thinking about software product development
- Consider some proven techniques as well
- It takes a whole team to succeed
- Understand your stakeholders
- Understand organizational context
- Make your products consumable
- Align with your stakeholders goals
- Define success in your stakeholders terms
- Become an outside-in developer
- The leaders role in outside-in development
- Essential point: You can get started now
Define success in your stakeholders’ terms
Have you ever been to a “final ship” party? The product is complete, testing is over, and the download images or discs are built. Tomorrow morning the product will be available to customers. It’s over.
Or is it?
Don’t get us wrong, we like parties too.
Let’s just be clear what it is we’re celebrating.
It definitely is time to celebrate the completion of a major milestone. But it isn’t success. Success comes when your clients can achieve their business goals through your product.
You are, however, now firmly in the production phase of a software product’s life cycle. You’re about to face three waves of work, each requiring specific outside-in development techniques to adequately manage.
The first wave is brief, and it continues until a target number of early-adopter clients declare success with the product. The second continues for quite some time, until the next milestone event of shipping a follow-on release. That signals the start of the third wave: long-term product support.
Because outside-in development is a stakeholder-based approach, it should be no surprise that success must be defined in the stakeholders’ terms. Beyond that, a variety of OID techniques can assist you to succeed with your stakeholders in all three waves and to leverage your experiences to improve subsequent products.
We cover this in depth in Chapter 6, Defining Success in Your Stakeholders’ Terms.