We do not lead a standard methodology Case study

docx

School

Masinde Muliro University of Science and Technology *

*We aren’t endorsed by this school

Course

MISC

Subject

Management

Date

Nov 24, 2024

Type

docx

Pages

8

Uploaded by mutorofred

Report
1 Case Study: We Do Not Need a Standard Methodology Student’s Name University Course Code + Name Instructor Date
2 Case Study: We Do Not Need a Standard Methodology Introduction The evolution in project management has given way to new approaches to managing projects with higher levels of efficiency and productivity. The case of Zeus Inc. provides evidence of how project standardization can help improve project success and efficiency. However, it is important to know the factors that play a role in promoting project standardization, its benefits, and how to deal with resistance to standard methodology implementation. This paper will examine how some factors play a role in the implementation of project standardization, how an organization can deal with resistance during the implementation, and how implementation can benefit the organization in project management. The Role of the Following Items in Standard Methodology Implementation Project Characteristics Projects are unique and, thus, are characterized by key features distinguishing them from any other type of work. Their features include the clarity of purpose for which the work is being done, the nature of the work, which must be temporary, the uniqueness of the project, and the final delivery, which refers to the specific goal and timeline ( Michaud et al. 2019) . These factors are important when defining a project since they enable one to differentiate it from routine work. In project standardization, the features are very important, which help align the work with the standards put in place. This is because standardization establishes a clear framework for how things will be done. Therefore, the project features help develop the framework, such as reporting, budgeting, and sharing of information about the project, which must consider the
3 project's goals, schedule, and uniqueness. Although the standardized methodology should be in place, it should not narrow down to the technical work because that will affect the project's goals. Project Organization Project organization is the method used to ensure that expectations and goals of the project are clear and more structured to be accomplished through the project. They help define the project characteristics and provide a way to achieve its goals. Project organization narrows down to define roles besides the responsibilities of the people on the project, starting from the project manager. In project standardization, the roles of the project team, starting from the project manager, affect the standardization methodology. This is because, in the standardization method, each project member has a role. The project manager has to update the system on the project's progress, any issues identified, and what is expected of the project. The project team members can also be given a role in updating the project management system to ensure effective information sharing ( Milosevic et al. 2010) . Take, for instance, the case provided. Tim, from his experience, created PDX, which allows project managers by their office to update the PDX about the project's progress and any critical issue and provide reports which allow Tim to know everything about the project without going down to the project itself. Readiness of Project Managers Project managers are the leaders who manage individual projects within a portfolio. The project managers are responsible for ensuring communication and collaboration between the projects, project team, and the organization's leadership. This is important because it affects the success of the project.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
4 Let us focus on the case study to highlight the role of project manager readiness in project standardization. Tim, the head of the project portfolio, creates PDX based on his experience to ensure he stays ahead by learning about the project and everything about them. However, this cannot be successful without the support of the project managers, who are required to send reports and share information and anything relevant through the PDX ( Milosevic et al. 2010) . This means that without the project manager's readiness, there cannot be a successful standardization methodology at Zeus Inc. An Approach to Alleviate Resistance to the Use of Standard Methodology Expand internally and intensify and Value Stream Mapping methodology The method proposed is the internal expansion and intensification of the process. This process will be implemented alongside the Value stream mapping approach. Internal expansion is a method that proposes the proposal and implementation of the standardized methodology from within a single department and on a smaller scale first to prove to the project team that the approach can help create value in their work. After the first phase of implementation, the implementors of the approach should intensify the approach to the entire department and in all aspects that will need standardization. This helps reduce the shock and resistance from the project team and other stakeholders affected by the standardization. In this case, the value stream mapping approach should be integrated into the first approach by implementing the standardized method internally and then moving on to map the value created through the process ( Michaud et al. 2019) . Value mapping should bring out the impact of standardization on the projects, project managers, and the entire organization. This helps create a support base for the implementation based on the value map.
5 Let us examine the case and how standardization has been applied and implemented to know how the proposed method works. In starting the implementation process, Tim creates a PDX and ensures that all his project managers are certified. From this step, Tim ensures that all project managers report and update the PDX about the project while documenting everything on the individual projects within his portfolio. This approach is successful, and the entire organization feels the impact. James is reluctant when he proposes the idea of using PDX, to James. After all, he is unsure whether the approach will work because his projects are technically different from Tim's. However, from the advice he gets from Tim and the value map provided through Tim's department, James decides to implement PDX on a smaller scale ( Milosevic et al. 2010) . finally, James implemented the PDX in his department. This shows how Tim could use the proposed approach in fighting resistance and ensuring the implementation of project standardization in James' department. Benefits of Standard Methodology Using a standardized methodology in an organization's project management can offer unlimited benefits. The use of standardization improves the project's success and quality of results because the shared data enables easier visibility, making it much easier to identify issues on the project and improve on time. Project productivity improves significantly with standardization. This is because when there is collaboration and effective communication on the project, it is easier to consult, collaborate and liaise to ensure that productivity is maximized.
6 The level of consistency is higher. When projects within a portfolio are implemented within a standardized environment, things are done the same way. This reduces defects which allows consistency in the product outputs. High levels of efficiency. Before standardizing projects, roles besides responsibilities must be clearly defined. This means that every team member knows what they should do on the project and when. Due to this, there is an increase in accountability which will, in turn, increase the general efficiency of human resources on the project. Shortcomings of Standard Methodology Reduction in creativity. In an organization that uses standardization, things must be done in a certain way with no exceptions. Although this may cut costs, it discourages and closes doors to creativity. This is because no different way of doing things is acceptable n such an environment. Reduction in resilience. Project management operates in a dynamic environment that requires a robust system to adapt to changes. This is one of the reasons for the wide adoption of agile projects. However, when project standardization is adopted, there is no room for resilience since the rigidity locks out any creativity which would have helped deal with changes in the market. Conclusion The evolution in project management has led to different ways of managing projects to improve efficiency and productivity. Project standardization helps meet these objectives while offering an organization to build experience and reduce the cost of managing projects. Although adopting project standardization can face resistance, using internal expansion and value-stream
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
7 mapping, as seen in Zeus Inc., can improve adoption and reduce resistance. Implementing project standardization can provide businesses with consistency, and productivity but also result in reduced resilience and creativity. Thus, the application of standard methodology should be done in recognition of both the benefits and the shortcomings associated with the methodology.
8 References Milosevic, D. Z., Patanakul, P., & Srivannaboon, S. (2010). Case studies in project, program, and organizational project management. John Wiley & Sons. Michaud, M., Forgues, D., Meyer, J., & Ouellet-Plamondon, C. (2019, July). A case study on improving standardization in the conception phase by developing tools and protocols. In 27th annual conference of the international group for lean construction (pp. 927-936).