Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [epf-dev] IMPORTANT: Monday 8 AM PDT Meeting - OpenUP Refocus

Per
Sorry but I am not able to join the call, as I am on a long weekend vacation with my family.
Please let me know any actions you need me to pick up. I will be making sure that all roles, tasks and products are submitted for architecture by Friday - writing outstanding items myself if required.
Regards
Mark
Mark Dickson
SE&E Practice
Xansa
0780 1917480
*** sent from my blackberry ***


  ----- Original Message -----
  From: Per Kroll [pkroll@xxxxxxxxxx]
  Sent: 07/07/2006 06:10
  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

Whilst this email has been checked for all known viruses, recipients should undertake their own virus checking as Xansa will not accept any liability whatsoever.

This email and any files transmitted with it are confidential and protected by client privilege. It is solely for the use of the intended recipient.
Please delete it and notify the sender if you have received it in
error. Unauthorised use is prohibited.

Any opinions expressed in this email are those of the individual and not
necessarily the organisation.
Xansa, Registered Office: 420 Thames Valley Park Drive,
Thames Valley Park, Reading, RG6 1PU, UK.
Registered in England No.1000954.
t +44 (0)8702 416181
w www.xansa.com
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev

Back to the top