Encourage Team Roadmaps and Planning

Registered by Jono Bacon on 2009-11-09

This session discusses how to encourage teams to build per-cycle roadmaps to better coordinate work.

Blueprint information

Status:
Complete
Approver:
Jono Bacon
Priority:
High
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Informational Informational
Milestone target:
None
Completed by
Jono Bacon on 2009-11-16

Related branches

Sprints

Whiteboard

Gobby notes from UDS-L:

Problems:
- Need to document decisions, especially UDS ones
- Often a lot of commitment but no actual production

Project Roadmaps:
wiki.ubuntu.com/Roadmaps
 - We all hate bureaucracy, todo lists, many forms of planning
 - Teams can make roadmaps (eg ubuntu-uk-loco-team)

Example: wiki.ubuntu.com/Roadmaps/Lucid/LocoDirectory

Structure:
 * Objective: Overall goal you're trying to accomplish (eg "make better")
 * Success criteria: Be as specific as possible (binary yes/no)
 * Actions: A list. Get specific volunteers to do specific things, name them, link to launchpad bugs (and use assignment on them)
 * Blueprint: Have a launchpad blueprint for your roadmap.
   - Project Management 101 shows that writing things down after people agree to them makes it much more likely to actually happen.
   - When the success criteria are done you can also mark the blueprint as implemented, then we have an automated list of all successful roadmaps.
   - Can also use blueprint whiteboard to track progress.
   - Everyone involved can subscribe to the blueprint (it'll inform them when whiteboard is updated too).
 * Driver: Someone specific to manage the blueprint

Only include things you're committing to in the cycle!

This process helps focus things on the particular cycle (perhaps limiting it).

TODO:
 * (./) Need to update the roadmaps wiki page to explain the blueprints usage - Scott Ritchie.
 * Explain and document how to have observers keep up to date with blueprints - Jono Bacon.
 * Explain on Roadmap wiki page how to manage progress and evaluation note that teams should have a launchpad project - Jono Bacon.
 * Mention Roadmaps elsewhere - membership applications and team approval applications - Jono Bacon.

Italian experience of a previous use of blueprint for marketing activities
https://blueprints.edge.launchpad.net/ubuntu-it/+spec/promozione-goal

The Launchpad team wants help with making things easy for nontechnical users. We're not just about bazaar branches and bug tracking!

(?)

Work Items