branching strategy agile development

"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 command pattern masks its versatility, which can

must be familiar with this process. Another related problem is: do not combine a bunch of new users into a development team to do low-level coding work alone. This person who is fond of playing ball games must know that if there is no expert in the team, the level of everyone will not be substantially improved because of the accumulation of work experience. On the contrary, he will introduce several experts to guide his work, it is the best

What kind of Project version control tool are you using? Now the more popular version control has parallel (SVN), distributed (Git), streaming project versioning.what principles or specifications do you generally need to know about using version control? Frequent check-in and check-out In agile development, code-sharing, frequent check-in and check-out, and everyone on the team can see each change There

picky questions about any technology you want to use, and answer them truly.Consider when introducing new technologies:Can this technical framework really solve this problem?Will you be tethered to it?How much is the maintenance cost?Remain available for release, early integration, and frequent integration.The main point is versioning issues, the company has a master branch for continuous iterative development and develop branch for releaseBut found

even worse is that another project was to be completed in December April 9, and my project was to be completed by the end of December April. I thought carefully that it was impossible to finish it in such a short period of time. In addition, agile development guidance should not be overly committed to avoid affecting the development quality in order to make prog

Hacker and agile development Some time ago, I read Paul Graham's hackers and painters: big ideas from the computer age. Although this book has been published for a long time, however, reading is often time-free, and it is good to get the harvest. This book is a collection of articles with relatively scattered contents. It is not intended for people in the industry, so different people can tell this book f

My point of view-agile development pursuing simple design 1. What is simple design? Introduction: There is a famous lazy principle in extreme programming, called the KISS Principle. KISS is the abbreviation of Keep it simple and stupid. To put it simply, the design should be as simple as possible. Naresh Jain explains the simple design in this way. "A simple design doesn't affect my work schedule ". My poi

First, let's analyze the background. What are the most unstable factors in the software development process? -- The answer is demand! Requirements may change all the time during software development. Then, how to flexibly cope with changes is the most important and difficult issue in software structure design. A good design brings great flexibility, and a bad design is filled with a rigid smell. This leads

. A real software architect is involved in the code that he or she designs. 14.5 ConclusionUML is a tool, not the end result. As a tool, it can help you to think and communicate the design. If you use it sparingly, it will bring you great benefits. If used excessively, it will waste you a lot of time. When using UML, less is better.Excerpt from: "Agile Software Development: principles, patterns and Pra

Introduced: In agile software development, the speed of code generation is much higher than that of traditional waterfall. Because we have made the time more compact. How can so much code guarantee the quality of the code? Many people may think directly of static code detection tools. Yes, those are the ones that can define a code-checking rule to ensure the quality of the code, but is that just from the l

From: http://kmhz.blog.163.com/blog/static/6918022200832314144955/ Recently, my colleagues and friends talked to me about all aspects of the design pattern. With the development of object-oriented and agile development, more and more programmers hope to use the design model to make their code more reusable, more understandable, and more reliable. In different sit

classshapecomparer:icomparer{Private StaticHashtable priorities =NewHashtable (); StaticShapecomparer () {priorities. ADD (typeof(Circle),1); Priorities. ADD (typeof(Square),2); } Private intpriorityfor (Type type) {if(priorities. Contains (type))return(int) Priorities[type]; Else return 0; } Public intCompare (ObjectO1,ObjectO2) { intPriority1 =priorityfor (O1. GetType ()); intPriority2 =priorityfor (O2. GetType ()); returnPriority1.compareto (Priority2);

style or let them first each implementation of the page demo again unified modification will be better, perhaps after the subsequent experience rich, processing will be more handy bar.Iteration FourThe first agile development encountered a change in people, or at such a critical moment, it is not known to be fortunate or unfortunate. The beginning of the last iteration, the above member X because the commu

This is the eighth article in the agile development product management series. (Column directory) In product development, product performance problems are often encountered, which will greatly affect the product architecture. However, to solve these performance problems, do not think it is only a matter of technical personnel. The product manager and product dire

construction and development strategy appears to be particularly important. We and the website is divided into two stages: the first is the new station short-term agile development phase, the second is the site advanced stage development. In order to adhere to the site to c