Agile experience to share, how to implement DoD enterprise in agile development

First, what is the DoD?

When you have two or more people involved in the same thing, our "team" arises, then we have the most important thing is to set expectations and unified team, in this paper, which is "complete the standard."

After an iterative done, to conduct inspection team to decide this iteration is complete. But each team is unable to reach unity is complete, some believe that coding is completed, it means the job is done; some think we need a simple self-test to make sure that function is available; there is a need to consider finished and automation use cases testing done by considered.

To avoid this problem, agile software development, commonly Definition of Done "to complete the definition of" to indicate whether the work has been completed, different activities have different complete the definition. First of all you know, all of the DoD are not immutable, at Over time, the accumulation of change members change the experience of the project, our DoD will be very different, so we also need to regularly check and improvements.

Two, DoD classification

With mental preparation above, we will look at the following definitions DoD, will feel not so difficult.

A, iteration DoD

The most typical is iterative DoD, this is the first place to DoD applications. Some common rules are:

1. All of the code through static testing, serious problems have been modified, the rules of static analysis See ...

2. All the new labor code gets reviewed

3. All completed user stories has a corresponding test cases

4. Test cases have been executed

5. All users complete story of validated Product Owner

Second, the DoD released

For the release, there is generally more stringent requirements, typical terms posted DoD are:

1. Complete focus on the needs of release planning required

2. At least once by the total amount of regression testing

3. Repair all defects grade 1, 2, 3 and 4 not more than 20 defects

Third, the DoD version

DoD version is aimed at some of the rules before and after each version on-line, such as:

1. Product documentation have been updated

2. Code has been deployed to a production server

3. Operation and maintenance on a smoke through acceptance testing environment

4. The author of the original requirements have been accepted by the function

5. Operation and maintenance, new features training market, customer service has been completed

Fourth, the daily DoD

Other typical DoD has daily DoD, typical provisions are: to build a daily build environment, evening automatic static code checking, compiling, deploying and testing, repair defects and problems of daily build and test the day before the discovery.

1. Before work must be checked in code written in the same day, check in to fill clear the backlog

2. The code must be the same day or the second day and inviting peers code review on the same day

3. Check the function code must have a corresponding test unit (using strict TDD)

4. Every evening trigger static code checking, automated regression testing

5. Day continuous integration, build issues in the environment, please solve day

Fifth, the user story DoD

As well as for user stories (or use cases) of the DoD, such as:

1. The final description of user stories in line INVEST

2. User stories get covered by the corresponding test cases

3. Users get the story corresponding automated test cases

4. PO trial and user stories get preliminary approval

When the test set relatively large, can not be completed within one day of the test, they can conduct full weekly amount of regression test automation, so there is a weekly DoD, typical provisions are:

1. Defects found last week on whether to solve

2. Automated testing last week whether to join the new features to the test set per week.

Tips: DoD must be a team at the start of the project to discuss it, the team is willing to abide by the principle, once determined, the team should abide by.

Three, DoD practical value

A, DoD is a list of valuable software activities

DoD is a simple checklist, contains a series of activities. For example: coding, annotate, unit testing, integration testing, release notes, design documents, and so on. All of these activities can bring real value to the product. The use of DoD, you can let the team focus on those things that must be done, while allowing those useless, only complicates the software development activities are eliminated.

Two, DoD is the main reference for the state team members

For reporting iteration in its simplest form is only one sentence: "This feature complete." After all, a feature or a product Backlog Item of only two states: complete or incomplete. DoD is "feature complete" best complement this sentence. DoD use as a reference standard, team members can quickly and effectively so that other team members or PO understanding of state.

Three, DoD is not the same

DoD will change over time. Help increase the capacity of the organization and the team lost more obstacles can be removed, so that more activities can be included in the sprint or feature of the DoD in the past.

Four, DoD is a review of the list can be

feature / story sprint plan meeting the user and can be split into the sprint task. DoD can not be used to measure all the major work is planned, including the (remaining time). Moreover, when a feature or the end of the sprint, DoD can not be used to examine all value-added activities must have been completed.

Attention is necessary, DoD itself is flawed. Not all value-added activities can be applied to every feature above, and DoD audit system itself is a large and comprehensive examination of the matter. Team needs to look at each feature based on a value-added activities apply to this feature.

For example, the pursuit of the user experience for web services such feature is a plus, but for some other feature of it is unnecessary.

Finally, it should be noted that the criteria for acceptance is not necessarily determined by the Product owner, should be determined according to the display case, each team must select the appropriate DoD principles according to their own situation. CORNERSTONE offer including task / demand / test management, iteration planning, defect tracking, reports, statistics, teamwork, WIKI, share files and calendar function modules, the following team of 20 people is free, you can register for free click CORNERSTONE .