Firefox OS/Comms/Dialer/Standup Guidelines: Difference between revisions

From MozillaWiki
< Firefox OS‎ | Comms‎ | Dialer
Jump to navigation Jump to search
Line 4: Line 4:
# If you're not available for a standup that you're scheduled to host, then ask for someone else to host instead for just that time.
# If you're not available for a standup that you're scheduled to host, then ask for someone else to host instead for just that time.
# Start by pinging everyone who should be participating.
# Start by pinging everyone who should be participating.
# List with any administrative items you have, and then ask for more from other people (look at the Etherpad).
# List any administrative items you have, and then ask for more from other people (look at the Etherpad).
# Move to individual updates. Go alphabetically, in descending order.
# Move to individual updates. Go alphabetically, in descending order.
# If someone's update is taking longer than 3-4 minutes, you should generally cut them off and ask them to talk about it after the standup.
# If someone's update is taking longer than 3-4 minutes, you should generally cut them off and ask them to talk about it after the standup.

Revision as of 14:00, 12 August 2014

Hosting the Standup

  • Current hosts: drs, gtorodelvalle, Rik, thills
  • Hosts rotate every week.
  1. If you're not available for a standup that you're scheduled to host, then ask for someone else to host instead for just that time.
  2. Start by pinging everyone who should be participating.
  3. List any administrative items you have, and then ask for more from other people (look at the Etherpad).
  4. Move to individual updates. Go alphabetically, in descending order.
  5. If someone's update is taking longer than 3-4 minutes, you should generally cut them off and ask them to talk about it after the standup.
  6. Copy the reports from the standup Etherpad to the wiki page for that day. Use the Etherpad-to-Wiki converter to format it. You can just copy and paste the whole thing and the converter will do everything for you.
  7. Update the burndown chart for the day. Use the Burndown chart generator to format it.
    • In the total cost, exclude bugs with "c=" and no number. Treat anything without any "c=" or number as 1 point. Ignore anything not assigned to someone on the team.
    • You will then have to download the image, then upload it in place of this sprint's burndown chart image. For example, the chart for sprint v2.1-S2 is at [1].
    • You should also update the burndown values to help the next host continue generating it.
  8. Ask the person who should be hosting the week after you if they'll be available. If not, move onto the next person.