[Australian Team] [1.0] Roadmap
Building Your Roadmap
Each goal in the roadmap has a set structure which you should stick to. This is how it works:
Objective' - An Objective is a goal that you want to achieve. Summarize your objective here in one sentence (e.g. 'Exhibit Ubuntu at OSCON' and 'Create Lucid Marketing Materials').
Success Criteria - This is a statement that can be clearly read to determine success on the above 'Objective'. This needs to be as clear as possible and not vague: it will indicate if you achieved the 'Objective' (e.g. 'A successful exhibition at OSCON' and 'Lucid website buttons, banner ads and wallpaper provided for LoCo Teams').
DATE - This is a DATE that the plan needs to be acted on for the 'objective' to be achieved
Actions - This is a set of steps that need to be executed to achieve the 'Objective'. It is recommended that if someone volunteers to commit to delivering on an action, you put it in brackets (e.g. 'Print out LoCo logo on a banner (Jono Bacon)'). There can be multiple actions for each Objective.
Blueprint (optional) - It is recommended to use a launchpad blueprint for your objective. Launchpad isn't just for developers, but is also great for community tasks.
Driver (optional) - If someone is coordinating this objective and helping those involved to deliver on their actions, list that person here. If you're using a blueprint it's especially convenient to mark the driver as the Drafter and Assignee of the launchpad blueprint.
Tracking Progress
Here are some tips on tracking progress on your roadmap:
- Review it at meetings - your roadmap should be an agenda item at every meeting your team has. Review progress, identify problems, ensure everyone is clear on what they are doing and unblock blockers.
- Review mid-cycle - it could be useful to review progress on the roadmap halfway through the cycle in detail.
- Evaluate at the end of a cycle - when the cycle is complete, review the roadmap and see how much the team achieved.
Roadmap
UBUNTU-AU
OBJECTIVE: Team building
SUCCESS CRITERIA:
ACTIONS:
Read Team building to get some ideas
- Item.
BLUEPRINT: <link>
DRIVER:
As there are are many REGIONS and existing LUGS across Australia, each State should co-ordinate activities/objectives on a local level.
QLD
OBJECTIVE: Organise a LUCID release party
SUCCESS CRITERIA: A Date & Venue is set and people RSVP to attend.
DATE: 11th April 2010
ACTIONS:
Organise a Date & Venue
- - 8th May @ Breakfast Creek Hotel
- Publicise the event
- Take bookings
BLUEPRINT: <link>
DRIVER: AndrewGaydon
OBJECTIVE: Create a Wiki for ubuntu-au-bne loco group
SUCCESS CRITERIA: A working wiki
DATE: FEB 28th
ACTIONS:
- Item.
- Item.
- Item.
BLUEPRINT: Ubuntu-au-bne
DRIVER: AndrewGaydon
OBJECTIVE:
SUCCESS CRITERIA:
* DATE:
ACTIONS:
- Item.
- Item.
- Item.
BLUEPRINT: <link>
DRIVER:
NSW
OBJECTIVE:
SUCCESS CRITERIA:
* DATE:
ACTIONS:
- Item.
- Item.
- Item.
BLUEPRINT: <link>
DRIVER:
ACT
OBJECTIVE:
SUCCESS CRITERIA:
DATE:
ACTIONS:
- Item.
- Item.
- Item.
BLUEPRINT: <link>
DRIVER:
VIC
OBJECTIVE:
SUCCESS CRITERIA:
DATE:
ACTIONS:
- Item.
- Item.
- Item.
BLUEPRINT: <link>
DRIVER:
TAS
OBJECTIVE:
SUCCESS CRITERIA:
DATE:
ACTIONS:
- Item.
- Item.
- Item.
BLUEPRINT: <link>
DRIVER:
SA
OBJECTIVE: Organise a LUCID release party
SUCCESS CRITERIA: A Date & Venue is set (drop in event).
DATE: Date of LUCID release.
ACTIONS:
- Item. Email announcement to LinuxSA list and Ubuntu-UA
- Item. Update LUCID release party page.
- Item. Go to Party.
BLUEPRINT: TBD (Use previous party as example.)
DRIVER: PaulSchulz (and BillThePenguin)
WA
OBJECTIVE:
SUCCESS CRITERIA:
DATE:
ACTIONS:
- Item.
- Item.
- Item.
BLUEPRINT: <link>
DRIVER:
NT
OBJECTIVE:
SUCCESS CRITERIA:
DATE:
ACTIONS:
- Item.
- Item.
- Item.
BLUEPRINT: <link>
DRIVER: