My vote below.

Thanks and best regards,
Peter Haumer.

______________________________________________________________

PETER HAUMER, Dr. rer. nat.
Rational Method Composer | Eclipse Process Framework
Rational Software | IBM Software Group
Tel.: +1 408 863-8716
______________________________________________________________



"Chris Armstrong" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]

07/07/2006 10:18

Please respond to
[EMAIL PROTECTED]; Please respond to
Eclipse Process Framework Project Developers List <[email protected]>

To
"'Eclipse Process Framework Project Developers List'" <[email protected]>
cc
Subject
[epf-dev] Ballot for voting on PM process element names and next PM        call





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 ([EMAIL PROTECTED]), 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: _______________ : Iteration plan refers to items of #2 plus other things, e.g. risks, goals, etc.

Work Product #4: [ ] Task list, [ ] Sprint backlog, [ X] Work item list, [ ] Team work item list, [ ] Iteration work item list, [ ] Other: same as #2; this should be a report as it is a sub-set of #2 in which additional attributes are filled in; if you remove an item from an iteration you do not want to loose that information but keep it for when it is assigned again to an iteration. You cannot do that with Chris' model easily as it requires to mange two elements in two lists; recommended representation of placing this inside of Work Product #3

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 _______________________________________________
epf-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/epf-dev

_______________________________________________
epf-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/epf-dev

Reply via email to