DEV Community

Jonathan Hall
Jonathan Hall

Posted on • Originally published at jhall.io on

How to release 2 years of unfinished code, the "Agile way"

I was recently conversing with someone who just joined a new team. This new team has been working on a new software project for about 2 years, and they haven’t released anything yet. Now management has decided it’s time to release something, and the team has 8 weeks to get something out the door.

How would you address this situation?

Take a moment and consider, if you like. I’ll wait.

I'll wait...

So what did you come up with?

I, and the others talking with this person, came up with a few pieces of advice. I’ll mention some of them briefly. Let me know if you agree or disagree, or what you might do differently.

  • Release something ASAP.

  • Treat the last 2 years worth of code as “warehouse of old parts”

  • Don’t make an 8-week plan.

There’s a ton more that could be said. Unless/until I hear back from this person in 8 weeks time, it’s a hypothetical from my standpoint. So it’s fair game for any other suggestions. I’d love to hear yours!


If you enjoyed this message, subscribe to The Daily Commit to get future messages to your inbox.

Hostinger image

Get n8n VPS hosting 3x cheaper than a cloud solution

Get fast, easy, secure n8n VPS hosting from $4.99/mo at Hostinger. Automate any workflow using a pre-installed n8n application and no-code customization.

Start now

Top comments (0)

A Workflow Copilot. Tailored to You.

Pieces.app image

Our desktop app, with its intelligent copilot, streamlines coding by generating snippets, extracting code from screenshots, and accelerating problem-solving.

Read the docs

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay