Hello,
One scenario we might consider is to
create 3 shorter iterations to complete the project, for instance 4 weeks each
for M5 & M6, and 2 weeks for M7. Or possibly 4/3/3 weeks. Then we could focus
on creating solid deliverable content for each iteration rather than trying to improve
all content each iteration.
For instance, M5 could focus on
delivering, in final form, all tasks. M6 could focus on artifacts, CPs, and
DPs. And M7 could focus on guidelines. This way we know we’ve accomplished an
iteration when all elements of a particular type have been written, reviewed,
and accepted. And each iteration would result in solid, usable content. Of
course, this is just one possible way the work could be sliced up.
- Jim
____________________
Jim Ruehlin, IBM
Rational
RUP Content
Developer
Eclipse Process
Framework (EPF) Committer
email:
jruehlin@xxxxxxxxxx
phone:
760.505.3232
fax:
949.369.0720
From:
epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx] On Behalf Of Per
Kroll/Cupertino/IBM
Sent: Thursday, July 06, 2006
10:10 PM
To: epf-dev@xxxxxxxxxxx
Subject: [epf-dev] IMPORTANT:
Monday 8 AM PDT Meeting - OpenUP Refocus
Hi,
it
is increasingly obvious that OpenUP is not tracking according to plan. Even
worse, we do not have a meaningful way of assessing where we are at....
We
need to refocus our efforts, prioritize what needs to be done, ask everybody to
step up, establish a credible plan, and track to that plan.
Some
example problems:
-
Our burndown spreadsheet is after 4 weeks still not showing enough uptodate
data to be relevant.
-
Burndown chart has major flaws: If you do not update status for a week, your
remaining work by default goes down to zero... Makes the data look nice, but it
does not reflect reality....
-
Glidepath is not used correctly. The point was that each team lead should
update the glidepath once, and then only update the glidepath at iteration
ends. We still have the dummy data I put in.
-
It is hard to assess, but the remaining work seems to not go down very much...
when you adjust for incomplete data, but it is hard to say
-
We have no prioritization of remaining work (at least not that is visible),
which makes it hard to know whether we work on the most important issues
-
We will fail to reach our M4 milestone with content freeze
-
We have no assessment of how much work is associated with each task, so all
tasks are given equal weight in the burndown
-
My gut feeling is that we are not prioritizing some critical and time-consuming
tasks associated with ensuring a good initial user experience
To
discuss what to do, I would like to have a meeting on Monday 7/10, 8 AM PDT.
I
would like each content leader to come. Others are also welcome.
Agenda:
-
An honest analysis of where we are at (team leads, please update the burndown
spreadsheet)
-
Discuss a credible plan for the end game
-
Be crisp on what we need to do in the short term
-
Discuss how to best mobilize our team
Toll-free
dial-in: 1-877-421-0003
Toll
dial-in: 1-770-615-1374
IBM
Tie-line: 421-0003
Participant
passcode: 667201
Thanks
Per
Kroll
STSM, Manager Methods: RUP / RMC
Project Lead: Eclipse Process Framework
Rational Software, IBM Corp
408-342-3815
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
