What is Test Estimation?

Share The Knowledge. It Grows !!!

Estimation is one of the most important and challenging topics in software development model. Software development planning and control could not be managed effectively if you don’t have reliable estimation with you. If we skipped the proper estimation then software development team or company may have to suffer far more than expected.

Under Estimation may cause following issues in the project.

  • Under Staffing.

  • The quality of a product may sacrifice.

  • Security of product may compromised.

  • The risk of missing deadline losing credibility.

Over Estimation may cause following the issues in the project.

  • More resources would be required than the actual requirement

  • It will cost more than the actual cost.

  • Delivery date may get extended than the normal required time.

  • It may impact next line up the project.

  • Top on that Over Estimated project impact the organization image.

Estimation in Agile

As per the principle of Agile, we need to develop a system in bits and bytes. So team gather the enough knowledge about the user stories and efforts required for the task. During multiple sprints, agile team members encountered with different user stories because of this estimation of the agile team goes more accurate day by day.

It’s a basic principle of Agile Estimation that every team member will be present in meeting. So that they can contribute and add more value in the estimation process. It makes more sense to involve all team member to achieve the effective and more accurate estimation.

Any software estimation process can be divided into Heuristic and Parametric type.

Heuristic (Expert Base)

• By comparing similar projects

• Expert Judgment

• Activity Based

• Task-Based

Parametric (Calculated)

• Function Points also called FP estimation

• Use Case Points

• Object Points

Common mistakes while estimating the task.

  • Underestimate the efforts required for static testing like walkthroughs, reviews and inspections.

  • Underestimate the efforts required to write paper documents.

  • Missing travel expense and stay costs for the large project.

  • Training required for tools, languages, and cultural differences.

  • Testing requirements are not testable.

  • Ignoring project management support.

  • Ignoring efforts required from the user side.

  • Ignoring efforts required in maintenance after releasing the product.

Share The Knowledge. It Grows !!!

Leave a Reply

Your email address will not be published.

Ops!! You Can not Copy from The Digital Mentor.