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: Friday, 2011/02/18 (YYYY/MM/DD)
  • Time: 10PM, UTC±0

Meeting type

Twice-weekly Scrum meeting.

Meeting place


Meeting goals

  • Report back progress
  • Raise awareness for impediments

Meeting guidelines

  • Strict 30 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

  • Start time: 10PM UTC
  • Roll call (2.5 minutes)
  • Note about Trac login issues (2.5 minutes)
  • Progress & impediment reporting (25 minutes)
  • End time: 10:30PM UTC


  • Chair: barra
  • Scribe: no scribe; every department tracifies their tasks
  • Attending developers:
    • Beliar
    • KB1PKL
    • qubodup
    • Q_x
    • rowanas
    • Technomage
  • Missing developers:
    • aspidites


Progress report



  • As there are currently no UI & mechanics tasks to tackle within the sprint, q_x, qubodup & rowanas will team up and create additional (non-sprint-related) mockups for GUI screens like dialog and/or barter interface


  • Technomage closed #306 & #307 and created a follow-up ticket: #313
  • #313 deals with attaching character statistics to characters
  • Beliar will support technomage in that field
  • Beliar also wrote skeleton functions for #305; as soon as the skeleton functions are complete, they will be commited into SVN so the other programmers can take a look and provide feedback on the planned API; however the code shouldn't be commited before it's ensured that it doesn't break running PARPG
  • KB1PKL has taken a look into aspidites' object XML generator GUI:
  • KB1PKL will use these files as starting point, further tweak them and bring them into our SVN trunk
  • While aspidites wasn't around today, the other programmers provided feedback on the directory restructuring task:
  • The other programmers reviewed aspidites' proposed changes, agreed with them and encourage aspidites to move forward with implementing them

Identified impediments

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