How to fail your next software development project

The process of creating software seems simple but is often met with difficulties. Here is the ultimate guide on how to succesfully fail your next project.


Do not over communicate, as a matter of fact do communicate as little as and as infrequently as possible. Do not reply to emails and messages on Slack (if you are unlucky to use it) and if by any chance you do, then delay your response as much as possible.

Objectives and specification of deliverables: be as vague as possible, do not define precisely what needs to be done. If you are asked to actually spend time to think things through and define those deliverables yourself, be sure to spend as little time as possible on this, just give the impression you did your homework would do just fine.

Work with people you don’t like. Life is short so you should spend as much time with people you don’t get along well.

When you bring people onboard your team, make sure you bring people with no experience. Get them to do the work with no supervision, bonus point if you agree to pay them per hour.

Processes are un-necessary. Just improvise every single time and make sure to re-invent the wheel because it so much fun.

Working remotely is not rocket science, you can benefit from a team with the best combination of: motivation, commitment and skills and experience.

Working remotely well as the added benefit of: Agile + Scrum + Skilled workforce + Communication

  • Transparency
  • Efficiency
  • Speed, Velocity, faster feedback loop for your product
  • Less time spent = lower costs.
  • Larger pool of suitable candidate = less time spent on recruitment (cheaper HR costs). and more time spent on your product.

Good definition of the work

Either spend a lot of time at the beginning, before the development start of start the development very quickly with very short development cycle and frequent planning sessions.

The sprint based approach: a clear objective + fixed amount of time and a fixed set of time and people. Tasks a divided in small and manageable chunks and assigned to team members.

  • 1 week product & design planning sprint
  • 1 weekly sprint & review planning session
  • 1 daily standup meeting

Placeholder text by Space Ipsum. Photographs by NASA on The Commons.