Schedules - breaking it down

Hi, Doug, Renoir & Alex:

As we discussed in the last meeting, we need to make sure the various projects are coordinated. So I thought I would share with you what needs to happen to make sure we have rough schedules that we can compare:

Migration:

 1.  Doug needs to provide the end-date for the HP contract.
 2.  Renoir can then sketch a high-level schedule for migration.

Compatibility tables:

 1.  Doug needs to follow up with Ronald regarding the Compatibility Tables Phase 1 work: what's the end-date?
 2.  Then, someone needs to estimate the time it'll take the frontend dev person to script parsing the object Ronald comes up with & inserting it into the property pages.
 3.  If the timeline for either of these two items is too lengthly, we should meet to come up with a manual workflow for getting the data into the pages.

CSS Properties project:

 1.  Julee needs to come up with a new endgame schedule (dependent on the Compat-tables schedule).
 2.  Alex needs to come up with a relative launch schedule.

I hope this helps breaking it down so we can get these out. If we need swim lane diagrams, I can work them up based on the information you provide. But let's keep them really simple: even just starting out with bullet points might give us a lot of info.

Regards!

Julee
----------------------------
julee@adobe.com
@adobejulee

Received on Thursday, 24 October 2013 19:11:44 UTC