Short-Term Project Plan

ECOACH - Reading Assessment

Bradley John (B.J.) Barton - Spring 2002

Table of Contents

Personnel

Name Roles Email Address
Bradley (B.J.) Barton Software Manager bj.barton@ttu.edu
Jason Pharis Configuration Manager jpharis@ttu.edu
Robin D'Souza Requirements Lead / Trainer robin_dsouza@yahoo.com
Daniel Jack Requirements Analyst / Trainer djack@ttacs.ttu.edu
Vu Le Requirements Analyst / Training Lead vule69@yahoo.com
Ayotunde Phillips Design Lead / SQA Analyst ayotundephillips@hotmail.com
Keith Brumbaugh Design Analyst kbrumbau@ttacs.ttu.edu
Jeremy Stanley Design Analyst jestanle@ttacs.ttu.edu
Matt Mason Programming Lead imyy4u99@hotmail.com
Stephen Hill Programmer cygnwulf@yahoo.com
Chris Galanos Programmer chris.galanos@ttu.edu
Adam Thomas-Murphy SQA Lead deckard0047@aol.com

Work Packages

Management (Software Manager - B.J. Barton, Configuration Manager - Jason Paris)

Artifact Work

WP ID Resource Names Role Tasks Start Finish % Work Completed
1.1.1.1 B.J. Software Manager
  • Long Term Plan posted with title section revised.
  • Short Term Plan template posted with title section and personnel section filled out.
 3/4 3/11 100
1.2.1.1 Jason Configuration Manager Configuration Management Plan posted with title section revised. 3/4 3/11 100
1.1.1.2 B.J. Software Manager
  • Long Term Plan, revised, completed and posted
  • Short Term Plan completed and posted (work packages should be outlined but not necessarily competed.)
 3/11 3/21(3/18) 100
1.2.1.2 Jason Configuration Manager Configuration Management Plan revised, completed, and posted. 3/11 3/21(3/18) 100
1.1.1.3 B.J. Software Manager
  • Long Term Plan revised as necessary and posted.
  • Short Term Plan revised and posted (most work packages should have specific names and tasks).
 3/18 3/25  

100
1.2.1.3 Jason Configuration Manager Configuration Management Plan Revised and posted 3/18 3/25 100
1.1.1.4 B.J. Software Manager
  • Long Term Plan revised as necessary and posted.
  • Short Term Plan revised and posted (most work packages should have specific names and tasks).
 3/25 4/1 100
1.2.1.4 Jason Configuration Manager Configuration management plan revised and posted 3/25 4/1 100
1.1.1.5 B.J. Software Manager
  • Long Term Plan revised as necessary and posted.
  • Short Term Plan revised and posted (most work packages should have specific names and tasks).
  • EOS document template posted with title section filled out.
  • Review requirements and design documents.
 4/1 4/8 100
1.2.1.5 Jason Configuration Manager
  • Configuration management plan revised and posted
  • Review software manual, execution, and code
 4/1 4/8 100
1.1.1.6 B.J. Software Manager
  • Long Term Plan revised as necessary and posted.
  • Short Term Plan revised and posted (most work packages should have specific names and tasks).
  • EOS document revised and posted with all sections filled out.
  • Requirements and design reviews posted
 4/8 4/15  
1.2.1.6 Jason Configuration Manager
  • Configuration management plan revised and posted.
  • Software manual, execution, and code reviews posted.
 4/8 4/15  
1.1.1.7 B.J. Software Manager
  • Long-term plan completed and posted
  • Short-term plan completed and posted
  • EOS Document completed and posted
 4/15 4/22  
1.2.1.7 Jason Configuration Manager Configuration management plan completed and posted. 4/15 4/22  

Meetings

WP ID Resource Names Role Tasks Start Finish % Work Completed
             
             
             

Other Project Work

WP ID Resource Names Role Tasks Start Finish % Work Completed
1.2.3.1 Jason Configuration Manager
  • Team submissions posted to web site
  • Web Site Backed Up
 3/4 4/22 20
1.1.3.1 B.J. Software Manager Communicating with team and various managerial tasks (e.g. responding to team member emails, questions, and phone calls.) 3/4 4/22 100
1.2.3.2 Jason Configuration Manager
  • Restructured web server directories from last semester
  • Created new folders and directories for new semester
  • Archived previous semesters documents
  • Removed links to old documents and placed links in Historical Archives page
3/19 3/21 100
1.1.3.2 B.J. Software Manager Assumed Jason's job's while he was out of town (post submitted documents on web page.) 3/21 3/25 100

 

