什麼是Definition of Done (DoD)?
What is Definition of Done (DoD)?
http://www.scrumalliance.org/articles/105-what-is-definition-of-done-dod

Definition of done (DoD) 對一個Scrum的team來說非常的關鍵, 因此你必須要和team找出你們共同的DoD出來. 以下是DoD所擁有的特性, 和你的team檢查看看, 是否你們都有注意這些重點


1. DoD是檢查它們完成程度的checklist
- A simple list of activities that add verifiable/demonstrable value to the product.
- Focusing on value-added steps allows the team to focus on what must be completed in order to build software while eliminating wasteful activities that only complicate software development efforts.
- For example: writing code, coding comments, unit testing, integration testing, release notes, design documents, etc.


2. DoD 對team members來說, 它是主要的reporting mechanism
- Reporting in its simplest form is the ability to say, “This feature is done.”
- DoD is a simple artifact that adds clarity to the “Feature’s done” statement.  
- Using DoD as a reference for this conversation a team member can effectively update other team members and the product owner.


3. DoD 是根據現實狀況來回報的
(1) Scrum asks that teams deliver “potentially shippable software” at the end of every sprint.
- Potentially shippable software is a feature(s) that can be released, with limited notice, to end users at the product owner’s discretion.
- Ideally, potentially shippable is equivalent to the Definition of Done.

(2) In reality, many teams are still working towards a potentially shippable state.  Such teams may have a different DoD at various levels:
- Definition of Done for a feature (story or product backlog item)
- Definition of Done for a sprint (collection of features developed within a sprint)
- Definition of Done for a release (potentially shippable state)

(3) There are various factors which influence whether a given activity belongs in the DoD for a feature, a sprint or a release.  
- Ultimately, the decision rests on the answer to the following three questions:
    Can we do this activity for each feature? If not, then
    Can we do this activity for each sprint? If not, then
    We have to do this activity for our release!

(4) Teams should, “Discuss all of the obstacles which stop them from delivering this each iteration/sprint”. Common root causes for impediments include:
    - Team does not have the skillset to incorporate activities into the definition of done for a sprint or for a feature.
    - Team does not have the right set of tools. (Example: continuous integration environment, automated build, servers etc.)
    - Team members are executing their sprint in mini-waterfalls.
    - Aha! Here’s an opportunity to be more cross-functional and share responsibilities across functional silos.


4. DoD 不是一成不變的
- The DoD changes over time.
- Organizational support and the team’s ability to remove impediments may enable the inclusion of additional activities into the DoD for features or sprints.


5. DoD 是一份auditable checklist.
- Features/stories are broken down into tasks both during sprint planning and also within a sprint. The DoD is used to validate whether all major tasks are accounted for (hours remaining).
- Not all value-added activities will be applicable to each feature since the definition of done is intended to be a comprehensive checklist.
- The team has to consciously decide the applicability of value-added activities on a feature-by-feature basis.

創作者介紹

David Ko的學習之旅

kojenchieh 發表在 痞客邦 留言(0) 人氣()