- 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
This chapter is from the book
This chapter is from the book
This chapter is from the book
Become an outside-in developer
Outside-in development is a way of thinking about software development supported by a set of techniques. You might wonder, “How do I get started?” Let’s first point out what you don’t need to do:
You don’t need to change your entire firm.
You don’t need to change your development process.
You don’t need to change the tools you use today.
You don’t need to change the way everyone in your organization does his or her work.
Okay, now that we’ve taken some of the difficult items off the table, here is what you can do.
You can do OID in place; in other words, inside your current set of practices and processes. With your current tools. Within your immediate function, if you’d like. Any member of a development effort can exert tremendous positive change on the whole team.
The leaders within the development team who can drive the adoption of OID are not just those who have leadership titles or positions. A number of tips for the effective deployment and use of outside-in development will make it an easier and more enjoyable way to work.
We cover those techniques in depth in Chapter 7, Becoming an Outside-in Developer.