Lucid Lynx Development Process

robbiew and I covered how we plan to schedule and track development during the Lucid Lynx cycle. Here is a video of our plenary session at UDS where we explain it:
(our part starts at 13m52s)


Slides are here.
The plan boils down to two things:

1. We will use burndown charts to track progress over the course of the release.


2. We will be building a bit more agility into our schedule by working in three separate milestones. These are simply overlaid on top of the normal Ubuntu schedule.

The milestones look like this:

Goal	Milestone	Date
Initial Integration and Risky Work	Alpha 2	2010-01-14
Development	Alpha 3	2010-02-25
Clean Up and Completion	Beta 2	2010-04-08

The Lucid Lynx Release Schedule is not effected by this plan,

The desktop team kept a burndown chart for Karmic, and it worked quite well.