Why Agile PM Is Necessary
Agile PM is increasingly important in modern project environments because:
1. Things change quickly
Whether youâre building software or LEGO islands, requirements shift and ideas evolve. Agile allows teams to adapt fast without throwing away all previous work.
2. It breaks big tasks into achievable chunks
Instead of feeling overwhelmed, the team focuses on completing small pieces of work in short cycles. This helped us concentrate on one element at a time during the build.
3. Teams work better when communication is constant
Agile encourages collaboration and transparency. In the workshop, everyone could see what tasks were planned, in progress, or done, which avoided confusion and overlap.
4. It makes progress visible
With tools like the Kanban board and burn-down chart, we could instantly see how much we had left to complete. This kept everyone focused and motivated.
Agile isnât just a project method â itâs a mindset that values teamwork, flexibility, and learning by doing. Todayâs workshop proved exactly why it works.
⸝
Agile Tools Used in the Workshop (and How They Helped)
â 1. Kanban Board
The Kanban board was divided into columns:
Product Backlog â To Do â In Progress â Done
We wrote each required island feature on sticky notes and moved them across the board as we worked.
It helped us:
⢠Visualise the whole project at a glance
⢠Keep track of what was done and what still needed attention
⢠Avoid people working on the same task by accident
This tool made our teamwork much more structured despite the pressure.
⸝
â 2. Product Backlog
This was the list of everything our island needed, written on sticky notes with numbers representing priority or difficulty (e.g., Stadium 9, Fire Station 12, Healthy Citizens 26).
The Product Backlog helped us:
⢠Break the big assignment into smaller tasks
⢠Prioritise what to build first in the limited time
⢠Understand the scope of the project before we started building
Without it, we would have spent half the time figuring out what we were supposed to make.
⸝
â 3. Burn-down Chart
The burn-down chart tracked how many tasks were remaining across the sprint (our 10-minute âmini sprintâ). The red line dropped as we completed tasks, showing our progress over time.
It helped us:
⢠See whether we were on track to finish
⢠Notice when progress slowed
⢠Stay motivated by seeing the workload decrease
Even though this was a physical chart drawn on a flip chart, it worked exactly like a real Agile workspace.














