Example Critical To Quality (CTQ) Assessment Survey
This is a brief survey
There are two purposes for this survey.
- This survey is here to gather “Critical To Quality” (CTQ) assessments for the design
of a small project portfolio database. This is my fourth iteration of this project.
Once for SiteLite, once for Ameriquest, once for Tickets.com and now for my web
site as a part of a Six Sigma demonstration project.
- This survey is also here as a demonstration of the Design for Six Sigma (DFSS)
approach to a development project.
There are only a few questions. I do not think this should take
you more than ten minutes to complete. First, however, we need a common understanding
on a couple key concepts.
- White space is the blank area on a screen. Each design needs to balance the
density of the information with the amount of white space. More white space
makes the screen easier to look at. More information means there are fewer
screens.
- We all have preferences. THink about your preferences.
Would you like to be able to view all the details about a project on one screen, or
would you prefer to push buttons in order to get more information.
Let’s start with some specifics.
|
1. Do you need to see all of the history of prior activities on the main screen for the project?
| | | One screen with everything
| | | One screen with current activities and a button to click to view the history
|
|
2. Do you want to see a complete list of all the projects on one screen?
| | | One screen with everything
| | | One screen with just my projects and a button to click to see other projects
| | | One screen with only my current projects and a button to see other projects
|
|
3. Look at the format of this survey. Is this a good balance of information and white space?
| | | I would prefer more information and less white space
| | | This is a perfect balance
| | | I would like more white space
|
Here are a few more definitions that you will need for the second part of this survey.
The PMI hierarchy of objects is:
- Enterprise – the entire group of projects for the company or division
- Portfolio – a group of projects focused on one business area
- Program – a grouping of interrelated projects
- Project – a temporary endeavor to create a unique product or service
- Package – the lowest level in a work breakdown structure
- Activity – the next decomposition below the package
- Task – a specific work item that is assigned to a specific resource
|
4. Is it important to be able to group all of the enterprise projects into one location?
| | | All projects need to be in one location
| | | The different divisions can manage their own projects
|
|
5. Is it important to be able to group all of the portfolios for one division in one location?
| | | All projects for the division need to be in one location
| | | The different departments should be allowed to manage their own portfolios
|
|
6. Do you use programs or do you manage each project separately?
| | | Programs are important
| | | Programs are used sometimes
| | | We never use programs
|
|
7. Do you consistently use a work breakdown structure, either as a diagram or just as a concept when laying out your project schedule?
| | | We always create a work breakdown structure as part of our methodology
| | | We use a work breakdown structure sometimes
| | | I think about a work breakdown structure and might put one on a white board
| | | We do not use work breakdown structures
|
|
8. Should your project management system be your time tracking system?
| | | We manage projects separately from how we track time
| | | We sometimes track time through our project management system
| | | We require that all resources use our project management system to report their time
|
Thank you. I appreciate the time you spent thinking about these questions.
|