This time, we'll explain another 7 Agile terms that will help you decode this software development methodology.
- Acceptance Testing
- Burn Down Chart
- Daily Meeting
- Effort Estimates in Abstract Units (Points)
Acceptance TestingThe functional testing of a user story by the software development team during the implementation phase. Usually the customer specifies scenarios to test when a user story has been correctly implemented. A user story is not considered complete until it has passed its acceptance tests. This means that new acceptance tests must be created each iteration or the development team will report zero progress.
BacklogA list of user stories, bugs and features that need to be done.
Product BacklogA list of customer requirements for the entire product.
Release BacklogA list of user stories, features and bugs that should be implemented in a defined release.
Iteration BacklogA list of user stories, features and bugs that should be implemented in a defined iteration.
Burn Down ChartRelease/Iteration Burn Down chart shows implementation progress during a release/iteration. It provides answers to the following questions: When can the release/iteration be completed based on previous progress? What is the highest possible team Velocity in future iterations?
Daily MeetingIs a status check where the team meets and share progress, impediments and short term assignments. Usually three questions are asked: "What did you do yesterday?", "What will you do today?" and "What is blocking progress?".
Effort Estimates in Abstract Units (Points)Relative abstract effort units work great for experienced agile teams. Points are a relative measure of user story size. It is recommended to use discrete points scale. For example: 1,2,3,5,8,13,20. This scale means that user story with 3 points is about two times simpler than user story with 5 points, no more.
Estimation with points is easier, since you estimate-by-compare: "We'll give this story 2 points because it seems like it's twice as big as that 1-point story and about half as big as that 4-point story".
ImpedimentA thing that blocks task or user story execution. For example, J.Mouse worked on a complex algorithm and his workstation exploded. Now he can't execute his tasks and that is an Impediment. Usually impediments are reported by developers during daily meetings.
IterationA time period (usually from 2 weeks to 2 months) in which development team implements and delivers a set of functionality (user stories). It is recommended to use iterations with equal duration to have good Velocity measurement.