Put yourself in the role of a project manager collaborating with MTD, an events company.
Considering the difficulties and problems that MTD encounters in their projects, what insights have you gained this week that could offer assistance?
If an iterative approach were employed in organizing an event as a project, what would be the consequences? Similarly, what are the implications of adopting an agile approach? If the company sought your advice, what would you recommend?
Contribute your thoughts and ideas to the discussion.
The VUCA framework tools is an insight I will bring in a project manager working with MTD.
The implications of using the agile method means the project plan will be more flexible and adaptable, projects risks will be reduced and changes can be implemented.
I will advice them to use the best approach (MTD code of conduct) , but remain flexible and quick to respond to changes that will occur as is in the case of most MTD projects.
I need to gain full knowledge of my environment as a project management so as to know what approach to apply (linear or iterative). And also know the challenges related to these approaches in order to carry out a project properly.
With what we have learned thus far about MTD and the projects they handle difficult/unforeseen issues occur at intervals. If I was to advise MTD, I would adopt a hybrid approach to the projects keeping in mind the tripartite priorities of time, cost, and quality.
At the initial phase the project would be handled with a linear approach. Here we gather as much information as possible, get clarifications on specifics and budget, as well as time frame. I would handle the deployment phase as iterations; here I would break up my project team into specialized sub teams to focus on the different technicalities specified by the client.
The consequences of this approach would be mostly positive, as the teams will be nibble enough to deal with any uncertainty that springs up real time without distorting the time frames, ensuring quality is maintained, and mitigating against costly risks. Overall the teams are more productive and the project scope sustained devoid of creepers. It is the more pragmatic approach.
Okwulu Paul
Cohort 8, Team 3
Taking an iterative approach to setting up an event as a project involves breaking down the event planning process into smaller, manageable phases or iterations. Each iteration focuses on specific aspects of the event, and after each iteration, there is a review and adjustment phase before moving on to the next iteration. On the other hand, an agile approach would involve applying agile principles and practices throughout the event planning process, with a strong emphasis on adaptability, collaboration, and continuous improvement.
Implications of an Iterative Approach:
Focused Planning: By dividing the event planning into iterations, the team can concentrate on a limited set of tasks at a time, which allows for a more focused and detailed planning process.
Early Feedback: Each iteration produces tangible results or prototypes that can be presented to stakeholders, allowing for early feedback and adjustments. This reduces the risk of significant changes being required later in the process.
Risk Mitigation: Identifying and addressing potential issues and risks becomes more manageable in each iteration, leading to better risk management throughout the event setup.
Progress Monitoring: It becomes easier to track progress at different stages of the event setup since the team can measure accomplishments after each iteration.
Implications of an Agile Approach:
Flexibility and Adaptability: An agile approach promotes flexibility, allowing the event planning team to respond quickly to changes in requirements, stakeholder feedback, or external factors that might impact the event.
Regular Communication: Agile practices encourage frequent communication among team members and stakeholders, ensuring everyone remains informed and aligned throughout the planning process.
Continuous Improvement: The team focuses on learning from each iteration to improve the planning process, event quality, and overall efficiency.
Increased Collaboration: An agile approach fosters a collaborative environment, promoting cooperation between team members, suppliers, and stakeholders, leading to a more successful event.
Advice for the Company:
If I were to advise the company on setting up an event as a project, I would recommend adopting an Agile iterative approach. Here’s why:
Adaptability to Changing Conditions: Events often involve numerous variables and may be influenced by factors beyond our control. An Agile iterative approach enables the team to adjust plans and responses promptly when faced with changes, ensuring a more successful event outcome.
Early Stakeholder Involvement: Engaging stakeholders early and frequently in the iterative planning process allows their input to shape the event, resulting in higher satisfaction and better meeting their expectations.
Continuous Learning and Improvement: Agile promotes continuous learning, which can lead to better event planning and execution in subsequent iterations and future events.
Risk Mitigation: By addressing risks and potential issues iteratively, the company can minimize the impact of unforeseen challenges and ensure a smoother event execution.
Increased Efficiency: Breaking down the planning into iterations can enhance efficiency, as the team can concentrate on a limited scope of tasks and make more focused progress.
Collaborative Culture: Adopting an Agile approach nurtures a collaborative culture, encouraging teamwork and shared responsibility, which are vital for successful event planning.
By embracing an Agile iterative approach, the company can effectively navigate the complexities of event planning in a VUCA environment and increase the likelihood of hosting successful and memorable events.
Ekwuribe Uzochukwu
Team 4
I will first study the purpose/goal of the project because this will inform my decision on the best approach to employ.
Haven done that, I will employ vuca framework as well as the hybrid approach in other to reduce any project risk that may occur.
I think the implications of using iterative method is because budgeting or estimating cost can’t be properly done.since it focus on completed works.. there is no reference for others to learn .. also implications of using agile approach is same as iteration because it uses iteration method. My advice for the company is to use the hybrid method because it will blend both agile and water cycle methods to produce a great project
I will apply both Linear and iterative as a PM.
Linear will be used if all parameters and conditions are stable.
Iterative comes into play when nothing is stable.
As a PM with MTD, I will first study the purpose of the project because this will inform my decision on the best approach to employ.
Having done that, I will rightly employ the hybrid approach in other to reduce any project risk that may occur.
The VUCA framework will also be employed to develop suited responses to tackle any issues that may arise.
As PM of MTD I will use iterative approach to solve challenges that MTD is faced with. Iterative approach works in complex situations
Being the Project Manager of MTD Company, I will go through the Project purpose and come up with the suitable approach that will benefit the company to achieve its aims and objective. I will analyze the project with all the available procedure either Linear, Iterative or Agile so as to guide against any unforeseen change or review with the plan and come up with the suitable one to achieve the purpose of the project.
As the project supervisor for MTD, I’ll carefully evaluate the project and adopt the best practices from both linear and iterative approaches that fit how we want to work towards achieving the project’s objectives. In this case, I’d have mapped out an ability to communicate with my team to know the best form of approach to take, making me more than just a boss but a leader who seeks out others’ opinions for proper project establishment.
Understanding this will enable my team and I to significantly reduce the danger of the project failing. With a team-like attitude, decision-making is simple.