Myvote below ... I have an assumption (based on the reading of the different thread) : we are talking Development Management rather than generally speaking Project Management (Development Mgt could be a part of a more global Project or a project by itself but dediciated to development). This assumption is confirmed by the current target usage of Eclipse: Development.
|
[EMAIL PROTECTED]
|
| |
| Pascal Negros/France/IBM, 33-0869 [EMAIL PROTECTED], +33 (0) 149 050 869 Enterprise Architectures Engineering, Business Strategy Alignment, Governance of Transformation Blue Pages Get more |  |
| "Chris Armstrong"
<[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 07/07/2006 10:18
|
|
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 should be a combination of work plan, risk plan, resource plan, finacial plan, ..... I should also be placed in context of the global project plan (the one which contains the considered Development (sub-)project plus other (sub-) projects within the global endeavour of the engagement).
Work Product #4: [ X] Task list, [ ] Sprint backlog, [ ] Work item list, [ ] Team work item list, [ ] Iteration work item list, [ ] Other: The Task List should be organized in a breakdown structure, based on a product breakdown structure and the resource organization. Notice that there is a dependency between the WBS and the PBS but not a 1 to 1 correspondance; 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: [ X] Development burndown, [ ] Release burndown, [ ] 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
_______________________________________________ epf-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/epf-dev
