Case Study Essay Example | Topics and Well Written Essays - 750 words

Case Study - Essay ExampleThese prior meetings have been based upon the contract to update the stakeholders on the progress of the wander on far simpler issues. As a result, these past meetings have been much smoother, but this term, serious ch in allenges that touch on the foresee scope get out arise. These imply an extension of the project deadline by up to four weeks the proposal for implementation of a formal change-order summons and managing the clients resistance to change. Timeline delay Although, as a software project manager my mantra is keeping an eye on sequence, and budget, sometimes the two issues may require adjustment due to unexpected issues that solution from the implementation process (Wysocki, 2010). Owing to the fact that most of such projects are not completed within the timeline as agreed upon at the beginning of the project implementation process, this one is not an exception. This project is expected to delay by between one to four weeks due to change s in the requirements of the system. More specifically, we have worn-out(a) more time that we expected, waiting for new resources. The need to expand the functionality of technology in order to allow for a seamless way to monitor the conglomerate human resources functions have extended past the original scope. The clients systems need gold plating, which is expected to consume more time that was expected. An extension of time to allow for successful completion of the project and ensure that the deliverables are realized is therefore imperative. It is important to note that, even though the stakeholders came together to develop all their requirements before starting the project, system requirements have changed, making the project to wait for the shipments of new product supplies. Change-order Process Owing to the variation of costs and the timeline for completing the project, change-order processes lead help the stakeholders to make the necessary modifications to the original pro ject plan and scope as a trade-off for the realization of quality project deliverables (Wysocki, 2010). The original proportionateness spelt out the structure of the network systems and the expected final result. However, due to the changes in the system requirements, it is important for the client to give in to extra keep in order to keep an eye on quality, as effective measures have been put in place to guard against project creep. More specifically, the stakeholders need to adjust to the new timeline for the completion of the project by at most four weeks so as to satisfy all the stakeholders new expectations. The client will be required to sign the change order form detailing the modified plan, including the system services, hardware and software, and designs as a way of formalizing a in return binding agreement. Resistance to change This project had a clear scope within which to work, hence should be respected. However, due to the fact that changes that arise during the impl ementation process are inevitable, all the stakeholders should work in tandem to respond to the changes reasonably and more appropriately to ensure that the final deliverables are achieved (Wysocki, 2010). The existence of new stakeholders is the study risk facing the project, even as some flexible stakeholders are striving not to compromise quality for limiting costs and the amount of time that is required to successfully complete the