Member-only story
Having a pragmatic approach to anything in life is always a good idea because it helps you to avoid any hiccups in the longer run.
Today let’s talk about 3 rules that every developer should follow to avoid any hiccups in software development.
1. Be practical when you give project estimates:
Estimates are driven by project requirements, and sometimes project requirements change during development or are ambiguous, to begin with.
The problem with an ambiguous project requirement is, different people when they read it will have different ideas about the requirement and its complexity.
A bigger problem arises when developers read such requirements and provide estimates for it, so before you give the estimate here are some of the rules you can follow
A. Read the project requirement carefully.
B. Ask all your doubts, no matter how silly they sound, leave no room for assumptions.
C. If you see a complex module, which would need some proof of concept work then make sure you mark those modules as spike and communicate the same with your manager.
D. Do not give estimates based on your gut feeling or assumptions, be very clear on what the…
