Craft "High-Quality" Requirements
From the Voices on Project Management Blog
by Cameron McGaughy,
Lynda Bourne, Kevin Korterud, Peter Tarhanidis, Conrado Morlan, Jen Skrabak, Mario Trentim, Christian Bisson, Yasmina Khelifi, Sree Rao, Soma Bhattacharya, Emily Luijbregts, David Wakeman, Ramiro Rodrigues, Wanda Curlee, Lenka Pincot, cyndee miller, Jorge Martin Valdes Garciatorres, Marat Oyvetsky
Voices on Project Management offers insights, tips, advice and personal stories from project managers in different regions and industries. The goal is to get you thinking, and spark a discussion. So, if you read something that you agree with--or even disagree with--leave a comment.
View Posts By:
Cameron McGaughy
Lynda Bourne
Kevin Korterud
Peter Tarhanidis
Conrado Morlan
Jen Skrabak
Mario Trentim
Christian Bisson
Yasmina Khelifi
Sree Rao
Soma Bhattacharya
Emily Luijbregts
David Wakeman
Ramiro Rodrigues
Wanda Curlee
Lenka Pincot
cyndee miller
Jorge Martin Valdes Garciatorres
Marat Oyvetsky
Past Contributors:
Rex Holmlin
Vivek Prakash
Dan Goldfischer
Linda Agyapong
Jim De Piante
Siti Hajar Abdul Hamid
Bernadine Douglas
Michael Hatfield
Deanna Landers
Kelley Hunsberger
Taralyn Frasqueri-Molina
Alfonso Bucero Torres
Marian Haus
Shobhna Raghupathy
Peter Taylor
Joanna Newman
Saira Karim
Jess Tayel
Lung-Hung Chou
Rebecca Braglio
Roberto Toledo
Geoff Mattie
Recent Posts
Project 2030: Skills We Need to Cultivate Now
The Technical Program Manager: How to Stay Relevant in 2025
5 Things Your Operational Plan Should Do
5 New Project Guardrails for Adaptive Leaders
The Leader's Voice: Respect It, Protect It, and Use It Properly!
Categories
2020,
Adult Development,
Agile,
Agile,
Agile,
agile,
Agile management,
Agile management,
Agile;Community;Talent management,
Artificial Intelligence,
Backlog,
Basics,
Benefits Realization,
Best Practices,
BIM,
business acumen,
Business Analysis,
Business Analysis,
Business Case,
Business Intelligence,
Business Transformation,
Calculating Project Value,
Canvas,
Career Development,
Career Development,
Career Help,
Career Help,
Career Help,
Career Help,
Careers,
Careers,
Careers,
Careers,
Categories: Career Help,
Change Management,
Cloud Computing,
Collaboration,
Collaboration,
Collaboration,
Collaboration,
Collaboration,
Communication,
Communication,
Communication,
Communication,
Communications Management,
Complexity,
Conflict,
Conflict Management,
Consulting,
Continuous Learning,
Continuous Learning,
Continuous Learning,
Continuous Learning,
Continuous Learning,
Cost Management,
COVID-19,
Crises,
Crisis Management,
critical success factors,
Cultural Awareness,
Culture,
Decision Making,
Design Thinking,
Digital Project Management,
Digital Transformation,
digital transformation,
Digitalisation,
Disruption,
Diversity,
Diversity,
Documentation,
Earned Value Management,
Education,
EEWH,
Enterprise Risk Management,
Escalation management,
Estimating,
Ethics,
execution,
Expectations Management,
Facilitation,
feasibility studies,
Future,
Future of Project Management,
Generational PM,
Governance,
Government,
green building,
Growth,
Horizontal Development,
Human Aspects of PM,
Human Aspects of PM,
Human Aspects of PM,
Human Aspects of PM,
Human Aspects of PM,
Human Resources,
Inclusion,
Information Technology,
Innovation,
Intelligent Building,
International,
International Development,
Internet of Things (IOT),
Internet of Things (IoT),
IOT,
Knowledge,
Leadership,
Leadership,
Leadership,
Leadership,
Leadership,
lean construction,
LEED,
Lessons Learned,
Lessons learned;Retrospective,
Managing for Stakeholders,
managing stakeholders as clients,
Mentoring,
Mentoring,
Mentoring,
Mentoring,
Mentoring,
Methodology,
Metrics,
Micromanagement,
Microsoft Project PPM,
Motivation,
Negotiation,
Neuroscience,
neuroscience,
New Practitioners,
Nontraditional Project Management,
OKR,
Online Learning,
opportunity,
Organizational Culture,
Organizational Project Management,
Pandemic,
People management,
Planing,
planning,
PM & the Economy,
PM History,
PM Think About It,
PMBOK Guide,
PMI,
PMI EMEA 2018,
PMI EMEA Congress 2017,
PMI EMEA Congress 2019,
PMI Global Conference 2017,
PMI Global Conference 2018,
PMI Global Conference 2019,
PMI Global Congress 2010 - North America,
PMI Global Congress 2011 - EMEA,
PMI Global Congress 2011 - North America,
PMI Global Congress 2012 - EMEA,
PMI Global Congress 2012 - North America,
PMI Global Congress 2013 - EMEA,
PMI Global Congress 2013 - North America,
PMI Global Congress 2014 - EMEA,
PMI Global Congress 2014 - North America,
PMI GLobal Congress EMEA 2018,
PMI PMO Symposium 2012,
PMI PMO Symposium 2013,
PMI PMO Symposium 2015,
PMI PMO Symposium 2016,
PMI PMO Symposium 2017,
PMI PMO Symposium 2018,
PMI Pulse of the Profession,
PMO,
PMO,
pmo,
PMO Project Management Office,
portfolio,
Portfolio Management,
Portfolio Management,
portfolio management,
presentations,
Priorities,
Probability,
Problem Structuring Methods,
Process,
Procurement Management,
profess,
Program Management,
project,
Project Delivery,
Project Dependencies,
Project Failure,
project failure,
Project Leadership,
Project Management,
project management,
project management office,
Project Planning,
project planning,
Project Requirements,
Project Success,
Ransomware,
Reflections on the PM Life,
Remote,
Remote Work,
Requirements Management,
Research Conference 2010,
Researching the Value of Project Management,
Resiliency,
Risk Management,
Risk Management,
Risk management,
risk management,
ROI,
Roundtable,
Salary Survey,
Schedule Management,
Scheduling,
Scope Management,
Scrum,
search,
SelfLeadership,
SelfLeadership,
SelfLeadership,
SelfLeadership,
SelfLeadership,
Servant Leadership,
Sharing Knowledge,
Sharing Knowledge,
Sharing Knowledge,
Sharing Knowledge,
Sharing Knowledge,
Social Responsibility,
Sponsorship,
Stakeholder Management,
Stakeholder Management,
stakeholder management,
Strategy,
Strategy,
swot,
Talent Management,
Talent Management,
Talent Management,
Talent Management,
Talent Management,
Talent Management Leadership SelfLeadership Collaboration Communication,
Taskforce,
Teams,
Teams in Agile,
Teams in Agile,
teamwork,
Tech,
Technical Debt,
Technology,
TED Talks,
The Project Economy,
Timeline,
Tools,
tools,
Transformation,
transformation,
Transition,
Trust,
Value,
Vertical Development,
Volunteering,
Volunteering #Leadership #SelfLeadership,
Volunteering Sharing Knowledge Leadership SelfLeadership Collaboration Trust,
VUCA,
Women in PM,
Women in Project Management
Date
Project requirements derive from concrete business needs or business-use cases and constitute the foundation for the project work. Without requirements, projects cannot exist.
Incomplete and unclear requirements may result in project failure. Moreover a significant part of project rework is attributable to problems with the project requirements.
On the other hand, requirements that are clear, complete and understood by all the parties are of "high quality." They build a solid foundation for the project work.
Collecting high quality requirements can be a challenging endeavor for several reasons:
• Stakeholders often don't speak the same language (business vs. technical)
• Stakeholders have different understandings and views of the product
• Stakeholders have different backgrounds and expertise on the matter
It may not be the project manager's role to collect, qualify and write requirements. But he or she is often the one planning the framework and determining or approving the guidelines by which requirements are elicited, qualified and accepted.
The following guidelines should help in collecting high-quality project requirements:
1. No requirements without a use caseUsually, requirements can be linked to concrete business cases, which are generally task- and user-centric. Use cases help understanding the requirements' context and purpose.
2. Requirements languagePay attention to the wording. Avoid ambiguous words. Use words and terms consistently.
You might consider using a glossary of terms to ensure common understanding.
Avoid words that have subjective meaning (nice, substantial, safe, simple) and that enforce direction weakly or that undermine commitment (often, always, partially, usually). Use "shall" or "must" instead of "should" or "might."
Remove any room for interpretation. Avoid the usage of "and/or" together or "including but not limited to."
3. Requirements characteristics checklistBuild a checklist of requirements characteristics that are relevant to your project's quality standards. Evaluate each requirement against the checklist.
Here are 10 characteristics that I successfully use to evaluate the quality of requirements:
Atomic: Is this a single requirement or multiple requirements in one?
Complete: Is this comprehensive enough to start working on it?
Traceable: Is this related to a use-case or need?
Logical and Clear: Does it make sense? Does it leave no room for interpretation?
Consistent: Is this consistent with the project objectives and other related requirements?
Measurable: Is this measurable once a solution is delivered?
Compliant: Is this aligned to the current product features, system architecture and legal framework?
Feasible: Is this realistic and doable given the complexity and the project context and constraints?
Necessary: Is this really required given the project objectives and constraints? Or is it more of a want than a need?
Prioritized: What are its criticality, urgency and priority?
What best practices do you use to ensure that project requirements are of high quality?
Posted
by
Marian Haus
on: April 18, 2012 12:51 PM |
Permalink
Comments (1)
Please login or join to subscribe to this item
Thank you, very good reading
Please Login/Register to leave a comment.
|
"The remarkable thing about television is that it permits several million people to laugh at the same joke and still feel lonely."
- T.S. Eliot
|
