Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 328167

Summary:	Drop process engineer role?
Product:	z_Archived	Reporter:	Bruce MacIsaac <brucesclan>
Component:	EPF	Assignee:	epf.content-inbox <epf.content-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	apereira, balduino, mark, toddfr
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Bruce MacIsaac

2010-10-19 14:19:20 EDT

A typical small project typically does not have a process engineer, especially if following a pre-defined process.
I'm wondering if we should drop this role in favor of having the project manager role do any necessary project process tailoring.
I'm not sure myself if this is the right thing to do, mostly I'm hoping to spark some discussion.

Comment 1 Ana Pereira

2010-10-19 15:25:52 EDT

In agile we are moving from defined processes to empirical processess ... so I guess that the project eng. role does not make much sense anymore ....in my opinion the team owns the process...not the project manager ... that should be enough for carrying on with  the discussion :-)

Comment 2 Mark Lines

2011-01-13 18:58:52 EST

I used to be a "process engineer" but I am over it now ;-)  At the project level (vs PPM) there is little need for a PE, IMO.  If I am the Team Leader, my team owns the process, not me (within org constraints).  So I believe we don't need it.  I coach them, but they own the process.

Comment 3 Ricardo Balduino

2011-02-22 16:46:16 EST

One more comment to this discussion:
Per our process metamodel, we need to specify a primary performer (someone who will guarantee the task will be performed) and we can also specify additional performers (who collaboratively provide vital info for the task to be performed).

What would a compromise be if we removed the process engineer role?
Should we have the PM role as primary performer and the "Any Role" as additional performer? Or even list each individual role (i.e. Analyst, Architect, Developer, and Tester) as additional performers?

That said, would that change apply only to the process-related tasks (i.e. Tailor the Process and Deploy the Process) or would it also apply to tool-related tasks (Setup Tools and Verify Tool Config & Install)?

Comment 4 Bruce MacIsaac

2011-03-28 15:44:01 EDT

I agree with Ricardo's proposal.  The task for tailoring the process makes it clear that this is really a collaborative effort where you assess as a group what specific tailorings are required and who will do it.  It makes sense for the project manager to coordinate this, so having the project manager as primary performer works for me.
I'm ambivalent about adding additional performers.