Important Things to Keep in Mind for Project Rewrites
If you are taking charge of a project that's not in the best shape it is a daunting task, especially when you're given the task of transforming it into something successful. Whether you're stepping into a managerial or CTO role or simply leading a project team, here are some of the key things you need to remember based on my experience.
1. Avoid the Big Rewrite Trap
It's tempting to start fresh with means a complete rewrite of the project. However, my experience taught me that big rewrites often lead to more problems than solutions. As you step into the rewrite journey, the existing system continues to evolve, which causes a bigger gap to catch up. Moreover, even after a massive rewrite, there's a high chance of overlooking critical edge cases, leading to unforeseen complications and frustration for customers and stakeholders.
2. Embrace Incremental Changes
Instead of attempting a big rewrite, focus on making incremental improvements. Break down the project into manageable chunks, rewrite them, thoroughly test each iteration and deploy them gradually. This approach allows you to maintain functionality while steadily enhancing the system. Plus, having the option to revert to the old system provides a safety net in case of unexpected issues.
3. Gain Support from Other Teams
Acknowledging and addressing office politics is crucial for project success. While it's tempting to go ahead with your plans, ignoring the concerns and objections of other teams can lead to resistance and ultimately project failure. Take the time to listen to their feedback, understand their challenges and incorporate their insights where appropriate. Building alliances with other teams can turn potential rivals into valuable allies, driving the success of the project.
4. Communicate Upwards Effectively
Ensuring that senior executives understand the value and direction of your project is essential for its longevity. Keep them informed about your progress, the benefits of the changes you're implementing and how it aligns with the company's objectives. Clear communication and alignment with leadership reduce the risk of sudden project cancellations and ensure continued support and investment.
5. Avoid Hype Trap
In my 16 years of experience, I have seen many things like microservices, Single-Page Applications (SPA), etc. Don't pick technologies or frameworks because they are hot, pick them because they solve the problem, help the business and your team can use them and manage them without any headaches.
What's your experience what strategy helped you in the project rewrite?
If you need any suggestions for project rewriting message me.