What steps should you take to ensure that the impact of change requests is understood by all project stakeholders

The software development project that you are managing (using traditional, non-Agile methodologies) is going smoothly, but your users are requesting changes to the original requirements. What steps should you take to ensure that the impact of change requests is understood by all project stakeholders? What may happen if there is no formal process for project change management?

This week’s Discussion Question asks you to select only one of the following questions. Please include the question number in your initial post, so we all can better understand your post, such as “#1”, “#2”, etc.:

Imagine you are a member of the project approval committee. An ambitious young manager in the marketing department is well connected with the top management team in your company. He catches you in the hall and mentions that he is frustrated with how long it takes to get a simple system enhancement through the “bureaucratic” approval process. He wonders whether you could sign off on a small enhancement request for his team’s reporting application. With a wink, he promises to “owe you one.” What would you say to him and why?

The software development project that you are managing (using traditional, non-Agile methodologies) is going smoothly, but your users are requesting changes to the original requirements. What steps should you take to ensure that the impact of change requests is understood by all project stakeholders? What may happen if there is no formal process for project change management?

You interview for a job and the employer asks you if the project management process for systems development should be a structured or formal process. What will your answer be? Why?

How are the roles of the Scrum Master and the Product Owner different (or alike)? How do these roles interact in a SCRUM project? Why are both roles essential for SCRUM success?

“Traditional” project management has three constraints: time, cost, and scope. Agile methodologies—and SCRUM in particular—lack only one of these constraints, scope. Why? What is the advantage of doing that? What are the risks involved in doing that, if any?

Post your initial response early and check back often to continue the discussion. Support your discussion post with at least one academic source reference