Confirmed users
1,193
edits
MDN/Development/Process: Difference between revisions
Jump to navigation
Jump to search
→Working
| Line 82: | Line 82: | ||
The team occasionally encounters minor annoyances that affect their development work, such as receiving an overwhelming amount of error report emails. These problems are usually not serious on their own, but they can become more serious as they pile up. To manage this, each team member opens a Bugzilla bug with the keyword [dev-papercut] in the Status Whiteboard. At each planning meeting, the team considers a list of [http://mzl.la/UeVyMo ignored papercuts] when building the Sprint Backlog. | The team occasionally encounters minor annoyances that affect their development work, such as receiving an overwhelming amount of error report emails. These problems are usually not serious on their own, but they can become more serious as they pile up. To manage this, each team member opens a Bugzilla bug with the keyword [dev-papercut] in the Status Whiteboard. At each planning meeting, the team considers a list of [http://mzl.la/UeVyMo ignored papercuts] when building the Sprint Backlog. | ||
=== PTO === | |||
Team members notify the Scrum master when they file PTO, so that he can help the team prepare accordingly. | |||
== Updating the MDN == | == Updating the MDN == | ||
Throughout the Sprint, the team occasionally pushes new changes to our production server. The team does this about once per week, usually on Tuesdays or Thursdays. Pushes on Monday and Friday are avoided. | Throughout the Sprint, the team occasionally pushes new changes to our production server. The team does this about once per week, usually on Tuesdays or Thursdays. Pushes on Monday and Friday are avoided. | ||