pmbok agile

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

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

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

When we recall the process of software development, the first 10 years of the 21st century may be the Agile age. Agile Development developed from a large number of consultants who stated software development methods at the meeting. Now we have held a meeting dedicated to Agile development. Agility is no longer an exclusive discussion of a small number of people;

# 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:

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

1. Our top priority is to make our customers happy by delivering valuable software early and continuously. There is a strong correlation between the delivery of partially functional systems and system quality as early as possible. The less functionality that is included in the system that is initially delivered, the higher the quality of the final delivery system. There is a strong correlation between delivering the system and the final quality on a regular basis in a way that incrementally incr

What agile means. Agile can be said to be one of the most "hot" words in software engineering in recent years, with countless articles, books and discussions about it. Still, there are plenty of practitioners who misunderstand and confuse agile. What does agile really mean? Is it just some pretty, funky publicity? Wha

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

Whenever I hear other software executives complaining about their "cascade" development process, I always ask them why they don't try more agile methods. And the most common answer is that they don't know how to start. In fact, if a book is all about agile development, it won't make agile easier. Explain to the project management team that you want to give up eve

This article is the second of an open Agile implementation series. If you haven't seen the first one, you should look at it: better agile implementation. Open Agile Implementation (OAA) is a repeatable technique for fast and continuous implementation of agile processes. Whatever you are doing now, it can work with it

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

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

The most heard description of agile development is iterative development, side doing demand side doing development and so on. It is also argued that agile development is a pattern, as long as it is as agile as any other methodology to observe what time to do. The sense that these statements are not accurate description of agi