From Process to Project
Hi all,
I'm trying to create a tutorial for academic use that demonstrates how one can go from the Process to Project and I found the terms used around the Jazz initiative very confusing.
Typically a team moves from Process Engineering to Process Enactment (Project) where the former creates Work products,Tasks,Roles,Processes, Guidance (according to Method Authoring Method (MAM), EPF Composer) and the latter creates concepts such as Development Line, Iteration, Release, Plan, Stream, Team Area, WorkItem, etc.
It seems there isn't a smooth transition from Process Engineering (EPF or RMC ) to Process Enactment (RTC) as the terms do not match. Am I missing something?
regards
Toacy
I'm trying to create a tutorial for academic use that demonstrates how one can go from the Process to Project and I found the terms used around the Jazz initiative very confusing.
Typically a team moves from Process Engineering to Process Enactment (Project) where the former creates Work products,Tasks,Roles,Processes, Guidance (according to Method Authoring Method (MAM), EPF Composer) and the latter creates concepts such as Development Line, Iteration, Release, Plan, Stream, Team Area, WorkItem, etc.
It seems there isn't a smooth transition from Process Engineering (EPF or RMC ) to Process Enactment (RTC) as the terms do not match. Am I missing something?
regards
Toacy
One answer
Process Engineering in RTC would be the admin background tasks such as creating work item types, roles, process configuration such as permissions and operation behaviour (ie. defining how a team should operate). Process Enactment would be actually using RTC to create the work items etc (ie. actual behaviour).
Here is an article which may help:
http://jazzpractices.wordpress.com/2010/06/27/whats-process-enactment/
Here is an article which may help:
http://jazzpractices.wordpress.com/2010/06/27/whats-process-enactment/