Question Description

From your experience, you already know the value of a comprehensive quality assurance plan. In order to convince the NearlyFree.com management that the NEO project turnaround will be successful you will perform the following tasks.

  • Prepare a cost of quality (COQ) analysis using a common method to classify cost. See Project Management – A Systems Approach to Planning, Scheduling and Controlling, Chapter 20, “Quality Management,” Section 20.8 (pages 890–893) and the PMBOK® Guide Section 8.1.2.2. (page 235).
  • Develop a Quality Assurance Plan for both planned and systematic activities.
  • Explain how the Quality Assurance Plan supports project quality. Consider its impact throughout the project.
Task Name Work
NearlyFree Employee Orientation Project 992 hrs
  Initiating 0 hrs
   Develop project charter 0 hrs
   Review charter 0 hrs
   Charter signed 0 hrs
  Planning 272 hrs
   PM Jones 136 hrs
   Develop project plan 128 hrs
   PM Jones 128 hrs
   Review project plan 8 hrs
   PM Jones 8 hrs
   Project plan approved 0 hrs
   PM Jones 0 hrs
    Kickoff Meeting 0 hrs
   PM Jones 0 hrs
  Executing 712 hrs
   Interface Requirement 24 hrs
   Tom Johansen Webmaster 24 hrs
   Software Requirement 32 hrs
   Alice Yee Software Specialist 32 hrs
   User Documentation 16 hrs
   Alice Yee Software Specialist 16 hrs
   Training Materials 48 hrs
   Cheryl Gladstone HR Manager 48 hrs
   Product Requirements Review Meeting 20 hrs
   Tom Johansen Webmaster 4 hrs
   Alice Yee Software Specialist 4 hrs
   John Sachs Quality Assurance Admin 4 hrs
   Cheryl Gladstone HR Manager 4 hrs
   PM Jones 4 hrs
   Construction 392 hrs
   Develop Software Application 360 hrs
   Analyze Interface Needs 16 hrs
   Tom Johansen Webmaster 16 hrs
   Analyze Software Needs 16 hrs
   Alice Yee Software Specialist 16 hrs
   Write Interface Specs 80 hrs
   Tom Johansen Webmaster 80 hrs
   Write Software Specs 80 hrs
   Alice Yee Software Specialist 80 hrs
   Code Software Application 80 hrs
   Alice Yee Software Specialist 80 hrs
   Develop Interface 40 hrs
   Tom Johansen Webmaster 40 hrs
   Test Interface 16 hrs
   Tom Johansen Webmaster 16 hrs
   Test Software Application 16 hrs
   Alice Yee Software Specialist 16 hrs
   Application Development Review Meeting 16 hrs
   Tom Johansen Webmaster 4 hrs
   Alice Yee Software Specialist 4 hrs
   John Sachs Quality Assurance Admin 4 hrs
   PM Jones 4 hrs
   Develop User Documentation 16 hrs
   Alice Yee Software Specialist 16 hrs
   Develop Training Materials 16 hrs
   Cheryl Gladstone HR Manager 16 hrs
   Integration and Testing 64 hrs
   Put Application on Intranet 24 hrs
   Tom Johansen Webmaster 24 hrs
   Quality Assurance Test 24 hrs
   John Sachs Quality Assurance Admin 24 hrs
   Integraton and Testing Review Meeting 16 hrs
   Tom Johansen Webmaster 4 hrs
   Alice Yee Software Specialist 4 hrs
   John Sachs Quality Assurance Admin 4 hrs
   PM Jones 4 hrs
   Training 116 hrs
   Software Training for HR 96 hrs
   Tom Johansen Webmaster 24 hrs
   Alice Yee Software Specialist 24 hrs
   Cheryl Gladstone HR Manager 24 hrs
   PM Jones 24 hrs
   Training Review Meeting 20 hrs
   Tom Johansen Webmaster 4 hrs
   Alice Yee Software Specialist 4 hrs
   Cheryl Gladstone HR Manager 4 hrs
   Jennifer Beal Project Sponsor 4 hrs
   PM Jones 4 hrs
  Controlling 0 hrs
   Status Report 0 hrs
   Status Report 1 0 hrs
   Status Report 2 0 hrs
   Status Report 3 0 hrs
   Status Report 4 0 hrs
   Status Report 5 0 hrs
   Status Report 6 0 hrs
   Status Report 7 0 hrs
   Status Report 8 0 hrs
   Status Report 9 0 hrs
   Status Report 10 0 hrs
   Status Report 11 0 hrs
   Status Report 12 0 hrs
   Status Report 13 0 hrs
   Status Report 14 0 hrs
   Status Report 15 0 hrs
   Status Report 16 0 hrs
   Status Report 17 0 hrs
   Status Report 18 0 hrs
   Change reports 0 hrs
  Project Close 8 hrs
   PM Jones 4 hrs
   Post Mortem Lessons Learned 4 hrs
   PM Jones 4 hrs

Total Cost of Quality =External Failure + Internal Failure + Appraisal + Prevention Costs

Project activity

Hours spent

Is part of CoQ

Componenet of CoQ

The following table identifies:

  • Theproject processes subject to quality assurance.
  • Thequality standards and stakeholder expectations for that process.
  • Thequality assurance activity – e.g., quality audit or reviews, code review -that will be executed to monitor that project processes are properlyfollowed.
  • Howoften or when the quality assurance activity will be performed.
  • Thename of the person responsible for carrying out and reporting on thequality assurance activity.

Project Process

Process Quality Standards/

Stakeholder Expectations

Quality Assurance Activity

Frequency/Interval

Who is Responsible

Example:

Review software development practices ofsoftware application X.

Software requirements specification.

