MDN/Development/Planning: Difference between revisions

MDN/Development/Planning (view source)

Revision as of 20:43, 7 September 2012

183 bytes added , 7 September 2012

no edit summary

John Karahalis

Confirmed users

1,193

edits

@@ Line 1: / Line 1: @@
-The MDN development team works in two week periods called <em>Sprints</em>. At the beginning of each Sprint, we decide on a handful of features to work on and add those features to a <em>Sprint Backlog</em>.
+The MDN development team works in two week periods called <em>Sprints</em>. At the start of each Sprint, we decide on a number of features that we will work on during the Sprint and capture this information in a list called the <em>Sprint Backlog</em>. After the Sprint ends, we meet again to start the process from the top and build a new Sprint Backlog.
 To learn more about our process, please see the [[MDN/Development/Process|Process page]].
@@ Line 19: / Line 19: @@
 == What will we work on next? ==
-When our current Sprint ends, we will meet again to build a new Sprint backlog based on our priorities, which are determined by a combination of thoughts from the development team, feedback from users, and strategic planning. Our priorities are reflected in our [http://is.gd/346lcK product backlog].
+After the current Sprint ends, we will meet again to build a new Sprint Backlog based on our priorities, which are determined by a combination of thoughts from the development team, feedback from users, and strategic planning. These priorities are reflected in our [http://is.gd/346lcK Product Backlog], our running list of possible features.
-Please keep in mind that while our product backlog is currently very large and at times difficult to understand, we plan to reorganize it soon to make it more understandable to outsiders.
+To learn more about our process, please see the [[MDN/Development/Process|Process page]].
-To learn more about our process, please see the [[MDN/Development/Process|Process page]].
+Our product backlog is currently very large and sometimes difficult to read. We plan to soon reorganize it to make it more understandable to people outside of the development team.
 == What have we worked on in the past? ==