Project Quality Plan


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Project Quality Plan

  1. 1. PROJECT MODELS FOR SYSTEM UPGRADE BY: JASON E LEWIS DATE: 9/04/2009 Comparing Project Management Models & Methodologies
  2. 2. Project Summary <ul><li>Discussion o f comparing Project Management Models for the Email systems upgrade </li></ul><ul><li>Discussion of a variety of Project Management Methodologies </li></ul><ul><li>Discussion Models </li></ul><ul><ul><li>Dynamic Systems Development Model </li></ul></ul><ul><ul><li>Maturity Model </li></ul></ul><ul><ul><li>Prince2 Model </li></ul></ul><ul><ul><li>Waterfall Model </li></ul></ul><ul><ul><li>Spiral Model </li></ul></ul><ul><li>Project Summary/ Problem Statement </li></ul><ul><ul><li>Identified email system business interruptions </li></ul></ul><ul><ul><li>Identified the need for the reduction of redundant systems </li></ul></ul><ul><li>Focus </li></ul><ul><ul><li>New email standards </li></ul></ul><ul><ul><li>Upgrade of the email system </li></ul></ul><ul><ul><li>One email system </li></ul></ul><ul><li>Scope </li></ul><ul><ul><li>Consolidation of the five email systems </li></ul></ul><ul><ul><li>Users will have both LAN and Remote access to email </li></ul></ul><ul><ul><li>User PCs will be upgraded to accommodate the new email system </li></ul></ul><ul><ul><li>Take advantage of the opportunity to develop collaboration among the 12 departments </li></ul></ul><ul><ul><li>Maximize coat savings potential by generating direct coat savings </li></ul></ul>
  3. 3. Dynamic Systems Development Model (DSDM ) <ul><li>DSDM was developed in the U.K. in the mid 1990’s. </li></ul><ul><li>Boast of being better than the Agile techniques. </li></ul><ul><li>Philosophy that nothing is built perfect. </li></ul><ul><li>Believes software is a exploratory endeavor. </li></ul><ul><li>Uses nine principles and five phases. </li></ul><ul><ul><ul><ul><li>Active user involvement </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Empowered teams that the authority to make decisions </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Focus on frequent delivery of products </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Fitness of business as the essential criterion for acceptance of deliverables </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Iterative and incremental development to ensure convergence on accurate business solutions </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Reversible changes during development </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Requirements that are baselined at a high level </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Integrated testing throughout the life cycle </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Collaboration and cooperation between all stakeholders </li></ul></ul></ul></ul>
  4. 4. Maturity Model <ul><li>Model was formed t refine an organization software development process. </li></ul><ul><li>Methodology is to optimize the development process. </li></ul><ul><li>It is used by DOD and is promoted by SEI and was founded in 1984. </li></ul><ul><li>Easily establishes the framework for continuous process improvement. </li></ul><ul><li>Has five maturity levels and operates on the following. </li></ul><ul><ul><ul><li>Initial Level </li></ul></ul></ul><ul><ul><ul><li>Repeatable Level </li></ul></ul></ul><ul><ul><ul><li>Defined Level </li></ul></ul></ul><ul><ul><ul><li>Managed Level </li></ul></ul></ul><ul><ul><ul><li>Optimizing Level </li></ul></ul></ul>
  5. 5. Prince2 Model <ul><li>Prince2 is a project management Methodology that is process-based. </li></ul><ul><li>Has Eight high level processes. </li></ul><ul><ul><ul><li>Directing a Project </li></ul></ul></ul><ul><ul><ul><li>Planning </li></ul></ul></ul><ul><ul><ul><li>Starting up a Project </li></ul></ul></ul><ul><ul><ul><li>Initiating the Project </li></ul></ul></ul><ul><ul><ul><li>Controlling a Stage </li></ul></ul></ul><ul><ul><ul><li>Managing Product Delivery </li></ul></ul></ul><ul><ul><ul><li>Managing Stage Boundaries </li></ul></ul></ul><ul><ul><ul><li>Closing a Project </li></ul></ul></ul>
  6. 6. WaterFall Model <ul><li>Waterfall model is a methodology for software engineering. </li></ul><ul><li>Considered a classic approach to the systems development life cycle. </li></ul><ul><li>The model is a development method that is rigid and linear. </li></ul><ul><li>Often falls short of expectations as it does not embrace the inevitable changes and revisions. </li></ul><ul><li>Difficult to make changes during testing. </li></ul><ul><li>Alternatives to the Waterfall model include </li></ul><ul><ul><ul><li>JAD – creates a shorter development time and greater customer </li></ul></ul></ul><ul><ul><ul><li>satisfaction </li></ul></ul></ul><ul><ul><ul><li>RAD - is a variation on JAD, creates an application more quickly through </li></ul></ul></ul><ul><ul><ul><li>strategies that include fewer formal methodologies </li></ul></ul></ul>
  7. 7. Spiral Model <ul><li>Extends the Waterfall model by prototyping and is preferred over Waterfall. </li></ul><ul><li>Has Nine high-level steps </li></ul><ul><ul><ul><li>System requirements needs to be defined in large detail. </li></ul></ul></ul><ul><ul><ul><li>A preliminary design is created for the implementation. </li></ul></ul></ul><ul><ul><ul><li>First prototype for the new system is constructed off of the preliminary design. </li></ul></ul></ul><ul><ul><ul><li>At the second prototype evolves four steps. </li></ul></ul></ul><ul><ul><ul><ul><ul><li>Evaluate the first prototype </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Define the requirements of the second stage </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Plan and design the second prototype </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Construct and test the second prototype </li></ul></ul></ul></ul></ul><ul><ul><ul><li>Sponsor can choose to stop the project due to high risk factors shown during prototype. </li></ul></ul></ul><ul><ul><ul><li>The prototype is evaluated in the same way as the previous prototype </li></ul></ul></ul><ul><ul><ul><li>The preceding steps are iterated until the customer is satisfied </li></ul></ul></ul><ul><ul><ul><li>The final system is constructed based on the refined prototype </li></ul></ul></ul><ul><ul><ul><li>The final system is thoroughly evaluated and tested </li></ul></ul></ul>
  8. 8. Benefits of Implementing Spiral Model <ul><li>Easy to implement </li></ul><ul><li>Customizable for company size </li></ul><ul><li>Implementation in months not years </li></ul><ul><li>Increase Profitability </li></ul><ul><li>Reduce paperwork </li></ul><ul><li>Ability to track business </li></ul><ul><li>Generate sales leads </li></ul><ul><li>Technical support available </li></ul>
  9. 9. References <ul><li>  Active Directory & E-Mail Consolidation.(2005) Category Enterprise IT Management Initiatives . Retrieved August 29 th , 2009 from </li></ul><ul><li> </li></ul><ul><li> Project Management Models . Retrieved September 2, 2009 from </li></ul><ul><li>Cutter Consortium Business Intelligence.(2006) A Strategy for implementing BI/BPM to gain competitive advantage . Retrieved August 18, 2009 from </li></ul><ul><li> </li></ul><ul><li>Computer Security Resource Center (May 8, 2009). Risk Management Framework (RMF) Overview. Retrieved August 21, 2009 from </li></ul><ul><li> </li></ul><ul><li> Waterfall/spiral. Retrieved September 2, 2009 from </li></ul><ul><li>  </li></ul><ul><li>Statz, J. TeraQuest Metrics, Inc., Microsoft TechNet (December 1999). Site Server – Risk Management Process for Product Development, Retrieved August 21, 2009 from </li></ul><ul><li> </li></ul>