CourseScheduler
General Policies
Version 1.0
Revision History
Date
Version
Description
Author
2009-09-19
0.01
Initial Draft
Dario Vuljanić
2009-09-30
1.0
Full version
Dario Vuljanić
Doc. No.:
1.
Introduction
1.1
Purpose of this document
The purpose of this document is to explain general policies. Policies about communication and
organization tools used on the CourseScheduler project, document formats and rules for week report
submission are considered to be general policies.
1.2
Document organization
This document is organized as follows:





1.3
Section 1, Introduction, describes this document general info, purpose and contents.
Section 2, Communication policy, describes rules for usage of communication tools.
Section 3, Collaboration policy, describes rules for usage of collaboration tools.
Section 4, Document format policy, describes rules for usage of document formats.
Section 5, Week report policy, describes rules for submission of week reports.
Intended Audience
The intended audience is:
 Team members of the CourseScheduler project.
1.4
Scope
This document includes all the policies considered as general policies. Specific policies, such as SVN
or coding policy, are not the part of this document.
1.5
Definitions and acronyms
1.5.1
Acronyms and abbreviations
Acronym or
abbreviation
MS
SVN
DSD
MoM
Definitions
Microsoft
Subversion
Distributed Software Development
Minutes of Meeting
2.
Communication policy
Team members should communicate using defined primary communication tools, but other tools can
be also used if necessary.
Primary communication tools:
 Skype – primary communication tool for group meetings and synchronous communication
 Google Groups (http://groups.google.hr/group/dsd-coursescheduler) – primary
communication tool for discussions
 Email – primary communication tool for asynchronous communication (please use it rarely)
3.
Collaboration policy
Tools specified in this document must be used for task and document management and for project
collaboration. No secondary tools should be used without previous discussion with team members.
Collaboration tools:
 Google Docs – for sharing documents
 Google Groups (http://groups.google.hr/group/dsd-coursescheduler) – for upload (small files)
 DSD-CourseScheduler Files (http://dsd.poslek.com/) – for upload (large files)
 Google Calendar – for scheduling appointments and milestones
 Taskmind (http://www.taskmind.net) – for task management
 SVN (svn://161.53.67.144/svn/dsd09/coursescheduler) – for code and documents management
 CourseScheduler site (http://www.fer.hr/rasip/dsd/projects/coursescheduler) – for MoMs,
various reports and documentation (only major versions)
4.
Document format policy
Document formats specified in this document must be used for any kind of documentation on the
CourseScheduler project. Working copies of documentation can be in some other document formats.
Document formats:
 MS Office Word 97-2003 Document (.doc) – for text documents
 MS Office Power Point 97-2003 Document (.ppt) – for presentations
 MS Office Excel 97-2003 Document (.xls) – for spreadsheets
5.
Week report policy
Week reports must be submitted every week, no later than Sunday at 23:59 CET. Week reports must be
written using DSD official week report template.
Week reports must be named Week_Report_Name_Surname_wXX, where Name must be replaced with
name of a team member, Surname must be replaced with surname of a team member and XX must be
replaced with the number of the week (example: week report document for week 39 for a team member
John Doe must be named Week_Report_John_Doe_w39).
Week reports must be submitted using SVN and placed into directory prepared for the reports and
named Week XX, where XX stands for the week number (example: week report for week 39 must be
submitted to directory \trunk\Project Documents\Weekly Reports\Week 39).
All team members (including project leader) must submit their week report following the rules in this
document. Team member who doesn’t submit the week report following the rules defined in this
document will not be included in the summary week report for the week when the week report wasn’t
submitted.