MDN/Development/Process: Difference between revisions

We work in two week periods called <em>Sprints</em>. A Sprint starts with a Sprint Planning Meeting (see the section [[MDN/Development/Process#Planning_and_retrospective_meeting|Planning and retrospective meeting]]) and ends one day before the next Sprint Planning Meeting.

During each Sprint, we work on a subset of features (see the section [[MDN/Development/Process#Sprint_Backlogs|Sprint Backlogs) that we committed to in the Sprint Planning Meeting.

The <em>Product Backlog</em> is a large list of features that we plan build, prioritized by a combination of thoughts from the development team, feedback from users, and strategic planning. Priorities are re-evaluated according to these criteria before each Sprint.

Our Product Backlog is very large and somewhat difficult to understand right now, but we are planning to reorganize it to make it more understandable to people outside of the development team.

=== Organization ===

At times, features in the Product Backlog can become broad and vague. To avoid this, John will break features into smaller actions when necessary. For example, he might open subtasks like "Create a mockup for this feature" or "Research how we should implement this portion of the feature."

At each Sprint Planning Meeting, we consider the highest priority features on the product backlog and decide which ones we should complete during the upcoming Sprint. We capture these features in a list called the <em>Sprint Backlog</em>. Each Sprint has its own Sprint Backlog.

During this part of the meeting, we discuss what about our process has been working well, and what about our process could use improvement. We update this page based on this discussion.