Managing Failure In The Critical Path Coursework Example

Managing Failure in the Critical Path
Name
Institutional Affiliation

Managing Failure in the Critical Path
It is the wish of every project manager that the steps of the work breakdown structure and the defined critical path follow the project plan. Notably, project success is evaluated based on the time and cost it incurs. When the project is delivered on time and within the stipulated budget, then it is likely to be remembered as one that gave back value to the investors and the stakeholders. Ideally, the key practices of project management such as adequate planning, the management of scope creeps, watching of the milestones and conducting regular audits all have significant effects on the project. The work breakdown structure also provides appropriate tools, which can be used to conduct the evaluation of project success (Şandru, & Olaru, 2013). Thus, careful investing in the appropriate tools to help manage a project will provide feasible mechanisms to realize its success
Work Breakdown Structure vs. Network and their Roles
The work breakdown structure provides a framework upon which projects can be reduced to specific task levels and subtasks. The work breakdown structure ensures that the project manager can effectively assign subtasks within each task and change their numbers if the priorities of the task do not change. Conversely, the schedule network diagram helps the manager to identify the dependencies between the existing tasks and thus the flow and sequences of the project.

The two tools are instrumental in supporting each other to ensure the completion of projects. Using the Work Breakdown structure, which aids managers in the identification of the tasks and the deliverables of a project. It represents the structure that helps in ranking project priorities and provides relevant guidance to all its stakeholders on what is expected of them in as the project progresses (Snyder, 2015). When well analyzed, the project network reveals dependencies of the process and provides a framework for the identification of any problems in the work breakdown structure.
Reason for WBS rather than Network alone
Project managers always try to identify the most feasible mechanism for the completion of projects. Experts have identified that a combination of the two tools offers superior results as opposed to when the network is used (Şandru & Olaru, 2013). The work breaks down structure is essential in enabling the project manager to organize all the processes and schedule of the project (Shimura & Nishinari, 2014). The work breakdown structure ensures the establishment of the baseline upon which the project assignment should be created.
Use of Project Slack
Slacks provide a chance to facilitate flexibility in projects. A typical instance in which a slack was used was when a project entailed the management of multiple information technology projects all of which are dependent on each other. The manager relied on the slack to identify the ability of the projects to complement each other. The manager was able to implement the slack appropriately and even had time for testing the applications. The application of slacks depends on the sensitivity of the project. It also looks at the project flexibility. In the above case, the project had to give such flexibility to ensure that testing and other processes take place as scheduled.
Options to Consider in the event of failure
The risk identification process provides a framework for the assessment of successful project completion. The project manager must have other methods to make sure that the process moves smoothly after a failure. A method that may be employed to rectify a project when the slack does not work as expected is to consider running the processes concurrently. The manager utilized a risk management process in which the tasks were compressed to ensure that the schedules would run concurrently. The action was appropriate given that there was limited time left to ensure the project completion. Time lost in the process was three months. A typical lesson learnt is that rather than employ slacks, it is ideal to be ahead of the project schedule, rather than buy time, which may never be recovered. Careful assessments of projects should be conducted to help managers make informed decisions on the available resources.
Ethical Considerations for Building a Project Slack
Ethical considerations must be taken into account when employing project slacks. Slacks are appropriate business practices when deemed necessary. There are instances when there are resource constraints, or unexpected risks occur. As a result, employing a project slack provides ample time for the manager to plan better to ensure the delivery of the project (Sánchez, 2015). The manager must inform all the stakeholders regarding the application or use of slack in the project. Besides, the manager must explain explicitly the impacts of the slack on the project and its outcomes. Communication would ensure that the project managers are aware of any changes that take place in the project and can inform relevant stakeholders of the expectations that they have regarding the project. Poor communication may hamper the effective progression of the project and create disharmony amongst its members. Successful project thrives on the ability to maintain effective communication and share the progress and milestones of the project. Thus, all unexpected steps must be disclosed to the project owners.

References
Sánchez, M. A. (2015). Integrating sustainability issues into project management. Journal of Cleaner Production, 96, 319-330.
Şandru, M., & Olaru, M. (2013, January). Critical path method applied to the multi project management environment. In ECMLG2013-Proceedings For the 9th European Conference on Management Leadership and Governance: ECMLG 2013 (p. 440). Academic Conferences Limited.
Shimura, K., & Nishinari, K. (2014). Project Management and Critical Path Analysis: A Cellular Automaton Model. Journal of Cellular Automata, 9.
Snyder, C. S. (2000). A guide to The Project Management Body of Knowledge: PMBOK (®) guide. Newtown Square, PA: Project Management Institute.