Friday, 2 November 2012

Does a tight scope give better delivery performance?

When an improvement project is being designed it is a good idea to give the right degree of consideration to the scope of the project; what's in and what's out. Many projects take longer than necessary, or never get completed, due to an unclear scope that leaves the team attempting to implement a continuously evolving change project. Some points to consider:

Even if the scope does not include all the possibilities you can always go back and complete a second smaller follow up project.

Completing something is better than not completing anything, especially for ongoing motivation.

Small tight packets of work are very productive due to the marriage of focus with short term achievement.

If your projects are stalling, or just seem to keep on going without ever coming to a conclusion, then review / revise the scope and 'put them to bed'.

Smartspeed Consulting Limited
Taking the frustration out of on time delivery.

C'mon! Just write the SOP!