Requirements Team (Requirements Lead - Robin D'Souza, Requirements Analysts - Daniel Jack, Vu Le)

Artifact Work

WP ID Resource Names Role Tasks Start Finish % Work Completed
2.0.1.1 Requirements Team Requirements Lead and Analysts
  • Post Requirements Document with title section revised.
 3/4 3/11 100
2.1.1.2 Robin Requirements Lead Review and revise as you see necessary the external interfaces, functional requirements, performance requirements, and the To Do list of the current requirements document. 3/11 3/21(3/18) 100
2.2.1.2 Daniel Requirements Analyst Review and revise as you see necessary the software system attributes, other requirements, and current client system requirements of the current requirements document. 3/11 3/21(3/18) 100
2.3.1.2 Vu Le Requirements Analyst Review and revise as you see necessary the logical database requirements, design constraints, and user constraints of the current requirements document. 3/11 3/21(3/18) 100
2.1.1.3 Robin Requirements Lead Review and revise as you see necessary the external interfaces, functional requirements, performance requirements, and the To Do list of the current requirements document. 3/18 3/25 100
2.2.1.3 Daniel Requirements Analyst Review and revise as you see necessary the software system attributes, other requirements, and current client system requirements of the current requirements document. 3/18 3/25 100
2.3.1.3 Vu Le Requirements Analyst Review and revise as you see necessary the logical database requirements, design constraints, and user constraints of the current requirements document. 3/18 3/25 100
2.1.1.4 Robin Requirements Lead Post requirements assessment report. 3/25 4/1 100
2.2.1.4 Daniel Requirements Analyst Post requirements assessment report. 3/25 4/1 100
2.3.1.4 Vu Le Requirements Analyst Help post requirements assessment report. 3/25 4/1 100
2.1.1.5 Robin Requirements Lead Develop evaluation requirements. 4/1 4/8 100
2.2.1.5 Daniel Requirements Analyst Develop evaluation requirements. 4/1 4/8 100
2.3.1.5 Vu Le Requirements Analyst Help develop evaluation requirements. 4/1 4/8 100
2.1.1.6 Robin Requirements Lead Develop Requirements Interference and non-interference part of the software. 4/8 4/15  
2.2.1.6 Daniel Requirements Analyst Work on Design Characteristics and client materials 4/8 4/15  
2.3.1.6 Vu Le Requirements Analyst Concentrate on Online Help 4/8 4/15  
2.1.1.7 Robin Requirements Lead
  • Develop Requirements Interference and non-interference part of the software.
  • Post completed Requirements Document
 4/15 4/22  
2.2.1.7 Daniel Requirements Analyst
  • Develop Requirements Interference and non-interference part of the software.
  • Post completed Requirements Document
 4/15 4/22  
2.3.1.7 Vu Le Requirements Analyst
  • Develop Requirements Interference and non-interference part of the software.
  • Post completed Requirements Document
 4/15 4/22  

Meetings

WP ID Resource Names Role Tasks Start Finish % Work Completed
2.2.2.4 Daniel Requirements Analyst Meeting with client to discuss requirements document. - March 28th 11:00am 11:30am 100

Other Project Work

WP ID Resource Names Role Tasks Start Finish % Work Completed
2.2.3.4 Daniel Requirements Analyst Provide soft copies of client reading materials acquired from meeting with client. 03/25 04/01 100

 

Design Team (Design Lead - Ayotunde Phillips; Design Analysts - Keith Brumbaugh, Jeremy Stanley)

Artifact Work

WP ID Resource Names Role Tasks Start Finish % Work Completed
3.0.1.1 Design Team Design Lead and Analysts Design Document Template posted with title section filled out 3/4 3/11 100
3.1.1.2 Ayotunde Design Lead Review and revise, as you see necessary, the Detailed Design, Implementation Platform, and Cross Check of the current design document. 3/11 3/21(3/18) 100
3.2.1.2 Keith Design Analyst Review and revise, as you see necessary, the Design Approach, Similar and Supporting Work, Systems Architecture, and the Deployment of the current design document. 3/11 3/21(3/18) 100
3.3.1.2 Jeremy Design Analyst Review and revise, as you see necessary, the User Interaction, Data Storage/Format, and the External System Interface of the current design document. 3/11 3/21(3/18) 100
3.1.1.3 Ayotunde Design Lead Review and revise the Evaluation Page, Reading Results Page and any other pages Keith comes up with in the Requirements document. 3/18 3/25 100
3.2.1.3 Keith Design Analyst Review and revise the main page subsystem, Guest login page, and the Reading Tips page in the Requirements document. 3/18 3/25 100
3.3.1.3 Jeremy Design Analyst Review and revise the Information Page, Instruction Page, and the Passage Page in the Requirements document. 3/18 3/25 100
3.1.1.4 Ayotunde Design Lead Revise the Evaluation Page, Reading Results Page and any other pages Keith comes up with in the Requirements document. 3/25 4/1 100
3.2.1.4 Keith Design Analyst Revise the main page subsystem, Guest login page, and the Reading Tips page in the Requirements document. 3/25 4/1 100
3.3.1.4 Jeremy Design Analyst Revise the Information Page, Instruction Page, and the Passage Page in the Requirements document. 3/25 4/1 100
3.1.1.5 Ayotunde Design Lead
  • Cross reference requirements sections 3, 4 and 5.
  • Update the error external interfaces
  • Redo the external interface diagrams, and add the following descriptions to the use cases:  Error messages, Files accessed, and  Files changed.
 4/1 4/8 100
3.2.1.5 Keith Design Analyst
  • Redo the main page subsystem diagram.
  • Cross reference requirement, sections 1-2.2.
  • Redo the external interface diagrams, and add the following descriptions to the use cases:  Error messages, Files accessed, and  Files changed.
 4/1 4/8 100
3.3.1.5 Jeremy Design Analyst
  • Cross reference 2.3-2.7.
  • Design the main page prompt as previously discussed with the design team
  • Redo the external interface diagrams, and add the following descriptions to the use cases:  Error messages, Files accessed, and  Files changed.
 4/1 4/8 100
3.1.1.6 Ayotunde Design Lead
  • Complete entity relationship diagrams for sections 3.1-3.5 of the requirements document.
 4/8 4/15  
3.2.1.6 Keith Design Analyst
  • Add  Error Messages, Files Accessed and Files changed to the use cases and cross check your part of the cross reference table)
  • Evaluation Page picture and use cases to include questions.
 4/8 4/15
