I should imagine the structure and content of a 'Project Plan' relating to 'Process Mapping' in a commercial bank would be very similar (if not identical) for any organisation embarking on such a project whether they be from services, manufacturing or the public sector. As all organisations are made up of a series of interconnected processes designed to convert inputs into outputs - well at least I can't think of any that aren't.
In addition how about this…just about everything we do can be considered as a process including your process mapping project. If you view it in this way then a very rough project plan would set out:
- the goals / objectives for the project (deliverables or OUTPUTS)
- Scope of the project
- Resources required (human, material, financial, time, information etc. or INPUTS)
- How and when the project is to be completed (this would breakdown the project into manageable chunks over a timeline and could maybe be described with a simple Gantt chart)
- Doing the work (the processing or the hard bit)
- Measuring the progress of the project against the Gantt chart (EFFICIENCY) as well as the results achieved against your desired outputs (EFFECTIVNESS).
- Review and refine the project plan (PDCA)
If you develop a project plan based on the above this will help you to clarify what you are trying to achieve and I don't think you will be too far away. Obviously you should start to map the processes from the beginning of the supply chain.
Hope this is of some help to you Parlikad.
Regards,
Simon
:)