Emergency work on our most recent software release has caused work on the next year's build slip a couple months. Because we have a hard deadline for this current version, we have to address any and all issues that pop up as the highest priority. This means that parallel work for the next two major releases (a one year schedule) has suffered. That's not such a big deal, since plans can change.
Next week we were to travel to our sister site for a 3 day re-plan meeting to decide what schedules to slip or what scope to reduce. This is really not an easy thing to do since a lot of our capabilities for these next two builds are poorly defined. It's really no ones fault there, it is just that a lot of information and expertise has to come together, along with management issues, for these details to come to light. So this re-plan meeting should be a good thing.
However, we just learned this morning that our customer wants to be briefed on our re-plan changes early next week. So now we are having to try to pull together what information we can.
Basically, we need to brief this important man on the results of our re-plan meeting before we have our re-plan meeting.
I'm still looking for that Scott Adams e-mail addres...