Estimation made fun! The Ulassa app is designed to assist you in your daily work as a Scrum master or member of an agile developer team. Aimed specifically at remote teams, the upcoming first release will allow you to play online rounds of Planning Poker in order to collectively evaluate the complexity of your next development tasks.
Planning poker is a classic example of Delphi being applied in an agile scenario. Many organizations repeat similar work and they capture effort details about the tasks. If the organization has sufficient historical data, it may be possible to use that historical data to estimate the work in hand.
Planning Poker is a consensus-based estimation technique to estimate product backlogs. It can be used with various estimating units, but we use Planning Poker with Story Points. Find out how we build Scrummer - an app for Planning poker.
Negotiate estimates with Planning Poker. Planning Poker is one of the gross-level estimation techniques, using a modified version of Fibonacci sequence: 1, 2, 3, 5, 8, 13, 20, 40, 100. To estimate items from the product backlog, team members get the same sets of cards with numbers on them.
Scrumpy Planning Poker is a free online planning poker application for distributed agile teams with Jira integration. It runs on mobile, tablet and desktop computers connecting multiple participants in a real-time story estimation session. It has many nice features like.
More details. Agile Poker is a flexible toolkit for estimating your backlog to get it ready for grooming and planning.Inspired by the most popular estimation methods, it derives the best scrum estimating practices from each of them. The app supports team managers in getting trustworthy estimates for accurate planning, by engaging all team members in the process.
One pitfall of Planning Poker resides in making “convergence to consensus estimate” an obligation rather than a natural result of the conversation that follows a round of play. Doing so runs the risk of erasing useful information, i.e. the degree of uncertainty conveyed by a wide spread in the initial estimates.
Estimating time for software development in groups can be tricky. The first person's response often plants an idea in the heads of the rest of the group, leading to an incorrect estimate. One way of getting around this is to play a few rounds of planning poker.