Developers have completely and accuratelycaptured application requirements.

Peer review of software requirementsspecification.

At regular intervals during the collectionof requirements and a final review at the conclusion of requirementscollection.

Lead developer in conjunction with otherknowledgeable developers.

From your experience, you already know the value of a comprehensive quality assurance plan. In order to convince the NearlyFree.com management that the NEO project turnaround will be successful you will perform the following tasks.Prepare a cost of quality (COQ) analysis using a common method to classify cost. See Project Management – A Systems Approach to Planning, Scheduling and Controlling, Chapter 20, “Quality Management,” Section 20.8 (pages 890–893) and the PMBOK® Guide Section 8.1.2.2. (page 235).Develop a Quality Assurance Plan for both planned and systematic activities.Explain how the Quality Assurance Plan supports project quality. Consider its impact throughout the project. Task Name Work NearlyFree Employee Orientation Project 992 hrs   Initiating 0 hrs    Develop project charter 0 hrs    Review charter 0 hrs    Charter signed 0 hrs   Planning 272 hrs    PM Jones 136 hrs    Develop project plan 128 hrs    PM Jones 128 hrs    Review project plan 8 hrs    PM Jones 8 hrs    Project plan approved 0 hrs    PM Jones 0 hrs     Kickoff Meeting 0 hrs    PM Jones 0 hrs   Executing 712 hrs    Interface Requirement 24 hrs    Tom Johansen Webmaster 24 hrs    Software Requirement 32 hrs    Alice Yee Software Specialist 32 hrs    User Documentation 16 hrs    Alice Yee Software Specialist 16 hrs    Training Materials 48 hrs    Cheryl Gladstone HR Manager 48 hrs    Product Requirements Review Meeting 20 hrs    Tom Johansen Webmaster 4 hrs    Alice Yee Software Specialist 4 hrs    John Sachs Quality Assurance Admin 4 hrs    Cheryl Gladstone HR Manager 4 hrs    PM Jones 4 hrs    Construction 392 hrs    Develop Software Application 360 hrs    Analyze Interface Needs 16 hrs    Tom Johansen Webmaster 16 hrs    Analyze Software Needs 16 hrs    Alice Yee Software Specialist 16 hrs    Write Interface Specs 80 hrs    Tom Johansen Webmaster 80 hrs    Write Software Specs 80 hrs    Alice Yee Software Specialist 80 hrs    Code Software Application 80 hrs    Alice Yee Software Specialist 80 hrs    Develop Interface 40 hrs    Tom Johansen Webmaster 40 hrs    Test Interface 16 hrs    Tom Johansen Webmaster 16 hrs    Test Software Application 16 hrs    Alice Yee Software Specialist 16 hrs    Application Development Review Meeting 16 hrs    Tom Johansen Webmaster 4 hrs    Alice Yee Software Specialist 4 hrs    John Sachs Quality Assurance Admin 4 hrs    PM Jones 4 hrs    Develop User Documentation 16 hrs    Alice Yee Software Specialist 16 hrs    Develop Training Materials 16 hrs    Cheryl Gladstone HR Manager 16 hrs    Integration and Testing 64 hrs    Put Application on Intranet 24 hrs    Tom Johansen Webmaster 24 hrs    Quality Assurance Test 24 hrs    John Sachs Quality Assurance Admin 24 hrs    Integraton and Testing Review Meeting 16 hrs    Tom Johansen Webmaster 4 hrs    Alice Yee Software Specialist 4 hrs    John Sachs Quality Assurance Admin 4 hrs    PM Jones 4 hrs    Training 116 hrs    Software Training for HR 96 hrs    Tom Johansen Webmaster 24 hrs    Alice Yee Software Specialist 24 hrs    Cheryl Gladstone HR Manager 24 hrs    PM Jones 24 hrs    Training Review Meeting 20 hrs    Tom Johansen Webmaster 4 hrs    Alice Yee Software Specialist 4 hrs    Cheryl Gladstone HR Manager 4 hrs    Jennifer Beal Project Sponsor 4 hrs    PM Jones 4 hrs   Controlling 0 hrs    Status Report 0 hrs    Status Report 1 0 hrs    Status Report 2 0 hrs    Status Report 3 0 hrs    Status Report 4 0 hrs    Status Report 5 0 hrs    Status Report 6 0 hrs    Status Report 7 0 hrs    Status Report 8 0 hrs    Status Report 9 0 hrs    Status Report 10 0 hrs    Status Report 11 0 hrs    Status Report 12 0 hrs    Status Report 13 0 hrs    Status Report 14 0 hrs    Status Report 15 0 hrs    Status Report 16 0 hrs    Status Report 17 0 hrs    Status Report 18 0 hrs    Change reports 0 hrs   Project Close 8 hrs    PM Jones 4 hrs    Post Mortem Lessons Learned 4 hrs    PM Jones 4 hrs Total Cost of Quality = External Failure + Internal Failure + Appraisal + Prevention Costs Project activity Hours spent Is part of CoQ Componenet of CoQ The following table identifies: The project processes subject to quality assurance. The quality standards and stakeholder expectations for that process. The quality assurance activity – e.g., quality audit or reviews, code review – that will be executed to monitor that project processes are properly followed. How often or when the quality assurance activity will be performed. The name of the person responsible for carrying out and reporting on the quality assurance activity. Project Process Process Quality Standards/ Stakeholder Expectations Quality Assurance Activity Frequency/Interval Who is Responsible Example: Review software development practices of software application X. Software requirements specification. Developers have completely and accurately captured application requirements. Peer review of software requirements specification. At regular intervals during the collection of requirements and a final review at the conclusion of requirements collection. Lead developer in conjunction with other knowledgeable developers.