Software Project Management Plan (SPMP) - Southern Polytechnic ...

More documents

Recommendations

Info

5.3.5. Reporting Plan 5.3.5.1. Status Reporting Page 34 of 60 Test Management Tool (TMT) Software Project Management Plan (SPMP) TMT-SPMP-1.2 27-Sep-2010 The TMT PM generates and provides weekly project status to the TMT Project Advisor on Monday at 7:45 PM. There are 12 weekly status reports and the detailed of each status report is noted in the TMT Team’s Metric Program under Project Management Tasks. All team members are required to be present in all weekly status meetings. 5.3.5.2. Internal Reviews The TMT Team holds in-progress reviews at least once month for the purpose of monitoring and adjusting the internal process toward meeting the scheduled milestones, reviewing problems encountered, presenting proposed resolutions, presenting near-term plans, reviewing risks and mitigation plans, and individual performance assessments using earned value data extracted from the TMT Team’s Metric Program. The TMT PM is also responsible to provide internal reviews to each team member based on individual in-progress performance and task assignments. 5.3.5.3. Meetings As the project progress become more aggressive toward the deliverable deadline, the TMT Team is more likely to call at least one meeting every Wednesday for the purpose of monitoring progress, work coordination, issues and resolutions, and etc. as needed. 5.3.5.4. Information Repository All project information needs to be submitted to the TMT PM for reviews and sign-offs. Source codes need to be uploaded to the test environment at http://www.winhost.com for sharing purposes among the team members as well as posted on the TMT Team’s website at http://cse.spsu.edu/ftsui/SWE7903.html. *** NOTE: An alternative to uploading files to http://www.winhost.com, team members can also upload files to Google Group; however, it is not recommended to for the purpose of having one central information repository. 5.3.5.5. Communication In addition to the aforementioned means of reporting and project communication, the TMT members are recommended to communicate through email and phones as needed. The following is the listing of the TMT team members contact information: Table 5.3-1: TMT Team Member Contact Information Name Email Phone Comment Adam Scott ascott4@spsu.edu 770-940-0988 Busy on Wednesdays. Harish Sreenivas hsreenivas@spsu.edu 678-896-0727 Work at SPSU Mon – Wed, 11:00 – 5:00.
Page 35 of 60 Test Management Tool (TMT) Software Project Management Plan (SPMP) TMT-SPMP-1.2 27-Sep-2010 Name Email Phone Comment Jagati Vempaty jvempaty@spsu.edu 404-751-7896 N/A. Seth Zaah sethzaah@yahoo.co.uk 678-485-8014 Work at Client Support/Real Estate, 9:00 AM - 7:00 PM, Mon - Sat. Tom Le tomle75@comcast.net 404-791-3816 Work at LM Aero Mon – Fri, 9:00 – 3:00. 5.3.6. Metrics Collection Plan The TMT Team’s metric program follows the Goal-Question-Measurement (GQM) approach to establish team’s goals, define goal-oriented questions, and determine measurements for the defined goals and questions. The following table shows various metrics the TMT Team needs to collect and report: Table 5.3-2: TMT Metrics Metric Category Metric Name Purpose Cost per Unit To project future cost estimation. MTBF To collect the mean time between failures to project product availability. Product Metrics Product Size To provide future effort estimation. Performance To provide product performance assessment since it is an online service. Quality Level To assess the product quality level. Phase-based Effort To assess the effort by various development phases (i.e., requirements, design, code, test, and documentation). EDR per Phase To assess the effectiveness of defect removal per phase. Process Metrics Response Time of Fix To assess responses to fixes, future effort estimations, and early risk mitigations. Fix Backlog To assess future workloads and schedule risks. Fix Quality To assess rework. Defect Density To assess defects per product size. Schedule To identify root causes for schedule slippage and work under-estimates. Project Metrics Cost To identify cost variance and task allocation. Productivity To assess productivity and task reallocation. Scope To identify changes to project scope. ***NOTE: The detailed GQM metric program is defined in a separate MS Excel file and posted on the TMT website at http://www.cse.spsu.edu/ftsui/SWE7903.html. 5.4. Risk Management Plan To ensure all milestones and work packages delivered on-time, within budget, at product quality, the TMT Team’s strategy is to follow the steps below:
Page 1 and 2: Software Project Management Plan (S
Page 3 and 4: SIGNATURE PAGE Page 3 of 60 Test Ma
Page 5 and 6: REVISION HISTORY Page 5 of 60 Test
Page 7 and 8: PREFACE Page 7 of 60 Test Managemen
Page 9 and 10: TABLE OF CONTENTS Page 9 of 60 Test
Page 11 and 12: Page 11 of 60 Test Management Tool
Page 13 and 14: LIST OF TABLES Page 13 of 60 Test M
Page 15 and 16: 1.1. Project Summary 1. OVERVIEW Pa
Page 17 and 18: 1.1.3. Project Deliverables The TMT
Page 19 and 20: 1.3. Document Overview This plan is
Page 21 and 22: 2. REFERENCES 2.1. Standards, Docum
Page 23 and 24: 3. DEFINITIONS Page 23 of 60 Test M
Page 25 and 26: 4.1. External Interfaces 4. PROJECT
Page 29 and 30: 5.1. Start-up Plan 5.1.1. Estimatio
Page 33: 5.3.2.3. Schedule Reviews Page 33 o
Page 37 and 38: 6.1. Process Model 6. TECHNICAL PRO
Page 39 and 40: Table 6.2-1: TMT Programming Langua
Page 41 and 42: 7. SUPPORTING PROCESS PLANS 7.1. Co
Page 45 and 46: There are no other addition plans.
Page 47 and 48: APPENDIXES Appendix A: Requirements
Page 49 and 50: Appendix C: Code Review Checklist P
Page 51 and 52: Appendix E: Defect Report Form Use
Page 53 and 54: Appendix G: Review Closeout Form Us
Page 55 and 56: Appendix I: Data Collection Point C
Page 57 and 58: Appendix L: Defect Types Page 57 of

Software Project Management Plan (SPMP) - Southern Polytechnic ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?