Confirmed users
1,193
edits
MDN/Development/Process: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 51: | Line 51: | ||
Available at: [http://standu.ps/project/mdndev Standups] | Available at: [http://standu.ps/project/mdndev Standups] | ||
The team tracks its progress throughout each Sprint. Each team member shares a status update occasionally as important work is completed. If a member of the team is having a hard time making progress on a task, he or she can add the tag <code>#blocked</code> to his status report to request help from the | The team tracks its progress throughout each Sprint. Each team member shares a status update occasionally as important work is completed. If a member of the team is having a hard time making progress on a task, he or she can add the tag <code>#blocked</code> to his status report to request help from the Scrum Master. | ||
== Meetings == | == Meetings == | ||
| Line 63: | Line 63: | ||
In the first part of the meeting, the team discusses aspects of its process that have been working well and aspects of the process that could use improvement. | In the first part of the meeting, the team discusses aspects of its process that have been working well and aspects of the process that could use improvement. | ||
All thoughts shared in the Retrospective are reflected on this page. The | All thoughts shared in the Retrospective are reflected on this page. The Scrum Master treats this page like a Developer Bill of Rights, and works to ensure that the policies written here are enforced. | ||
==== Planning ==== | ==== Planning ==== | ||
| Line 85: | Line 85: | ||
=== PTO === | === PTO === | ||
Team members notify the Scrum | 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. | ||