In any phase, the sooner we see a defect, the less is the cost spent on rectifying the defect. It becomes a costlier affair in later stages. The best phase is Requirements phase. When the defect is found in later phases, it costs more for its correction.
Above answer was rated as good by the following members: s_prachu
RE: Best to solve defects - requirements, plan, design...
In any phase, the sooner we see a defect, the less is the cost spent on rectifying the defect. It becomes a costlier affair in later stages. The best phase is Requirements phase. When the defect is found in later phases, it costs more for its correction.
RE: Best to solve defects - requirements, plan, design...
The best time to solve the defect is “Now”. As soon As possible.
Nobody can tell at what phase the defects comes. As soon as the defect comes, it is better to rectify it as soon as possible. It will help in budget, time constrains and quality.
RE: Best to solve defects - requirements, plan, design...
Requirement phase, as early the bug is detected and solved, it costs less as compared to later stages because there goes various inputs to it which attracts cost.
RE: Best to solve defects - requirements, plan, design...
best time to solve defects is the first stage itself that is requirement stage. and the last attempt where we can solve a defect is testing stage as that is the bottle neck stage for solving.
1 
0