agile manifesto

This is the second article in the agile development series. (One, two, three, four, five, six, seven, eight, nine) The so-called "no living" includes two meanings: not living in the law, not living in the air. The former is better understood, and the latter will be detailed in the next article. Instead of believing that there is the best way in the world, we must abide by it.Legal Statement The persistence of law is known as law enforcement. The typic

In order not to fall behind, I also began to learn scrum, today mainly on my recent reading of the relevant information, according to their own understanding, in their own words to describe the various aspects of scrum, the main purpose is two, one is to carry out the summary of knowledge, Another is that a lot of learning information on the Internet so that beginners are not easy to understand; So I decided to write a literacy blog, while also trying to share with the garden friends, hope to he

In the previous three articles on the agile development of a background, is based on the author's personal experience as the main line to gradually understand the agile development from a personal point of view. Through the pair programming to complete the development framework of the building, in the framework of the fact that our formal agile process has not y

1.Brief introduction:Agile project Management in our country started relatively late, the successful use of a few projects65% of Agile Project users are scrum2, the characteristics of the Internet era, lei June words:Focus, extreme, word of mouth, fast (Agile project development is to be fast)3, agile development of the various portals　　4. Four

First, it is declared that this parallel development does not refer to parallel computing, but to some experiences and practices summarized by practical software engineering. Agile parallel development is a rapid development model that integrates software component technology and Platform + plug-in development technology. parallelism refers to the product's lifecycle, the project management process, Project R D process, and organization support pro

In my recent face-to-face interactions with customers, I have been fortunate enough to share with our team how to develop agile software in our daily work. There is no doubt that this is a hot topic among Chinese developers, and I would like to use the blog as a platform to communicate with more readers in writing. Of course there is a lot of debate about the pros and cons of agile development, and the rela

members have 7 people; one-person design, one-person app interface, one-person app integration, one-person app interaction, one-person web front-end, one-person Java backend, and I do Architecture project management. OK, simple pre-bedding is here, followed by the theme of this article, according to the Agile Development Manifesto route. Agile Development Manif

Introduction to Agile (Agile) developmentBefore starting this article, let's take a closer look at the Agile development content:The first manifesto for Agile Development:1. Individuals and interactions outweigh processes and tools2. Work-ready software trumps all-encompassi

Agile results for personal work and life is mainly to cultivate result-oriented, planned, and targeted Manage personal time, regularly focus on some hot spots, efficient work, learning, and happy living habits! Three core elements: 1.3 rules (the rule of 3) 2. Monday goals, daily results, and Friday reviews (Monday vision, daily outcomes, and Friday reflection) 3. Hot Spots) The rule of 3 ): Three tasks are solved every day, three tasks are complete

that it meets the required standards. Each level of "completion" has different completion criteria, and a very different "good" quality standard. There is a group of people who are not only well suited to helping define "well done", but also to help define processes and techniques for finding "well done" levels. Step one, define "finish" ... Well, it looks simple--ensure that the performer completes all the components that need to be delivered at the "Finish" level. Well, so far it sounds good

First, the Agile practice　　1. The Agile Manifesto　　　　Individuals and interactions outweigh processes and toolsWork-ready software trumps all-encompassing documentationCustomer cooperation is better than contract negotiationResponding to change is better than following plan　　　　1.1 Bodies and interactions outweigh processes and toolsCollaboration, communication, an

Transferred from: http://www.infoq.com/cn/news/2009/02/agile-documents/ There are many types of documents in a software project, including requirements documentation, design documentation, API documentation, bug reports, progress reports, handover documents, acceptance documents, and so on. In traditional software project development, each team member spends a lot of time and effort to maintain documents and fill in various forms and reports. The seco

Programming (XP) is one of the most famous agile methods. It is made up of a series of simple but interdependent practices . These practices combine to form a whole that is better than a partial combination. Agile Development The interaction between people is complex, and its effect is never expected, but it is the most important aspect of the work.

# Practice group # register with the second batch of agile individual promoters Note: group activitiesDeadlineBy March 2014March, Members of the first and second batch of PromotersThe annual fee ends here. If you join in any month in the future, you will only pay the annual fee until January 1, February 2014..2014Whether to continue the group activities or other forms to be determined after March. Registration address: http://www.minjiegeren.cn/ho

Agile basic knowledge----demand management based on story (II.) (1) Periodical release Regular release of the line, the whole project divided into iterations, each iteration time size fixed (basic fixed), the end of the iteration on line delivery. (2) Iterative planning Iterative planning is the equivalent of a plan for the entire iteration, helping us manage and guarantee delivery for each iteration. A. Prerequisites for iterative planning:

No matter how far the road goes, it's wrong to return again!Agile development Approach: focus only on what's really important, and pay less attention to unimportant things that take up a lot of time and nothing to benefit!Agile Development Manifesto: People-oriented, team work, rapid response to change and work as the purpose of the software development Method!Th

First, development and testing of the continuity of trouble?Facing complexity (customer): constantly revising plans, increasing budgets, inferior product quality ... Face Complexity (Project team members): Often work late into the night, submitted products are not qualified ...ii. Agile Testing objectives in Agile Development:The Agile

Differences between agile development and code writers without standards and documents Contrary to some ideas, agile developers are not the unique owners who do not write code according to rules or restrictions. "Cowboy code" is a sign of poor rules and management, and is not professional. If the team has such code writing, you should do your best to change this situation for the benefit of the customer. W