3.3.1.6 Jeremy Design Analyst
  • Update the database tables in Data Storage format section. 
  • Figure out where to incorporate the Software Systems attributes in the requirements document into the design document.
4/8 4/15  
3.1.1.7 Ayotunde Design Lead Design document completed and posted 4/15 4/22  
3.2.1.7 Keith Design Analyst   4/15 4/22  
3.3.1.7 Jeremy Design Analyst   4/15 4/22  

Meetings

WP ID Resource Names Role Tasks Start Finish % Work Completed
3.9.2.4 Design Team Design Team and Team Leader Talk about the new changes from the client-team meeting.  Also discussed future changes for the design document. - April 1st 5:15p 7:15p 100

Other Project Work

WP ID Resource Names Role Tasks Start Finish % Work Completed
             
             
             

 

Programming Team (Programming Lead - Matt Mason; Programmers - Stephen Hill, Chris Galanos)

Artifact Work

WP ID Resource Names Role Tasks Start Finish % Work Completed
4.0.1.1 Matt, Stephen, Chris Programming Team Software manual posted with title section revised 3/4 3/11 100
4.0.1.2 Matt, Stephen, Chris Programming Team
  • Software manual revised as necessary and posted
  • Software index page revised as necessary and posted
 3/11 3/22(3/18) 100
4.1.1.3 Matt Programming Lead Software manual revised as necessary and posted. 3/18 3/25 100
4.2.1.3 Stephen Programmer Software index page revised as necessary and posted. 3/18 3/25 100
4.3.1.3 Chris Programmer New software version with one component edited. 3/18 3/25 100
4.1.1.4 Matt Programming Lead
  • Work on results page.
  • Review software manual and index page.
 3/25 4/1 100
4.2.1.4 Stephen Programmer
  • Create new software version
  • Work on Evaluation Plan
 3/25 4/1 100
4.3.1.4 Chris Programmer Work on evaluation page and results page. 3/25 4/1 100
4.1.1.5 Matt Programming Lead
  • Added instruction page.
  • Reviewed Software Manual
 4/1 4/8 100
4.2.1.5 Stephen Programmer
  • Edit Index Page
 4/1 4/8 100
4.3.1.5 Chris Programmer
  • Administration Pages (includes main page, stats page, evaluation page, questions page, and evaluation process page)
  • User Pages (includes results page and information page)
 4/1 4/8 100
