Program Management/ProjectPlanTemplate

From MozillaWiki
< Program Management
Revision as of 20:26, 30 October 2012 by LawrenceMandel (talk | contribs) (Risks)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Project Name

problem statement or why we do this project

Goal

keep the goal statement as simple as possible and include criteria to make it clear when the project will be completed. one way to think of this statement is, what is the benefit of completing this project?

Scope

list items that are both in and out of scope for the project

Duration

estimated project time

Projects

list any sub-projects - depending on complexity you may want to create a project page for each sub-project

Sub-project

at a minimum, a sub-project should have a name and description. it may also include a link to the project page or inline text for a simple sub-project.

Communication

Communication Type Mechanism Audience
Announcements dev-platform and dev-planning lists all
General discussion dev-platform list devs
Meetings meeting time
  • Dial-in: Audio-only conference# conf number
    • People with Mozilla phones or softphones please dial x4000 Conf# conf number
    • US/Toll-free: +1 800 707 2533, (pin 4000) Conf# conf number
    • US/California/Mountain View: +1 650 903 0800, x4000 Conf# conf number
    • US/California/San Francisco: +1 415 762 5700, x4000 Conf# conf number
    • US/Oregon/Portland: +1 971 544 8000, x4000 Conf# conf number
    • CA/British Columbia/Vancouver: +1 778 785 1540, x4000 Conf# conf number
    • CA/Ontario/Toronto: +1 416 848 3114, x4000 Conf# conf number
    • UK/London: +44 (0)207 855 3000, x4000 Conf# conf number
    • FR/Paris: +33 1 84 88 37 37, x4000 Conf# conf number
    • Gmail Chat (requires Flash and the Google Talk plugin): paste +1 650 903 0800 into the Gmail Chat box that doesn't look like it accepts phone numbers
    • SkypeOut is free if you use the 800 number
  • Vidyo: video room
  • IRC: #ircchannel
  • Agenda:
all
Meeting summaries this wiki all

Press & Blog Posts

optional - you may want to capture press, blog posts, etc. about the project

Minutes and Progress Reports

2012
  • minutes go here

People

list required competencies for people and, once defined, the people working on project. note that not all of these competencies will be required for every project

Project Champion
Program Management
Product
UX
Engineering primary devs working on project
Other Engineering subject matter experts contributing to project
Accessibility
Localization
Services
Incoming Bug Triage this may be someone listed elsewhere, the key is to list people who handle triage
QA
Security
Privacy
Releng
Marketing
Legal

Milestones/Iterations/Tasks

high level milestones can be included in this page. more complex milestones and tracking information (typically bug lists) should be included on a milestone specific tracking page

Dependencies

feature, partner, resource, etc.

Risks

list risks in table below. assign a unique risk id to each risk. for ex., the project plan template may define risk ids prefixed with PPT like PPT001.

Risk ID Description
PPT001 Sample risk

References

other references, very useful catch all category for existing links and text when cleaning up existing project pages