Objective Statement

To create Drupal forms that enable all staff to generate standardized individual profile webpages, and to provide accompanying help documentation, training, and feedback mechanisms by January 28, 2008.

Milestones

12/20/07 - final draft of designs

12/20/07 - module exploration complete; meeting to discuss findings and detail plan remaining stages

1/21/08 - staging complete

1/25/08 - live version complete

1/28/08 - staff training and help documentation complete

2/12/08 - final summary report complete

Work Breakdown Structure 

Tasks ordered by phase

MS Project file

 Issues log

 Enter issues that delay tasks here.  Delayed tasks on the critical path will push out the final deadline.

Resources 

Project Team:

• Anne Marie Deitering - 4 hrs/week
• Margaret Mellinger - 4 hrs/week
• Susan McEvoy - 12 hrs/week

 I'm not sure if these numbers reflect reality so we should try and track this for more accurate planning in the future.

Constraint Matrix

• Scope is most constrained because the resulting pages will not be usable if they are missing information
• Resources is moderately constrained because we have other work to do, but could ask about postponing other projects if needed to get the work done by schedule deadline.
• Schedule is least constrained. We will push out the scheduled deadline if we run into unforseen problems and can't find more time to dedicate to the project.

(This is what we talked about, but I actually think our resources are most constrained and scope isn't so much.  We already talked about saving the Subject discussion for later, so that's an example of cutting scope.  But Resources is more constrained  because we have to work around so much time away (xmas break, ala, other meetings)

Deliverables

1. A checklist indicating all profiles are complete
2. Summary document including feedback from staff on content entry processes.

Planning Horizon and Approach

Much of Drupal is new to us. We have an idea of which modules we need to use, but haven't fully explored their implementation, and so don't have a good idea of how long that part will take.
Accordingly, we will detail plan the design, testing, help and training stage, and the data collection/summary stage, but only phase plan the module exploration and staging phase with large estimates of time.  After we complete the module exploration phase, we will have another meeting to detail plan the rest of the stages.

Team Policies and Procedures

• Progress and deadline changes will be noted on this wiki page.
• Issues will be recorded in an issues log, linked to this wiki page.
• Task owners will email Susan when tasks are complete so that she can update and track the plan in Microsoft Project.
• Work done in Drupal (modules, configurations, etc) will be documented for future reference.  The type of documentation will be decided on at a later meeting.

Content Migration

 The following people have content in their staff directories:

• Bonnie Avery
• May Chau - all these seem like they could be easily uploaded
• Jeanne Davidson - I'm wondering if someone might want this content...
• Valery King - easily uploadable (1 file has a template that needs removed
• Paula McMillen - delete?
• Cheryl Middleton
• JoLynn (1 web form)