Scooby2beDue Project Plan

Spring Quarter 1996 4/07/96 Document Author: Jason "Jay" Pierce Project Sponsors: GregoryAbowd

Scooby2beDue Team: Jon A. Preston (Manager) Ken Griggs (Architect) Tony Saladino (Programmer) Minh Ho (Programmer) Jason Pierce (Technical Writer/Manager(Jon's absence)

Having a straightforward yet detailed interface will make life much easier than using the old-fashioned paper and pen(cil) method of keeping track of tasks. Providing different color codes will also help one notice which tasks are the more urgent or more leisurely. Also using editable/updateable windows is much more effective than trying to keep track of postponed or backlogged events on several sheets of paper which may require more than one entry for the same task.

Using a platform independent langauge/envrionment also has several advantages. There is the security of knowing that you can go anywhere that as internet access and get to your planner. Therefore, you do not have to worry about forgetting it. Obviously, some places may not have internet access but in these times most significant companies and schools do. There also is no problem getting to the same data if you run one platform at home but your employer runs a different platform.

Project Schedule

Activities description

Status Meetings/Demo Prep (15 hours)

We will be having group meetings with our project sponsor for status upadates and to prepare for our demos. All members are required to be at these meetings. These meetings will be to coordinate the team memebers end and to prepare for our demos.

Roles:

Architect (3 hrs.), Programmers (6 hrs.), Manager (3 hrs.), Writer (3 hrs.)

Project Plan Development (19 hours)

We will have one meeting to outline the project plan. The manager and the tech writer will convert the outline to html in accordance with the template provided by Professor Abowd. These two will also meet during the quarter to revise the project plan.

Roles:

Architect (6 hrs.), Manager (6.5 hrs.), Writer (6.5 hrs.)

Design (22 hours)

The architect will be doing most of the design while coordinating with the manager and the programmers. The majority of the designing will take place during the fourth week. There will be little or no designing after the sixth week.

Roles:

Architect (18 hrs.), Programmers (8 hrs.), Manager (2 hrs.), Writer (0 hrs.)

Notebook (18 hours)

Throughout the quarter the tech writer will be building the project notebook. This development will stem from meetings with the manager.

Roles:

Architect (0 hrs.), Programmers (0 hrs.), Manager (4.5 hrs.), Writer (13.5 hrs.)

Requirements (18 hours)

During the 3rd through 6th weeks we will be determining all the requirements for this project. The production of the requirements document will be primarily up to the manager and tech writer communicating with the architect.

Roles:

Architect (7 hrs.), Programmers (0 hrs.), Manager (7 hrs.), Writer (4 hrs.)

Training (73 hours)

We will be developing the prototype using the Java programming language. All members of the team will be engaged in this activity. The programmer and architect will spend the most time gathering tutorial materials and going through exercises to build up their experience. We will then have a group training session on Java for the benefit of the remaining project team members. (I borrowed most of this description from the template because it was pretty much in line with our project)

Roles:

Architect (20 hrs.), Programmers (40 hrs.), Manager (5 hrs.), Writer (8 hrs.)

Integration (20 hours)

Integration and interface testing of seperately-written code. Does not include final system test.

Roles:

Architect (10 hrs.), Programmers (10 hrs.), Manager (0 hrs.), Writer (0 hrs.)

Debugging (40 hours)

Debugging will be an ongoing process, but the official stage will be a cooperative effort between all the members to find and solve problems with the program. The manager and writer will help perform system test while the architect and the programmers will perform system and unit test and cooperatively find solutions to the problems that are found.

Roles:

Architect (10 hrs.), Programmers (20 hrs.), Manager (5 hrs.), Writer (5 hrs.)

Learn Html (11 hours)

The memebers operating as the writer and manager need to focus on learning html primarily. These two are the ones who will be responsible for creating and editing most if not all of the teams web pages. The other members are familiar enough with html so that only an hour of html refreshing will allow them to help edit our various web pages.

Roles:

Architect (1 hrs.), Programmers (1 hrs.), Manager (4 hrs.), Writer (4 hrs.)

Coding (125 hours)

During weeks 3 through 8, we will be coding our program. The programmers will do most of the coding but the architect will also help out and serve as liason between them and the rest of the team to keep documentation up to speed with actual progress.

Roles:

Architect (45 hrs.), Programmers (80 hrs.), Manager (0 hrs.), Writer (0 hrs.)

Organizational Meetings (27 hours)

This is one of the manager's major responsibilities. These meetings will be coordinated by him. This will be the time when all the members get up to speed with what the others are doing. There will also be one on one time for the manager to speak directly with the individual members of the team.

Roles:

Architect (5 hrs.), Programmers (10 hrs.), Manager (7 hrs.), Writer (5 hrs.)

Html Generation (37 hours)

This will be one of the writer's major responsibilities. He will be responsible for taking everything we have on paper and converting to html. He also will be the one primarily responsible for editing the html we have.

Roles:

Architect (0 hrs.), Programmers (0 hrs.), Manager (7 hrs.), Writer (30 hrs.)