| ID | Task Name | Duration | Start | Finish | Resource Names | % Complete |
| 1 | Scope | 1.38 days | Thu 1/31/02 | Fri 2/1/02 | | 100% |
| 2 | Secure project sponsorship | 2.5 hrs | Thu 1/31/02 | Thu 1/31/02 | Client,Team | 100% |
| 3 | Analyze client needs | 4 hrs | Thu 1/31/02 | Thu 1/31/02 | Team | 100% |
| 4 | Determine project scope | 120 mins | Thu 1/31/02 | Fri 2/1/02 | Team | 100% |
| 5 | Define preliminary resources | 150 mins | Fri 2/1/02 | Fri 2/1/02 | Team | 100% |
| 6 | Prepare Class Presentation | 2 hrs | Fri 2/1/02 | Fri 2/1/02 | Team | 100% |
| 7 | Analysis/Software Requirements | 14.02 days | Sat 2/2/02 | Wed 2/20/02 | | 100% |
| 8 | Conduct needs analysis | 1 hr | Sat 2/2/02 | Sat 2/2/02 | Team | 100% |
| 9 | Draft preliminary software specifications | 1 hr | Sat 2/2/02 | Sat 2/2/02 | Team | 100% |
| 10 | Review software specifications with team | 1 hr | Sat 2/2/02 | Sat 2/2/02 | Team | 100% |
| 11 | Finalize class presentation | 30 mins | Sat 2/2/02 | Sat 2/2/02 | Team | 100% |
| 12 | Develop delivery timeline | 45 mins | Sat 2/2/02 | Sat 2/2/02 | Team | 100% |
| 13 | Present project to class | 10 mins | Tue 2/5/02 | Tue 2/5/02 | Team,Class,Instructor | 100% |
| 14 | Incorporate feedback on software specifications | 10 mins | Tue 2/5/02 | Tue 2/5/02 | Class,Instructor | 100% |
| 15 | Obtain approvals to proceed (concept, timeline) | 1 hr | Tue 2/5/02 | Tue 2/5/02 | Client,Instructor | 100% |
| 16 | Setup future client meetings | 0.5 days | Wed 2/6/02 | Wed 2/6/02 | Team,Client | 100% |
| 17 | Formulate rationales and requirements | 3 days | Wed 2/6/02 | Mon 2/11/02 | Team | 100% |
| 18 | Attend class meeting | 3 hrs | Tue 2/12/02 | Tue 2/12/02 | Team,Class,Instructor | 100% |
| 19 | Refine Rationales and Requirements | 3 days | Thu 2/14/02 | Sat 2/16/02 | Team | 100% |
| 20 | Prepare Formal report and class presentation | 4 hrs | Mon 2/18/02 | Mon 2/18/02 | Team | 100% |
| 21 | Present Requirements to class | 10 mins | Tue 2/19/02 | Tue 2/19/02 | Team,Class,Instructor | 100% |
| 22 | Setup meeting with client | 1 day | Tue 2/19/02 | Wed 2/20/02 | Team,Client | 100% |
| 23 | Design | 22.02 days | Wed 2/20/02 | Tue 3/19/02 | | 100% |
| 24 | Review preliminary software specifications | 2 hrs | Wed 2/20/02 | Wed 2/20/02 | Team | 100% |
| 25 | Develop functional specifications | 1 hr | Wed 2/20/02 | Wed 2/20/02 | Team | 100% |
| 26 | Develop prototype based on functional specifications | 3 days | Thu 2/21/02 | Sat 2/23/02 | Team | 100% |
| 27 | Review functional specifications | 1 day | Sun 2/24/02 | Sun 2/24/02 | Team | 100% |
| 28 | Incorporate feedback into functional specifications | 2 hrs | Mon 2/25/02 | Mon 2/25/02 | Team | 100% |
| 29 | Prepare Mid-Term client presentations | 2 hrs | Mon 2/25/02 | Mon 2/25/02 | Team | 100% |
| 30 | Mid-Term client presentations and client feedback | 1 day | Wed 3/13/02 | Wed 3/13/02 | Team,Client | 100% |
| 31 | Prepare final design documentations | 2 days | Thu 3/14/02 | Fri 3/15/02 | Team | 100% |
| 32 | Prepare System Design class presentation | 2 days | Sat 3/16/02 | Mon 3/18/02 | Team | 100% |
| 33 | Present System Design to class | 15 mins | Tue 3/19/02 | Tue 3/19/02 | Team,Class,Instructor | 100% |
| 34 | Obtain approval to proceed | 3.3 mins | Tue 3/19/02 | Tue 3/19/02 | Instructor,Team,Client | 100% |
| 35 | Development | 13.5 days | Wed 3/20/02 | Sat 4/6/02 | | 100% |
| 36 | Review functional specifications | 1 day | Wed 3/20/02 | Wed 3/20/02 | Team | 100% |
| 37 | Identify design parameters | 1 day | Thu 3/21/02 | Thu 3/21/02 | Team | 100% |
| 38 | Develop code | 11 days | Fri 3/22/02 | Fri 4/5/02 | Team | 100% |
| 39 | Developer testing | 4 hrs | Sat 4/6/02 | Sat 4/6/02 | Team | 100% |
| 40 | Testing | 7.03 days | Sun 4/7/02 | Tue 4/16/02 | | 100% |
| 41 | Develop test plans using product specifications | 3 hrs | Sun 4/7/02 | Sun 4/7/02 | Team | 100% |
| 42 | Develop integration test plans using product specifications | 3 hrs | Sun 4/7/02 | Sun 4/7/02 | Team | 100% |
| 43 | Modify code | 4 hrs | Mon 4/8/02 | Mon 4/8/02 | Team | 100% |
| 44 | Re-Test modified code | 2 hrs | Mon 4/8/02 | Mon 4/8/02 | Team | 100% |
| 45 | Integration Testing | 4.03 days | Wed 4/10/02 | Tue 4/16/02 | | 100% |
| 46 | Test integration | 2 hrs | Wed 4/10/02 | Wed 4/10/02 | Team | 100% |
| 47 | Modify code | 2 days | Wed 4/10/02 | Fri 4/12/02 | Team | 100% |
| 48 | Re-test modified code | 1 day | Fri 4/12/02 | Mon 4/15/02 | Team | 100% |
| 49 | Prepare Prototype presentation | 2 hrs | Mon 4/15/02 | Mon 4/15/02 | Team | 100% |
| 50 | Present Prototype to class | 15 mins | Tue 4/16/02 | Tue 4/16/02 | Team,Class,Instructor | 100% |
| 51 | Training | 0.38 days | Wed 4/17/02 | Wed 4/17/02 | | 100% |
| 52 | Develop training materials | 3 hrs | Wed 4/17/02 | Wed 4/17/02 | Team | 100% |
| 53 | Documentation | 0.25 days | Wed 4/17/02 | Wed 4/17/02 | | 100% |
| 54 | Develop user manuals | 2 hrs | Wed 4/17/02 | Wed 4/17/02 | Team | 100% |
| 55 | Pilot | 3.63 days | Thu 4/18/02 | Tue 4/23/02 | | 100% |
| 56 | Install/deploy software | 2 hrs | Thu 4/18/02 | Thu 4/18/02 | Team | 100% |
| 57 | Final client presentations | 1 day | Thu 4/18/02 | Fri 4/19/02 | Team | 100% |
| 58 | Obtain user feedback | 2 days | Fri 4/19/02 | Tue 4/23/02 | Team | 100% |
| 59 | Attend class meeting | 3 hrs | Tue 4/23/02 | Tue 4/23/02 | Team | 100% |
| 60 | Final Project Presentation | 13.75 days | Tue 4/23/02 | Sat 5/11/02 | | 0% |
| 61 | Prepare Presentation | 9 days | Tue 4/23/02 | Mon 5/6/02 | Team | 0% |
| 62 | Present to Faculty | 5 mins | Tue 5/7/02 | Tue 5/7/02 | Team,Faculty,Instructor | 0% |
| 63 | Team Party | 3 hrs | Sat 5/11/02 | Sat 5/11/02 | Team | 0% |
| Task ID | Task Name | Resource Name | Work | Start | Finish | % Work Complete |
| 2 | Secure project sponsorship | Client | 2.5 hrs | Thu 1/31/02 | Thu 1/31/02 | 100% |
| 2 | Secure project sponsorship | Team | 2.5 hrs | Thu 1/31/02 | Thu 1/31/02 | 100% |
| 3 | Analyze client needs | Team | 4 hrs | Thu 1/31/02 | Thu 1/31/02 | 100% |
| 4 | Determine project scope | Team | 2 hrs | Thu 1/31/02 | Fri 2/1/02 | 100% |
| 5 | Define preliminary resources | Team | 2.5 hrs | Fri 2/1/02 | Fri 2/1/02 | 100% |
| 6 | Prepare Class Presentation | Team | 2 hrs | Fri 2/1/02 | Fri 2/1/02 | 100% |
| 8 | Conduct needs analysis | Team | 1 hr | Sat 2/2/02 | Sat 2/2/02 | 100% |
| 9 | Draft preliminary software specifications | Team | 1 hr | Sat 2/2/02 | Sat 2/2/02 | 100% |
| 10 | Review software specifications with team | Team | 1 hr | Sat 2/2/02 | Sat 2/2/02 | 100% |
| 11 | Finalize class presentation | Team | 0.5 hrs | Sat 2/2/02 | Sat 2/2/02 | 100% |
| 12 | Develop delivery timeline | Team | 0.75 hrs | Sat 2/2/02 | Sat 2/2/02 | 100% |
| 13 | Present project to class | Team | 0.17 hrs | Tue 2/5/02 | Tue 2/5/02 | 100% |
| 13 | Present project to class | Class | 0.17 hrs | Tue 2/5/02 | Tue 2/5/02 | 100% |
| 13 | Present project to class | Instructor | 0.17 hrs | Tue 2/5/02 | Tue 2/5/02 | 100% |
| 14 | Incorporate feedback on software specifications | Class | 0.17 hrs | Tue 2/5/02 | Tue 2/5/02 | 100% |
| 14 | Incorporate feedback on software specifications | Instructor | 0.17 hrs | Tue 2/5/02 | Tue 2/5/02 | 100% |
| 15 | Obtain approvals to proceed (concept, timeline) | Client | 1 hr | Tue 2/5/02 | Tue 2/5/02 | 100% |
| 15 | Obtain approvals to proceed (concept, timeline) | Instructor | 1 hr | Tue 2/5/02 | Tue 2/5/02 | 100% |
| 16 | Setup future client meetings | Team | 4 hrs | Wed 2/6/02 | Wed 2/6/02 | 100% |
| 16 | Setup future client meetings | Client | 4 hrs | Wed 2/6/02 | Wed 2/6/02 | 100% |
| 17 | Formulate rationales and requirements | Team | 24 hrs | Wed 2/6/02 | Mon 2/11/02 | 100% |
| 18 | Attend class meeting | Team | 3 hrs | Tue 2/12/02 | Tue 2/12/02 | 100% |
| 18 | Attend class meeting | Class | 3 hrs | Tue 2/12/02 | Tue 2/12/02 | 100% |
| 18 | Attend class meeting | Instructor | 3 hrs | Tue 2/12/02 | Tue 2/12/02 | 100% |
| 19 | Refine Rationales and Requirements | Team | 24 hrs | Thu 2/14/02 | Sat 2/16/02 | 100% |
| 20 | Prepare Formal report and class presentation | Team | 4 hrs | Mon 2/18/02 | Mon 2/18/02 | 100% |
| 21 | Present Requirements to class | Team | 0.17 hrs | Tue 2/19/02 | Tue 2/19/02 | 100% |
| 21 | Present Requirements to class | Class | 0.17 hrs | Tue 2/19/02 | Tue 2/19/02 | 100% |
| 21 | Present Requirements to class | Instructor | 0.17 hrs | Tue 2/19/02 | Tue 2/19/02 | 100% |
| 22 | Setup meeting with client | Team | 8 hrs | Tue 2/19/02 | Wed 2/20/02 | 100% |
| 22 | Setup meeting with client | Client | 8 hrs | Tue 2/19/02 | Wed 2/20/02 | 100% |
| 24 | Review preliminary software specifications | Team | 2 hrs | Wed 2/20/02 | Wed 2/20/02 | 100% |
| 25 | Develop functional specifications | Team | 1 hr | Wed 2/20/02 | Wed 2/20/02 | 100% |
| 26 | Develop prototype based on functional specifications | Team | 24 hrs | Thu 2/21/02 | Sat 2/23/02 | 100% |
| 27 | Review functional specifications | Team | 8 hrs | Sun 2/24/02 | Sun 2/24/02 | 100% |
| 28 | Incorporate feedback into functional specifications | Team | 2 hrs | Mon 2/25/02 | Mon 2/25/02 | 100% |
| 29 | Prepare Mid-Term client presentations | Team | 2 hrs | Mon 2/25/02 | Mon 2/25/02 | 100% |
| 30 | Mid-Term client presentations and client feedback | Team | 8 hrs | Wed 3/13/02 | Wed 3/13/02 | 100% |
| 30 | Mid-Term client presentations and client feedback | Client | 8 hrs | Wed 3/13/02 | Wed 3/13/02 | 100% |
| 31 | Prepare final design documentations | Team | 16 hrs | Thu 3/14/02 | Fri 3/15/02 | 100% |
| 32 | Prepare System Design class presentation | Team | 16 hrs | Sat 3/16/02 | Mon 3/18/02 | 100% |
| 33 | Present System Design to class | Team | 0.25 hrs | Tue 3/19/02 | Tue 3/19/02 | 0% |
| 33 | Present System Design to class | Class | 0.25 hrs | Tue 3/19/02 | Tue 3/19/02 | 0% |
| 33 | Present System Design to class | Instructor | 0.25 hrs | Tue 3/19/02 | Tue 3/19/02 | 0% |
| 34 | Obtain approval to proceed | Instructor | 0.05 hrs | Tue 3/19/02 | Tue 3/19/02 | 0% |
| 34 | Obtain approval to proceed | Team | 0.05 hrs | Tue 3/19/02 | Tue 3/19/02 | 0% |
| 34 | Obtain approval to proceed | Client | 0.05 hrs | Tue 3/19/02 | Tue 3/19/02 | 0% |
| 36 | Review functional specifications | Team | 8 hrs | Wed 3/20/02 | Wed 3/20/02 | 0% |
| 37 | Identify design parameters | Team | 8 hrs | Thu 3/21/02 | Thu 3/21/02 | 0% |
| 38 | Develop code | Team | 88 hrs | Fri 3/22/02 | Fri 4/5/02 | 0% |
| 39 | Developer testing | Team | 4 hrs | Sat 4/6/02 | Sat 4/6/02 | 0% |
| 41 | Develop test plans using product specifications | Team | 3 hrs | Sun 4/7/02 | Sun 4/7/02 | 0% |
| 42 | Develop integration test plans using product specifications | Team | 3 hrs | Sun 4/7/02 | Sun 4/7/02 | 0% |
| 43 | Modify code | Team | 4 hrs | Mon 4/8/02 | Mon 4/8/02 | 0% |
| 44 | Re-Test modified code | Team | 2 hrs | Mon 4/8/02 | Mon 4/8/02 | 0% |
| 46 | Test integration | Team | 2 hrs | Wed 4/10/02 | Wed 4/10/02 | 0% |
| 47 | Modify code | Team | 16 hrs | Wed 4/10/02 | Fri 4/12/02 | 0% |
| 48 | Re-test modified code | Team | 8 hrs | Fri 4/12/02 | Mon 4/15/02 | 0% |
| 49 | Prepare Prototype presentation | Team | 2 hrs | Mon 4/15/02 | Mon 4/15/02 | 0% |
| 50 | Present Prototype to class | Team | 0.25 hrs | Tue 4/16/02 | Tue 4/16/02 | 0% |
| 50 | Present Prototype to class | Class | 0.25 hrs | Tue 4/16/02 | Tue 4/16/02 | 0% |
| 50 | Present Prototype to class | Instructor | 0.25 hrs | Tue 4/16/02 | Tue 4/16/02 | 0% |
| 52 | Develop training materials | Team | 3 hrs | Wed 4/17/02 | Wed 4/17/02 | 0% |
| 54 | Develop user manuals | Team | 2 hrs | Wed 4/17/02 | Wed 4/17/02 | 0% |
| 56 | Install/deploy software | Team | 2 hrs | Thu 4/18/02 | Thu 4/18/02 | 0% |
| 57 | Final client presentations | Team | 8 hrs | Thu 4/18/02 | Fri 4/19/02 | 0% |
| 58 | Obtain user feedback | Team | 16 hrs | Fri 4/19/02 | Tue 4/23/02 | 0% |
| 59 | Attend class meeting | Team | 3 hrs | Tue 4/23/02 | Tue 4/23/02 | 0% |
| 61 | Prepare Presentation | Team | 72 hrs | Tue 4/23/02 | Mon 5/6/02 | 0% |
| 62 | Present to Faculty | Team | 0.08 hrs | Tue 5/7/02 | Tue 5/7/02 | 0% |
| 62 | Present to Faculty | Faculty | 0.08 hrs | Tue 5/7/02 | Tue 5/7/02 | 0% |
| 62 | Present to Faculty | Instructor | 0.08 hrs | Tue 5/7/02 | Tue 5/7/02 | 0% |
| 63 | Team Party | Team | 3 hrs | Sat 5/11/02 | Sat 5/11/02 | 0% |