Skip to content

Category: velocity

  • warning: Invalid argument supplied for foreach() in /home/artemmarchenko/agilesoftwaredevelopment.com/modules/cck/content.module on line 1270.
  • warning: Invalid argument supplied for foreach() in /home/artemmarchenko/agilesoftwaredevelopment.com/modules/cck/content.module on line 1270.
  • warning: Invalid argument supplied for foreach() in /home/artemmarchenko/agilesoftwaredevelopment.com/modules/cck/content.module on line 1270.
  • warning: Invalid argument supplied for foreach() in /home/artemmarchenko/agilesoftwaredevelopment.com/modules/cck/content.module on line 1270.
  • warning: Invalid argument supplied for foreach() in /home/artemmarchenko/agilesoftwaredevelopment.com/modules/cck/content.module on line 1270.
  • warning: Invalid argument supplied for foreach() in /home/artemmarchenko/agilesoftwaredevelopment.com/modules/cck/content.module on line 1270.
  • warning: Invalid argument supplied for foreach() in /home/artemmarchenko/agilesoftwaredevelopment.com/modules/cck/content.module on line 1270.

Unpublished
n/a

Unpublished
n/a

Unpublished
n/a

Unpublished
n/a

Unpublished
n/a

Unpublished
n/a

Unpublished
n/a

Unfinished work

November 21, 2007 by Artem Marchenko

half iPod

Agile processes recognize and try to effectively use the fact, that software creation is a difficult and not very predictable process. Therefore quite often teams applying agile processes end up with the not completing all the committed product backlog items by the iteration end. Teams just starting to employ Scrum or XP can sometimes end up with half of the items being not completely done. Naturally in such a situation people are tempted to finish the uncompleted stuff as soon as possible. Some think about extending the iteration length for a week or two, some think about marking the item half-done, adding half of its size to the team velocity and continuing with it during the next iteration.

Measures of size

December 11, 2006 by Artem

Measurement is fundamental to any engineering discipline and the planning of a software creation work is no different. Whenever you plan to make or renew a piece of software the most important metric as the workload size. Measure of size is important because knowing the amount of work to do and the team skills (i.e. velocity) you can easily derive the work costs and duration. Agile software development methods do strive against the overplanning and overdetalization.

Best of AgileSoftwareDevelopment.com