cprime agile

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

thanks to the overwhelming majority of users to support the soft, now the Force Soft Agile Framework 7.0 version of the update released as follows:1 The newly added 1. multi-lingual function; 2. code generator template; A. Editable List code generator (Excel style ) template; B. report the actual code generator template; 3. tree-shaped code generation function; 4. Dynamic Configuration Home page function 5. external Mail sending and receiving functi

Introduce my friend Jane and John. John is a long-time analyst at a large company, responsible for capturing the needs of new software products and existing software products. He uses SRS (software Requirements specification) to record all customers ' requirements for specific products being developed or maintained. Jane is a developer of the same company. She usually receives John's software Requirements Specification (SRS) and then starts to analyze and design the content to be implemented.

Introduction to Automatic Build and deployment framework for incremental code Introduction to Concepts and tools Agile and Delta Code agile-Agile Development. In recent years, people have been widely concerned. It advocates dividing a complete software version into multiple iteration cycles. Each iteration implements a different attribute. Significant, high pr

the characteristics of the waterfall model (Traditional way of development) 1. Emphasis on document  The output from the previous phase is the input to the next stage, and the document is the only information that is linked to the stage. So many developers seem to be developing documents rather than developing software, because the software's "look" can be seen later in the development. 2, no iteration and feedback. The waterfall model does not involve feedback, so it is very difficult to

Today, there is a discussion of such an old topic, does it feel like a cliché? Because Mr. Dening, who was Google's China Test manager two years ago (at the end of 2010), wrote an article on "What is an Agile software test" (Posted on the INFOQ website [1]), has already touched on this topic, "Agile software testing is more of an idea, not a process." In 2011, I also wrote an article, "thinking and new deve

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

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

Ten big mistakes in agile developmentOriginal: Http://www.computerweekly.com/opinion/The-top-10-myths-about-agile-developmentPeter MeaseyTranslator: Zhang Sb er http://blog.csdn.net/xinxing__8185/article/Absrtact: For the rapid development of agile software development field, this article will be the most common error understanding of the analysis.In today's glob

10 big mistakes in agile development Original: Http://www.computerweekly.com/opinion/The-top-10-myths-about-agile-development Author: Peter Measey Translator: Zhang Sb er http://blog.csdn.net/xinxing__8185/article/ Absrtact: For the rapid development of agile software development field, this article will be the most common error understanding of the analysis.

Rugby and software development (8)This article is excerpted from agile and invincibleBook All bookstores are on sale Everything at the Palo Alto went exceptionally well.Charles only mentioned the candidate as the project manager candidate, so there was almost no pressure on the Project Manager during interview. After warm up answered the question of the year in which he joined agile and what kind of positi

ArticleDirectory 3. No principles "Agile individual", this is unknown at first, but once heard of it, I will like the synonym for personal growth. It has now evolved from fragmented sharing two years ago to a systematic growth system. Many of my friends have helped me to promote it to people around me. I feel more responsible for promoting "agile individuals" and helping more people start th

Uncle Bob in the programmer's professional literacy book talks about the best team 12 people, is basically a team, 1 coaches plus 11 football players. The 12-person team consists of a project manager, 2 testers, 2 analysts, and 7 programmers. The analyst develops the requirements and writes the automated acceptance test script, and the tester writes the acceptance test script. Different perspectives are different, analysts focus on business value, testers focus on correctness. The analyst write

Programmer A has met programmer B. "Scrum is terrible," said programmer. "Why? I heard that SCRUM is good. Our company is also preparing to implement scrum ." Programmer B answers. "Never, you will regret it ." "Are you implementing real scrum ?" "Of course, we have three roles, four meetings, and three products in scrum ." Agility is very simple, but extremely difficult. Agile Methodology consists of a series of