Bridging the Gap Between Agility and Planning
The paper introduces Milestone Driven Agile Execution (MDAX), a method-agnostic hybrid framework that retains agile's empirical control while aligning backlog prioritization with strategic milestone plans to bridge the gap between agility and long-term planning.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are leading a group of friends to build a massive, custom treehouse in your backyard. You want the process to be fun, flexible, and adaptable (like Agile), but you also need to make sure you have enough wood, the right tools, and a finish date before the neighborhood block party (like Planning).
Usually, these two ideas fight each other. Traditional planning is like a rigid blueprint that says, "Hammer this nail at 9:00 AM, then saw that board at 9:15 AM." If a storm comes or you find a rotten branch, the whole plan breaks. Pure Agile is like saying, "Let's just start building and see what happens!" which is great for creativity but terrible if you need to promise the neighborhood you'll be done by Saturday.
Dr. Eduardo Miranda's paper introduces MDAX (Milestone Driven Agile Execution) as the perfect bridge between these two worlds. Here is how it works, explained simply:
1. The Core Idea: Plan the "States," Not the "Steps"
Most people plan by listing tasks (e.g., "Cut wood," "Paint wall"). MDAX says: "Stop planning the steps; plan the states."
Think of it like a video game. You don't plan every single jump and button press. You plan the levels (Milestones).
- Level 1: The foundation is poured.
- Level 2: The frame is up.
- Level 3: The roof is on.
- Level 4: The treehouse is ready for the party.
In MDAX, you define these "states" (Milestones) clearly. You know what the treehouse needs to look like at each stage, but you don't dictate how the team gets there. Maybe they paint the walls before the roof, or maybe they do it after. The team figures out the specific steps (tasks) as they go, but they are always marching toward the next "Level."
2. The Two Main Maps
To make this work, MDAX uses two specific maps:
A. The Milestone Plan (The "Destination Map")
This is a short list of the big goals. It's like a treasure map showing the islands you must visit.
- Hard Milestones: These are non-negotiable. "The Block Party is on June 1st." If you aren't done by then, the party is ruined. These are your anchors.
- Soft Milestones: These are goals you set for yourselves, like "Finish the roof by May 15th." If you slip a little, it's okay, as long as you catch up.
B. The Work Package Schedule (The "Puzzle Map")
This is where the magic happens. Imagine you have a giant puzzle board.
- You have a pile of puzzle pieces (the work your team needs to do).
- You have a grid with time on the bottom and people on the side.
- You take the pieces and fit them into the grid like a game of Tetris.
- You make sure the pieces fit before the "Hard Milestone" (the Block Party) arrives.
- Crucially, you don't glue the pieces down permanently. If you realize a piece is too big or the team is tired, you can move the pieces around. The goal (the Milestone) stays the same, but the path to get there changes.
3. The Team's Role: The "Visual Workshop"
MDAX suggests doing this planning in a room with big whiteboards and sticky notes.
- Everyone plays: The boss, the builders, and the designers all move the sticky notes around.
- Why? If you just tell the builders, "Build this," they might feel like cogs in a machine. If they move the notes themselves, they say, "Oh, if we do the painting first, we can finish the roof faster!"
- The Result: The team owns the plan. They aren't following orders; they are solving a puzzle together.
4. The "Just-in-Time" Detail
Here is the best part: You don't plan the tiny details yet.
- You know you need to build the "Frame" (Milestone).
- You know you have two weeks to do it.
- But you don't decide exactly which screw goes where until the week you start building the frame.
- This keeps the plan flexible. If you find a better type of wood halfway through, you use it. You don't have to rewrite a 100-page manual.
5. Keeping an Eye on the Clock
The paper suggests using simple charts to see if you are on track.
- The "Slip Chart": Imagine a train schedule. If the "Roof" train is supposed to leave on Tuesday but you see it's already Wednesday, the chart turns red. It tells you immediately, "Hey, we are slipping!"
- The "Earned Value" Chart: This tells you if you are working too hard for too little progress (like running on a treadmill that isn't moving) or if you are ahead of schedule.
Summary: Why is this a game-changer?
Traditional planning is like a train on a track: It's fast and predictable, but if the track is blocked, the train crashes.
Pure Agile is like surfing: It's flexible and fun, but you might get swept out to sea if the waves get too big.
MDAX is like a guided tour on a river raft.
- You have a map of the big rapids (Milestones) and the finish line (The Party).
- The guide (the Plan) tells you where the dangerous rocks are.
- But the rafters (the Team) decide how to paddle, when to lean left or right, and how to navigate the current in real-time.
This way, you get the predictability of a plan (you know when you'll arrive) with the flexibility of agility (you can handle whatever the river throws at you). It bridges the gap between "We need a schedule" and "We need to be flexible."
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.