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

More documents

Recommendations

Info

Page 36 of 60 Test Management Tool (TMT) Software Project Management Plan (SPMP) TMT-SPMP-1.2 27-Sep-2010 1. Identify risks a week ahead of current build schedule (i.e., Table 1.1-2: Master Build Schedule). 2. Enter risks in the TMT Team’s Metric Program. 3. PM and technical leads analyze risks, determine resolution, and implement resolution. 4. PM and technical leads provide follow-ups on risk’s resolution results. 5.5. Closeout Plan The TMT aims to complete the project 2 week earlier than the assigned deadline (i.e., 12-Dec- 2010). All work activities need to be finished by 28-Nov-2010. The project closeout occurs on 12-Dec-2010 with a presentation to the Industrial Advisory Board (IAB) referred by the SPSU Software Engineering Department. Along with the written reports and final documents (i.e., Table 1.1-1: Project Deliverables & Figure 1.1-1: Project Document Tree), the TMT Team is required to present the following information: 1. Requirements. 2. Designs. 3. Test Results. 4. Code/Product Demo. 5. Development Status.
6.1. Process Model 6. TECHNICAL PROCESS PLANS Page 37 of 60 Test Management Tool (TMT) Software Project Management Plan (SPMP) TMT-SPMP-1.2 27-Sep-2010 Due to uncertainties in product requirements (i.e., product functionalities are open for market competitiveness), small team size, no project historical data, and new product type being developed, the TMT Team tailors the Agile process model to decompose the high-level work packages into low-level tasks and group tasks by product feature. Each product feature is developed, reviewed, demonstrated, and modified in an increment of 2 weeks. This process is described in the figure below: Initial Development Increment # 1 . . . Increment # 12 Activity Output/Artifact Planning Requirements Design Code Test Install/Support Status Report Documents, Reviews Documents, Reviews Documents, Reviews Documents, Reviews Documents, Reviews Documents, Reviews Documents, Reviews SDSR SUM STD & STR SVD & Demo Figure 6.1-1: TMT Software Development Life Cycle (SDLC) SDD SRS SPMP & STP The development of the TMT tool is broken into one initial development and 12 incremental developments. Each incremental development spans through all activities from requirements, design, code, test, install/support, and status reporting, except the initial development spans from the planning activity. The purpose of the initial development is to produce the following the following software artifacts: 1. A complete project plans (=> SPMP & STP). 2. Requirements specification for the overall system framework => SRS). 3. Overall system architectural and high-level component designs (=> SDD). 4. Source codes for the system architecture and framework (=> SVD). 5. Test cases, procedures, and results for the framework (=> STD & STR). 6. A draft installation and user manual (=> SUM). 7. A draft development status report (=> SDSR). Source code listing and versions Software user manual Reports the overall development status Test procedures and results as planned
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 and 34: 5.3.2.3. Schedule Reviews Page 33 o
Page 35: Page 35 of 60 Test Management Tool
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?