agile software development book

. Developers choose to feel comfortable with their tasks and maintain high quality of work.Managers always get data at each iteration. They use this data to control and manage projects. They don't have to impose, threaten, or plead with developers to express arbitrary, unrealistic goals.It sounds like a nice, relaxing thing, but it's not. Using the data generated by the stakeholders is not always satisfactory, especially when it is just beginning. The use of

I have always been interested in some methods and principles of Agile Software Development and have many ideas. However, because I have little work to use and no one can communicate with each other, all those ideas only exist at the theoretical level, I hope to share these theoretical knowledge with you in your work or practice, but I am not very familiar with th

Thinking Paradigm leads to many obstacles in learning English. Therefore, after reading a large number of English books, you may find that Chinese statements are strange when reading Chinese. Even Chinese statements cannot be written in the future. At least I feel like this now. So the paradigm is actually a way of thinking. In the previous development paradigm that adopted database priority, we need to switch to the object-oriented paradigm in t

well as the ORM code based on the Division class and the interface-driven Dal solution and project, we need to explain that one problem is the division class. In application development, our database operations are not only simple operations such as reading, updating, adding, and deleting, but also complicated database processing that works with the business logic in the Dal layer. This requiresProgramThe member modifies the generated code, which rai

I released an Online Demo Based on activexform/smartclient a few days ago. In activexform and/smartwin, we tried to demonstrate agileeas in two ways. net in winform development technology, today I am releasing a program based on agileas.. NET platform online demonstration based on webform technology. This online demonstration is based on agileeas. net project, I will show it with his consent, because the project time is tight during

What is Agile development?Agile Development (development) is a human-centric, iterative, and progressive approach to development. How do you understand it? First, we have to understand that it is not a technology, it is a

"Agile Software Development Reading notes of the second"Next, I will show you the third part of the "pay-for-pay case study" and the fourth part of the "packaged pay system," the two parts of the understanding, as well as the gains from it:Here's what I learned from the third part of the pay-for-pay case study and some personal summaries:The simplicity of the com

extension to the system might add a new subclass that is likely to support the same responsibilities in new ways. At this point, the newly created superclass might be an abstract class.The OCP is at the heart of many of Ood's claims. If this principle is applied effectively, the application will be more maintainable, reusable, and robust. LSP is one of the main principles that makes OCP known as possible. The substitution of a formal subtype allows a module that uses a base type to be extensibl

environments, the "best method" is constantly changing and must be analyzed based on specific conditions.. Of course, there is another extreme opposite. I think that any method is not a good method, so I would rather follow the stream or talk about it later than pursue the universal value in this case. This will cause a lot of waste and mistakes, because when the "specific scenario" comes, without prior thinking and accumulation, I often feel unable to start. Therefore,For a specific environmen

The methodology is methodology in English. The programming methodology should refer to a complete set of methods, processes, rules, practices, and technologies for software development. However, the methodology we generally mention focuses on projects, processes, and personnel. The methodology proposed by Alistair Cockburn, author of agile

In the previous article, the plug-in interface IModule of AgileEAS. NET introduced the basic contract meaning of the plug-in, that is, the interface. This article will provide the definition of another module plug-in, using the property tag plug-in. We have defined the ModuleAttribute attribute: ModuleAttribute // And ModuleRunAttribute attributes ModuleRunAttribute /// We only need to mark ModuleAttributes on the class of the module plug-in we want to public, and add ModuleRunAttribute on t

On csdn, we can see some comments about Agile Software Development by Uncle Bob. For details, see: Http://java.csdn.net/page/9677ea1c-b851-4135-aeaf-11d59585af42 Of course, I saw some spams and thought of some things. Here I will record them and share them with you. About a year ago, I talked to a program development