Story Points in estimating work

One of effective way to estimate the work in software development is to use Story points. The story points are based on size and complexity, not duration.  They are also become unitless, they not measured by time or another units. One other good quality of story points is that they are additive, unlike time. Also they extremely easy to understand.

User Story Scenarios

Each User Story needs to be testable, need to demonstrate, that requirement has been met. Here is effective formula, which demonstrate, that specific user story has been met:

User Stories

User Stories are an Agile term for what traditionally have been called “software requirements“. They are a brief statements of the intent or need that the system must do for a particular users.

What characteristic should requirement possess?

The requirement should be Complete

3 Levels of requirements in Agile development

Requirement levels

In Software Development Requirements have 3 levels:

Business requirements (Vision and Scope document)
– expanded description of customers business
– business point of view requirements
– functionalities which should be made in our application