1 / 21

PROJECT MANAGEMENT SYSTEM APPLICATION (PMSA)

PROJECT PLAN. PROJECT MANAGEMENT SYSTEM APPLICATION (PMSA). SWE 6633 Software Project Management Dr. Frank Tsui Team JKS 3 PROJECT MEMBERS: Verrell J ordan Steven K erckhof Ross S immerman John S ineath Tarus D. S tills Thursday, October 25, 2012. DESCRIPTION.

nerita
Download Presentation

PROJECT MANAGEMENT SYSTEM APPLICATION (PMSA)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PROJECT PLAN PROJECT MANAGEMENT SYSTEM APPLICATION(PMSA) SWE 6633 Software Project ManagementDr. Frank Tsui Team JKS3 PROJECT MEMBERS:Verrell Jordan Steven Kerckhof Ross Simmerman John Sineath Tarus D. Stills Thursday, October 25, 2012

  2. DESCRIPTION Tsui Education, LLC has contracted for a custom Project Management System Application (PMSA) that will enable Project Managers to better manage software development projects and provide more accurate project status reporting to management. This powerpoint is a presentation of the Project Plan and will be used moving forward as the format for weekly Project Status meetings.

  3. DELIVERABLES • The following customer deliverables will be provided: • Project Plan and Weekly Project Status Document which includes: • Project Goals • Project Assumptions • Project Risks and Risk Mitigation • Business Requirements • Project Schedule • Project EVM Monitoring Metrics • Appendices with supporting detail • Test Plan Document • Actual Hours Worked Document • Project Management System Portal Web-Application

  4. PROJECT GOALS • This PMSA Project has the following project goals: • Provide an easy-to-use web application that will enable Project Managers to better manage SW development projects. “Easy-to-use” being determined by a training effort (classes) of no less than 1 hour and not greater than 2 hours. • Provide high quality sw artifacts measured by: • Number of sw defects decreases by 1 each week based on execution of test plan • Keep the project schedule on track by committing to an EVM SPI of not less than .9

  5. PROJECT RISKS • This PMSA Project has the following project risks that will be managed: • SW development tools and technology learning curves may affect productivity • Resource constraints • Critical Path dependencies may adversely affect Project Schedule

  6. PROJECT RISK MITIGATION • This PMSA Project risks will be managed as follows: • Rapid Application Development tools and technologies will be used to maximize developer productivity • Additional time has been added for tool and technology learning curves • Weekly project status update meetings will be held to measure actual vs. planned effort using EVM metrics so any impacts to project can be managed quickly and adjusted

  7. PROJECT ASSUMPTIONS • This PMSA Project has the following project assumptions: • The PMSA application is a thin-client web app that will consist of 1 or more JSR168 portlets within a Portal development framework. • The PMSA application will be delivered as 1 or more portlets in a portal development framework that will satisfy the business requirements listed in this Project Plan • Only Internet Explorer 7 or Internet Explorer 8 will be supported. No other browser version will be supported. • The scope of the project consists of the business requirements and features documented in this Project Plan. Any other requirements or features requested other than what is specifically documented in this Project Plan will be considered out-of-scope.

  8. COMMITTED PROJECT REQUIREMENTS

  9. COMMITTED PROJECT REQUIREMENTS (con’t)

  10. PROJECT EFFORT FP ANALYSIS FOR COMMITTED PROJECT BUSINESS REQUIREMENTS Rational: FP methodology was used to calculate project effort based on the business requirements and the design of the PMSA database as it was agreed by the team this would be more accurate than LOC.

  11. PROJECT EFFORT FP ANALYSIS FOR COMMITTED PROJECT BUSINESS REQUIREMENTS (con’t)

  12. PROJECT SCHEDULE FOR COMMITED REQTS Rational: Due to the tight timeframe and delivery constraints, an iterative “prototype” development process has been chosen. One milestone prototype will be delivered for review and assessment with the final version delivered at project completion.

  13. EVM ANALYSIS DETAIL FOR COMMITTED REQTSPROJECT STATUS DATE: 10/25/2012

  14. EVM ANALYSIS DETAIL FOR COMMITTED REQTS (con’t)PROJECT STATUS DATE: 10/25/2012

  15. EVM TRACKING METRICS PROJECT STATUS DATE: 10/25/2012 EV = 50 per-hrs / 244 per-hrs = 19% SV = 50 per-hrs – 50 per-hrs = 0  on schedule CV = 50 per-hrs – 42 per-hrs = 8  8 per-hrs cost under-run SPI = 50 per-hrs / 50 per-hrs = 1  on schedule CPI = 50 per-hrs / 42 per-hrs = 1.2  CPI > 1 = cost under-run

  16. APPENDIX A – PROJECT EFFORT FP ANALYSIS FOR ALL PROJECT BUSINESS REQUIREMENTS Rational: FP methodology was used to calculate project effort based on the business requirements and the design of the PMSA database as it was agreed by the team this would be more accurate than LOC.

  17. APPENDIX A – PROJECT EFFORT FP ANALYSIS FOR ALL PROJECT BUSINESS REQUIREMENTS (con’t)

  18. APPENDIX B – COMPLETE LIST OF PROJECT REQUIREMENTS

  19. APPENDIX B – COMPLETE LIST OF PROJECT REQUIREMENTS (con’t)

  20. APPENDIX B – COMPLETE LIST OF PROJECT REQUIREMENTS (con’t)

  21. APPENDIX C – PMSA Database ERD

More Related