author Shaojian posted on December 8, 2010 4:51 A.M.
Eric Landes recently described code reviews as a tool to help teams improve their software maturity, and ultimately to deliver higher value to customers, in an article called Agile skills: when and how to conduct code reviews.
He introduces code reviews from the following sections
Agile Engineering Practice
Eric first suggests starting with the engineeri
no longer as focused on being a "process executor" as it used to be, but rather as a role of consultant support to ensure that the entire process support team plays its best role. At present, most of the it organization are agile. Agility changes the way people work, not just the development department, but also other departments, such as hr , finance and pmo pmo A classic pmo po scrum need to prepare the project plan for each month.
[This is the fifth article in Agile testing theory and practice (article 1, article 2, article 3, article 4, article 5, article 6, article 7 )]
In the previous article "using tools to achieve agile development", I have already talked about the current development situation of our company and I will not repeat it here. It is mainly about using devsuite of techex
story of agile development, so that complicated concepts can be easily understood without deep terminology, it can help readers who like agile development learn what agile development is and increase the pleasure of reading.
Wang Lijie is a friend and colleague of mine for many years and has rich practical experience in Agil
updated?
B) further details and decomposition can be considered if you need to ask for the reason for your work that has been suspended for more than two days.
C. Encourage exchanges at regular meetings to gradually form an atmosphere of communication.
3. All work and progress are displayed on the whiteboard or wiki for unified management.
A) The initial job description can be simple, but verbal consensus should be formed at the planning and summary meetings to prevent ambiguity. The implementa
Agile has been widely recognized in the software industry today, but most agile methods are specific methods or practices that have been summed up to address a particular problem, and there has been a lack of a system that can link the entire development process. User story-driven agile development (user Stories Driving agile
http://www.infoq.com/cn/articles/agile-version-control/Version control between multiple agile teamsIf we have multiple Agile teams working on the same code base, how can we minimize the risk of conflicting code with each other? How do you ensure that each iteration ends with a clean, published version of the software? This article describes an example of how to w
/ Leanthinking.pdf), it takes a lot of effort to hand over the document first, and then much of the information is lost during the handover, and there is always some new information added at each stage. All team members (PO, Dev, QA, Doc) sit together and use the whiteboard for face-to-head communication, saving time and effort and being effective. (See Alistair Cockburn, communication http://www.agilemodeling.com/essays/communication.htm in Agile pro
At present, many companies are implementing or requiring developers to"Agile R D practices", What is agile development?
We have all seen or experienced projects that fail due to redundant, cumbersome, and complicated development processes. There should be a better method of software development in the world: focus only on things that really matter and focus less on things that take up a lot of time and do
, a big data analysis project requires an extremely high cost, and it cannot quickly see earnings expectations as other investments do.
2. The implementation phase is long. The implementation period of traditional bi is generally no less than 6 months, or even longer. As a result, enterprises cannot use such tools in a timely manner, even due to the change of time, the model we expected was abolished.
3. The usage rate after successful deployment is l
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
value.
How agile facilitates commitment
Encouraging teams to pull from a prioritized work list
Manage your own work
Focus on improving work practices.
Practice is the basis of self-organization, driving force for achieving results
Agile methodologies value individuals and interactions over process and tools
Working software over comprehensive documentati
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
The first article in this series, "User story-driven agile development –1." Planning chapter "To share with you how to use user stories to help teams create requirements, in this article, we look at how to use these user stories and feature points to form a product backlog." A product backlog is a tool that is used in agile development to manage requirements lists, prioritize, form iteration plans, and orga
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 implement
like this.
In this way, Evernote becomes a story wall. Every user story is a blog. Currently, those in backlog and those in WIP are clearly displayed. All you need to do is try to move user stories to done.Use agile blog tools
The above is just to use agile methods to manage blogs. Is there any corresponding tool to support blog writing like code? Yes, that is,
The first part of Agile developmentAt the beginning of 2001, as many of the company's software teams were caught up in the growing process, a group of industry experts gathered together to summarize some of the principles of value that could enable software development teams to work quickly and respond to change. They call themselves the Agile Alliance. In the months that followed, they created a statement
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
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 Manifesto is more valuable
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.