smartsheet agile

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

Masters should not only sum up some theories about agile methods, but also have practical methods to operate and cooperate with the corresponding business models. Otherwise, they will always say that agile declarations are principles, practices, or experiences, there is no theoretical or business model support, and there is nothing to talk about when it comes to charging problems. Who pays for

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

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

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;

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

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

At the invitation of my friend, I am prepared to write a group of articles on Agile software development practices, but also to help the vast number of people who have not used agile or just stay on the book content to visit the Agile software development of this thrilling process. The so-called agile, there are many

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.

1 Introduction Agile development methodologies are becoming increasingly popular, while most "agile" experts and analysts are discussing agile in isolation, which means ignoring the system "architecture" (Kirk Knoernschild is an exception, he wrote a book called "Java Application Architecture" Books to illustrate this idea). This omission is surprising consideri

Agile, agile Development These words are very hot recently. Agile development refers to the ability to quickly develop software in the event of rapid changes in demand. The most common and agile-related nouns are: Extreme programming (XP), pairing programming, test-driven development (TDD), and so on.

Words such as agile, agile development have been very hot lately. Agile development refers to the ability to quickly develop software in the context of rapidly changing requirements. The most common and agile-related nouns are: Extreme programming (XP), pair programming, test-driven development (TDD), and so on.