Skip to content
Sam Joseph edited this page Jun 26, 2013 · 9 revisions
  • The project is co-ordinated through a number of resources including:

  • Pivotal Tracker is used to co-ordinate tasks, and supports the agile approach of client stories with points, which team members vote on. In addition tasks can be in a number of states: "Started", "Finished", "Delivered", "Accepted" which we use as work is started, and code is eventually deployed and approved by the customer.

  • A Google site was initially set up to replace the EdX wiki pages that were being used to coordinate the project. The Google site offered the advantages of being able to embed videos, provide navigation, and be accessible to individuals without EdX logins. The Google site suffers from a complicated login process for editing.

  • The Google Group (mailing list) provides mailing list functionality which some team members preferred, although the Skype text chat room seems to be the key channel for communication. Skype text chats have some odd properties :-) YouTube playlists are used to created an archive of recordings of all client meetings, team meetings and pair programming sessions.

  • There is also a Google community which is used to register events such as weekly meetings and of course GitHub stores all the project code (and this wiki), while Heroku is used to host the live RoR sites.

  • Responsibility for transcription of meeting notes is rotated through the team members.


Previous (Customer (Voluntary Action Harrow)) ::: Next (Remote Pair Programming Strategy)


Return to Top (Project Overview)