Search a title or topic

Over 20 million podcasts, powered by 

Player FM logo
Artwork

Content provided by Brian Marick. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Brian Marick or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.
Player FM - Podcast App
Go offline with the Player FM app!

E47: Oops! The Winston W. Royce Story

26:45
 
Share
 

Manage episode 471354957 series 3373101
Content provided by Brian Marick. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Brian Marick or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

In 1970, Winston W. Royce published a paper “Managing the Development of Large Software Systems.” Later authors cited it as the justification for what had come to be called the "waterfall process." Yet Royce had quite specifically described that process as one that is "simplistic" and "invites failure."

That's weird. People not only promoted a process Royce had said was inadequate, they cited him as their justification. And they ignored all the elaborations that he said would make the inadequate process adequate.

What's up with that? In this episode, I blame metaphor and the perverse affordances of diagrams.

I also suggest ways you might use metaphors and node-and-arrow diagrams in a way that avoids Royce's horrible fate.

In addition to the usual transcript, there's also a Wiki version.

Other sources

Credits

Dawn Marick for the picture of the fish ladder. Used with permission.

  continue reading

52 episodes

Artwork
iconShare
 
Manage episode 471354957 series 3373101
Content provided by Brian Marick. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Brian Marick or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

In 1970, Winston W. Royce published a paper “Managing the Development of Large Software Systems.” Later authors cited it as the justification for what had come to be called the "waterfall process." Yet Royce had quite specifically described that process as one that is "simplistic" and "invites failure."

That's weird. People not only promoted a process Royce had said was inadequate, they cited him as their justification. And they ignored all the elaborations that he said would make the inadequate process adequate.

What's up with that? In this episode, I blame metaphor and the perverse affordances of diagrams.

I also suggest ways you might use metaphors and node-and-arrow diagrams in a way that avoids Royce's horrible fate.

In addition to the usual transcript, there's also a Wiki version.

Other sources

Credits

Dawn Marick for the picture of the fish ladder. Used with permission.

  continue reading

52 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Listen to this show while you explore
Play