Preliminary Project Plan

Project Plan

NOTE: The bew deadline for this plan is 11.3.

This is a template of a preliminary project plan. You are not required to plan how the features are technically implemented. The purpose of this document is more on time management and deciding what kind of practices your group is going to use. Technical knowledge about the project, however, might help to estimate your employment of time. You will also have to decide what are features you are going to implement and how those features are assigned for group members.

You can use this HTML template if you like but your deliverable can also be a plain txt document.

1. Introduction and goals

1.1 Project group

Present the actual project group; the members and their contact information.

1.2 Personal goals

What are your own goals for the project (e.g. What would you like to learn and how much time you are are willing to use for the project)?

1.2 Scope of project

What features you are going to implement (select from your personal list - not freely from all the features)? How different tasks are divided between group members. There should be one corresponding author for each feature you are going to implement.

If you you have a great idea about a feature that is not listed, you can also apply personal topics. In that case you should contact Petri Ihantola.

2. Schedule

How you are going to divide your time during the project?

Week Tasks Total Effort estimation Effort of member 1 Effort of member 2 Effort of member 3
9-10 Project planning        
? design meeting        
11.3. (NEW!) DL: Project plan        
10-13 First iteration        
? task 1        
... ... ... ... ... ...
? task n        
3.4. DL: First submission        
14-17 Second iteration        
? task 1        
... ... ... ... ... ...
? task n        
28.4. DL: Final submission        

3. Team work and practices

You are required to use cvs during the project, but there are still many other practices you can decide to use or not.

3.1 Time management control

How you are going to measure and control your time management?

3.2 Meetings and communication

How you are going to arrange your team work? How you are going to communicate (e.g. face to face meetings, email, irc)? How you are going to record common decisions of your group?

3.3 Testing and bug reporting

How you are going arrange testing and how you are going to keep track about possible bugs?

3.4 Other

What other things are relevant for your team work? For example, you might have some coding standards to follow.

Appendix 1:Examples from different types of tasks

Following examples of different types of tasks might help you to realize that there are many other things than coding that will also take time.

Work type Explanation
Design Technical design, e.g., reading  use cases or design documentation. Designing and documenting architecture.
Testing Executing system tests and reporting found bugs.
Infrastructure Installing, configuring and maintaining tools for the project. Problems with the tools.
Project management Project planning, tracking and control. Iteration planning. Defining work practices.
Studying Learning new project related issues (e.g. tools, technologies, standards, topic's domain).
Meetings General status/planning meetings.
Programming Creating, modifying, debugging, unit testing and commenting code. Low-level design done while writing code.
Pair programming Time spent as a partner in pair programming session.