Susanne Madsen - Developing Project Leaders
  • Home
  • Services
    • Workshops
    • Speaking
    • Coaching
    • Stress management
    • Testimonials
  • Bio
  • Books
  • Blog
  • Resources
  • Videos
  • Contact
  • Library

Top Tips for Gathering Requirements

5/7/2011

7 Comments

 
As a project manager, you may be in a situation where the customer
delivers the requirements to you in a neat and structured way ready for the team to estimate and deliver a solution. However, in many cases it is up to the project team to work with the customer and users to extract, analyse and
document what the requirements are. In that situation you may want to use the following tips: 

Agree the approach to managing requirements. First of all, agree with your team, customer and end users what the process will be for gathering, documenting and controlling requirements and who will be responsible for each part of the process. Formally capture the steps, tools and roles and responsibilities in a requirements management plan and get it signed off by the stakeholders.

Engage the right people. Make sure you talk to the end users and senior stakeholders who have the actual authority to sign off on requirements and who will ultimately be using the end product. They can tell you what they want and what they expect from the product you are building.

Be proactive. Do not sit back and wait for the customer to deliver a detailed, concise and well  structured requirements document. In most cases you need to be proactive and work with the stakeholders and end users to help them structure and articulate their needs. 

Organize a workshop.  Workshops are a very powerful technique for gathering requirements. Set up an initial workshop to uncover the vision and high level requirements. Involve all major stakeholders and make it last for several days if necessary. 
 
Describe the product vision. Take a top down view and capture the essence of the envisaged product to be developed. Determine the objectives, needs, wants, limitations and constraints. Document the vision and get the customer to sign it off.

Identify the users. Identify all the users who in one way or another will be using and interacting with the end product. Each user group is likely to have unique requirements to the product.

Specify what is out of scope. Specifically focus on and write down items that are out of scope. Make it as explicit as possible and clearly draw up the boundaries between what you will and what you will not deliver.

Analyze the problem. Agree with the senior stakeholders what the overall problem is that your product is there to resolve. Drill down and identify the problems behind the problem. Prioritize them and document them. 

Break the requirements down. Break the high level requirements and products down into its constituent parts. Set up workshops in turn which focus on specific parts or components of the product and involve the necessary stakeholders.  

Ask open questions. Engage all user groups, interview them and ask open questions about what they want from a specific component, product or sub-product. Ask them what the product will enable them to do and how they will be interacting with it. Focus on their needs and problems and how they will determine if the product works according to their specifications.

Be creative. Use a variety of techniques in addition to workshops such as, interviewing, storyboarding, brainstorming, role playing, and prototyping.

Verify the requirements. Play back your understanding of the requirements to the stakeholders to ensure they have been correctly captured and understood. Illustrate or demonstrate it in whichever way is the most effective and ensure the requirements get formally signed off.

Capture non-functional requirements. Capture all non-functional requirements which the users may not have thought of. This includes requirements around maintainability, scalability and performance. Seek to understand what will happen after the project completes and which requirements relate to the long term usability of the solution. 

Organize the requirements. Depending on the size of the project you may not be able to define the requirements in one single document. Maintain multiple requirements sets; one for each of the products and sub-product you have identified.   

Incorporate acceptance criteria and test cases. As you gather and document the requirements, simultaneously document how each product or requirement will be tested and what its acceptance criteria are. 

Use a requirements traceability matrix. Keep track of all requirements and their associated test cases in a requirements traceability matrix. It helps you carry out completeness checks and track the progression of each requirement. Get the matrix signed off so that it serves as a baseline scope document against which you can track and control changes.  On the RESOURCES page you will be able to download a requirements traceability matrix template.
 

If you liked this post, you may also like:
8 Tips for Managing Project Costs
Risk management is how adults manage projects!  
10 guidelines for estimating project effort


7 Comments
Senthil link
5/7/2011 02:33:56

Hi Susanne,

Do you use any specific tool for Requirement trace-ability matrix? Or excel sheet?