4.1.1.6 Matt Programming Lead
  • Updated Software manual.
  • Revise both instruction pages.
  • Polish Software.
 4/8 4/15  
4.2.1.6 Stephen Programmer
  • Develop printer friendly version for the results page.
  • Polish software.
 4/8 4/15  
4.3.1.6 Chris Programmer
  • Document all administration pages.
  • Implement randomization of passages without duplication, and format results page for retrieval of results from more than one passage.
  • Polish Software.
 4/8 4/15  
4.1.1.7 Matt Programming Lead
  • Software manual completed and posted.
  • Software index page completed and posted.
  • Software work completed with software done.
 4/15 4/22  
4.2.1.7 Stephen Programmer 4/15 4/22
4.3.1.7 Chris Programmer   4/15 4/22  

Meetings

WP ID Resource Names Role Tasks Start Finish % Work Completed
4.9.2.5 Programming Team Program lead and programmers Met with design team to discuss new design. - April 4th 9:00a 9:30a 100

Other Project Work

WP ID Resource Names Role Tasks Start Finish % Work Completed
4.0.3.1 Programming Team Programming Lead and Programmers Learn ASP 3/4 4/1 100

 

SQA Team (SQA Lead - Adam Thomas-Murphy; SQA Analyst - Ayotunde Phillips)

Artifact Work

WP ID Resource Names Role Tasks Start Finish % Work Completed
5.0.1.1 SQA Team SQA Lead and Analyst Test log template posted with title section filled out. 3/4 3/11 100
5.1.1.2 Adam SQA Lead Review the requirements document and the software manual. 3/11 3/22(3/18) 100
5.2.1.2 Ayotude SQA Analyst Review the design document. 3/4 3/22(3/18) 100
5.1.1.3 Adam SQA Lead
  • Post the requirements document and software manual reviews.
  • test log revised and posted with validation test cases filled out.
 3/18 3/25 100
5.2.1.3 Ayotude SQA Analyst
  • Post the design document review.
  • Test Log revised and posted with validation test cases filled out.
 3/18 3/25 100
5.1.1.4 Adam SQA Lead
  • Requirements and software manual review.\
  • Execute the validation test cases and get the software unit test cases filled out.
 3/25 4/1 100
5.2.1.4 Ayotunde SQA Analyst
  • Design document review
  • Execute the validation test cases and get the software unit test cases filled out.
 3/25 4/1 100
5.1.1.5 Adam SQA Lead Complete integration test cases and to meet with the client about any problems. 4/1 4/8 100
5.2.1.5 Ayotunde SQA Analyst Complete integration test cases and to meet with the client about any problems. 4/1 4/8 100
5.1.1.6 Adam SQA Lead Finish software unit and validation cases. 4/8 4/15  
5.2.1.6 Ayotunde SQA Analyst Finish validation cases 4/8 4/15  
5.1.1.7 Adam SQA Lead
  • Test log completed and posted
 4/15 4/22  
5.2.1.7 Ayotunde SQA Analyst 4/15 4/22

Meetings

WP ID Resource Names Role Tasks Start Finish % Work Completed
             
             
             

Other Project Work

WP ID Resource Names Role Tasks Start Finish % Work Completed
             
             
             

 

