148k views
3 votes
Which of the following is the technical manager not responsible for?

A. Determining the adequacy of the requirements specifications.
B. Controlling the volatility of the requirements and manage change history.
C. Re-estimating the cost and schedule of the project when the requirements change.
D. Negotiating requirements changes between the acquirer (customer) and the developer.

User Rasalom
by
7.3k points

1 Answer

5 votes

Final answer:

The technical manager is responsible for determining the adequacy of requirements, managing requirement changes, and re-estimating project cost and schedule. However, they are typically not responsible for negotiating requirement changes between customer and developer; this role usually falls to a project manager or business analyst.

Step-by-step explanation:

The responsibilities of a technical manager can often intersect with other roles within a production or project management setting. In this particular context, the options A, B, and C are typically within the scope of a technical manager's responsibilities. Determining the adequacy of the requirements specifications involves ensuring that the project's technical aspects are properly outlined and feasible. Controlling the volatility of the requirements and manage change history is essential in maintaining project integrity and alignment with goals. Furthermore, re-estimating the cost and schedule of the project when the requirements change is also crucial to successful project outcomes. However, the technical manager is usually not in charge of negotiating requirements changes between the acquirer (customer) and the developer; this is more commonly the role of the project manager or a business analyst, who liaises between the technical team and stakeholders. These distinct roles highlight the collaborative nature of project management, where understanding and fulfilling responsibilities are paramount to the success of the project.

User Ootoovak
by
8.2k points