AVO Chief

Most of the IT world seems to follow one of two camps of development methodologies. They either accept a very long-term yet sometimes rigid Waterfall method or a very flexible yet sometimes unscalable Agile Method. I have devised a methodology that can handle either/or or best of both. This methodology is built on AVO’s (Agile Value-based Objectives) and provides the benefits of Rapid Release Appplication Development along with the strategic benefit of scalability.

This article will discuss at a high-level how long-term planning can be combined with tactical actions to deliver faster and more successful project results.

First of all, long-term strategies must be defined. These Strategies are then broken down into more flexible and achievable AVO iterations or releases while still keeping the long-term objectives in mind. These objectives of course represent what we are trying to achieve.

AVO principles can help make existing processes more agile while maintaining long-term vision and scalability. Listed below are seven key AVO principles.

The Seven Key AVO Principles are:

1. Focus on Strategic Objectives. Plan accordingly.
2. Aim for and deliver a Base-Working Solution that covers at least 80% of needs in a timely manner (this will filter out supposed needs that were really wants and would have only slowed down progress)
3. Maximize Value to Company (Decisions must be based on greatest value to Company; not just stakeholders). This will lead to prioritizion of components and features that deliver higher value.
4. Find solutions which meet the company goals and of all stakeholders.  Components and features that are not in the base release can be added to future releases based on priority.
5. Solution should be multiple release oriented (First release must be a working solution)
6. Manage changes and fixes through a release process.
7. Manage complex projects by delivering lean high value releases successively.

As listed above the key objectives are as follows:

1. Provide an overall solution based on a strategic vision with the ability to deliver a working version in rapid release form.
2. Then the decision can be made at each release interval whether the solution is acceptable as/is or needs to go on to next release or needs to be modified before going to next release.
3. Additional features can also be added in successive releases.

The AVO method solution must be seen as part of a whole, which includes other systems and projects. It must be robust enough to be changed and extended over time.  As many are aware often times requirements change as market conditions or technology changes so the solution must support change. Changes are managed through the Release Process.

The cost of change is significant in any major real-world systems, so the AVO solution architect must balance planning for change against other goals. The AVO solution architect must also seek to manage and minimize complexity, which helps to maximize value. The aim is a solution which is neither simplistic and brittle, nor overly-complicated.

Written by AVO Chief

Efren Duarte is Director of Products & Services and AVO Chief (Strategist/Evangelist) at Avocera Products & Services Consulting and principal of the AVMI Group, a market research based venture management firm. The AVO Chief provides 2-Week Money Back Guarantee Product Marketing/Management Services Trial for qualified Startups and SMBs with growth potential. Inquire at avochief@ymail.com for more details.

Visit AVO Chief's Website

Follow AVO Chief on Twitter