Shulou(Shulou.com)06/03 Report--

Pay attention to Jiawei Technology and gain New knowledge of Operation and maintenance

First, why not use "man and nature"?

Traditional IT projects, especially software development projects, often use "human nature" as the quantifier of workload assessment, or even represent a way of evaluation. In the classic work of software project development, the Myth of Man and Moon, it clearly points out the great disadvantages of evaluating the workload of requirements according to "man-month" or "man-heaven". One of the main reasons is that this word gives people the illusion that "software development can be completed more quickly with more developers". In Agile agile projects, the use of "human nature" during the rapid needs assessment phase is mostly avoided. Please refer to the Myth of Man and Moon for details.

The most famous illustration "Tar Pit" in the Myth of Man and Moon

II. Story Point story point

As a new mode, intelligent edge computing makes every edge device of the Internet of things have data acquisition, analysis and calculation, communication, and the most important local or nearest "intelligence". The new intelligent edge computing also takes advantage of the power of cloud computing, using the cloud to securely configure, deploy and manage edge devices on a large scale, and the ability to allocate intelligence according to device types and scenarios, thus allowing intelligence to flow between the cloud and the edge, achieving the best of both worlds.

Planned poker is based on Story Point story points, which are the huge numbers printed on playing cards.

So, what is the story point?

"story point" is a concept used in Scrum agile development, which represents an abstract standard workload selected within a development team. A story point can be the whole content of a more independent and simple work that we are familiar with, for example, all the development work involved in a common function page, including the design of the page UI, the writing of the code, the design of the database table, and so on.

In this way, in the process of rapid assessment, the approximate amount of work of a new requirement is twice that of the above "standard workload", then the rough workload of the new requirement is two story points.

A set of planned poker provides a discontiguous set of story points to represent the workload of different sizes.

Planned poker story point sequence, a set of 13, the same color

III. The meaning of card numbers

0 means that the selected requirement block is very simple, or it can be done quickly through reuse and can be done without effort.

? It means that according to the current situation, it is not possible to assess how many story points are needed for the requirement block, and further understanding and refinement of the requirements are needed.

Coffee cups are used to remind team members that it is time to rest. They are too tired.

Similar to the rules of paper money, points that are not on the face of a card can be accumulated by multiple cards.

Fourth, the maximum number of cards is only 100, what if it is not enough?

Any large requirement needs to be detailed step by step until it is small enough and detailed enough to be designed and coded. Therefore, super-large or very coarse-grained requirements do not make much sense for developers to design. For many teams, a requirement with a size of 100 story points can take several iterations, let alone more than 100.

Developers who play 100 cards often want to express confusion or fear, or technical input or risk, about the size and complexity of the business. For those who feel more unreliable, you can play the question mark card directly.

For large requirements that most people would evaluate as 40 or 100 cards, Product Owner needs to be responsible or take the lead to refine them until they are broken down into multiple and sufficiently detailed and small enough sub-requirements before it is possible to move on to the development schedule of the next iteration cycle.

A flexible combination of cards.

V. matters needing attention

Each deck of cards will contain 1 or 2 instructions in Chinese or English, introducing the basic rules for the use of poker.

Each developer should be given a set of 13 cards to express his or her quick assessment of the workload of a demand block. Some models of planned poker will have four sets, each in a different color. There are many developers involved in the evaluation, so you need to use multiple sets of cards at the same time.

For each new requirement explained by Product Owner, all developers need to play cards at the same time in order to express each person's independent point of view.

The evaluation conclusions with the most concentrated points are often adopted. Evaluators who are very different from most may be asked to state the basis of their assessment. The assessment of people who know best about this need is often highly valued, rather than the minority being subordinate to the majority.

VI. Summary

Planning Poker plan poker is a favorite gadget for many agile development teams. The ultra-low cost of several yuan per pair allows each team to participate wholeheartedly and express their views independently "without nonsense" in the rapid assessment stage of requirements. If used properly, it may greatly improve the efficiency of early workload assessment and demand scheduling. Each team can also fine-tune and explore the game that best suits itself and the characteristics of the project. After the successful completion of this stage of assessment, the requirements are still rough, and further requirements refinement and specific development work are needed to split and claim.

[note:] part of the picture and text content of this article comes from relevant companies and the Internet, and the copyright of this part belongs to the original owner.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.