Agile vs Waterfall: Waterfall Wins! + CHEAT SHEET

Summary

In 'Development That Pays', Gary contrasts Agile and Waterfall methodologies through a DIY challenge of hanging shelves. His initial Waterfall approach, though efficient, resulted in a crooked shelf. His father's iterative Agile method triumphed with a level outcome. However, when scaling to hang 20 identical shelves, Gary's Waterfall strategy, aided by a custom jig, proved faster and more effective. The key to Waterfall's success was predictability; it thrives with high confidence in repetitive tasks, unlike Agile, which excels in unpredictable scenarios. The video concludes that both methodologies have their merits, depending on the project's nature.

Takeaways

• 🛠️ The classic DIY challenge of hanging a shelf serves as a metaphor for comparing Agile and Waterfall methodologies.
• 🏆 The father's Agile approach, which involved iterative steps and multiple checks, resulted in a level shelf, symbolizing a victory over the son's Waterfall approach.
• ⏱️ The son's Waterfall method, characterized by a linear, planned process, was efficient but less effective due to the resulting wonky shelf.
• 🔄 The father's iterative process was adaptable, allowing for adjustments and checks, which is a key advantage of Agile methodology.
• 🛠️ The son introduces a 'jig' tool for hanging 20 identical shelves, which shifts the advantage towards a Waterfall approach when dealing with repetitive tasks.
• 🏗️ The jig's success hinges on two conditions: flat walls and identical shelves, highlighting the need for predictability in Waterfall projects.
• 🔧 The father's process remains effective regardless of wall or shelf variations, showcasing the flexibility of Agile in diverse conditions.
• 📉 The script suggests that Waterfall is more suitable for predictable, repetitive tasks, while Agile thrives in unpredictable or novel situations.
• 📚 The narrative illustrates that the choice between Agile and Waterfall should be based on the nature of the task at hand, rather than a one-size-fits-all approach.
• 🌟 The episode concludes with the message that both methodologies have their place, emphasizing the importance of selecting the right process for the right job.

Q & A

What was the initial challenge presented in the 'Development That Pays' episode?

The initial challenge was a DIY task of hanging a shelf, which was a competition between the speaker's 19-year-old self and his father.

Why did the father's method of hanging the shelf win in the first challenge?

The father's method, which was more iterative and Agile, won because it resulted in a level shelf, highlighting the effectiveness of Agile over the speaker's Waterfall approach.

What is the Waterfall approach in the context of the script?

The Waterfall approach refers to the speaker's method of hanging the shelf, which involved measuring, marking, drilling, and screwing in a linear, non-iterative sequence.

How does the script suggest that the Waterfall approach could be improved for hanging multiple shelves?

The script suggests using a jig to standardize the process for hanging multiple shelves, which is more efficient in a Waterfall scenario where predictability is high.

What are the two conditions that must be true for the jig to work effectively in the Waterfall approach?

The two conditions are that all walls must be reasonably flat and all shelves must be identical for the jig to work effectively and ensure the holes align correctly.

Why did the Waterfall approach win in the scenario of hanging 20 identical shelves?

The Waterfall approach won because the jig allowed for a standardized, efficient process that was faster and more suitable for hanging multiple identical shelves.

What does the script imply about the adaptability of the father's Agile method?

The script implies that the father's Agile method is adaptable and would work regardless of wall conditions or shelf variations, unlike the Waterfall approach which requires specific conditions.

What is the key takeaway from the script regarding the choice between Agile and Waterfall processes?

The key takeaway is that the choice between Agile and Waterfall processes depends on the predictability and familiarity of the task at hand; Agile is better for unpredictable or new tasks, while Waterfall is more suitable for predictable, repetitive tasks.

How does the script use the analogy of hanging shelves to discuss software development methodologies?

The script uses the analogy of hanging shelves to illustrate the principles of Agile and Waterfall methodologies in software development, comparing the efficiency and effectiveness of each approach in different scenarios.

What is the significance of the term 'jig' in the context of the script?

