Program Management/Sprint Guide

Overview

Let's come up with a set of common things between projects and iterative approach to how we make software. In software development, we often fall into design patterns like MVC. Why not consider a design pattern for how we build software?

Why?

How can we ship software with less chaos? How can we organize to maximize efficiency. How can we make planning slightly more predictive? How can we iterate and change course more quickly? How can Product craft a better feature set?

Outcomes

• Product wants to build a product that can adapt and meet a change market.

Events and Actions

• Sprint Planning Meeting: to define and prioritize the high level goal and backlog
  • All tasks in Bugzilla with rank, iteration, whiteboard themes, and priority
• Devs pick up tasks and update bugs in preferably the order of task rank (what makes sense).
• Devs have a midpoint check in on status, Devs can choose frequency of standups
  • Stand ups are streamlined meetings where each person provides status on what they worked on yesterday, today, and if blocked. Any questions or blockers should have a quick break out session after.
• Sprint Review: Review what was 'done' for the sprint, demos, and retrospective (what went well and not so well).