A SPRINT project is self documenting, in that each task that is undertaken will have its own output, that together create a repository of evidence.
We have already suggested that keeping the project documentation on a shared server or in a similar electronic form will allow everyone involved in the project to have access to documents as and when they need them.
There is no specific "project document" produced at the end of a SPRINT project. This is because every project is different.
The phases of SPRINT are closely related - process redesign coming out of the investigation of existing processes - and you may want to produce a report at the end of each phase: initial recommendations from phase I, more detailed redesign in phase II.
When planning your outputs you need to think about the following :-
- Who is the audience?
- What level of detail is needed?
- How is it to be presented?
- What happens next?
The audience might be the project steering group; a particular service manager; the e-government project board; or a combination of these. Also there may be more than one audience and your output needs to reflect this.
Therefore you might produce an executive summary for management, and a more detailed set of recommendations for those who are tasked with implementing the work.
Consider as well how the work might be presented. Even if a paper based report is required, it can still be combined with a presentation - or be used as the basis for a workshop.
Once the BPR work is complete, the question of "What happens next?" is critical to the success of the project. Have you formal handover procedures in place? What role do the BPR team undertake once the work has been handed over? Does the culture of 'shared information' that has been critical in the BPR work continue once the technical specialists are involved?
|< Prev||Next >|