-
A Project Charter for Lazy Teams
February 8, 2012
-
The Power of Process: How Bad Project Management Kills Great Ideas
February 7, 2012
-
The Benefits of Virtual Project Management
February 7, 2012
-
Lessons Learned and the Project Council
February 7, 2012
-
Project Management Across the Knowledge Domain
February 6, 2012
-
Genius PMO: Five Steps to An Honest Project Team!
February 6, 2012
-
Low Bid Project Award: Friend or Foe?
February 6, 2012
-
The League of Project Superheroes
February 5, 2012
-
10 Essential Steps to Portfolio Management
February 4, 2012
-
Portfolio Management Process - The Process for the Process
February 3, 2012
Facilitating a Requirements Validation Meeting with Ease!
August 31, 2010 | Author: PM Hut | Filed under: Requirements Management
Facilitating a Requirements Validation Meeting with Ease!
By Dana Brownlee
The Problem
Ensuring that a requirements document is accurate, complete, and fully supported by key stakeholders can be critically important. Unfortunately, requirements validation sessions can be protracted and challenging. Oftentimes, the goal of the session is to gain agreement among various stakeholders on a lengthy, detailed requirements document. This can certainly be a tall order, but it can be done!!!
Consider These Suggestions:
- Ensure that all key stakeholders are present at the session. Oftentimes, senior managers or other extended team members will participate in this important session. Ensure that the meeting is on their schedule far in advance.
-
Conduct pre-meetings with relevant functional groups to work out the details, review appendices, etc. Ideally, there should be no major surprises at the validation meeting.
-
Ensure everyone comes to the meeting prepared by expressing the importance of each person reviewing the document in detail. Give the group a choice of whether to review the document in detail during the session (2 day offsite) or review it individually offline and only conduct a high level review and discuss questions during the validation session (2-3 hours). Most groups will opt for the shorter meeting.
-
Ask participants to send their questions three days prior to the session and follow up with anyone who has not sent their questions by the stated due date.
-
At the beginning of the meeting ask each person to introduce themselves and their role in case there are new faces in the room. Also, provide a high level overview of the project before getting into any detailed requirements discussion to ensure everyone has appropriate context.
-
Define any assumptions or acronyms at the beginning of the meeting to avoid misunderstandings
-
Assign specific SMEs to lead the discussion for individual sections of the document.
-
Ask for a volunteer to be the timekeeper and another to document key decisions or action items on a whiteboard or flipchart.
-
Ensure that the requirements document is well organized with prioritized requirements.
-
Post IEEE standards for well formed requirements (Accurate, Consistent, Complete, Traceable, Prioritized, Unambiguous, Modifiable, Verifiable and Testable) on the wall (or on a slide if using collaborative software). As you review individual requirements, ensure that each requirement meets this checklist.
-
Document traceability within the document and across documents.
-
Let participants know that signatures will be expected at the conclusion of the meeting. Ensure that participants sign the document on behalf of their organization.
© 2010 Professionalism Matters, Inc.
Dana Brownlee is President of Professionalism Matters, Inc. a boutique professional development corporate training firm. Her firm operates www.meetinggenie.com, an online resource for meeting facilitation tips, training, and instructional DVDs. Her latest publications are “Are You Running a Meeting or Drowning in Chaos?” and “5 Secrets to Virtually Cut Your Meeting Time in Half!” She can be reached at danapbrownlee@professionalismmatters.com.
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