TABLE OF CONTENTS How small a job or project does it have to be before I stop trying to apply PRINCE2 to it? When does PRINCE2 become a bureaucratic overkill? How do I control a job that is too small to be called a project? How do I control a project that needs more than one person? In this part we look at scaling down PRINCE2 for small projects.
Chapter 1 explores the use of work packages for very small projects. The idea here is that often some jobs can seem so small that it would be ridiculous to treat them as projects, yet they often go wrong because we forget to apply basic project discipline to them.
Chapter 2 looks at the bare minimum of PRINCE2 that can be used in smaller projects while still retaining the key features, particularly in the area of control.
Chapter 3's approach is to use a matrix, where you can balance certain of your prospective project's characteristics against the scope of the PRINCE2 elements that you should use. In...
