Agile development One Thousand and One question series: how to estimate agility (medium )?

This is the first article in The One Thousand and One Q & A series of agile development. (Here, I would like to ask, one, two, three, and the General Directory of the question)

The previous article is expected to include an article in the future.

Solution 1: Use the early function point estimation method for quotation or early project planning

This has been mentioned many times before. For details, refer to Chapter 6 and Chapter 7 of the agile development performance management series. In addition, the classification and organizational structure of user stories in Agile development (phase I) (phase I of the entire activity) are described in detail.

This is the only method that has been widely used in the world so far. The upcoming national standard in China is based on this. Currently, there are more than 6000 certified function point estimation experts in the world, and there are only two (I am not) in China, so it is not very famous. This may be the biggest Knowledge Area in the software industry.

Solution 2: using agile poker to prevent large-scale waste of code and work

It's not about using playing cards, but agile estimation. For example, the following method is used:
1. randomly draw a card.
This is the fastest poker card estimation, and it is very fast and there is no dispute. But I believe no one like it, so"Fast" is not our goal of agile Estimation.
2. Each card is assigned by the number of people.
This may sound more rational and democratic, and a little decentralization. Is it a positive solution? Hmm ...... What should I do if one person tries and another person tries to leave 100 person-days? (1 + 100)/2 = 50.5? It seems that,Democracy and Decentralization may not be a positive solution..
3. Don't use poker, take the initiative to get it, who has the right to decide who to do it, and how to work with your own estimation
This is also very agile, decentralization, encouragement, commitment ...... Yes. However, whether it is agile or not, if the first few lines of 4000 and 0.19 million code come, it will be over. No matter how powerful the experts are and how enthusiastic they are, code redundancy is inevitable. When a newbie writes a resume, he probably thinks about what I did over the past two years, it was actually rewritten by a guy for two months.
Here is a standard question: do you choose to comply with agile standards or the minimum code and workload?
Yes. I will select the latter. After all, agility is to serve us, not to "follow" or "follow". If it hurts the interests of teams and projects, how can it be agile.

So how should we estimate it? Before you describe the correct method, you must first find the correct purpose. Decentralization, encouragement, commitment, democracy ...... Aren't these purposes? No, these are means. The goal is to directly see the progress, quality, cost, and demand improvements.Instead of turning around and turning around. As we mentioned earlier, it is worth a day. The purpose of estimation is to effectively reduce code lines and workload.. To achieve this goal, the estimation process should be: 0. the product manager will explain the requirements and ask questions (if you want to, you can discuss them a little. We recommend that you do not have to wait too long). 1. estimation (do not highlight the cards when the cards are deducted) 2. open the cards 3. the maximum value and the minimum value can be used. after the primary key, do not reach an agreement directly (for example, "Let's take three days"), but rather play a new 5. returns 2 until "approximate consistency" is reached. 6. the rules for determining the final result are complex-in fact, there are no precise rules, so we need to "adapt to the situation" and discuss them in the next part of this topic in the future. According to this practice, these things may happen: 0. Product Manager :...... Well, that's probably the case. If you don't have any questions, just play the cards ...... 1. Xiao Zhang: Well ...... I guess at least these (X days); Old Wang: I 've been talking about this for a long time. At most these (Y days). 2. Scrum master: Are all done? Open a card! Everybody: Dear, x = 20 & Y = 0.53. Old Wang: up to 55 rows of a small function can be used. Why so many days? Xiao Zhang: A function has 55 rows. However, to process different types of 13, there must be 5 different constant values. Lao Wang: Yes. a wildcard + A for loop can input up to 56 parameters. Branch A4. Xiao Zhang: Wait ...... Loop. Why didn't I think of it ...... And ...... Generic ...... That makes sense ...... I think ...... 5 & 6. Scrum master: x = 1 & Y = 0.5 ...... This is almost the case. It takes about one day. Next. Branch B4. Xiao Zhang: Wait ...... Loop. Why didn't I think of it ...... This is understandable ...... Generic? What is generics? If branch B is encountered, see agile development loose Pair Programming series, you can directly read Step 3 and Step 4 (the wildcard will be transferred to the apprentice by the master in the "Key Points" mentioned in "Step 4"), or start from scratch.

I am participating in the csdn blog Star Selection. If you often come to this blog to read or have downloaded the "Martian agile development manual", please vote (You need to log on ):

Http://vote.blog.csdn.net/item/blogstar/cheny_com

Each user can vote for 10 bloggers, so if you see other bloggers who often visit, please vote!