From Post-Apocalyptic RPG wiki

Jump to: navigation, search

Sprint meeting.png This article covers a twice-weekly Scrum meeting!

Twice-weekly Scrum meetings take place at our sprint IRC channel. They're utilized to report back progress and raise awareness for impediments that are slowing the team down. Sprint team members who can't attend the twice-weekly Scrum meetings have to hand in their progress and impediment report at the sprint boards of the forums instead.

This template can be used for all twice-weekly Scrum meetings.



Timeslot for the meeting:

  • Date: Tuesday, 2011/02/08
  • Time: 22:00 (10PM), UTC±0

Meeting type

Twice-weekly scrum meeting.

Meeting place


Meeting goals

  • Report back progress
  • Raise awareness for impediments
  • Discuss task distribution among the sprint team devs (we'll make an exception in this case as it's our first twice-weekly Scrum meeting and we didn't have the time to talk things through in that regard in the sprint prioritization & planning meeting)

Meeting guidelines

  • Strict 45 minutes timebox
  • No problem solving during the meeting
  • The chair moderates the meeting
  • Speakers use the <end> tag to indicate that they've given their report to speed up the meeting
  • Missing sprint developers give their progress and impediment report at the sprint boards of the forums

Meeting timeline

  • 22:00, UTC±0: meeting starts
  • Roll call (5 minutes)
  • Progress & impediment reporting (20 minutes)
  • Task distribution discussion (20 minutes)


  • Chair: barra
  • Scribe: each department tracifies their specific tasks
  • Attending developers:
    • Beliar
    • Qubodup
    • Qx
    • Technomage
    • zenbitz
  • Missing developers:
    • KB1PKL
    • rowanas
    • Taldor


Progress report



  • Graphics for tickets #297, #303, #304 are currently in the making and are planned to be available until Friday


  • Works on most sprint related mechanics has been started
  • Zenbitz will be out of town for a week, starting at Sunday, 13th of February
  • He encouraged the other developers to move forward with implementing mechanics even while he's not around



Task distribution

  • Tasks are properly distributed and enough tasks are left to tackle to keep us busy until the next meeting at Friday

Parking lot

The parking lot is used for topics that can't be explored within the meeting due the meeting's time limit. These topics will be added to the parking lot. The sprint team will briefly discuss the parking lot items after the meeting has officially ended and volunteers for each parking lot item have to be identified to ensure that these tasks are actually tackled until the next meeting:

Meeting logs

Personal tools