- Accelerate time to market
- Manage changing priorities
- Increase productivity
- Ability to manage changing priorities
- Improved project visibility
- Increased productivity
Let’s look at the barriers and concerns about agile to see if there are any correlations between why an expected benefit like accelerated time to market wasn’t realized. The top 3 barriers to agile adoption were:
- Inability to change their organization’s culture
- Availability of the personnel with the right skills
- General resistance to change
- Lack of up-front planning
- Loss of management control
- Management opposition
A benefit like accelerated time to market requires change to expand beyond the development team, which means that organizations must overcome some of those barriers and concerns that are listed. If you are using agile development as a vehicle for software development improvement only without really changing how the business specifies software features, you most likely won’t gain much ground on the speed-to-market front.
Why? Well, you could be attempting to cram too many features at once into your product. In fact, your existing way of doing business may be causing you to specify features that you don’t really need. So yes, adopting agile development might translate into allowing you to build all of those features a little bit faster, but if you want speed to market, you need to figure out what not to build. You need to figure out how to go to market with a minimal viable product.
Yes, you can get some immediate, easy wins with agile. Other, more meaningful and lasting benefits can come – but they will come at a higher price. True change involves changes in mindsets and behaviors at all levels of the organization.