Homework Assignment: Week 10
Instructions
Please put your name/date in the header. Answers should be no longer than six sentences per question. Please refer to the class syllabus for the grading rubric. Assignment is worth a total of 10 points. Questions are located in the Discussion Questions section at the end of each chapter.
Please save the file using the following naming system: Class_Name_Week#_Assignment. For example, if Rosie Dodson was submitting her week 7 homework, her file would be saved with the following title: MGMT410_RDodson_week7_homework.
Discussion Question 11.2:
In considering how to make a big change in organizational operations (as in the case of switching to CCPM), why might it be necessary to focus on changing the organization’s current culture? That is, why does a shift in project scheduling require so many other linked changes to occur?
One of the main problems that a project might encounter during its implementation is limitations in organizational culture. In some instances, the organization’s culture might limit implementation. As such, it is necessary to make organizational changes. Especially when it comes to an organizational culture that affects basic operations or implementation of the project can place significant limitations on the project’s successful completion. As such, it is vital for the company often has to take a systematic approach that applies a change methodology within the company to facilitate the completion of the project. Additionally, since a project is often designed with the company’s organizational culture in mind, a change in project scheduling or requirements often necessitates changes in organizational culture or policies for them to be allowed. This is especially true for organizations with strict cultural policies.
Discussion Question 11.3:
Why are traditional project planning methods insufficient when project deliverables are subject to changing requirements or continuous input from the project client?
Traditional methods often fail when it comes to projects that require continuous input from clients. This is because these methods assume a linear process for project development from the requirements gathering through design. As such, it can be flawed when it comes to projects such as the ones in IT that require rapid design, changing needs, technological shifts, and other pressures throughout its implementation.
Communication Question 11.5:
What are the advantages and disadvantages of Agile PM?
Agile is designed for unpredictable environments which include changing customer requirements and technology shifts. As such, it is useful in complex projects that require multiple iterations and projects that have vague initial requirements. It recognizes the importance of user stories as the best means to develop specifications. This ensures a proper understanding of what the user wants and how to achieve it. Despite its advantages, it has disadvantages such as not being useful in projects that require a fixed and unchangeable set of requirements or short projects. It can also quickly get out of control when dealing with multiple customers or those who require constant changes. It can quickly escalate from constantly shifting the project to the point where it is never “right”.
Communication Question 11.7:
What is the main purpose of sprint reviews in Agile PM?
Reviews are an important part of every project management system and project. Sprint reviews are particularly important as they occur at the end of every sprint and help inspect the increment and adapt the backlog if needed. During this process, the team and stakeholders come together to review what was done during the sprint. As such, this allows them to identify points of interest and changes that would optimize value in the next sprint. As such, incremental improvements can be made throughout the project.