rally agile software

Today, another blog Park team was founded, it is Agile Software Development Organization. http://www.cnblogs.com/team/Agile.html Over the past one year, I have been very interested in Agile Software development. In addition, I have recently reflected on my current project, so I had the idea of building an

Enterprise Product Lifecycle Management product records for Oracle Agile product lifecycle management are connected to SAP ERP. With Oracle Application Integration Architecture (AIA), this pre-set process integration package helps companies accelerate time-to-market for new products while reducing costs, improving quality, and minimizing supply chain disruption. Oracle Agile Product Lifecycle Management de

In general, choosing a software development approach is more like joining a cult than making a technical decision. Many companies have never even tried to evaluate these methods, but simply blindly adopt the most popular methods, creating a variety of agile methods today. Therefore, we will use some standard metrics including function point, defect removal rate (DRE), quality cost (COQ) and total cost of ow

After thinking about it, I decided to record the course of reading in the form of a date. The comments will be part of the discussion and Thoughts on reading. 2005-06-01: I am very happy to have time to read these good books due to my lack of project tension in the past few days. I once again picked up Agile Software Development-principles, models, and practices. I was excited and bought this book a year ag

Agile Alliance defines 12 principles for people who want to achieve agility: 1) The top priority is to satisfy customers by delivering valuable software as soon as possible and continuously. 2) You are welcome to change your requirements even after development. Agile processes use changes to create competitive advantages for customers. 3) Work-ready

I have been asked the same question twice recently: If a software requires a lot of Intensive design work, resulting in an independent design and development team, how should we implement agile development? On the whole, agile development does not want the separation of design and development, because it will produce a "design document". Because the two teams ar

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 the future. Currently,

quadrantSecurity:Static code Analysis: Identify potential vulnerabilities. (Firebug)Dynamic analysis: SQL injection or cross-site attack. (fuzzing)Maintainability:Success is 0, and failure must be negative.Each class or module has a single responsibility.All functions must be single entry single exit???Two fields on a page cannot have the same name.Compatibility:OS, browser. Includes different versions and types.Reliability:First failure time, average failure time.Scalability:Whether the system

Remote distributed software Development (Distributed software development) refers to the same software by multiple teams in different geographic locations. Project Development process. This word is frequently used in various technical media. Different from outsourcing, remote distributed software development

Remote distributed software development (Distributed Software Development) Refers to the development process of the same software project by multiple teams located in different geographic locations. This word is frequently used in various technical media. Different from outsourcing, remote distributed software develo

These three companion articles are written by Brian Swan. They are very good at agile development. ArticleI believe you will have some knowledge about agile development. 1. Agile Software Development (Part 1) Http://zdnet.com.cn/developer/code/story/0,3800066897,39375631,00.htm 2.

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

programmers may consider some of the functions that this class may need. At this time, you should add these considerations as comments, but never write any code, until these potential features are actually needed; L never add a data member before a use case actually needs it This is recommended to be the same as the previous one, but its object becomes a data member of the class. Sometimes it may seem obvious that a "user" record will be used somewhere; but you should never add that data me

Agile Software Development Declaration Http://www.agilemanifesto.org/iso/zhchs/ We have been exploring better software development methods in practice and helping others. Therefore, we have established the following values: Individuals and interactions are higher than processes and tools Working software is higher than

Principles of Agile Software Development We follow the following principles:1. The first thing we need to do is to satisfy our customers by delivering valuable software as soon as possible and continuously.2. Even after development, you are welcome to change your requirements. Agile processes use changes to create c

Text scanning recognition software How to operate-Agile scanning text recognition software tutorial Companies in order to facilitate the purchase of the scanner, for some paper documents processing is much more convenient, can be scanned through the scanner and stored in the computer. But in the day-to-day work of paper files need not only archive, a large part

consistent. Public classBubbleDemo2 { Public Static voidaction () {integer[] array=Newinteger[]{1,2,3,5,6,8,10,0,2,3 }; GenericsorthandleNewGenericsorthandle(); Bubblesorter Bubblesorter=NewBubblesorter (Intbublesorter); Bubblesorter.sort (array); for(inti=0;i) {tracelog.i (array[i].tostring ()); } }}Or that sentence, the use of design patterns, depending on the circumstances, if the requirements, the environment changes, there may be no design patterns, to refactor code, the

Address: http://www.infoq.com/articles/agile-kanban-boards I have refined the original article, reserved some core ideas, and removed the advertisement in Japan. 1. task board Tasks are the actual tasks at hand. Paste the tasks, tasks, and completed tasks on the whiteboard with simple tips. Different colors indicate different importance levels. You can draw horizontal lanes to indicate who should complete the task. 2 requirement feature Board