Relative Estimation | Glossary

Definition

Relative estimation is one of the various types of estimation methods that are used in Agile Teams. It comprises of the process of estimating tasks and user stories, but not in absolute units of time.

Relative Estimation avoids some of the drawbacks of estimating in general, like seeking unwanted precision, and confusion of estimates with commitments. This is due to it being synchronous with units other than time in estimation.

Further Reading

  • “Agile Estimating and Planning” (book), by Mike Cohn.

 

Principles | Glossary

Definition

Agile Manifesto has a set of 12 principles. They are as follows :

  • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software
  • Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage
  • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale
  • Business people and developers must work together daily throughout the project
  • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done
  • The most efficient and effective method of conveying information to and within a development team is face-to-face conversation
  • Working software is the primary measure of progress

 

Further Reading

  • “Understanding The Agile Manifesto: A Brief & Bold Guide to Agile” (book), by Larry Apke