Doing Project Requirements Gathering In SPM

[yungng]

Greetings, everyone!

I wanted to see if anyone used SPM to do their project requirements gathering and how.  Do you have a specific template (out of the box or customized) to document the requirements?  How do you handle things like network diagram or wireframes or other attachments?  Currently, we have Word docs that we use to document the requirements and we're trying to centralize everything within SPM so there aren't extra documents floating around and SPM remains our authoritative source for project information.  However, we still need to send the requirements to the stakeholder so they can approve and sign off.  Any insight you can share would be most appreciated!

Please and thank you!

[lpruit2]

Greetings @yungng. Are you wanting to capture individual project requirements or are you wanting to capture data at the Portfolio level? If you are interested in capturing requirements at the Project level, have you considered Project Workspace instead of SPM? SPM is better and building and displaying Portfolio Plans and Project Workspace is better and visualizing the individual Projects. They have recently announced "Playbooks" in Project Workspace which is a great use-case for standardizing the requirements data capture. I'll include a link to another article with more information about these Playbooks. I hope this helps answer your question but always interested in what others have to share. 

Playbooks in Project Workspace: Guided Project Exe... - ServiceNow Community

[yungng]

Thanks so much, @lpruit2 !  I am looking for something to help us standardize the capture of individual project requirements.  Preferably all in one tool rather than multiple Word docs.  We're still new to SPM and still learning everything it can do and everything we can use it for.  We do use Project Workspace but was not aware of Playbook.  I will definitely need to look into that feature.  Thanks bunches!

[phil_bool_unifi]

Hi @yungng .  The Project Workspace is a great interface to track all the activities involved within a project's lifecycle to make sure the activity is a success.  Examples might be the workshops, the creation of the high level design, the finalization of requirements and the creation of the stories.   The playbook is a great way to give guidance on how each of those tasks should be done according to your company's best practice.

There is also a 'Requirement' table available on Demands and projects, that can be displayed as a related list on Project records.  This may give you a useful framework to capture the requirements, but if your work is agile in structure (and you have SPM Pro licensing), a better approach may be to define the stories on the project, rather than duplicate the effort as requirement records.

[Namita Mishra]

Hi @yungng ,

You may want to look at the Docs feature available in the project workspace.

This not only centralize all project-related collateral in one place, but also offers strong template capabilities to standardize documentation.

For example: With the project charter, you can establish governance to ensure every project manager captures and presents key information in a consistent and structured manner across all projects. 

You can also create your own templates as per the organization need.

In addition to this, you can also export the doc and share with the stakeholders in case they are outside of SPM.

Hope this helps and if it does, please mark the response as correct answer.

Thank You!

Namita Mishra