In the context of the script, 'jig' refers to a tool that aids in the efficient and accurate hanging of multiple shelves, symbolizing the use of tools and templates in the Waterfall approach to ensure consistency and efficiency.

Outlines

00:00

🛠️ The Waterfall vs. Agile DIY Challenge

In this episode of 'Development That Pays', Gary recounts a DIY challenge where he, at 19, competed against his father in hanging a shelf. His father's Agile approach, which involved iterative steps and multiple checks for level, resulted in a perfectly hung shelf. In contrast, Gary's Waterfall method, characterized by a one-time measurement and execution, led to an uneven outcome. Gary ponders whether there are scenarios where the Waterfall approach could be superior, suggesting a shift in the challenge's parameters to hanging 20 identical shelves.

Keywords

💡Waterfall

Waterfall is a project management methodology that follows a sequential design process where each phase of the project must be completed before the next one can begin. In the video, the 'Waterfall' approach is initially portrayed as less effective for hanging a single shelf, but later is shown to be efficient when adapted with a jig for hanging multiple identical shelves. It is highlighted as a method that excels in predictable and repetitive tasks.

💡Agile

Agile is a project management approach that emphasizes flexibility, iterative progress, and customer feedback. It is often used in software development and other fields where requirements may change over time. In the video, Agile is depicted as the winning method for hanging a single shelf due to its iterative nature, allowing for adjustments and checks at each step, leading to a level shelf.

💡DIY Challenge

A DIY (Do-It-Yourself) challenge refers to a task or project that individuals attempt to complete on their own, often without professional assistance. In the video, the challenge is to hang a shelf, and it serves as a metaphor for comparing the Waterfall and Agile methodologies in a practical, everyday scenario.

💡Efficiency

Efficiency in the context of the video refers to the ratio of productive work to time spent and resources consumed. The Waterfall method is described as being efficient in terms of time when hanging multiple shelves with the help of a jig, as it streamlines the process into a single, repeatable set of actions.

💡Effectiveness

Effectiveness is the extent to which a project achieves its intended purpose or outcome. The video contrasts the effectiveness of the Waterfall and Agile methods, showing that while the Waterfall method was efficient, it was initially ineffective for hanging a single shelf straight. Agile, on the other hand, was effective for a single shelf but less efficient.

💡Jig

A jig is a device used to hold or guide tools or workpieces in the right position for an operation, such as drilling. In the video, the creation of a jig is a turning point that allows the Waterfall method to become efficient for hanging multiple shelves, demonstrating how tools can enhance a methodology's performance.

💡Iterative Process

An iterative process is one that is repeated with the possibility of change and improvement at each step. The Agile method is described as iterative, with the video showing how each hole is drilled, checked for level, and adjusted as needed, which is crucial for achieving a level shelf in the single shelf scenario.

💡Level

In the context of the video, 'level' refers to the horizontal alignment of the shelf. It is a key outcome measure for the effectiveness of the hanging process. The video uses the levelness of the shelf as a criterion to judge the success of the Waterfall and Agile methods.

💡Predictability

Predictability in the video refers to the ability to anticipate the steps and outcomes of a process with confidence. It is suggested that when tasks are predictable, as with hanging identical shelves, the Waterfall method can be more effective due to its structured, linear nature.

💡Flat Walls

Flat walls are mentioned as a necessary condition for the jig to work effectively in the Waterfall method. It highlights the importance of environmental factors in the success of a project management methodology, as the jig's effectiveness is contingent upon the wall's flatness.

💡Identical Shelves

The video emphasizes that the Waterfall method's success with the jig is dependent on all shelves being identical. This underscores the importance of standardization in processes and how it can impact the choice of project management methodology.

Highlights

The classic DIY challenge of hanging a shelf serves as a metaphor for comparing Agile and Waterfall methodologies.

Gary's 19-year-old self represents the Waterfall approach, while his dad symbolizes Agile.

Waterfall's high efficiency in the shelf-hanging challenge is noted, but it results in a wonky shelf, indicating low effectiveness.

