Checklist to be used as a guide to navigate the 5 stages of the 6 Sigma DMAIC project methodology.
  • Mark all that apply.
  • DEFINE
    • Have you defined the project scope, objective, and schedule?
    • Have you defined the project team members?
    • Have you defined the stakeholders?
    • Have you gained authorization from the necessary project executive sponsors?
    • Have you assembled and trained the project team at a high level?
  • An appropriate benchmark has been chosen?
    • The Benchmark is based on statistical similar projects?
    • Average/median practice was used instead of best practice?
  • The benchmark has been compared to the forecast?
    • The variance of the forecast has been compared to the benchmark variance?
    • The forecast of ramp-up has been compared to the benchmark ramp-up?
    • The data used to create the forecast ramp-up has been provided?
  • The forecaster's track record has been reviewed and considered?
    • Did the forecaster provide ex post data on actual forecasting accuracy?
    • The available data for actual performance indicates accurate forecasts?
    • There is no "Bad Press" on the forecaster?
  • Further demand risks have been identified? Consider using PESTEL analysis:
    • Political
    • Economic
    • Social
    • Technological
    • Environmental
    • Legal
  • The expected outcome based on the benchmark analysis has been calculated?
  • The forecaster has been given the opportunity to respond to the analysis?
    • The forecaster's response is factual and supported by evidence?
    • The forecaster's response does not rely on the "uniqueness" of projects?
    • The forecaster's response does not rely on the "confidentiality" of projects?
*As based on original work by Professor Bent Flyvbjerg
 
Checklist ensures a proper record of information is kept about each project configuration item.
 
  • Mark all that apply.
    • A process exist by which the Configuration Item Records are defined and updated.
    • Configuration Item Records show products' version histories.
    • Configuration Item Records show products' version history dates.
    • Configuration Item Records show products' version history owner.
    • The records are kept together in a secure location.
    • The records reflect the status of the products accurately.
    • Version numbers match the actual products.
     
    Checklist to ensure the project Daily Log is used effectively.
     
  • Mark all that apply.
    • Consideration has been given to access rights for the Daily Log.
    • Date, person responsible and target date are always filled in.
    • Entries are sufficiently documented to be understandable later.
     
    To be used when creating and approving the project Communication Management Strategy document.
     
  • Mark all that apply.
  • A common standard for communication has been considered.
  • All stakeholders have been identified and consulted for their communication requirements.
  • For projects that are part of a programme, the lines of communication, and the reporting structure between the project and programme, have been made clear in the Communication Management Strategy.
  • The Communication Management Strategy incorporates corporate communications facilities where appropriate.
  • The formality and frequency of communication is reasonable for the project’s importance and complexity.
  • There is agreement from all stakeholders about the content, frequency and method of communication.
  • The time, effort and resources required to carry out the identified communications have been allowed for in Stage Plans.
  •  
    For general guidelines for professional communication, see also 7 "C"s of Communication Checklist
    To be used throughout the "Initiating a Project" process. We suggest submitting a completed checklist at the initiation end stage assessment!
     
  • Mark all that apply.
  • Are any project interdependencies stated?
  • Are project tolerances defined?
  • Are reporting procedures, contents and frequencies defined?
  • Are the project objectives stated?
  • Are the reasons for the project given?
  • Did the Project Board formally approve the PID?
  • Was the Project Board committed to the process?
  • Does the PID contain the Project Plan?
  • Has the Configuration Management Strategy been defined?
  • Has the Risk Management Strategy been defined?
  • Have project constraints been identified?
  • Is the PID produced to PRINCE2 or company specific standards?
  • Is the project scope stated?
  • Is there a Business Case in the Project Initiation Documentation?
  • Is there a Communication Management Strategy (plan) covering both inward and outward communication needs?
  • Is there an investment appraisal or cost benefit analysis?
  • Is there Project Initiation Documentation (PID)?
  • Was initiation done before work on Products began?
  • Was the initiation stage formally authorised?
  • Was the next Stage Plan presented at the initiation end stage assessment?
  • Was the PID quality reviewed?
  • Was there an initiation end stage assessment (Authorising a Project)?
  • Were the Authorising Initiation agenda items covered?
  •