Project Documentation

[Rick Mann]

I have a question regarding the PPM tool and project documentation (charter, statement of work, UAT). Do other people using the tool simply attach this documentation to the parent project or do they create documentation tasks to have it completed? Just curious to see how others are using the tool. Thanks.

Rick

[tony_fugere]

I've seen both methods being used. Depends on your business processes. Do you need a task that must be completed for tracking or is the existence or non-existence of the attachment enough?

[dhanna]

I am currently experimenting with something called Managed Documents:
http://wiki.servicenow.com/index.php?title=Managed_Documents

My disclaimer is that I am more of a PM than an admin, but I've been given some freedom to really explore our implementation of Project Portfolio Management. In doing so, I did the following in a test environment:
-Create new column of type glide_list on the Documents table with a reference to planned_task
-Create a new relationship between Task and Document via your new column
-Add it as a related list to your project layout

The interface is a little cumbersome since you have to drill down a bit to get to the actual document, but it gives some basic versioning controls, check in/out, and, most importantly, it gives me an integrated approval mechanism via our directory integration.

I'm definitely open to any suggestions as to how we could improve this.

[tony_fugere]

Nothing wrong with your approach. I would have used a Many-to-Many relationship table, but the glide_list works as well with a bit more fancy footwork for the related list on the project table side.

http://wiki.servicenow.com/index.php?title=Creating_a_Many-to-Many_Relationship

M2M tables automagically create the related lists for you.

[scharmcclanahan]

I know this is an old topic but as a PM, I was looking for a solution for this as well.   I actually used David Hanna's suggestion and it worked great.   We are on the Kingston version.