Lucid Community Progress
Mar 16, 2010, 23:02 (0 Talkback[s])
(Other stories by Jono Bacon)
No-Size-Fits-All! An Application-Down Approach for Your Cloud Transformation REGISTER >
"In the Lucid cycle I was keen to track work on this set of
projects in a more effective way. To do this the process worked a
little like this:
"1. We first had a series of discussions at both UDS and online
in which we discuss each project, what is involved and what targets
and goals are in scope for the Lucid cycle. Targets beyond the
Lucid cycle were explicitly deferred until the 10.10 cycle.
"2. The conclusions generated from these discussions were first
documented as a Roadmap on the Ubuntu wiki. This provides a
high-level set of goals that the project is striving for.
"3. We then produced a Blueprint for each project and a set of
actions that are assigned to people. The blueprint is what we use
to track progress on the project. The actions are stored in the
whiteboard on the blueprint (which anyone can edit) and anyone can
subscribe to the blueprint, which makes it great for keeping on
track projects even if you are not involved in them."