Welcome to Project Management Questions!

You can ask any question on Project Management and you can rest assured that real Project Managers will answer your shortly!

How to document project requirements?

0
votes
How can the project manager document the requirements of the project based on the feedback from the client? And how can he ensure that he's not missing any requirement?

Is using a software tool (like a Wiki or something) the best way to document the project requirements? Or can they be documented efficiently using merely a notepad? (the good old way!)
asked 7 years ago by anonymous

1 Answer

0
votes
If you're building a requirements set based on discussions with a client they need to be captured in some form that allows the PM, the team and the customer themselves to see them clearly articulated.  Once that's done, whatever document/tool is used must be baselined.  By that I mean that the customer and the PM must formally agree on, and publish them.  That's the only way the PM is going to prevent scope creep and resultant cost and schedule variances.  The type of tool needed for baselining depends on the complexity of the project.  It can be as simple as a spreadsheet or, if necessary one of the many more sophisticated requirements tracking tools available commercially.  Whatever method is used, each requirement needs at a minimum to: 1) be clearly stated. 2) have it's source identified. 3) have it's linkage to other requirements identified.
answered 7 years ago by dsmcalis (1,570 points)

Related questions

0
votes
1
answer
0
votes
1
answer
+1
vote
1
answer
asked 8 years ago by anonymous
+1
vote
1
answer
0
votes
1
answer
© 2010 - 2012 Project Management Questions - All Rights Reserved