Evo-Steps are assumed to be small increments, typically a week in duration or 2% of total Budget. There are two purposes for Evo-Steps: to move us towards the long-range Requirements, and to learn early from Stakeholder experience (with a view to Changing plans and designs early).
Specification Object, Parameter.
S23: Step [<Time, Place, Event to be determined>]: F1, F2 [Europe], D3 [China].
The main difference between an Evo-Step package (above example with undetermined Qualifier) and a delivery-specified Evo-Step is that the latter has been assigned a sequence or timing and a place of application Qualifier. The Evo-Step package is just a specification of the step contents. An Evo-Step package can be deployed in multiple times and places. You could say that an Evo-Step package is a reusable specification. For example, every week it could be to different countries.
2. Dynamic Step Sequencing: Evo is Conceptually based on the Plan-Do-Study-Act-Cycle. An Evo-Plan for a project Consists-of a planned series of Evo-Steps sequenced in order for delivery. Step sequencing for delivery can be roughly sketched or planned in actual time-sequence. Step sequencing always remains finally contingent upon actual feedback results, and on external considerations, such as new Requirements, Changing priorities, or new technology. The step delivery sequence is determined dynamically, After the previous step results are analyzed (Study Phase) and a decision is made about the next step (Act Phase). Selecting the next step for delivery is the main focus of Evo-Planning activity.
3. Step Priority: Steps with the highest Stakeholder-value-to-cost ratios or performance-to-cost ratios ought to be scheduled for early delivery. Step dependencies have also to be considered.
4. Step Size: A step is typically, but not unConditionally, constrained to be between 2% and 5% of a project’s total financial Budget and total elapsed time. Why? Well, because 2% to 5% is a reasonable amount of Resource to gamble, if you are not absolutely sure whether a step will succeed.
6. Step Lifecycle Location: A step is developed and delivered within a Result-Cycle: any necessary step development occurs as part of the Development-Cycle, any step production required occurs as part of the Production-Cycle, and step delivery takes place as part of the Delivery-Cycle.
7. Step Content Reuse: It is possible for the same step Content to be repeated in several different steps (that is, in effect a ‘roll-out’ across a System, over time, such as to different countries or states or branch offices). In such cases, the step specifications will differ only in the qualifiers. For example, Step 1: Function XX [California], Step 2: Function XX [New York], and so on.
->☺ or ->:) “Symbolizing ‘Impact on Stakeholder’.”
This above Drawn-Icon is a series of any number of steps, each one representing an Evo-Step. I have used this for decades as a graphic icon for a set of Evo-Steps.
A hierarchical set of Evo-Steps (above). The left most can for example represent ‘years’, the middle one ‘months’ or ‘quarters’, and the rightmost steps ‘weeks’ or Elementary steps.
And we can Add specification in the form of tags of Function, design and qualifiers.
Add lines or arrows to indicate step and sub-step relationships.
Evo-Step-Specification *370 Evo-Plan *322 Evolutionary *196 Evolutionary-Project-Management (Evo) *355 PDSA-Cycle *168: See also the individual Plan, Do, Study, Act components Result-Cycle *122 Development-Cycle *413 Production-Cycle *407 Delivery-Cycle *049 Result *130
This Concept entered by Adore.
Table of contents: