An earlier post on this blog titled Process Tailoring, Process Deviation, Process Exception, Approval and Waiver dwelt upon concepts such as tailoring, deviation, exception, approval and waiver in relation to the defined process that gets used for performing any work.
In light of that, it can very well be said that process definition in the real sense happens over a wide continuum starting from standard process getting used to a situation of "no process".
As an aside, an important one though, it needs to be clearly understood that "no process" does not mean no process is being used but that their is no agreed/common/consistent process in place that is getting used.
The continuum view of process definition also implies that the process definition that is finally put into use is the one that happens at the granular level.
The granular level process would get captured as part of the project management plan, service delivery plan, product management plan, etc.
And even if localized processes are used or the "no process" type of process is used, there is still an overall governance layer to take care of deviations as also the exceptions.
The big thought here is that there is a well-defined process in place for handling any situation, including that of the situation of "no process" too!
The following figure presents the process definition continuum illustrating the different levels at which process definition at the project plan level would typically play out.
ORGANIZATION’S STANDARD PROCESS
In light of that, it can very well be said that process definition in the real sense happens over a wide continuum starting from standard process getting used to a situation of "no process".
As an aside, an important one though, it needs to be clearly understood that "no process" does not mean no process is being used but that their is no agreed/common/consistent process in place that is getting used.
- Everyone is on their own and supposed to deliver their piece
- Work would seemingly happen but their is no assurance about what exactly will be coming out of that work at the end of it, if the work even reaches its end ever!
- There will be a lot of friction between the manager and the team, between the team members and between various sub-teams engaged in that work
- There will rise out of the ashes some "heroes" who may happen to save the day, but only in certain instances and that too after they and the others would have undergone severe burn-out
The continuum view of process definition also implies that the process definition that is finally put into use is the one that happens at the granular level.
The granular level process would get captured as part of the project management plan, service delivery plan, product management plan, etc.
And even if localized processes are used or the "no process" type of process is used, there is still an overall governance layer to take care of deviations as also the exceptions.
The big thought here is that there is a well-defined process in place for handling any situation, including that of the situation of "no process" too!
The following figure presents the process definition continuum illustrating the different levels at which process definition at the project plan level would typically play out.
Here are the four levels in which the process definition continuum can be categorized into.
ORGANIZATION’S STANDARD PROCESS
- Ideally speaking, standard process should be followed by every project.
- This will enable meaningful comparison of performance across different projects in the organization.
- There are situations, where a project would require that it be allowed specified variation over the standard process without the need for any approval.
- Such variations should get included in the tailoring guidelines and govern any process tailoring.
- Then there are situations, which should be infrequent, where a project would follow an applicable process but in a manner that is different than the standard process as well as the tailoring guidelines.
- Such case-specific process deviation should get approved and waived-off by the topmost authorities accountable for process and delivery outcomes of the organization.
- And lastly, there are situations, which should ideally be rare, where a project would work with no basis in standard process, process tailoring or process deviation.
- Such process exception (either to few or all applicable processes) should get approved and waived-off by the topmost authority accountable for business outcomes of the organization.
No comments:
Post a Comment