best agile tools

After the review, the review will be held. Generally, the review will be held together to reflect and reflect on some things. In fact, this is just a sentence. If there is a review, you can change it, keep good things, and correct bad things. If you

Book DescriptionThis comprehensive set of cards is an indispensable resource for agile teams. The deckAgile in a flashCards teaches leadership, teamwork, clean programming, agile approaches to problem solving, and tips for coaching agile teams. team members can use the cards as reference material, ice breakers for conversations, reminders (taped to a wall or moni

Be happy, efficient, and balanced. Be a person who loves to learn, has goals, and understands the influence of life. From today until July 31, click http://t.cn/Rv3koHU to receive more than 1000 pages of "agile personal-Self-awareness, management self v0.8.pdf" for free Join us Training If you have learned about agile individuals and agree with the concepts a

From: Agile Software Development: Principles, models, and practices: Robert C. Martin, translated by Deng Hui] Agile Software Development Declaration:Individuals and interactionsBetterProcesses and toolsSoftware that can workBetterComprehensive documentationCustomer cooperationBetterContract negotiationRespond to changesBetterFollow plan(Although the right item also has value, the left item has greater valu

a background for agile development in the previous three articles , 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 completed the development of the framework of the building , in the framework of the fact that our formal agile process has not

ArticleDirectory Monday goals, daily results, review on Friday Hotspot In30-day agile results: OpeningSpeaking of the following, we will conduct agile results exercises. You are welcome to join us.30 days of getting resultsDay 1-take a tour of getting results the agile way. "The only reason for time is so that everything doesn't happen at

Document directory Growing agile developers Agile coaches Eliminate potential problems Conclusion About the author There are already many articles on Agile Methodology. A considerable number of articles address technical issues of agile methods, such as test-driven development and continuous integration. Simil

check in, while continuous integration encourages high frequency check in to achieve rapid feedback. As you can see, the continuous integration of high-frequency check in and fast feedback features provides a solid technical basis for effectively reaching agile. It can be said that without a good continuous integration environment as the basis, it is almost impossible to develop team software efficiently. So how do you build an environment like this

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

This is the second article in the agile ecosystem series (One, Two, Three, Four, Five ). If there are still some factors that cannot be controlled by the Team in demand management that lead to implementation difficulties, there is no problem in the planning and tracking process? In fact, I have seen the entire group with the authority of Leadership (many of which are simply unable to handle the issue), but there are still many problems within the team

There are two common scenarios in the Agile manifesto that say "working software is better than detailed documentation" and it seems that the documentation is redundant in the work:1, complete a summary of the design, but the development process, this design is not enough to guide the programming work, it is better to directly ask PO to direct, communication between each other smooth. Finally this outline design becomes the decoration, no one looks.2,

1, Agile Test Quadrant-the division of labor in each quadrant? Who will do it specifically? When do you do it? 2, soap opera Test 3, exploratory testing 4, session-based testing 5, WATIR6, Fit Fitnesse8, to ility testing (reliability, interactivity, scalability) 9, agile testing in the automated test can keep up with the development of the iteration speed? 10, CruiseControl should be class is Jenkins/hudso

Problem background Many activities in agile development involve full participation rather than personal involvement. Requirements analysis can also be a full participation of an activity. This reflects the agile development of "personal and interactive better than process and tool" values. Demand analysis is based on the understanding of requirements. Therefore, the full participation needs analysis helps

was looking at the final development; more importantly, there were many changes to requirements after the product was delivered. After that, I began to focus on methods, technologies, and tools throughout the software lifecycle, so I learned about agility. It was XP first, followed by scrum. In, I went to a new project team, and this group had no development process methods or requirements. So I practiced some new methods in this group, including scr

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:

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

Owners, developers, and users should be able to maintain a long-term and constant development speed. Compared with the previous software engineering, agility is the biggest innovation in improving the role of people to process first, as stated in the first article "individuals and interactions win over processes and tools" in the agile declaration. 1. agility is a "process" Agility is not a process, but a g

stated in the first article "individuals and interactions win over processes and tools" in the agile declaration. People-related problems are no longer covered by the process. They are now at the level of enterprise management, including corporate values and culture. This is also the biggest obstacle for agile implementation in China: 1. Think of the customer as

/01/23) is Saturday. I attended the "agile scrum training camp in Beijing and Shanghai" Shanghai held by infoq at zizhu Microsoft's new campus all day. There are two main activities: in the morning, Dr. Wu Qiong of Jacob's company called "Agile Software Development scrum practice (upper/lower )", introduce the knowledge of agile development and scrum in Beijing a