Watch or listen to this episode:

Summary and Resources

One of the most frustrating software projects I've been on was when we designed a product that never got built!

A couple different things happened on this project that made it difficult...

First, the project was being sold to use an agile process, but then was suddenly switched to fixed cost at the last minute.

Secondly, there were too many people in management positions. It created confusion where team members were getting conflicting instructions. The client was telling each manager different things!

And lastly the client had never designed a software product before. We tried to warn them to design a simpler product than their entire vision, but they wouldn't listen. Because they tried to design the product up front, they designed a product that was too complex for a first release.

Though we did what we could to keep the project on track, it ultimately was too expensive for them to build.

I hope this episode helps you avoid some of these mistakes on your software projects.

Have you ever been on a software project that was designed but never built? What created the situation? Leave me a comment below.