Theoretically one could argue that we should work top-down, first working on project-cycle activities, like scope and goals, and only then on the deliveries and only then on tasks. Theoretically. In practice, however,  we cannot master all things at once, so we should better use a bottom-up learning process.

Note that, when introducing the Evo way of working for the first time, you even may have to suppress the urge of working on the most important Delivery cycle and the most important Project cycle before the Task cycle techniques are well understood and applied. Trying to do too much too early is too much for normal people and usually spells disaster (most of us are normal people). The result: "We tried it and it doesn't work". This is a reason of failure of many so called Process Improvement efforts. So, better define the first tasks based on intuitive priorities, just as you did before. Apparently, your projects survived your previous ways, as you are still in business. Rushing things faster than people can absorb creates failure. Therefore, don't just follow theory. Follow the ways that create practical results.

To introduce the Evo way of working successfully, we start at the Task cycle, then add the Delivery and Project cycles and then ruturn to the Task cycle level again. We keep cycling through these levels, adding elements of Requirements and Risk management as people find out themselves that they need these elements.

1. Start disciplined way of working (short time vision: learning a disciplined way of working, where the discipline can be sustained because of successful results of tasks)
   1. Preliminary, intuitive Delivery selection
   2. Task cycles based on the preliminary Delivery selection
   3. Learning realistic rather than optimistic estimation
2. Generate TimeLine (project vision)
   1. Vision and scope on the current Project
   2. Vision on Deliveries
   3. Delivery strategy
   4. Define Deliveries
   5. Concurrency of Deliveries
   6. Task cycles based on Delivery strategy
   7. Checking assumptions, learning what is really needed
3. Project Synchronization (organization wide vision)
   1. Vision on Organizational level
   2. Concurrency of Projects
   3. Rearrange TimeLine based on concurrency or Projects
   4. Dynamic scheduling of resources through projects based on organisation-wide prioritization
   5. Learning how to run large and concurrent projects successfully

If you have any comments, something to add or change, or a different view, please tell me!

to Task, Delivery and Project Cycles