Your SlideShare is downloading. ×
Project Quality Plan
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Project Quality Plan

1,050
views

Published on


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,050
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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

×