Release Management/2014 Q1 Work Week/B2G Release Owner Notes

Responsibilities as a B2G Release Manager Why do we need this ?

• Clear ownership, leadership
• Division of responsibility
• Having a POC per release helps ease comminications with other teams as well

Things you'd be responsible for :

• Drive a release end-end and majorly until RTP (Release To Partner)
  • i.e we'd be alternating every 12 weeks on the following
• Drivers meeting on Monday, B2G cross-functional meeting
  • Apparently the drivers meeting need not be tied to a release but we will alternate and try this out irrespective of who is owning the release and once the product is more matured we could sync-it up per release as needed
  • Will need to try this out. Get Sheila's input as well. So not an agreed upon plan.
• Driving QC bugs
• Be an active POC for other teams that may need input
• You would be driving the decision on if a feature looks good, needs backouts etc
• Making Release notes
• Retrospective (post-mortem)

While you are not doing a major release :

• Help with approvals that come across
• Help stabilize the remaining pieces post RTP
• Help with at least one triage of the three
• Making sure the the security approvals/landings are taken care
• Work on goals, general improvements to RM processes & tools
• Work on "general" category bugs
• Blog

Between EPM/Relman :

• Owning the comms piece
• Feature walk through - EPM