Project management Discussion

Although this week's lecture focused on how to plan and execute the "collect requirements" process, not everyone agrees that the project manager should be too focused on the requirements collection process. After all, many people say, the project manager's job is to manage whatever the project requirements are within give cost and time parameters - particularly if a Business Lead or Business Analyst is available to oversee requirements collection.

What do you think? Strictly speaking, a project manager is responsible for keeping a project's triple constraints (scope, budget, schedule) in control, regardless of what the scope of the project is. That's already a big job. Should the project manager make the job more difficult by also acting as the "collect requirements" manager, including choosing requirements collection techniques and writing requirements documentation?

To answer this question, first identify whether you believe the project manager should (or should not) be deeply involved in requirements collection. Then, explain why you believe this is so.

To successfully complete this discussion board, you'll need to post your initial responses to these questions no later than this WEDNESDAY, 11:59pm U.S. ET. You'll also need to post at least ONE response to this discussion board no later than this SUNDAY, 11:59pm U.S. ET. This discussion board is worth a total of 2.5 points, half for your initial post and half for your response post. Good luck!

Second Discussion:

To answer this week's second discussion topic, first read the Rosa County case study update provided as part of this week's reading materials.

Second, given the requirements collection techniques identified in this week's lecture materials and the case study update provided, how would YOU collect requirements for the case study?

1. Which stakeholders would you collect requirements from? (And why those stakeholders? Consider the different ways stakeholders can be classified, as we discussed in this week's lecture materials. How does stakeholder classification affect how we collect requirements?)

2. What requirements collection techniques would you use, and why? Would you use different techniques for different stakeholder groups?

3. How long do you think the full requirements collection process would take?