Hi Folks,
Here are my votes.
Cheers,
Chris
Here is the ballot for voting on PM process element
names. I attempted to include the various names people have suggested for these
things as choices. If there are any that I overlooked or if there are new ones
that people would like to suggest, feel free to write them in under "Other". To
cast your vote, reply to this email message, copy me
(chris.armstrong@xxxxxxxxxxxxxxxxx), and place an '"x" in one of the boxes that
precede each choice to indicate your vote for each element. The voting closes at
12:00am Friday 7/14 which will allow us to tally the votes and report the
results at the next PM conference call (scheduled for 8am PST Friday 7/14) and
the epf-dev mail list.
============================================================
Role #1: [ ] Development lead, [ X ]
Project manager, [ ] Team lead, [ ] Technical lead, [ ] Other:
_______________
Work Product #1: [ ] Development plan, [ X ]
Project plan, [ ] Release plan, [ ] Other: _______________
Work Product #2: [ ] Development item list, [ ]
Product backlog, [ ] Development backlog, [ X ] Work
item list, [ ] Release backlog, [ ] Cross-project backlog, [ ] System work item
list, [ ] Project work item list, [ ] Other: _______________
Work Product #3: [ X ]
Iteration plan, [ ] Other: _______________
Work Product #4: [ ] Task list, [ ] Sprint
backlog, [ X ] Work item list, [ ] Team work item
list, [ ] Iteration work item list, [ ] Other: _______________; recommended
representation of placing this inside of Work Product #3 I think one artifact can
work, however there are different types of elements (Change Requests, Defects,
"Objective" elements and actionable elements) on this list and each has
different attributes and purposes. In order to use one list, the
elements must have a type attribute to classify them so that views of the
list can be produced to filter the list and present the appropriate
information. Also, it must be clear that this list does not contain the
requirements, which are are captured in other artifacts (Vision, Use Cases,
Supporting Requirements), but may reference
requirements.
Work Product #5: [ X ] Risk
list, [ ] Other: _______________
Work Product #6: [ X ]
Status assessment, [ ] Other: _______________
Report #1: [ ] Development burndown, [ ] Release
burndown, [ X ] Project burndown, [ ] Other:
_______________
Report #2: [ X ]
Iteration burndown, [ ] Sprint burndown, [ ] Other: _______________
============================================================
Thanks, Chris ~:|
Chris Armstrong ~:|
President
Armstrong Process Group,
Inc.
651.491.5575 c
715.246.0383 f
www.aprocessgroup.com
"proven practical process"
Come see APG at:
---------------
Agile 2006 International Conference
Minneapolis, MN, July 23-28, 2006 - www.agile2006.com
---------------
14th IEEE
International Requirements Engineering Conference
Minneapolis, MN, September 11-15, 2006 - www.re06.org