SMART Professional™ Agile Generalist
- Small group
- Free cancellation
- Duration: 2 Days
Rated 5 out of 51 Reviews
From CHF 1900
Planned versus Actual Velocity is a forecasting tool based on the on the observed and actual performance. The team can tell the customer whether they will finish the backlog of user stories by the planned number of iterations or not.
Planned vs. actual velocity is a predictive tool based on observations and actual performance. It enables the team to tell the customer if they will complete the backlog of user stories before the planned number of iterations.
The planned velocity is the team's expectation of the story points to be delivered in each iteration. Actual velocity refers to actual sum of the story points that they delivered in each iteration.
Burndown or Burnup charts show how much work has been completed and how much work is remaining as the iteration progresses.
Burndown and Burnup chart present the same data in a different way. Teams choose how they would like to see their data.
Some teams combine burndown and burnup charts into one chart. The chart shows the remaining actual story points as well as the completed cumulative story points.
Acceptance tests are written before new products are developed (on the back of the story cards). They ensure that the code meets the requirements. For software, the initial tests will fail because the code is not yet fully developed. If the code is written correctly, it will pass the tests.
The higher the success rate in the tests, the greater the probability that there will be no failure in production.
Escaped defects are the defects that slipped by the testing team. The defect rate measures how often defects are found. Escaped defects are the most expensive to fix. An increase in escaped defects signals that a process is flawed.
Kanban boards are sign boards. Kanban (Japanese – "cards you can see") is a pull system where resources prevent work from piling up in a constrained process so that the lead time to deliver value to the business is not compromised. Work in the Kanban board moves from left to right and only limited number of items can be in each stage of the project. Teams are disciplined and committed to working within their specified Work-in-Progress (WIP) limits to ensure optimal flow in the system.