agile programing

Ext.: http://blog.csdn.net/kerryzhu/article/details/8812589Today, we also discuss such an old topic, do you feel the same? Because Mr. Dening, who was Google's China Test manager two years ago (at the end of 2010), wrote an article on "What is Agile Software Testing" (published on the INFOQ website [1]), which has already been discussed, "Agile software testing is more of a concept than a process." [2] In 2

It is well known that the agile movement does not produce a completely workable revolutionary result. If the current program works, then at least now, thousands of organizations have already reached a self-sustaining, continuous, independent agile state. Obviously, that's not the case. The story is always full of typical failure patterns. At first it seemed to be a good organization, and in the end it deg

This article was first published by IEEE Software Magazine and reprinted by Infoq IEEE Computer Society. Agile development can not be separated from architecture? Architecture without agile development? Is it possible that the answers to these questions must be based on a satirical caricature of a confrontational view based on deep-rooted values, rather than on a clear definition of the two, an open, spec

This article is based on a pre-release version of Visual Studio team System (VSTS) 2010. All information is subject to change. This article describes the following: Product and Iteration Planning Product Backlog Workbook Capacity Planning and reporting Iteration Backlog Workbook This article uses the following techniques: VSTS 2010, VSTS Process for Agile Software Development 1.0 Are there any semantic contradictions in the

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

Introduced Over the past six years, the role of agile coaches has emerged in the IT labor market. I've been working in this role for the last 5 years, and most of the work is done in Suncorp. Suncorp is a large company in Australia's insurance and banking sector with more than 16,000 employees. As you all know, Suncorp is a leader in agile, and it is also a typical example of

Creating useful software is the door process. This is not a black-white formula for success. However, there are some agile engineering practices, practice has proved that it has repeatedly added value to the enterprise, but the premise is to be considered before use. In this article, I'll share with you 5 specific ways in which your organization can benefit from agile engineering practices. (Assuming we us

With the company's agile and DevOps work in depth, in a team squad in a clearer role, in many roles we have an IM role, this installment of the article we explore the next im in one or more squad in the positioning and role, The ability to provide support and quality assurance for better iterations and operations of the project, as well as the ability of team member to complete the assigned house within a limited amount of time while also ensuring a c

Wen/Zhu ShaominOnce, after the developer completes the code for the current sprint task, the testers, developers, and product managers come together to browse the product and go through it, and the product manager discovers the problem and thinks it needs to make a big change to the functionality. At this time the developer estimated that it would take two days to complete the code, but the testers opposed it, we had only 5 days to test time, plus this new function is more, the development code

I did not ask for advice from the company, I had to explore it myself. XP was selected at the beginning. Several programming methods: Code Review, standup meeting, Story wall, Pair programming. But it is really difficult to implement it. Sometimes even if you do not do it, you cannot see the results. In this case, we probably struggled between 4 and 5. A month later, "coincidentally", our project team has been dispatched to the current big project team to create another system. This large proje

phenomena, but also understand the essence ." Q: questioning: "What do you see? How do you feel ?" R is called spectives (Review): "What have we learned? What will we stick? What should be new ?" S is sensitive: "I'm wondering if they're ready ......" T is transparency (transparent): "I hope you can try it like this, because I think it will help you ......" U (unlock): "I didn't expect this team to do this !" V is vocabulary (Word): "yagni? Burn up? Muda ?" W is welcoming (a

Now agile development is getting more and more fire, everyone is talking about agile, everyone is learning scrum and XP ... In order not to lag behind others, so I also began to learn scrum, today is mainly about my recent reading of relevant information, according to their own understanding, with their own words to tell the various aspects of scrum, the main purpose is two, one is to carry out knowledge s

The origins of Agile developmentIn the late 90, the traditional way of software development because of its complicated process, as well as the strict requirements of the document, resulting in a large degree of efficiency decline, which is what people call "heavy crisis." For this reason, people begin to reflect on the pros and cons of traditional methods, and improve their drawbacks, and propose an agile a

In the product development process often need to write a lot of documents, such as: Requirements documents, design documents, API documents, acceptance documents and so on. Team members have to spend a lot of effort to maintain a large number of documents, even have "brother, I write code for you, you write documents for me" frustration. Agile Development Manifesto* Individuals and interactions are better than processes and tools* Working software is