-Senthil S

Reply
Pranjal R Nigam
16/7/2011 05:05:21

Please name any tool you use for requirement gathering?

Reply
Susanne Madsen link
16/7/2011 05:21:10

The main tool I use is the requirements traceability matrix which you can build up in Excel. What is important is that you are able to show traceability between business requirements through to end products or use cases and test cases etc. There is no right or wrong here. You build it to suit your specific needs.

Reply
Pranjal R Nigam
16/7/2011 05:34:48

Hi Susanne,

Thanks for the information. Do you have any sample excel templates that you can share with me?

Thanks
Pranjal R Nigam

Reply
go here link
25/6/2013 03:18:17

Thanks for a beautiful post that reflects the requirement steps that should be taken by the project managers to sort out a solution for the tasks they upheld. You had great ideas about this and is explained in a detailed way. Thanks for your dedicated service to readers.

Reply
STRAIGHTENING MACHINE link
22/7/2013 06:28:45

Requirement trace-ability matrix? Or excel sheet?

Reply
Susanne Madsen link
29/7/2013 04:21:43

Hi Everyone,

To download a template for the Requirements Traceability Matrix in Excel, please log into the RESOURCES page on this website (Resources tap).

You can request access to the Resources page here: http://www.susannemadsen.co.uk/resources-page-subscription.html

You will receive the password 60 minutes after requesting access.

Kind regards,
Susanne

Reply



Leave a Reply.

    Categories

    All
    Agile
    Authenticity
    Building Relationships
    Coaching
    Delegation
    Estimation
    Feedback
    Handling Conflict
    Innovation
    Iron Triangle
    Limiting Factor
    My Story
    Perception Of Failure
    Podcasts
    Positive Attitude
    Proactive Project Management
    Progress Reporting
    Project Costs
    Project Failure
    Project Initiation
    Project Leadership
    Project Management Mistakes
    Recruitment
    Requirements
    Resistance To Change
    Risk Management
    Self Esteem
    Stakeholder Management
    Stress Management
    Team Motivation
    Time Management
    Trust
    Vision And Mission

    Picture

    Susanne Madsen

    Susanne is a project leadership coach and the author of The Power of Project Leadership and The Project Management Coaching Workbook. She has over 20 years experience in leading large change programmes for global companies. Read more..

    Picture

    Register for FREE to get access to the RESOURCES page

    Picture
    Picture
    Picture
    Picture
    Picture
    Picture

    Archives

    October 2019
    June 2019
    May 2019
    March 2019
    February 2019
    December 2018
    November 2018
    October 2018
    August 2018
    July 2018
    June 2018
    May 2018
    April 2018
    March 2018
    February 2018
    January 2018
    December 2017
    November 2017
    October 2017
    September 2017
    August 2017
    July 2017
    June 2017
    May 2017
    April 2017
    March 2017
    February 2017
    January 2017
    December 2016
    November 2016
    October 2016
    August 2016
    July 2016
    June 2016
    May 2016
    April 2016
    March 2016
    February 2016
    January 2016
    December 2015
    November 2015
    October 2015
    September 2015
    August 2015
    July 2015
    June 2015
    May 2015
    April 2015
    March 2015
    February 2015
    January 2015
    October 2014
    September 2014
    August 2014
    July 2014
    June 2014
    May 2014
    April 2014
    March 2014
    February 2014
    January 2014
    December 2013
    October 2013
    September 2013
    August 2013
    July 2013
    June 2013
    May 2013
    April 2013
    March 2013
    February 2013
    January 2013
    December 2012
    November 2012
    October 2012
    September 2012
    August 2012
    July 2012
    June 2012
    May 2012
    April 2012
    March 2012
    February 2012
    January 2012
    December 2011
    November 2011
    October 2011
    September 2011
    August 2011
    July 2011
    June 2011
    May 2011
    April 2011
    March 2011
    February 2011

    View my profile on LinkedIn

    RSS Feed

Developing Project Leaders