It's great that we see people getting
involved and discussing enhancements for BUP!
Inclusion of Stakeholder role in BUP
is something we discussed in our meeting in Cupertino, and one bug was
created in Bugzilla to accommodate that.
I'd have one comment to make in order
to keep the discussion in the appropriate forum: since we have a bug created,
it's recommended we keep discussions related to that in Bugzilla (https://bugs.eclipse.org/bugs/show_bug.cgi?id=133269).
That said, Chris if you could please
post the comment you stated below on the referenced bug, it would be great.
Cheers,
Ricardo Balduino
IBM | EPF Committer
www.ibm.com
www.eclipse.org/epf
"Chris Sibbald"
<Chris.Sibbald@xxxxxxxxxxxxx> Sent by: epf-dev-bounces@xxxxxxxxxxx
03/28/2006 08:49 AM
Please respond to
Eclipse Process Framework Project Developers List <epf-dev@xxxxxxxxxxx>
To
<epf-dev@xxxxxxxxxxx>
cc
External Chris Sibbald <csibbald@xxxxxxxx>
Subject
[epf-dev] FW: [Bug 133269] New: Add
Stakeholder role to BUP
Hi Folks,
I propose to add the Stakeholder role to the RM discipline as this
appears to be the most natural fit of the existing disciplines (tightest
coupling, natural interface for stakeholders).
I will volunteer to incorporate the role and description and integrate
the role as an additional performer of the RM tasks.
As I mentioned at the meeting I have completed the updates to the RM
discipline, incorporating all of the comments/actions from the Feb 23
telecon. As soon as we complete an internal review I will deliver
this
content (this week).
Is it reasonable/acceptable to quote the referenced paper by Scott
Ambler for the definition?
Cheers,
Chris
-----Original Message-----
From: bugzilla-daemon@xxxxxxxxxxx [mailto:bugzilla-daemon@xxxxxxxxxxx]
Sent: Saturday, March 25, 2006 10:17 AM
To: Chris Sibbald
Subject: [Bug 133269] New: Add Stakeholder role to BUP
Summary: Add Stakeholder role to BUP
Product: EPF
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P3
Component: Content
AssignedTo: epf.content-inbox@xxxxxxxxxxx
ReportedBy: mark.dickson@xxxxxxxxx
CC: blyons@xxxxxxxxxxxxx,
mark.dickson@xxxxxxxxx
As discussed at the San Jose meeting, we want to add a generic
Stakeholder role
to BUP. The purpose is to provide a marker for the additional team roles
required in a collaborative process, such as the Scrum Product Owner,
DSDM
Ambassador User or XP Onsite User. The idea is to make the Stakeholder
an
explicit first-class citizen of BUP, rather than an implied participant.
A short white paper will follow soon to define the Stakeholder role in
more
detail. For now though, see Scott Ambler's definition at
http://www.agilemodeling.com/essays/activeStakeholderParticipation.htm
Broadly speaking, we will use the Stakeholder role to represent the
participation of those people not already covered by the "technical"
roles in
BUP (e.g. analyst, developer, tester). It is accepted that the other BUP
roles
are natural stakeholders (small "s") but, as they already have
a defined
role,
they are not described by the Stakeholder (large "S") role.
The Stakeholder in core BUP will be deliberately simplified to a single
role to
keep the method content light. Future plug-ins may of course extend this
role
to create specialisations.
Barry Boehm and Mark Dickson have volunteered to lead this work. All
contributions welcome.
--
Configure bugzilla e-mail:
https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--------------------------------------------------------------------------------
Telelogic Lifecycle Solutions:
Helping You Define, Design & Deliver Advanced Systems & Software
Learn More at www.telelogic.com
Chris Sibbald
Vice President, Standards and Technology
Telelogic North America Inc.
255 Albert Street, Suite 600
Ottawa
Ontario K1P 6A9
Canada
The information contained in this e-mail, including any attachment or enclosure,
is intended only for the person or entity to which it is addressed and
may contain confidential material. Any unauthorized use, review, retransmissions,
dissemination, copying or other use of this information by persons or entities
other than the intended recipient is prohibited.
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev