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 implications of taking an iterative approach is that there will be more stakeholders involvement through feedbacks, which will help the project team to deliver to the taste of the sponsor. The implications and an agile approach will be speedy delivery of project, better team work. I will advise the company to your a combination of both linear and iterative approach.
I have learnt that both linear and iterative methods can be used.
While linear method can not easily change, I will switch to iterative method which can be adjusted. Continous planning with the team, and seeing ways that adjustments can be made.
Then we will have a time frame to achieve one of the set goals for the project and also engage in feedbacks within the team and also to the stakeholders.
As a Project Manager, I will use several approaches to help the project team achieve it’s aim. Where there are issues I will proffer solution.
The project management can adopt the principles of VUCA (Volatility, uncertainty, complexity, ambiguity). Keeping in mind there may be uncertainties in the cause of carrying out the project. In addition to this, I will deploy effective communication between the stakeholders (project manager, project team, project sponsors, regulatory agencies, end-users etc.).
I will also ensure time management, teamwork, and a good knowledge of the regulatory environment, and good negotiation, adapting to changes or a disruption in a particular process.
The Implications of the iterative approach is that it focuses on making the project timeline cyclical to account for necessary rework and improvement. It does not address other aspects of a project like process, timeframes, or customer engagement. The process remains sequential, the timeframes are not specifically addressed, and there is no additional customer engagement. The iterative approach will give the project manager the opportunity of planning for uncertainties that may be encountered in the project, this would build transparency and accountability.
The implications of the Agile approach is that it focuses on responding to change and on the unpredictable nature of projects by being both iterative and incremental. It is less risky and guides the sponsors and stakeholders in the development of the project through scrum meetings, sprints reviews and progress.
my name is Akpan Andrew,
The tools were able to help me manage a project executed sometimes where after the details of beneficiaries has been compiled, they had to leave the terrain due to crisis encountered in the community, we had to engage the community leaders to help in distribution of the materials since they live and know the beneficiaries by acting on the information disseminated by the leaders for easy access to their whereabout.
My advice to others is change is an inevitable part of our daily process, in executing any projects let’s bear in mind that factors may come into been thereby forceing the initial plans to change, we should be ready to adapt and be flexible.
As a Project Manager I will deploy several approaches to help the project team achieve it’s aim, where there are issues I will proffer solution.
The project management with respect to it’s environment can adopt the principles of VUCA (Volatility, uncertainty, complexity, ambiguity) bearing in mind it will not always go as planned.
In addition to this, effective communication between the stakeholders: project manager, project team, project sponsors, regulatory agencies as well as the suppliers/end-users is key as well as time management, teamwork, a good knowledge of the regulatory environment, and good negotiation, adapting to changes or a disruption in a particular process.
The Implications of the iterative approach is that it focuses on making the project timeline cyclical to account for necessary rework and improvement. It does not address other aspects of a project like process, timeframes, or customer engagement. The process remains sequential, the timeframes are not specifically addressed, and there is no additional customer engagement. The iterative approach will give the project manager the opportunity of planning for uncertainties that may be encountered in the project, this would build transparency and accountability.
The implications of the Agile approach is that it focuses on responding to change and on the unpredictable nature of projects by being both iterative and incremental. It is less risky and guides the sponsors and stakeholders in the development of the project through scrum meetings, sprints reviews and progress.
Taking an iterative approach to setting up an event as a project can have several implications, both positive and negative. Here are some key implications to consider:
Flexibility and Adaptability: An iterative approach allows for greater flexibility and adaptability throughout the event planning process. By breaking the project into smaller iterations, you can incorporate feedback, make adjustments, and respond to changing requirements more effectively.
Improved Stakeholder Engagement: Iterative approaches encourage regular stakeholder involvement and feedback. This involvement can lead to better alignment of expectations, increased stakeholder satisfaction, and reduced risks of miscommunication or misunderstandings.
Early Identification of Issues: With each iteration, potential issues and challenges can be identified and addressed early on. This proactive approach allows for quicker resolution of problems, reducing the impact on the overall event timeline and budget.
Incremental Progress and Learning: Iterations provide opportunities for incremental progress, allowing you to continuously build on previous successes and learn from mistakes. This approach promotes a culture of continuous improvement and can lead to more refined and successful events over time.
Time and Cost Considerations: While an iterative approach can improve the quality of event planning, it may require additional time and resources. Each iteration involves planning, execution, and evaluation, which can extend the overall project timeline and potentially increase costs.
Resource Allocation: Iterations may require reallocating resources as the project progresses. This can involve adjusting team members’ roles, revising budgets, or reallocating equipment and materials. Efficient resource management is crucial to ensure smooth iterations and avoid bottlenecks.
Communication and Coordination: Regular communication and coordination among team members and stakeholders are vital in an iterative approach. Proper documentation, clear channels of communication, and well-defined roles and responsibilities can help maintain alignment and ensure that everyone is on the same page.
Monitoring and Evaluation: Iterations necessitate continuous monitoring and evaluation of progress, outcomes, and key performance indicators. Regular evaluation helps track the success of each iteration, identify areas for improvement, and inform subsequent iterations.
By considering these implications, a project manager working with MTD and adopting an iterative approach can leverage the benefits of flexibility, stakeholder engagement, and learning while effectively managing time, resources, and communication.
Implications of an Agile Approach:
Flexibility and Adaptability: Agile methodologies emphasize responding to change over following a rigid plan. This means that MTD would need to be open to modifying event requirements and deliverables throughout the project lifecycle.
Iterative Development: Agile promotes iterative development and delivery of small increments, allowing for early feedback and continuous improvement. MTD would need to break down event projects into smaller, manageable tasks or features that can be completed within shorter timeframes.
Stakeholder Collaboration: Agile fosters frequent collaboration and communication among project stakeholders, including clients, event organizers, and team members. MTD would need to ensure active involvement and participation from all stakeholders to gather feedback, validate assumptions, and make informed decisions.
Empowered and Cross-functional Teams: Agile encourages self-organizing teams with diverse skills to work together towards shared goals. MTD would need to establish cross-functional teams comprising individuals with different expertise, enabling them to collaborate and contribute effectively.
Emphasis on Continuous Improvement: Agile methodologies promote learning from experiences and continuously improving processes. MTD would need to establish feedback loops, conduct retrospectives, and implement changes to optimize event management practices for future projects.
Advice for MTD:
Embrace an Agile Mindset: Encourage the organization and its members to adopt an agile mindset that values flexibility, adaptability, and continuous improvement. This shift in mindset will lay the foundation for successfully implementing agile methodologies.
Select Appropriate Agile Framework: Evaluate various agile frameworks such as Scrum, Kanban, or Lean, and select the one that aligns best with MTD’s event management processes and goals. This framework will provide a structure for planning, executing, and delivering events iteratively.
Train and Educate the Team: Provide adequate training and education on agile principles and practices to the entire team, including project managers, event planners, and support staff. This will help everyone understand the agile approach and effectively collaborate within the framework.
Prioritize Effective Communication: Establish clear channels for communication and collaboration among stakeholders. Encourage regular meetings, such as daily stand-ups and sprint reviews, to ensure everyone remains informed, aligned, and able to provide timely feedback.
Implement Agile Tools: Utilize agile project management tools and software to facilitate project tracking, task management, and collaboration. These tools can help streamline workflows, enhance transparency, and improve overall team productivity.
Adapt Agile Practices to Event Management: Tailor agile practices to suit the specific needs of event management. Define event-specific user stories, set achievable sprint goals, and implement event-focused metrics to measure progress and success.
Continuously Learn and Improve: Foster a culture of continuous learning and improvement within MTD. Encourage team members to share lessons learned, conduct retrospectives after each event, and implement changes based on feedback to enhance future event management processes.
By embracing an agile approach and implementing the above advice, MTD can gain the benefits of flexibility, adaptability, and improved collaboration, ultimately delivering successful events that meet clients’ evolving requirements.
Project Team is a group of people, assigned to a task say for a particular department. The group would have been briefed on the scope, the budget and duration of the assigned task
As a PM with MTD, applying the Agile approach to our project planning and execution can be very crucial in risk assessment and mitigation. The team gets to work closely together daily on sprints of 2 – 4 weeks with specific tasks at each given time and at better speed. Having these specific tasks as focus enables the team stay very engaged for that time duration and they can clearly see the impact of the work they are doing by testing out the product and reviewing the users feedback and requirements.
By using this approach, stakeholders are carried along more effectively and transparency is maintained in cases of challenges that can be experienced. some of these challenges can come in form of Government policies and regulations, language barriers, logistics complications, changes/alterations in clients requests, sponsor dissatisfaction etc. some of these challenges can easily introduce uncertainty and complexity to the execution of a project.
At MTD, a hybrid of both Linear/Waterfall approach and Agile Project Management techniques would effectively work in the execution of the project.
As a Project Manager with MTD I will use several approaches to help the project team achieve it set aim and where there are issues to help proffer solution.
The project management can adopt the principles of VUCA, that is, Volatility, uncertainty, complexity, ambiguity. Keeping in mind it will not always go as planned. In addition to this, effective communication between the stakeholders( project manager, project team, project sponsors, regulatory agencies as well as the suppliers/endusers), time management, teamwork, a good knowledge of the regulatory environment, and good negotiation, adapting to changes or a disruption in a particular process.
The Implications of the iterative approach is that it focuses on making the project timeline cyclical to account for necessary rework and improvement. It does not address other aspects of a project like process, timeframes, or customer engagement. The process remains sequential, the timeframes are not specifically addressed, and there is no additional customer engagement. The iterative approach will give the project manager the opportunity of planning for uncertainties that may be encountered in the project, this would build transparency and accountability.
The implications of the Agile approach is that it focuses on responding to change and on the unpredictable nature of projects by being both iterative and incremental. It is less risky and guides the sponsors and stakeholders in the development of the project through scrum meetings, sprints reviews and progress. The Agile approach requires desired functionality for a specific user, to be completed in each iteration that agile uses, known as Sprints. Sprints are kept as short as possible. Here, Customer engagement, a focal point, occurs early and often.
My advice to the company would to adapt to flexibility in their project projections that no one approach is sacrosanct, that is, to important for the process. That following a strict linear approach for instance would mean that when problem arise in one particular stage of the project there will be difficulties in troubleshooting. However, if from the start of the project unforeseen circumstances are fathom in then plans will be made for such.
I have learnt that as a project manager, you must understand the crucial need for ;
1. communication between the PM, Stakeholders and even the project teams as proper communication and transparency can solve possible issues within a project.
2. Stakeholder management; this goes alongside communication. Being able to engage the stakeholders in every detail of this project can also reduce possible risks in the project.
3. Change Management: in projects such as event management changes are bound to happen and being able to communicate these changes helps makes the change in plan easier to follow through.
If my company sought my advice once what approach to take in regards to an upcoming event, I would first like to know the details of this said project and should this project need the iterative approach, the likely consequences would be:
* Increased flexibility; should any changes come up during said project it can be easily fixed.
* Enhanced Stakeholder collaboration.
* Improved risk management.
* Faster time to event execution.
* Potential for scope creep.
* Need for skilled teams.
Implications of using the agile approach:
* Continuous feedback and adaptations.
* Collaborative and empowered team.
* Flexibility and adaptability.
* Prioritization.
* Emphasis on value delivery.
* Client engagement and satisfaction.