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.
A project team is a group of individuals assembled to work together on a specific project, typically for a defined period of time with a clear set of objectives. Project teams are responsible for planning, executing, and completing projects to achieve specific goals or deliverables.
Here are some key characteristics that differentiate project teams from other teams in an organization:
Temporary Nature: Project teams are temporary and created for the duration of a specific project. Once the project is completed, the team disbands, and team members may be reassigned to other projects or teams.
Specific Goals: Project teams are formed to achieve particular objectives, such as launching a new product, implementing a software system, constructing a building, or organizing an event. The goals are well-defined, and the team’s success is often measured by its ability to deliver on these goals.
Cross-Functional: Project teams typically consist of members from different functional areas or departments within the organization. They bring diverse skills, expertise, and perspectives to the project. This cross-functional approach is valuable for tackling complex problems.
Project Manager: A project team is usually led by a project manager who is responsible for planning, organizing, and controlling the project. The project manager is in charge of assigning tasks, managing resources, and ensuring that the project stays on track.
Temporary Authority: Project team members often have dual reporting relationships. They report to their functional managers within their departments for day-to-day work but also report to the project manager for project-related activities. This temporary authority structure is designed to support the project’s success.
Time Constraints: Project teams work under time constraints and deadlines. The duration of a project is limited, and the team must complete its work within the specified timeframe.
Unique Composition: Project teams are often composed of individuals with the specific skills and expertise required for the project. Team members may come from different parts of the organization or even external contractors and consultants.
Scope and Deliverables: Each project has a defined scope and set of deliverables. The project team’s primary responsibility is to meet these deliverables within the defined scope.
Stakeholder Focus: Project teams consider the needs and expectations of various stakeholders, including customers, sponsors, and end-users, to ensure that the project’s outcomes align with their requirements.
Risk Management: Project teams are often involved in identifying, assessing, and managing project risks to minimize the potential for issues or delays.
While project teams have distinct characteristics, it’s essential to note that they are part of the broader organizational structure. They may collaborate with other teams or departments, and successful project outcomes contribute to the overall success of the organization. In contrast, other teams within the organization, such as functional or departmental teams, typically have ongoing roles and responsibilities related to the day-to-day operations of the company.
This week, I’ve learned about streamlined communication tools that enhance collaboration among team members, which could address challenges in project coordination for MTD.
Adopting an iterative approach to setting up an event would mean gradually refining event details based on feedback, potentially reducing last-minute changes.
An agile approach could improve adaptability to evolving client needs and market trends.
My advice would be to integrate agile methodologies, fostering open communication and regular feedback loops to enhance project flexibility and responsiveness.
As a project manager for MTD. I would firstly discover what difficulties they are having. Then using the iterative approach that allows us to test ideas and get feedbacks, I would go for such approach. Getting the team working regularly and frequently, because at that point what is more important for the client is getting the project done.
So with the aid of speed, feedbacks, negotiation and constant communication, I should be able to deliver my project accurately. The major implication I think I would encounter is the time limit which forces the project team to focus majorly on the highest priority requirement- which is getting the project done.
However, this would help change (or even stop) a project in order to achieve a relatively low cost budget.
As a project manager with the MTD, I will use the both approach, a linear approach may be more suitable for a water distribution project in a company like MTD. A linear approach typically involves a sequential and structured process, where each step is completed before moving on to the next. In this case, the process could involve purifying and testing the water, followed by distributing it through the existing pipeline channels to households, industries, and event centers. However, in the case of a contingency like a natural disaster, the approach taken for the water distribution project may need to be adjusted from a linear method to a more iterative approach. An iterative approach allows for flexibility and adaptability in response to changing circumstances. It involves breaking the project into smaller, manageable phases or iterations, where each iteration can be planned, executed, and evaluated separately. This allows for adjustments to be made based on the evolving situation caused by the natural disaster.
Considering the dynamics of projects undertaken by MTD and the likely challenges and issues (scope creep, budget constraints, revised deadlines, vendor defaults, natural disasters, etc.) that may arise, I have learned that we live in a world that is dynamic and rapidly evolving; therefore, project managers must constantly develop and evolve to successfully, handle projects in any particular environment.
Incorporating VUCA framework, will help the project manager understand the environment in which the projects will be undertaken and a cocktail of appropriate approaches and practices to adopt in managing those projects.
Iterative Approach: It is a process of repeated cycles which allow for revision and improvement, with each cycle building upon the previous one. Though projects are divided into several iterations, with each iteration serving as a feedback loop which offers a chance to thoroughly review progress thus far and make changes, Iterative approach uses one overall project timeline that moves toward a set of deliverables offered during project closure.
Pros For MTD:
Quality Control: Iterative approach provides better control over the project by breaking it down into smaller, more manageable cycles. This helps to improve the overall quality of the project.
Risk management: Iterative approach allows for better risk management by identifying and addressing issues early in the project.
Stakeholder involvement: Iterative approach encourages stakeholder involvement throughout the project. This leads to better communication, minimised errors, and better outcomes.
Cons For MTD:
Project progress is highly dependent on the risk assessment phase
Significant resources might be needed.
Significant scope creep can deviate the project from its initial objectives
Challenges in time and cost estimation.
Agile Approach: It is an iterative and incremental approach where sprints (iterations) are time-boxed (limited to certain amount of time, 1 to 4 weeks) and emphases are laid on collaboration, flexibility, continuous improvement and customer satisfaction in the management of the project.
Pros For MTD:
Flexibility: Flexibility and the ability to adapt to changes are encouraged by Agile approach, which allows MTD team to prioritise, focus and respond quickly to changing requirements or customer feedback.
Collaboration: Agile approach enhances collaboration between MTD team members, stakeholders, and customers. This engenders a more cohesive and productive MTD team which can yield a higher quality end product or better outcomes.
Transparency: Agile approach promotes transparency through visible progress and open communication between MTD team members, stakeholders and customers. This can involve clear reporting and tracking of project status and issues while ensuring that everyone is aligned and working towards the same project goal.
Risk Management: Agile approach divides projects into smaller, more manageable bits that can be completed and evaluated within sprints. It therefore, permits the identification and quick resolution of potential risks that could impact project success.
Continuous Improvement: Agile approach enhances continuous improvement as MTD team regularly reviews their progress and identify areas where they can improve their processes and performance.
Customer satisfaction: Agile approach prioritizes customer satisfaction in which the customer is involved throughout the project, providing feedback and direction to the team. This ensures that the end product meets or exceeds the customer’s needs and expectations.
Value Delivery: The Agile approach can allow MTD team to deliver working solutions faster through prioritising the most critical project elements, in which stakeholders can begin benefiting from the project’s output, much earlier.
Cons For MTD:
If there is a fixed scope, budget or timeline for MTD in setting up an event as project, Agile approach may not be well-suited for the project as it may be difficult to implement.
Agile approach requires a high degree of collaboration and communication among team members. If MTD team members are unable to effectively, work together, then an Agile approach may not be successful.
In Agile Project management practices, trainings may be expedient for teams. For MTD team, a significant investment of time and resources may be required.
Advice For MTD:
Choosing the right approach for setting up an event as a project will depend on several factors including project scope, MTD team size, budget, customer needs, the proposed project environment, etc. Therefore, it is expedient to apply the VUCA framework to understand the environment in which the projects will be undertaken and adopt the appropriate approach or combination of approaches to manage the project.
Nevertheless, the Agile approach is well-suited for projects that require flexibility and collaboration, while the Iterative approach is well-suited for projects that require better risk management and quality control. The Event organiser and the project sponsor’s priorities will play a critical role in the approach to be adopted.
Taking an iterative approach to setting up an event as a project:
1. Continuous Improvement: An iterative approach allows for ongoing refinement and improvement of event planning processes. You can gather feedback and make adjustments throughout the project, ensuring that the event’s details, logistics, and attendee experience continually improve. This approach promotes adaptability and responsiveness to changing requirements.
2. Enhanced Stakeholder Collaboration: An iterative process encourages frequent interaction with stakeholders, such as clients, sponsors, and event attendees. This collaborative approach ensures that their input is considered at every stage, leading to a better alignment of the event with their expectations and needs.
3. Risk Mitigation: By breaking the event planning process into smaller, manageable iterations, you can identify and address potential issues early in the project. This approach helps in mitigating risks, as problems can be identified and resolved before they escalate, ultimately leading to a smoother event execution.
Implications of an Agile approach to event planning:
1. Flexibility and Adaptability: An Agile approach is highly flexible and allows for changes in event requirements even late in the planning process. This adaptability is beneficial when dealing with evolving client preferences, last-minute adjustments, or unexpected challenges, making it easier to meet dynamic event goals.
2. Incremental Deliveries: Agile encourages incremental deliveries, enabling you to provide partial event solutions quickly. This can be advantageous in demonstrating progress to stakeholders and generating early excitement or support for the event.
3. Frequent Communication: Agile prioritizes frequent communication and collaboration with stakeholders. This ensures that their feedback and insights are continually incorporated into the planning, resulting in an event that closely aligns with their expectations.
If asked to advise the company, I would recommend combining both approaches when setting up an event as a project. An iterative approach can be employed for the broader event planning process, allowing for continuous refinement and improvement. Simultaneously, an Agile approach can be used for specific components or features within the event that require flexibility and rapid adaptation. This combination can help strike a balance between stability and adaptability, ensuring a successful and well-executed event that meets the evolving needs of clients and stakeholders.
As a PM I will incorporate various project management strategies to lead to the completion of the work. By using the iterative approach, I will be able to get the user’s and customers’ feedback at each stage of the project. Applying the necessary framework enables the use of definitive approaches to ensure the effectiveness and completion of the project. My advice to the company is that every event must be carefully evaluated, and effective strategies be developed for the changes that may occur at any phase
i learnt that the two approaches are important for a PM a know but that of iteractives seems to be more safe and reliable since every point in time the client might want to add or remove something from the project ongoing. the linear approach is just like a straight line graph that doesn’t demand much stress. i will also introduce my VUCA in respect to handling this project. this particular topic has really help in dealing with my clients at the field as a filed engineer.
As a project manager who has been well informed through learning, I will advise MTD to use both approaches.
As a Project Manager, considering the specific nature of MTD’s projects involving event setup, I recommend that the company embraces a flexible and hybrid approach that incorporates aspects of both iterative and Agile methodologies. This approach can be highly effective when accompanied by clearly defined project objectives, the use of Iterative Planning techniques, adherence to Agile principles, meticulous documentation, and well-structured communication channels with stakeholders.
By implementing this approach, we can ensure that all project participants are well-informed and engaged at every stage of the project. This proactive communication and collaboration will result in a successful final output, efficient resource management, reduced risks, and, most importantly, increased customer satisfaction.
Taking an iterative approach to setting up an event as a project allows for incremental progress and feedback, which can be beneficial for large, complex events. It enables you to make adjustments as you go, accommodating changing requirements and reducing the risk of significant issues arising. However, it may be less efficient for small, well-defined events.
An agile approach, on the other hand, emphasizes flexibility and collaboration. It’s particularly useful when requirements are likely to change, or when the event’s goals are evolving. Agile encourages regular communication with stakeholders and adjusting plans as necessary.
If advising a company on event project management, I’d recommend the following:
1. Assess the nature of the event: Consider the size, complexity, and how likely requirements are to change. For large events or those with evolving goals, an iterative or agile approach may be suitable.
2. Define clear objectives: Regardless of the approach, ensure that event goals and success criteria are well-defined from the start.
3. Select the appropriate methodology: Choose either an iterative or agile approach based on the nature of the event and the company’s project management capabilities.
4. Assemble a cross-functional team: Collaborate with individuals who have the necessary skills and experience, and maintain open communication.
5. Create a flexible plan: Develop a project plan that accommodates change, but also provides structure and milestones.
6. Regularly review and adapt: Continuously evaluate progress, gather feedback, and adjust plans accordingly.
7. Ensure stakeholder engagement: Keep all relevant parties informed and involved throughout the project.
Ultimately, the choice of approach depends on the specific circumstances and the company’s organizational culture and capabilities.
This week’s learnings talked about iterative and linear approach to setting up a viable project which will be beneficial for MTD. Iterative project management is a style that allows continuous improvement, and adaptation to a changing environment factor or other circumstances.This seems to be cost effective.
Agile approach focuses on team feedback ,and customer satisfaction and needs.
At MTD, an iteration approach involves scheduling the work to be done during an iteration and assigning individual work items to members of the team.
Project Management approaches is best suited to corresponding context for application. And each approach either ln