MDN/Development/Process: Difference between revisions
< MDN | Development
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== Organization == | |||
* John should break things down GTD-style. Often, we avoid taking on a bug because it's too vague or too big. John should break things down into smaller actions (for example, "Decide on a design", "Research: How will we do XYZ?", etc.) | |||
== Pushing == | == Pushing == | ||
Revision as of 22:19, 5 September 2012
Organization
- John should break things down GTD-style. Often, we avoid taking on a bug because it's too vague or too big. John should break things down into smaller actions (for example, "Decide on a design", "Research: How will we do XYZ?", etc.)
Pushing
- Do not push on Fridays or Mondays.
- We should push about once per week, usually on Tuesdays and/or Thursdays.
Planning
- After determining our actual velocity, we will plan for 2/3 of that. The last 1/3 will consist of things that people find interesting and want to pick up.
- At every planning meeting, we will assign bugs to people. When a person no longer wants to do something, they will unassign themselves from it and try to let others know. Developers will work from the sprint backlog, so if they see anything unassigned they should feel free to take it on.