practices for scaling lean agile development

Alibabacloud.com offers a wide variety of articles about practices for scaling lean agile development, easily find your practices for scaling lean agile development information here online.

Agile development practices 2: planning and design (large R & D team, learning team, 139 team, mentoring system, design review, predicate statement, joint estimation, and playing card estimation)

effective co-Anonymous estimation (this article also details ). 2. Acceptance Criteria In order to establish a Joint Estimation Based on the same goal, and to prevent the requirement from gold plating or the final software from meeting the requirement, the master and apprentice should establish a common understanding of the requirement. The simple method is to join the estimation meeting with the two (in fact, the master and multiple apprentices) and listen to the PO to explain the story. Howev

Agile Software Development: principles, patterns and practices--9th OCP: open-closed principle

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);

[Agile best practices] From poker to software development

I have always believed that software development is like a collaborative game.Jay fields masterpieceSoftware development lessons learned from pokerThen, I am more convinced of this point! We recommend it to you !!--------------------------------------------------------------------- I used to do not develop software. Two years before I joined thoughtworks, I made a living mainly by playing poker. Of course,

Two types of people, no need for agile development practices

The developers of cattle, who will be efficient in writing concise, high-quality code practice, has been naturally integrated into their own DNA , in the blood. Therefore, the design, development and testing can be integrated in a very high efficiency. The testers of the cattle have naturally put the required test paths clearly in their own minds. So, the cattle testers, not without the design of test cases, but he (she) has long been required test ca

Agile Software Development: principles, patterns and practices--the 13th chapter of UML Overview for C # Programmers

to change.Translate into natural language description: If the coin event is received in the locked state, it is migrated to the unlocked state and the unlock function is called. If the pass event is received in the unlocked state, it is migrated to the locked state and the lock function is called. If the coin event is received in the unlocked state, it remains in the unlocked state and calls the Thankyou function. If the pass event is received in the locked state, it remain

Agile Software Development: principles, patterns and practices--the 16th chapter, the 17th chapter, the 18th Chapter sequence diagram

has a separate internal thread called the active object. They appear as bold borders, as follows:18.2.6 sending a message to an interfaceExamples are as follows:Send a message to its derived type through an interface:18.3 ConclusionA sequence diagram is a tool. To be used in accordance with its design intent. Use them in front of the whiteboard to communicate with others in real time. Use them in short documents to record those core, important collaborations in the system.In the case of sequenc

Agile Software Development: principles, patterns and practices--the 4th chapter test

run, the faster you will find any deviations from those tests. If you can run all the tests multiple times a day, the system will not expire for more than a few minutes. This is a reasonable goal. We will never allow the system to regress. Once it is working at a specific level, it must not be reversed to a slightly lower level.However, validation is only one of the benefits of writing tests. Both unit and acceptance tests are a form of documentation. Such a document can be compiled and execute

Agile Software Development: principles, patterns and practices--the 14th chapter uses UML

. 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

Agile Software Development: principles, patterns and practices--the 12th ISP: The principle of interface isolation

and cannot be overused. If a class has hundreds of different interfaces, some of which are separated according to the client program, others are separated by version, then the class is hard to figure out, and this kind of hard-thinking is very frightening.12.5 ConclusionFat classes can cause unhealthy and harmful coupling relationships between their client programs. When a client program asks for a change to the Fat class, it affects all other client programs. Therefore, client programs should

Agile Software Development: principles, patterns and practices--the 10th chapter Lsp:liskov substitution principle

following code: Public class base{ publicvirtualvoid f () {/*some code* / }}publicclass derived:base{ publicoverride void f () {}}The function f is implemented in base. However, in derived, the function f is degenerate. Perhaps, derived programmers think that function f is useless in derived. Unfortunately, base users do not know that they should not call F, so there is a substitution violation.The existence of degenerate functions in degenerate classes does not always mean that the LS

Best practices for Agile Software Development-Scrum standing MEETING

What is a standing meeting? Standalone meeting is one of the technologies related to Scrum in Agile Software Development methodology. It can also be called the best practice of Scrum. The specific form is the same time every day. All members of an agile development team stand together face to face for a period of 15 ~

[Best practices] In the agile scrum software development model, how do we start a sprint planning meeting?

In the agile development framework of scrum, the most important part is the Sprint plan meeting. If the meeting fails, the whole sprint will make the scrum team suffer and it is difficult to complete the initial sprint goal. After several attempts, we finally found our own model. These methods and principles are the best for us. Based on our own knowledge and our own project scenarios, we may not try them o

Agile development practices (1)

Agile development is constantly using feedback for self-adjustment and improvement in a highly collaborative environment. 1. If the pipeline goes far, it is necessary to return again if the error occurs, knowing how to discard it, whether it is technology or zookeeper code or wrong design. 2. It is not required that all people are experienced professionals, but must have a professional working attitude.

Practices of agile development-code check

The loose pair is different from the tight pair. Two people don't always sit together to locate the problem and solve the problem at any time, but sit together for a short time. There are two main tasks at the post-Checkpoint: one is to check whether the results meet the requirements (what to do), the other is to check whether the code is faulty (how to do it), and the other is to check the code. Code check (also known as code review code inspection) is a long-standing but mysterious thing. It w

Total Pages: 2 1 2 Go to: Go

Contact Us

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.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.