The relation of project planning with project success

Answer 1:

Project planning is crucial for project success, but it does not guarantee it. Projects can face unexpected challenges, risks, and changes that can derail their success. The relation between project planning and project success is that effective project planning can increase the likelihood of success, but it is not a guarantee.

Two facts that support this statement are:

1. According to the Project Management Institute’s 2020 Pulse of the Profession report, only 47% of projects met their original goals and business objectives. This means that more than half of the projects did not meet their goals, despite planning and preparation.
2. Another study by McKinsey & Company found that 17% of IT projects go so badly that they threaten the very existence of the company. This highlights the importance of project planning and risk management to minimize the likelihood of failure.

Answer 2:

a) Integrated change control is a process that ensures that changes to the project scope, schedule, cost, or quality are coordinated, reviewed, and approved before implementation. Late changes in project requirements can be challenging to manage, but they can be addressed through the change control process. As an IT project manager, I would follow the following steps to manage integrated change control:

• Evaluate the impact of the new requirements on the project scope, schedule, cost, and quality
• Determine if the changes are necessary and aligned with the project objectives and stakeholder expectations
• Document the changes and submit them to the change control board for review and approval
• Update the project plan, schedule, and budget accordingly
• Communicate the approved changes to the project team and stakeholders

For example, if a stakeholder requests a new feature for the e-wallet app late in the project execution, I would evaluate the impact of the change on the project scope, schedule, cost, and quality. If the change is significant, I would submit it to the change control board for review and approval. Once approved, I would update the project plan, schedule, and budget, and communicate the change to the project team and stakeholders.

b) Scope creep refers to the uncontrolled expansion of the project scope beyond its original boundaries. It can lead to delays, cost overruns, and lower quality deliverables. To prevent scope creep while still allowing for some flexibility in the project plan, I would follow the following strategies:

• Establish clear project objectives and scope boundaries
• Define a change control process and communicate it to the project team and stakeholders
• Regularly review the project scope and compare it to the original objectives and requirements
• Prioritize changes and only approve those that are necessary and aligned with the project objectives
• Monitor the project progress and adjust the scope as needed

For example, if a stakeholder requests a new feature for the e-wallet app that is outside the project scope, I would evaluate its alignment with the project objectives and requirements. If the change is not aligned, I would decline it. If the change is aligned, I would prioritize it and evaluate its impact on the project scope, schedule, cost, and quality.

c) External dependencies are factors outside the project’s control that can impact its progress and outcome. Two potential external dependencies for the e-wallet project could be:

• Regulatory changes: Changes in regulations related to e-wallets, such as data privacy laws or financial regulations, could delay the project if they require significant changes to the project scope or design.
• Third-party services: The e-wallet app might depend on third-party services, such as payment gateways or cloud providers, that could experience downtime or disruptions that could impact the project schedule.

To address these external dependencies, I would take the following actions:

• Monitor the external environment and anticipate potential changes or disruptions
• Establish contingency plans and risk management strategies to mitigate the impact of external disruptions

• Maintain open communication with external stakeholders and partners to stay informed about changes that could impact the project
• Adjust the project plan and schedule as needed to account for external dependencies and potential delays
• Ensure that the project team has the necessary skills and resources to adapt to changes in the external environment.

For example, if regulatory changes are introduced that impact the e-wallet project, I would evaluate the impact on the project scope and schedule, and work with the project team to identify alternative approaches or solutions. If third-party services experience disruptions, I would work with the service provider to resolve the issue and adjust the project schedule if necessary. Overall, managing external dependencies requires proactive risk management and effective communication with stakeholders.