+7
большая тёрка
Большая Тёрка / Мысли / Личная лента amazingphotooftheday /
amazingphotooftheday
Customer Items and also Organizing Holdem poker : Several Price Concepts Coming from Scrum
Scrum has many exciting suggestions to get over the particular perennial challenge of accurate estimating. In this article I’d like to have a look at a collection of those approaches: story points, burn‑down velocities and also planning poker. Scrum is generally used for software development projects, but the ideas in this article could be applied to any type of work.
Step 1 : Collect Together Customer Stories
In Scrum each project is broken down into a collection of user stories. These are descriptions of a single piece of functionality that the delivered software must perform. They are really requirements, but as Kent Beck says in his excellent book “Extreme Programming Explained”, requirements sound mandatory, and much of what users initially ask for are “nice to haves. ” Each user story describes a journey through the software. For example, a story might say, “Log on using your user name and also password and be taken to the home screen. ”
The software team will work with their clients to decide on which user stories will be delivered during the next sprint of work. Sprints generally last around 20 days. To do this the development team need to estimate the work involved with each user story. This is where the particular ideas of user points and also planning poker are useful.
Step 2 : Estimate Each Customer Story In Terms of Story Items
One estimating pitfall is confusing effort (the number of hours something takes to do) with duration (over what period of calendar time something takes to do. ) For example, a developer might say a user story will take eight hours to complete and the team will assume he can do it in one day. However when he starts work he finds he has other time commitments, and can only work on the story for an hour a day. Eight days later he finishes the task. Durations are difficult to estimate; we all have good days and also bad days and some days have more interruptions than others. Scrum’s answer to this is to move the team entirely away from estimating times and instead estimate each user story in terms of story points. Story points are an abstract measure of size.
The best way of using story points is to start off with the first user story and give it a certain size, for example ten story points. Then, for the next story, ask the particular question, how big is this compared to the first one? If it is half the size it is assigned five story points. This relative comparison helps to anchor a size in the estimator’s mind.
