Please enable JavaScript.

Coggle requires JavaScript to display documents.

QUALITY Product Focus (Purpose (The PRINCE2 quality theme ensure that a…

- - - - The Customer Quality expectations are a statement about the quality expected from the project product, captured in the Project Product Description
      - The expecton s are defined and agreed early in the Starting up a project Process
      - The key quality requirments will drive the choice of solution.
      - Note the impact each of these choices might have on Time, Cost , Scope, Risk and Benefit performance target
      - The customer's quality expection are often expressed in broad terms intially, the detailed acceptance criteria being derived later.
      - The Customer quality expectations should be priorized wher possible
      - The customer's quality expecations should be reviewed at the end of each managment stage
      - They should Cover
        
        Any Measurements that may be useful to assess whether the Project Product meets the quality requirements
        
        Any Standards and processes that will need to be applied
        
        The Key quality Requirments
    - - A Project Acceptance Criteria comprise a prioritized list of criteria that the project product must meet before the customer will accept it, i.e. measurable definitions of the attributes required for the set of product to be acceptable to key stakeholeders
      - When a project has met all acceptance Criteria, it can be closed
      - The Acceptance Criteria should be agreed by the customer and supplier during Starting up a Project and documented in the Project Product Description. The acceptance criteria will often need refinement during initiating a project, but once agreed will be under change control
      - The Choice of acceptance method is crucial as it is relied on to prove that the project product is acceptable.
      - MoSCoW
      - Examples of acceptance criteria include ease of maintenance, appearance, capacity, reliability and security
    - - The Project Product Description is a special type of Product Description that is used to gain agreement from the user on the Project scope :star:and requirements, to define the customer's quality expectations and to define the acceptance criteria for the project
      - The Project Product Descripton is created during starting up a project and may be refined during Initiating a Project.
      - It is subject to change control and should be reviewed at stage boundaries
      - During Closing a project it is used to check that the project has delivered what was expected and that the acceptance criteria haven been met
      - The approved Project Product Description is included in the Project Brief :star:and is used to help select the project approach.
    - - The Quality Management Strategy is used to define the quality techniques and standards to be applied and the various responsibilities for achieving the required quality levels, during the project
      - The Quality mangement strategy is prepared during Initiating a Project and subsequently approved by the Project Board
      - It Describes how the quality management Systems of the participating organizations are going to be applied in this project. It also confirms any quality standards, Procedures, Tools and techinques that will be used
      - It also help to define how the Level of formality to be applied to quality can be scaled and agreed for teh specific project needs.
      - It should include details of quality assurance to be applied and of any independent audits.
      - It defines key responsibilities for quality, including a summary of the approach to project Assurance.
      - If the project is part of a programme with its own Quality Management Strategy it is only necessary to document measures that are specific to the project
      - The Quality management Strategy is maintained under change control throughout the life of the project
    - - The Purpose of a product Descriptoin is to :
        
        Understand the detailed nature, purpose, fucntion and appearance fo the Product.
        
        Define who will use the product
        
        Identifiy the source of information or supply for the product
        
        Identifiy the level of quality required of the product
        
        enable identification of activities to produce, review and approve the product
        
        Defin the people or skills required to produce, review and approve the product
      - Product Description for all of the projects' products are created once detailed planning gets underway
      - The Level of detail in Product Description is rather subjective, but there must be enough detail to provide a secure and appropriate measure of control sufficient to fulfill the customer's quality expectations.
      - IN a product Description, Note the sections specific to
        
        Quality Criteria
        
        Quality Tolerance
        
        Quality Method
        
        Quality Skills required
        
        Quality Responsibilites
      - Although Product Description should contain enough detail to fulfill their purpose, they should also not contain too much detail or they could unnecessarily increase the cost of quality for the product
      - Various factors will determine how long it takes to produce good Product Descriptions including how important, complex and unique each product is and how many stakeholders will review and approve each product
      - The quality criteria comprise the quality specifications that each product must meet and the quality measurements that will be applied
      - Quality tolerance can be specified as a range of values, e.g "60 mintues plus or minus 5 Minutes"
      - Quality methods are all of the activities related to quality during the development of a product and its final review and approval. Any specialized skills needed should be specified.
      - The two primary types of quality method are
        
        In-process methiods
        
        Appraisal Methods
      - Quality Responsilbility fall into three Categories
        
        Producer
        
        Reviewer
        
        Approver
    - - The Quality Register is a sort f "Diary" of planned and undertaken quality events.
      - The quality register is created during Initiating a project and Maintained througout the life of the project
      - the Quality register provides key audit and assurance information
      - the level of detail required will vary but make sure that there is enough information ot assist with process improvement
    - - Understanding the costumer's quality expectations
      - Defining the project's acceptance criteria
      - Documenting the customer's quality expectations and the project's acceptance criteria in the Project Product Description
      - Formulating a quality Management Strategy
      - Writing Clear Product Descriptions
      - setting up the Quality register
  - - - Project board agreement on the overall quality expectations, products required together with their quality criteria, the means by which quality will be achieved and assessed and the associated acceptance criteria
      - communicating these agreements to project stakeholders
      - Establishing an effective baseline for the project quality controls and thereby achieving products that are fit for purpose
- - - - Inprocess Method
        
        where by the quality is " built in " as the product are developed. often specialist tools and techniques are used such as piloting exercises and calibrated controls. But it is also beneficial to use quality inspections early on rather than just at completion.
      - Appraisal Method
        
        Where by finished products are assessed for completeness and fitness for purpose. Appraisal method fall into two groups:
        
        Testing , Where the quality criteria are sufficiently objective
        
        Quality inspection , where an element of subjective judgment is required
        
        A Quality inspection is a systematic, structured assessment of a prodcut conducted in a planned, documented and organized fashion
        
        Quality inspection can be used
        
        During Product development , either formally or informally
        
        To mark compleation and approval of products
        
        To complement Testing
        
        Various Systematic inspection techiques are available, but PRINCE2 also provides its own quality review techniques
        
        The PRINCE2 quality review technique is designed to work along side PRINCE2 product Descripiton
        
        Team
        
        Chair
        
        Presenter
        
        Reviewer
        
        Adminstrator
  - - - Product are complete
      - Products have met their quality criteria ( or not)
      - Agreed Process have been obsereved
      - Approval authorities and any key product stakeholders are satisfied
      - Planned audits have been conducted and reported
  - - - A signed document
      - an email or letter
      - a note in the minutes of a meeting
- - - - Fulfill the requirement for quality
      - Identify ways of eliminating causes of unsatisfactory