Performance Management of agile development: Preface and "whether Agile Development assesses individuals" (Performance Evaluation)

This is the first article in Agile development performance management. (One, two, three, four, five, six, and seven)

"Agile development performance management" is a pseudo proposition, because agile development itself does not want to involve performance management, which is similar to the combination of "C ++ Performance Management. However, there is a reason why people choose agile development as a management method: higher delivery guarantee, higher productivity, and higher quality ...... This is very similar to the reason why people choose C ++ (rather than C ):For higher performance. In all the articles below, "Agile development performance management" is no longer "how to manage performance in Agile development", but"How to use agile development to improve performance".

 

What is performance management?

Performance management is often regarded as performance appraisal, that is, how to determine individual performance and how to raise wages and bonuses. In fact, performance management also includesSet performance goals,Develop performance plans,Develop supporting systems to promote performanceAnd so on, including the finalPerformance AppraisalTo achieveObjective of Continuous Performance Improvement.

The above content has been taken into consideration in this series, and some practical cases are provided for discussion based on the author's past experience and experience.

 

Starting Point of performance management from a classic question

Performance management is not a requirement of agile development-if you can understand agile development and not a waterfall model, agile development enthusiasts may be relieved-performance management isEnterprise Management requirementsIs a measure taken by enterprises to continuously improve their performance.

From this perspective, we have a long history problem:"Does agile development assess individuals?"Many people will blurt out:" Agile development does not assess individuals ." But what should I do if I ask "enterprise management requirements must be assessed? After all, the salary and bonus are not sent to the team's general account. "The estimated answer is just to say that it is a flash.

In fact, this is also a pseudo proposition, so it is difficult to answer. The following is a little analysis.

The purpose of enterprise performance management is not to assess individuals, but to improve enterprise performance.Improving Enterprise Performance by assessing individuals"(Although improving personal performance will improve corporate performance, but do not enter this horn, because there is a tip in front ). Therefore, from the original point of view, the question should be:"Should enterprises improve performance by assessing individuals??", Then the answer is:"Agile development has more ways to improve performance than individual assessment". It is not because agile development cannot assess individuals,When agile development is selected, it means that you have selected a more effective way to improve performance than individual assessment.Therefore, there is no need to compete with enterprise management and agile development.

But what is this or more effective? This is the main content of this series of blog posts.

This series of blog posts will involve moreTeam-level performance managementThe content includes team management strategies, individual management, external goal setting of the team, how to break down to individual, performance management differences of different teams, non-material incentives, etc.

Another advanced topic isProduct-level performance managementIncluding Product release plan, product version plan, product line management, product owner and product owner team, and matching of different product types. However, this topic is organized more smoothly with another main line:Agile development product managementSo it will form another series, but its core content is still"How to improve performance through agile development and management products", If you think the scope of this series is too narrow, please stay tuned to http://blog.csdn.net/column/details/productmanagement.html.

 

(Some readers report that each article is too long. This series will be published in the form of many short articles, so that you can choose to read the content you are concerned about separately .)

 

I am participating in the csdn blog Star Selection. If you have read and liked this article, please vote:Http://vote.blog.csdn.net/item/blogstar/cheny_com

Click to download the free agile development textbook: Martian agile development manual