-
Management by Heroics
May 22, 2012
-
Project Planning for Project Sponsors: Why You Need To Be Involved
May 22, 2012
-
Lost in Projects - Integrated Project Management
May 22, 2012
-
10 Warning Signs that Your SharePoint Implementation May Be Heading for Difficulty
May 21, 2012
-
Smaller is Better and More Effective
May 21, 2012
-
Finding the Roots of Organizational Incompetence
May 21, 2012
-
Project Management Office Basics: Six Secrets For Efficient Shared Services
May 20, 2012
-
Project Management Foundations - What Makes Projects Fun?
May 19, 2012
-
How to Make a SWOT Analysis
May 18, 2012
-
Brutal ICT Development Project Classification
May 18, 2012
Kano and Quality Requirements
August 8, 2008 | Author: PM Hut | Filed under: Quality Management, Requirements Management
Kano and Quality Requirements
By Craig Brown
Project requirements specifications identify what the project has to change. An understanding of the business processes and the business data with their related problems and opportunities, as well as environmental constraints and guides is required to fully understand requirements.
Requirements can also be categorised into classes along the lines of the Kano model:
- Threshold / Basic attributes
- One-dimensional attributes (Performance/Linear)
- Attractive attributes (Exciters/Delighters)
All threshold requirements must be met, one-dimensional requirements should be weighed on cost-benefit assessments while attractive attributes should be included wherever possible, but are the ones usually washed out by time and cost considerations.
Craig Brown has worked as a project manager and business analyst mainly in the Australian ITC and the banking industries. He has also worked in the law, education and welfare industries, including starting a law firm. Craig now has a Master’s degree in project management from RMIT university, and is currently working with a Melbourne based IT consulting firm called OptimiseIT. Craig’s personal blog can be found at http://betterprojects.blogspot.com.
Related Articles
No comments yet.
feel free to leave a comment
Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!
XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
All fields marked with " * " are required.
- Agile Project Management
- Ask the Hut
- Certification
- Change Management
- Communications Management
- Computer Based Information Systems
- Concepts
- Corporate Transformation
- Cost Management
- Critical Chain Project Management
- Delegation
- History
- HR Management
- Implementing Project Management
- Integration Management
- Lessons Learned
- Management
- Miscellaneous
- People Issues
- PMBOK
- PRINCE2
- Procurement Management
- Program Management
- Project Lifecycle Phases
- Project Management Advantages
- Project Management Advantages
- Project Management as a Career
- Project Management Best Practices
- Project Management Charts
- Project Management Definitions
- Project Management Ethics
- Project Management for Beginners
- Project Management Guides
- Project Management Musings
- Project Management Office
- Project Management Proposals
- Project Management Templates
- Project Portfolio Management
- Project Workforce Management
- Quality Management
- Requirements Management
- Risk Management
- Scheduling
- Scope Management
- SCRUM
- Soft Management
- Time Management
- Training
- Uncategorized