Evolutionary Project Management (Evo) is a very successful project management method. It can be used to manage any type of project and to develop any type of product. It has been used on a wide variety of disciplines in systems engineering, software engineering and organizational development.

One characteristic of Evo, is that it scales elegantly from tiny projects, or sub projects, to huge or expensive projects that encompass many engineering disciplines. It is useful for doing one's personal work, and for managing a corporation.

Evo consists of many sub-methods that can be learned and used separately, or in any combination, or as a whole.

Some of the main components are:

1. a specification language called Planguage.

2. A practical and useful way to specify Requirements.

3. Design and Architecture; through the use of Impact Estimation Tables (IET) and design specification templates.

4. Developing and delivering a system Evolutionarily (Evo).

Planguage means Planning Language. It consists of over 650? well-defined concepts and a grammar. Each concept is specifically developed to enhance the communication ability for any aspect of? a project plan, or an engineering process.

For example, when we specify a Product Quality Requirement, Planguage has concepts for it.

Simple and short example.

Name Tag: Usability.Learn
Scale: average time to Learn to ...
Past [this year] 25 min.
Tolerable [next year] 15 min.
Goal [next year] 2 min.

Many people and organizations are struggling with requirements, they know they are not doing it well, but they don't really know what to do about it.

We think long and hard about requirements, read lots about it, have decades of experience working with requirements, and we have developed a unique, logical and very powerful method of specifying them.

Many multinational corporations have concluded that we teach the best requirements method of all.

The requirement method is easy to learn (it takes a little longer to master;-), and when it is normally reported to give a wow-aha kind of experience.

We are very excited about requirements, and we believe that soon, you will be too.

When the Requirement process is understood, a. Architecture and b. Design can be done intelligently, systematically and numerically.

With the use of Impact Estimation Tables (IET):

1. get an overview of the Solutions and their impact on both the Requirements, and on their consumption of Development Resources.

2. systematically and dynamically prioritize which Solutions or Evo steps to implement, and when to implement, and when enugh is enough.

3. balance your set of Solutions so you simultaneously satisfy all your Requirements, but don't over-design towards a few requirements.

4. systematically choose between two technical designs, or two suppliers, or whether to build it in-house, or contract it out, etc. Choose intelligently and with confidence.

5. communicate, and openly discuss, the positive and negative effects of Solutions, and the overall time schedule.

To do Evo well, to get all the benefits that Evo has to offer, you must have quantified the Requirements, and have specified Past & Goal levels. Then, in order to choose and track Solutions and Evo Steps wisely, we highly recommend using IETs.

Evo also implies breaking the development and the delivery of your project into cycles of about 2% of total project costs (for example 1 week cycles). Evo means learning from each cycle. Evo means changing anything according to what you just learned,. This agility of learning and changing guarantees success, and avids failure.