Agile's iterative process, as demonstrated by Gary's dad, ensures a level shelf through multiple checks and adjustments.

The narrative questions whether Waterfall is destined to lose or could have claimed victory under different circumstances.

Gary introduces a new challenge of hanging 20 identical shelves to test Waterfall's potential for success.

The bespoke nature of Agile is deemed too labor-intensive for hanging multiple shelves, calling for a more standardized approach.

Gary invents a jig to streamline the process for hanging multiple shelves, embodying the Waterfall methodology.

The jig's effectiveness relies on the assumption of flat walls and identical shelves, highlighting the need for predictability in Waterfall.

Gary demonstrates the jig's use, showcasing how it ensures holes are drilled at the correct location and angle.

The final result with the jig is a level shelf hung quickly, suggesting Waterfall's victory in this scenario.

The conditions for Waterfall's success are identified as the predictability of the task and the uniformity of the components.

Gary contrasts Agile's flexibility, which is not dependent on the predictability of the task, with Waterfall's reliance on it.

The conclusion is that both Agile and Waterfall have their merits, depending on the nature of the project at hand.

The episode ends with a reminder that the choice between Agile and Waterfall should be based on the specific requirements of the task.

Transcripts

Previously on Development That Pays...

My 19 year old self took on my dad at the classic DIY challenge of hanging a shelf.

To no one's surprise, my dad won

It was not just a victory of experience over enthusiasm.

It was also a victory of Agile over Waterfall.

Was waterfall destined to lose.

Or could it have claimed victory?

What has to be true for Waterfall to win?

Hi this is Gary.

Welcome to "Development That Pays"

If you missed the last episode...

you may decide that you were glad that you missed it.

Because we spent the entire time attaching this shelf

to this wall.

Not once...

but twice.

My method of hanging the shelf - very much a waterfall approach -

scored high on efficiency:

I measured everything

marked everything

drilled everything

screwed in all the screws

But it scored badly in effectiveness:

the result was a wonky shelf.

My dad's process was was much more iterative - much more Agile.

He marked one hole

He drilled ONE hole

He fitted one plug

He fitted one screw [And so on...]

He checked for level multiple times

so it came as no surprise that the end result was also

Level

It was a fair fight: my dad's method won fair and square.

But it did make wonder

But why did it win?

And could there be situations where

a Waterfall approach would be victorious.

Let's change the parameters a bit:

instead of the challenge being to hang a shelf,

the challenge now is to hang 20 identical shelfs.

My dad's process is awesome for a single shelf,

but for 20 shelves it's far too much work.

His process is bespoke

I need something more "cookie cutter"

I've come up with this jig

I think it's going too make all the difference.

Match this mark to the centre mark on the wall

adjust for level... using the built in spirit level.

Press it firmly against the wall ... The rubber backing keeps it in place

. The drill guides ensure that the holes are

in exactly the right location

it also ensures that the hole is drilled at right angles to the wall.

Drill all 4 holes.

Remove the jig

4 plugs in

Offer up the shelf

In go the screws... but not too tight.

Final check for level.

Tighten the screws all the way.

Not just a job done well.

But a job done quickly. Really quickly.

Waterfall just beat Agile

Why did Waterfall win?

Clearly, the jig made all the difference

But in order for the jig to work as expected,

at least two things must be true:

All of the walls must be reasonably flat

if they're not, then the jig won't "stick" to the wall.

All of the shelves are identical

if they're not, the holes drilled in the wall won't line up with the holes on the shelf.

Notice that neither of these conditions is necessary for my dad's process to work:

his process will always work:

On flat walls, on bumpy walls

with shelves of all shapes and sizes.

So it would appear that it's all about predictability.

If the steps can be predicted with a high level of confidence

- for example, if it's an activity that we've completed many times before -

then a waterfall process is likely to be the best choice.

Conversely, if the level of confidence is low

- for example, if we're attempting something for the first time -

then an Agile process is going to pay dividends.

Agile and Waterfall. Horses for courses.

Many thanks for watching. Talk to you next time.