A Collaborative Definition of Definition Of Done
Comments
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
%
123
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Still loading...
ABCDEFGHIJKLMNOPQRSTUV
1
A Collaborative Definition of Definition Of Done
2
3
CategoryQuestionFact (Rationale)This is useful so no one could say: "It's done, but..."Notes
4
5
DVCS
6
Is it on git?The code has been pushed on a blessed, shared repository...it's only on my computer
7
Does it have a tag?The blessed repository has a specific tag (or branch) which unambiguously identifies the functionality...you did checkout the wrong version
8
Did you merge?The feature branch has been merged with the main branch (DEV/STAGE/default) and any conflicts have been solved...it must be merged with dev, first (and the merge would fail)
9
10
Test
11
Are all the tests green?All the unit/integration/e2e tests pass...oh! Don't mind those few red tests
12
Are there no ignored tests?All the tests have been run...I had to ignore those tests, which would have failed
13
Does it work everywhere?All the Acceptance Tests pass, regardless the server that hosts the execution environment...it works on my computer
14
Did you use TDD?All functionalities/behaviors are covered by tests...I was in a hurry, and I developed without tests
15
16
Code
17
Does it compile?Every single component compiles with no errors and produces artifacts...doh! I missed a semicolon. Wait just a second, please...
18
No warnings?Compilation produces no warning...the code isn't, ehm, perfect
19
20
Log
21
Does it log?The code writes a convenient amount of log messages...I didn't know it was not working, since the bug leaved no trace
22
Are logs clean?Running the software for a reasonable long time, logs won't receive any Error/Fatal messages...there are many errors. Don't mind them, they have always been there since ages
23
24
Build
25
Can it build?There's a build script and a Continuous Integration system able to deploy the project on a server and the script succedes deploying this on the stage server...it runs on my computer only
26
Can it completely build from scatch?Cloning a pristine repository the whole project can build and deploy just running a script...in order to run it you should first install Foo and setup a FooBar
27
Is there everything needed on the database?There are fixture and migration scripts which can migrate the schema and the data from the previous version to the current one...it is just missing some data on the database
28
Is it running on the server?The Product Owner can access the software from his computer...you must come to my computer to see it work
29
30
31
Sharing
32
Did you review the code?The source code has been read and approved by other developers...I told Gimmi I would never have written such a crap code
33
What's the URL?The Customer and the Product Owner can access and use the software from their computers...you must come to my computer to see it
34
35
Documentation
36
Have been User Stories saved in some electronic format?User Stories are on the corporate document management system...I read another User Story
37
Is Documentation updated?If the new feature requires a change in the business flow, the relative documentation reflects the change...I'm the only one who knows how this works
38
Have stories been reviewed by Product Owner?Each User Story has been negotiated with the Product Owner...you did not ask for this feature: I dedided to deliver it
39
Have been Stories shared with the Customer?Acceptance tests have been shared and approved by the Customer...I knew I had to implement something else
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
 
 
 
Spazio comune