Training Team (Training Lead - Vu Le; Trainers - Robin D'Souza, Daniel Jack)

Artifact Work

WP ID Resource Names Role Tasks Start Finish % Work Completed
6.1.1.4 Vu Le Training Lead Revise the contents of the training plan 3/25 4/1 100
6.2.1.4 Robin Trainer Create an index for the training plan 3/25 4/1 100
6.3.1.4 Daniel Trainer Help with revising the contents of the training plan 3/25 4/1 100
6.1.1.5 Vu Le Training Lead Construct the training artifacts and tutorials (for the online help) 4/1 4/8 100
6.2.1.5 Robin Trainer Construct the training artifacts and tutorials (for the online help) 4/1 4/8 100
6.3.1.5 Daniel Trainer Construct the training artifacts and tutorials (for the online help) 4/1 4/8 100
6.1.1.6 Vu Le Training Lead
  • Continue to work on online help.
  • Work on Instruction page for software.
  • Work on Results page with programming team.
 4/8 4/15  
6.2.1.6 Robin Trainer Concentrate on requirements document. 4/8 4/15  
6.3.1.6 Daniel Trainer Concentrate on requirements document. 4/8 4/15
6.1.1.7 Vu Le Training Lead Training materials completed and posted 4/15 4/22  
6.2.1.7 Robin Trainer   4/15 4/22  
6.3.1.7 Daniel Trainer 4/15 4/22

Meetings

WP ID Resource Names Role Tasks Start Finish % Work Completed
             
             
             

Other Project Work

WP ID Resource Names Role Tasks Start Finish % Work Completed
             
             
             

 

Everyone (Work pertaining to everyone on the team)

Artifact Work

WP ID Resource Names Role Tasks Start Finish % Work Completed
9.1.1.1 All All Practice Weekly Report 3/4 3/5,6,7 100
9.1.1.2 All All Weekly Report 3/18 3/21,22(3/19) 100
9.1.1.3 All All Weekly Report 3/25 3/26,27,28 100
9.1.1.4 All All Weekly Report 4/1 4/2,3,4 100
9.1.1.5 All All Weekly Report 4/8 4/9,10,11 100
9.1.1.6 All All
  • Weekly Report
  • Client Software Presentation
 4/15 4/16,17,18  
9.1.1.7 All All
  • Weekly Report
  • Project Finished
 4/22 4/23,24,25  
9.1.1.8 All All Confidential Self and Peer Reviews Completed 4/22 4/29  

Meetings

WP ID Resource Names Role Tasks Start Finish % Work Completed
9.1.2.1 All All General Team Meeting - March 19th 8:30a 9:30a 100
9.1.2.2 All All General Team Meeting - March 21st 8:30a 9:30a 100
9.1.2.3 Managers and Leaders All Team Leader, and Managers Meeting with Client (Dr. Gregory) - March 25th 4:30p 5:00p 100
9.1.2.4 All All General Team Meeting - March 26th 8:00a 9:30a 100
9.1.2.5 All All General Team Meeting - April 2nd 8:30a 9:30a 100
9.1.2.6 All All General Team Meeting - April 9th 8:30a 9:30a 100
9.1.2.7 Managers, Leaders, and Programming Team All Managers, Leaders, and Programming Team Meeting with Client (Dr. Gregory) to preview newest software version - April 12th 2:30p 3:30p 100
9.1.2.8 All All General Team Meeting - April 11th 8:30a 9:30a 100
9.1.2.9 All All Client Presentation - April 16th 8:00a 9:30a 100

Other Project Work

WP ID Resource Names Role Tasks Start Finish % Work Completed
             
             
             

 

Project Schedule Update

Week Starting On/Off Schedule Reason Off Schedule Corrective Actions To Take
03/04/02 On N/A N/A
03/18/02 Off Spring break confused team members on the date that things were due. Pushed back the weekly report submit deadline to Friday and worked harder to get back on schedule.
03/25/02 On N/A N/A
04/01/02 On N/A N/A
04/08/02 On N/A N/A
04/15/02

Special Procedures

Procedure Name Steps
Weekly Report Submit Times All team members should submit weekly reviews at 4:30pm on their respective days (regulars members - Tuesday, team leaders and configuration manager - Wednesday, software manager - Thursday) to allow the configuration manager some time to get the documents posted before 5pm.
Email Policy All emails that are sent between teams and teams members should be copied to the Software Manager.

Short-Term Risks

Risk Probability of Becoming a Problem (Low, Medium, High) How to Avoid the Risk How the Risk Would Impact the Project
The project could go off schedule if not properly monitored. Medium To avoid this risk, the leaders and the managers need to keep a close watch on what is happening with the project.  Every team member be motivated to finishing the project.  Communication is also key to maintaining the status of the project. This could slow down the project and force it to extend into another semester.
Server containing project materials could crash. Low Continually back up the project material so that it could be easily recovered. This could definitely slow down the project as a result of having to redo some of the work that has already been done.

To Do List

Items
Finish writing work packages for each team member based on the way each team leader divides up the work.

Team Request Forms

Revision History

Date Name Revision
03/18/2002 B.J. Barton Created short term plan document based on the schedule posted on the class website.
03/21/2002 B.J. Barton Updated work packages and added second general meeting.
03/22/2002 B.J. Barton Updated Work Packages.
03/25/2002 B.J. Barton Updated Work Packages and the To Do List.
03/27/2002 B.J. Barton Updated work packages and added third general meeting.
04/01/2002 B.J. Barton Updated work packages and special procedures.
04/03/2002 B.J. Barton Updated short-term risks and fixed some formatting errors.
04/09/2002 B.J. Barton Updated Work Packages.
04/10/2002 B.J. Barton Updated Work Packages.
04/16/2002 B.J. Barton Updated Work Packages.