Re: [epf-dev] Ballot for voting on PM process element names and next PM

["Ana Paula Valente Pereira" <apereira@xxxxxxxxxxx>]

Here is my vote (and I will need a second internal ballot to translate
these names to Portuguese :-))

>
> ============================================================
>
> Role #1: [ ] Development lead, [X] Project manager, [ ] Team lead, [ ]
> Technical lead, [ ] Other: __Note: (changed my mind because a project
manager using agile techniques could be used for any kind of creative
project delivered in iterations... not just software)
>
> Work Product #1: [ ] Development plan, [X] Project plan, [ ] Release plan,
> [] Other: _
>
> Work Product #2: [ ] Development item list, [ ] Product backlog, [ ]
> Development backlog, [ ] Work item list, [ ] Release backlog, [ ]
> Cross-project backlog, [ ] System work item list, [ ] Project work item
> list, [X] Other: ____________Feature Backlog: if this workproduct is to
be costumer oriented and used for discussing with costumer the 
priorities and what features goes to each iteration then the costumer
language should be used... and they understand features...not "work
items"... these features will focus on delivering value to the
costumer... requirements for each feature could be detailed in each
iteration using the appropriate openup work products: use case
specifications, supporting requirements scenarios, etc (things such as
bugs should not go on this backlog)... and the detail for  open up work
products and tasks on each iteration would go to work products#3 and#4
(whatever their names )
>
> Work Product #3: [X] Iteration plan, [ ] Other:
>
> Work Product #4: [ ] Task list, [ ] Sprint backlog, [ ] Work item list, [
> ]
> Team work item list, [ ] Iteration work item list, [ ] Other:
> _merge with #3______________; 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, [x] Other: Feature Burndown for what was exposed in work item 2
>
> 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
> epf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/epf-dev
>