Extreme Programming - Value, Rule and Management
March-Bird Lucian Yjf Taopin WL Jazz Han Wei Nullgate Simon [Aka] (Reprinted from Cutter.com) September 15, 2003
Values and Principles values and rules On Saturday, 1 January 2000, the Wall Street Journal (you know, the "Monday through Friday" newspaper) published a special 58-page millennial edition. The introduction to the Industry & Economics section, titled "So Long Supply and Demand: there's a new economy out there - and it looks nothing like the old one, "was written by Tom Petzinger." the bottom line: creativity is overtaking capital as the principal elixir of growth, "Petzinger states in. On January 1, 2000, Wall Street Daily (published on Monday to Friday) has released a thousand edition of the annual commemoration with a 58-page layout. Tom Petzinger is labeled Tom Petzinger in the introduction of the industry and financial introduction: "Long-lasting demand and summons: new economic growth points - see the same episode." Petzinger under the bottom: "Creative is replacing the capital of 'Wanjin Medicine' in the primary factor." Petzinger is not talking about a handful of creative geniuses, but the creativity of groups - from teams to departments to companies Once we leave the realm of the single creative genius, creativity becomes a function of the environment and how people interact and collaborate. to produce results. If your company's fundamental principles point to software development as a statistically repeatable, rigorous, engineering process, then XP is probably not for you. Although XP contains certain rigorous practices, its intent is to foster creativity and communication. Petzinger not Talk about the creativity of a small number of genius, but talk about the following groups of creativity - from the group to the department. Once we look down on the individual's individual creation, creativity is the ability of the environment, and people use and mutual assistance to achieve our results. If your company believes that software development is just a statistical repetition test, engraved, technical process, then XP is not suitable for you. Although there is also a strict practice in XP, XP itself is pursuing "creation" and "communication."
Environments are driven by values and principles XP (or the other practices mentioned in this issue) may or may not work in your organization, but, ultimately, success will not depend on using 40-hour work weeks or pair programming -. It Will Depend On WHETHER or NOT The VALUES AND Principles of XP Align With Those of Your Organization. The environment is a system that drives with the value of the same rule. XP (or other similar) may not suit your unit, but it should be clarified that success is not crazy about 40 hours a week or paired programming, nor relying on XP in your unit. Value or rules. BECK Identifies Four Values, And Ten Secondary Principles - But I'll Mention Five That Should Provide Enough Background. Beck pointed out four values, five basic rules, and ten auxiliary rules - but I want to mention It is these five rules. Communication. So, what's new here? It depends on your perspective. XP focuses on building a person-to-person, mutual understanding of the problem environment through minimal formal documentation and maximum face-to-face interaction. "Problems with projects can invariably be traced back to somebody not talking to somebody else about something important, "Beck says XP's practices are designed to encourage interaction - developer to developer, developer to customer communication: Yes, communication, however, there seems to be no new thing in inside? Communication is mainly to see people's own opinions, the basics of XP construction is human and people, through the most concise documents, the most direct face-to-face communication to obtain understanding of the task environment. . Simplicity XP asks of each team member, "What is the simplest thing that could possibly work?" Make it simple today, and create an environment in which the cost of change tomorrow is low concise:. XP ask each member of the development team: "What is the most concise method that might achieve?".
Maintained concise today, can reduce tomorrow due to the changes brought about by the cost Feedback. "Optimism is an occupational hazard of programming," says Beck. "Feedback is the treatment." Whether it's hourly builds or frequent functionality testing with customers, . XP embraces change by constant feedback Although every approach to software development advocates feedback - even the much-maligned waterfall model - the difference is that XP practitioners understand that feedback is more important than feedforward Whether it's fixing an object that failed a test. Case or refactoring a desk, high-changing a change, high-changing a change, high-change, environment, of feedback. Feed: Beck said: "For programming, optimism is an adventure.", "and feedback is the corresponding Solve good medicine? Quot; whether the use of repeated build or frequent user function testing, XP can constantly receive feedback. Although we will say and feedback each time you discuss software development strategies - even very harmful Waterfall model - Different is that XP practitioners believe that feedback is more important than feedforward. Whether it is modified to test failure or software rejected by users from new rework, development environment rapid change Developers are required to have a better understanding of feedback.
Courage. Whether it's a CMM practice or an XP practice that defines your discipline, discipline requires courage. Many define courage as doing what's right, even when pressured to do something else. Developers often cite the pressure to ship a buggy product and the courage to . resist However, the deeper issues can involve legitimate differences of opinion over what is right Often, people do not lack courage -. they lack conviction, which puts us right back to other values If a team's values are not aligned,. THE TEAM WON 'Right, "Right," and, WITHOUT CONVICTION, Courage Doesn't Seem So Important. It's hard to work up the energy to fight for something you don't believe in. Courage: Whether you It is a method of using a CMM method or XP, which itself is required to be courageous. Many places define courage as the right to do something, even forced to do other things. Developers often excuses from pressure to emit products with many defects and adhere to this. However, a further should include other correct different things. Usually, people are not lack of courage, but lack of reasons for gaining correct practice, and don't believe this, courage is not as important as it seems. And if you don't have confidence, it is hard to try hard. "Courage is not just about having the discipline," says Jeffries. "It is also a resultant value. If you do the practices that are based on communication, simplicity, and feedback, you are given courage, the confidence to go ahead in A lightweight manner, "as opposed to being weight down by the more cumbersome, design-heavy phalices", Jeffries said that it is a final value. If you work in a mode based on "Communication", "Simple", "Feedback", you will get courage, the more important it is, the more you trust it.
Quality work. Okay, all of you out there, please raise your hand if you advocate poor-quality work. Whether you are a proponent of the Rational Unified Process, CMM, or XP, the real issues are "How do you define quality? "and" What actions do you think deliver high quality "Defining quality as" no defects "provides one perspective on the question; Jerry Weinberg's definition,"? Quality is value to some person, "provides another I get weary of methodologists who use. the "hacker" label to ward off the intrusion of approaches like XP and lean development. It seems unproductive to return the favor. Let's concede that all these approaches are based on the fundamental principle that individuals want to do a good, high-quality job What "Quality" means and how to achieve it - now the the gist of the real debate! Quality work: Ok, if you have a bad work, please leave here. Whether you are a Rational Unified Process, CMM, or XP's Predor, its essential point of view "How do you define quality and" What activities will win high quality ", define" no shortage "quality is a problem direction. Definition of Jerry Weinberg is "Quality is for most people benefit" Managing XP management XP One area in which XP (at least as articulated in Beck's book) falls short is management, understandable for a practice oriented toward both small project teams and programming. As Beck Puts IT, "Coaching IS One of Beck's Components Of Management Strategy.) For small projects and programming, in XP (at least BECK) The lack of management is understandable in the book.
