Definition of done

From Post-Apocalyptic RPG wiki

Jump to: navigation, search

Ongoing sprint.png This article covers an agile concept!

Agile concepts are currently evaluated by the development team to help us stay focused and make better progress on a more steady basis.

This article covers our definition of done that is applied during sprints. It can be used for the evaluation of sent in patches as well.

Why have a definition of done at all?

Whenever we tackle a user story in a sprint, we have to ask ourselves if we actually implemented this user story so the described feature can considered to be done. Definitions of done are criteria that simply help us to decide if we reached our goal; therefore they are an essential part of the development process.

Sprint DoD

This definition of done applies to sprints:

  • Assets follow the established asset conventions (naming scheme, documented licensing information)
  • Code follows the established coding standards (code style, code documentation, unit testing)
  • Documentation has been either created or updated as necessary
  • The game has been playtested on all targeted operating systems and it doesn't crash
  • Bugs that couldn't be fixed within a sprint have been documented as Trac tickets and moved into the defect backlog after the sprint has ended
  • Installer/packaging scripts for different platforms have been updated
  • The README file has been updated and contains the latest instructions how to install the game
  • The sprint is tagged in SVN and merged back into trunk after that
  • A sprint snapshot has been compiled and uploaded to sourceforge
  • The development blog is updated with information about the sprint and a link to the sprint snapshot

Release DoD

This definition of done applies to releases:

  • Assets follow the established asset conventions (naming scheme, documented licensing information)
  • Code follows the established coding standards (code style, code documentation, unit testing)
  • Documentation has been either created or updated as necessary
  • The game has been playtested on all targeted operating systems and it doesn't crash
  • Bugs that couldn't be fixed within a sprint have been documented as Trac tickets and moved into the defect backlog after the sprint has ended
  • Installer/packaging scripts for different platforms have been updated
  • The README file has been updated and contains the latest instructions how to install the game
  • The release is tagged in SVN
  • Release packages have been compiled and uploaded to sourceforge
  • The development blog is updated with information about the release and a link to the release packages
  • The word about the release is spread at an agreed upon list of websites & forums
Personal tools