Planning Poker Story Point Estimation in Agile

In software development, an estimate consists of a quantified evaluation of the effort which is necessary to carry out a given development task. 

What is meant by "Estimation"?

In software development, an estimate consists of a quantified evaluation of the effort which is necessary to carry out a given development task. This is most often expressed in terms of duration. The intent here is to aggregate many individual estimates, so as to obtain an indication of the overall duration, effort or cost of a software project. Planning Poker is a consensus-based estimating technique.In Agile, it is used to estimate the product backlog:

  • Story points
  • Ideal days
  • Any other estimating unit  that can be used with planning poker


Estimate instances in ZenTao

You could estimate product, sprint, story, task, test request, etc. when you are trying to create them in ZenTao. Some for specific hours, some for specific days or weeks.


How to use planning poker for Agile estimation and planning?

At the start of the planning poker session, every person in the team holds a deck of planning poker cards. Each card contains a value like 0,1,2,3,5,8,13,20,40 and 100. The product owner or customer then reads an agile user story or describes a feature to the estimators. Here the term ‘estimators’ means the whole team. 

The estimators discuss the feature to clearly understand all of its aspects. When they are done with discussing the features, each estimator privately selects one card to represent his or her estimate.  All cards are then revealed at the same time. 


If the value selected by all the estimators are same, then that value becomes the estimate for the story.If not, then all the estimators discuss their estimates further. The estimators who selected the highest and the lowest value should especially share their reasons.After further discussion, each estimator reselects an estimate card, and all cards are again selected and revealed at the same time. This process continues until the consensus of all the estimates is achieved.

When everyone holds up the same number, we are done. That number is written as the estimate and we move on. But if the numbers are different, we discuss it and estimate again. When there is a tie in the voting between two sizes which are consecutive, for example, 5 and 8, just pick the larger size and move on. It saves a lot of time and also saves from the perils of running out of time due to underestimation of the size of a task. If the difference between the estimates is very large, for example, 3 out of 5 people are holding 5 and one person is holding a 100, then there is clearly either a product uncertainty or technical uncertainty regarding the task. In such a case, it is better to put the story aside and come back in the next meeting after doing proper research. 

Know more about ZenTao Planning Poker


References

https://www.youtube.com/watch?v=TxSzo3lwwWQ

Comments

  1. philipDecember 12, 2020 at 4:51 PM

    We use zentao for agile development and test projects to track status. After being used by several project managers, the effect is quite remarkable. The tracking method is relatively simple and error free.

    Zentao will monitor the task in depth, and evaluate the task. We use user stories, backup logs, weekly iterations, which let us have precise control over the project process. We use various forms of software testing and development life cycle, such as test case, bug management, change request type, requirement analysis, etc. of Zen Tao.
    It can also cooperate with multiple development tools, such as github.
    Highly recommended.

    ReplyDelete

Post a Comment

Popular posts from this blog

ZenTao project management software: an Open source Scrum tool and self-hosted solution

Image
  ZenTao project management software: Open source Scrum tool and self-hosted solution What is ZenTao? How ZenTao workflow fits in Scrum ZenTao is a Scrum tool for software developers, teams, companies, remote developers, and freelancers. It offers a solution to do remote collaboration work or even locally. ZenTao has an open-source version and can be self-hosted easily.  ZenTao features ZenTao Biz includes the features as below, PHP Language Written Email&Webhook Notification Backlog Management Sprint and Task Bug Tracking Roadmap Burndown Kanban SaaS Self Hosting Gantt Customized Workflow LDAP MS Word/Excel Import&Export Attendance GIT/SVN Repo Effort Log Wiki Library Role Management API Calendar  Timesheet Dashboard: Where you could find everything related to you Dashboard Gantt: You could manage task dependencies here and view them by various groups Gantt Report: Tremendous kind of report you could check to evaluate  Workload report Wiki Library: where you could view doc, sh
Read more

Top 6 FREE and Open Source Project Management Systems in 2021

Image
  1- ProjeQtOr ProjeQtOr is a free open source project management software grouping in a single tool all the features needed to organize your projects. It is simple, easy to use while covering a maximum of project management features. ProjeQtOr is designed as a collaborative tool,  available in Web mode, and so requires the setup of a Web server.  However, the installation is easy and automated as much as possible. To setup and run ProjeQtOr, a simple PHP / MySql stack is needed, you can use your favorite stack (EasyPHP, ZEND, WAMP, XAMPP). Highlights Multilingual (14 languages) Cross-Platform. 100% collaborative (web based). Web 2.0 user interface. 2- ZenTao ZenTao  is an open source project management software whose main features are product management, project management, QA management, document management, bug management and todo management. It is a professional Application Lifecycel Mangement(ALM) , covering the core process of software development. It also has powerful search fea
Read more

Why Zombie Scrum Teams Don’t Ship Fast

Image
  In environments with Zombie Scrum, people don’t understand why it’s important to ship fast. When you   ask them, they respond with a shrug. Or with a dismissive smile, because “that can’t possibly work for a product or organization as complex as ours”. For them, shipping fast is only possible for small and inconsequential products or for huge tech companies like LinkedIn, Facebook, and Etsy. Even if they’d want to, the investment would simply be too large. It’s more convenient to keep batching many updates into large, infrequent releases. Honestly, this is not very different from seeing the appeal in a healthy lifestyle but refusing to do the frequent workouts to get there. Signs to watch for Regardless of how much work Scrum Teams complete within a Sprint, features are batched into large quarterly or yearly releases. Releases are “all hands”-affairs where people clear their schedule for the evening and the next day(s) to address issues caused by the release. “That doesn’t work here”
Read more