Program Management/ProjectPlanTemplate/Firefoxdesktop/Templates

Templates

retrospectives

• Goal: This is the teams chance to iterate on the Agile process and give feedback in a supportive environment.
• Frequency: can be weekly or bi-weekly.
• People can bring up where they are struggling and should be encouraged to.
• Invitees: anyone that is significantly engaged in the day to day - PM, UX, Dev, Architects, cross-team partners.
• Flow: For the first 5 minutes of the meeting - have folks independently add information to the retrospectives. This encourages participation from folks that might not talk as much. Then go through starting at the top (folks can add as the meeting goes on as well). Topics can be added throughout the week as they are thought of.
• Length: start with 1/2 hour

Etherpad Template for retrospectives

________________________

Date

• Review experiments from last week:
• Proposed experiment:
• What did we do well?
• What have we learned?
• What can we do better?
• What puzzles us?

cross-team

Goal: With teams that there is heavy interdependence with, this time is to make sure we are on the same page. Frequency: weekly or bi-weekly, depending on frequency of interaction needed. Invitees: depends on who interacts from the teams - good to have the doers and managers. Length: 1/2 hour, but usually aim for starting on time and getting off. If there aren't any agenda items - cancel the meeting before it happens. Etherpad Template for crossteam meetings We meet in _________ vidyo room. Here is the remote access information <room url, telephone number for different areas>

Please add agenda items (if there are any) an hour before the meeting or we may cancel the meeting for that day. Thanks. Even if it's a simple "we need an update on deployment" - that is a fine topic to have a quick meeting on.

postmortems

• Goal: Step back and look at the whole project and what could have been improved. Be sure to include the good along with the areas of improvements.
• Frequency: These don't need to be after every release, but should be every quarter.
• Invitees: anyone that was interacted with significantly over the time period you are looking to review. (UX, QA, Dev, PM, other teams, Marketing). Because of the breadth of invitees, schedule 3-4 weeks out to get a good time. Create the etherpad in advance for folks to pre-populate or at least see the questions in advance.

Etherpad Template for postmortems

• Key Accomplishments
  • What went right?
  • What worked well?
  • What was found to be particularly useful?
  • Project highlight
    • • Lean from the Trenches (spotify videos)

• Key Problem Areas [List problem areas experienced throughout the project. Be specific.]
  • What went wrong?
  • What project processes didn’t work well?
  • What specific processes caused problems?
  • What were the effects of key problems areas (i.e. resources, schedule, coordination, timing, etc.)?
  • Technical challenges

• Risk Management [List project risks that have been mitigated and those that are still outstanding and need to be managed.]
  • Project risks that have been mitigated:
  • Outstanding project risks that need to be managed:
• Next steps: