If your development starts before any design is in place, it’s like driving in a foreign country without a map. And the chances are you’ll ne to come back and rework things that weren’t design correctly. If this happens, and you identify refactoring that will be necessary, don’t delay it, because your coders will be building something that they’ll ne to fix later.
Or, you can change the design
Build it correctly the first time around. Now obviously it’s impossible to create a perfect design up front. Business requirements can and usually will change up until the day the project is finish, and reworking will be necessary to go in and make the changes to comply with them. But knowing that everything is not always in your control, try and be smart about planning the things that are in your control. That way you’re not accumulating technical debt at twice the spe.
Anticipate necessary integrations
While you’re in your planning stage, ask yourself what other areas of your infrastructure this project will affect. If there will be necessary integrations (which in all likelihood there will be) then figure out if your design can work in a plan for that. By doing this early on you save yourself the time on refactoring and reconfiguring if two systems overseas chinese in europe data won’t play nice. Be prepar. 3. Take your time to do it right the first time Of course you are going to get pressure from your higher ups to deliver on a project as soon as you can.
Decisions you make to cut corners
Will cost you down the line. If you just do the what name you saved your video under minimum amount to get a project finish, it will be releas with a substantial amount of technical debt. And the risks of any anticipat refactoring will increase dramatically, especially if it becomes integrat with the rest of your IT infrastructure. Save the nightmare later, do it now.
Document everything you do
Your 3rd grade math teacher taught you a valuable lesson, “show your work.” Make sure that your developers and project managers document their tg data work so that if/when any change nes to occur, there is a clear roadmap to do it. 5. Flexible is better Your IT nes are going to change, think about how much the landscape has chang in the last decade alone.