Agile Project Management for Event Planning: Zanzibar Case
Learn how to use Agile, Jira, and MoSCoW prioritization to manage complex logistics and stakeholder challenges in event planning and staff retreats.
Project Execution: Zanzibar Staff Retreat
Navigating Logistics, Stakeholders, and Agile Planning
Project Management Team
Project Context & Scope
Goal: Organize a 5-day team-building retreat for 50 staff members to boost morale and foster cross-departmental collaboration.
Timeline: 3 Months (Planning to Execution)
• International Flights & Transfers<br>• Accommodation (Resort Buyout)<br>• Structured Team Activities<br>• Gala Dinner & Awards
The Project Cast
Director
Project Sponsor. Approves budget and strategic vision.
Project Manager
Lead. Manages schedule, risks, and unified communication.
Finance Manager
Controls cash flow and audits vendor quotations.
Procurement Officer
Vendor selection (airlines, hotels) and contract negotiation.
Field Officer
Logistics execution and on-ground coordination in Zanzibar.
Methodology: Agile Implementation
Although this is an event, we adopted Agile/Scrum principles to manage volatility in pricing and requirements.
Sprints: 2-week cycles focusing on specific themes (e.g., 'Flight Sprint', 'Accommodation Sprint').
Standups: Daily 15-min syncs between Procurement, PM, and Field Officer.
Backlog: Prioritized list of activities and logistical requirements in Jira.
Challenge 1: Scope Creep
The Director requested a last-minute addition: A private sunset dhow cruise with live music, which was not in the original project charter.
Solution: Formal Change Control
1. Used the Change Control Board (CCB) process.<br>2. Finance Analyst calculated the cost impact ($5,000 extra).<br>3. PM presented trade-offs: Approve extra budget OR remove the standard team dinner.<br>4. Outcome: Director approved the budget increase formally.
Challenge 2: Resource & Budget Constraints
Conflict: Flight prices increased by 20% during the approval lag time. <br><br><b>Solution: Prioritization (MoSCoW)</b>. We categorized 'Premium Room Views' as 'Could Have' and downgraded to Standard Rooms to secure the 'Must Have' flights.
Challenge 3: Communication Breakdown
Issue: Stakeholders had misaligned expectations regarding the itinerary. The 'Relaxation Time' was interpreted differently by the Field Officer vs. the Director.
Mitigation: Weekly Governance Meetings & Visualization.
• Established a 'Friday Check-in' with all leads.<br>• Created a visual hour-by-hour itinerary heatmap shared on Confluence.<br>• Field Officer shared video walkthroughs of venues.
Tools & Technology
Jira (Task Tracking)
Used Kanban boards to track logistical tasks (To Do, Booking In Progress, Booked, Paid).
Confluence (Knowledge)
Central repository for flight manifests, dietary requirements list, and emergency protocols.
WhatsApp (Real-time)
Dedicated broadcast group for staff updates during the trip.
Risk Management Strategy
Medical/Health Incidents
Required Yellow Fever cards check 2 weeks prior. First aid kit on all buses. Hospital route mapped.
Weather Disruption
Indoor backup venues booked for all outdoor dinners. 'Rainy Day' activity list prepared.
Post-Project Outcomes
95% Satisfaction Score
Based on post-trip anonymous survey.
Under Budget by 3%
Saved on accommodation, reallocated to emergency fund which was unused.
Key Lesson: Early involvement of the Procurement Officer in the planning phase reduced vendor negotiation time by 2 weeks.
- project-management
- agile-methodology
- scrum
- event-planning
- case-study
- jira
- risk-management
- logistics