Project Assumptions

[akappeli]

I usually document assumptions when gathering requirements.   What do you think is the best way to capture assumptions in ServiceNow?   I was thinking that I could add a type called Assumptions under the Requirements table.   This would allow me to be able to report on any assumptions gathered.  

[kellykaufmann]

I typically have an 'Assumptions' section in my Project Charter. In SN, I have a 'Project Charter' tab on the Project form, with an 'Assumptions' section. If you don't mind it being paragraph form, you could do this. Otherwise you could create a table for assumptions.

[akappeli]

Oh okay.   I had to look back at the training you provided last year on Creating a PMO blueprint.   I noticed you have a screenshot of your 'Project Charter' tab.   This could be helpful for capturing information such as scope, summary milestone schedule and assumptions.   However, I am wondering what is the best way to capture this information.   I want to make sure this is as simple as possible and easy to view important details.   Do you experience any issues with this approach?  

[kellykaufmann]

It worked well at my last company & works here as well having a Charter tab with Assumptions in it. But what works for your company may be totally different!!! Here are some quick thoughts on Pro/Con of tab vs table:

• Pro for Assumptions field in a Charter tab for each project: I feel people are more likely to reference back at the charter tab for a quick view at all the assumptions.
• Con for Assumptions field in a Charter tab for each project: If you want to print out ONLY the Project Charter form (not using a report to just pull info into a List View into Excel), you have to do custom dev or view for this.
• Pro for an Assumptions table for each project: Ability to log assumptions 1-by-1, capturing who entered it and when. Probably can reference an assumption in another form/field if needed. IF this information is important to you, you'll probably want a table. But we never needed this level of detail. We do have a Decisions table with this level of detail of course!
• Con for an Assumptions table for each project: You can only print it in a list view / spreadsheet form. Couldn't print a nice pretty project charter form with an assumptions section

You ask for the best way to capture this information - were you instead asking for a process recommendation? If so...typically a PM gathers this information at the onset of the project & reviews it with the team.

Hope this helps?

[akappeli]

Thank you for the pros and cons.   That was exactly what I was looking for.   I like the idea of being able to print a 'pretty' project charter versus just a list.   Thank you for your help.