acceptance test driven development - mikael gunnefur, anders jonsson - ltg-9
TRANSCRIPT
Acceptance Test Driven Development –the agile connection/contract between Customers and IT
(a short story from Volvo)
Lean Tribe Gathering LTG-9
2012-05-08
Volvo IT
2
Speaker
• Name: Anders Jonsson• Experience: 22 years in Software
Development (Nordbanken, Cap Gemini, Rational/IBM, Volvo IT)
• Roles/Skills: Lean/Agile coach, Scrum Master, Kanban Master, PM etc.
• Specialties: Software Development, Scrum, Kanban, XP, project management
• Works at: Volvo IT - Global ADT• email:
Volvo IT
Speaker• Name: Mikael Gunnefur• Age: 45 years• Experience: 24 years in IT
Industry (Volvo IT, SAAB Xperientia, Enator, CAP Programator and more)
• Roles: Agile & Test Coach, Test Manager, Scrum Master, Software Developer and more
• Specialties: Software Development Techniques, Test, Quality Assurance, Quality Control, Scrum, XP, Internal Control (SOx), Quality (ISO 9000)
• Works at: Volvo IT - local Application Delivery in Skövde
• email: [email protected]
Volvo IT
History and Objectives· Traditionally when working with agile there is a product owner, that during the
best circumstances drives the development of a IT solution by defining, loosely coupled, requriements into a product backlog that works as an input to the development team that translates it into working software.
But ...· There are however several problems with this approach. The wrong person
being the product owner, product owner doesn’t have enought time to collaborate with the development team, unclear who is responsible for doing what between the product owner and the development team, lack of other needed expertise, e.g. business analyst, end users etc.
This leads to the following objectives· Customer and IT must collaborate closely together
· Well defined and visual way of working
· Product demands expressed as Acceptance Criteria’s
· Results in the shape of tested and running software
Volvo IT
Definitions
· ATDPBL = Acceptance Test-Driven Product BackLog
· BRA = Business Requirement Analysis (high-level specification of a Category)
· AC = Acceptance Criteria
· Category = Feature
· FN = Feature Notes
· TP = Test Plan (IT)
Volvo IT
Task boards - overview
Business driven boardCategory Not
startedIn
progressDone
IT driven boardAcceptance
CriteriaNot
startedIn
progressDone
Create BRACreate
AC
Create FN
G2Handle
Doc.of.Parts
G1Show Start Sequence
G2.1Add new record...
G2.2Edit record...
G2.3Connect doc
info...
Create TP
IT-tasks
Business tasks
Coding
Test
ValidateAC
Coding
Test
ValidateAC
Coding
Test
ValidateAC
Create BRACreate
AC
Create FN
Create TP
Volvo IT
G1 Show start sequencePresent as an Category in ATDPBL
Volvo IT
Task boards
Business driven boardCategory Not
startedIn
progressDone
IT driven boardAcceptance
CriteriaNot
startedIn
progressDone
Create FN
Create AC
G1Show Start Sequence
Create TP
Create BRA
IT-tasks
Businesstasks
Volvo IT
Task boards
Business driven boardCategory Not
startedIn
progressDone
IT driven boardAcceptance
CriteriaNot
startedIn
progressDone
Create FN
Create AC
G1Show Start Sequence
Create TP
Create BRA
IT-tasks
Businesstasks
Volvo IT
Task boards
Business driven boardCategory Not
startedIn
progressDone
IT driven boardAcceptance
CriteriaNot
startedIn
progressDone
Create FN
Create AC
G1Show Start Sequence
Create TP
Create BRA
IT-tasks
Businesstasks
Volvo IT
Task boards
Business driven boardCategory Not
startedIn
progressDone
IT driven boardAcceptance
CriteriaNot
startedIn
progressDone
Create FN
Create AC
G1Show Start Sequence
Create TP
Create BRA
IT-tasks
Businesstasks
Volvo IT
Task boards
Business driven boardCategory Not
startedIn
progressDone
IT driven boardAcceptance
CriteriaNot
startedIn
progressDone
Create FN
Create AC
G1Show Start Sequence
Create TP
Create BRA
IT-tasks
Businesstasks
Definition of Done - BRA• New BRA-document created
• Link to document, Column D, in ATDPBL
Volvo IT
G1 Show start sequenceLink to BRA-document added
Volvo IT
Task boards
Business driven boardCategory Not
startedIn
progressDone
IT driven boardAcceptance
CriteriaNot
startedIn
progressDone
Create FN
Create AC
G1Show Start Sequence
Create TP
Create BRA
IT-tasks
Businesstasks
Definition of Done - AC• Acceptance criteria defined and present
in ATDPBL
• Each Acceptance Criteria as a specific row
Volvo IT
G1 Show start sequenceAcceptance Criteria added
Volvo IT
Task boards
Business driven boardCategory Not
startedIn
progressDone
IT driven boardAcceptance
CriteriaNot
startedIn
progressDone
Create FN
Create AC
G1Show Start Sequence
Create TP
Create BRA
IT-tasks
Businesstasks
Volvo IT
Task boards
Business driven boardCategory Not
startedIn
progressDone
IT driven boardAcceptance
CriteriaNot
startedIn
progressDone
Create FN
Create AC
G1Show Start Sequence
Create TP
Create BRA
IT-tasks
Businesstasks
Definition of Done - FN• Hand-over meeting performed
• Feature Note created
Volvo IT
Task boards
Business driven boardCategory Not
startedIn
progressDone
IT driven boardAcceptance
CriteriaNot
startedIn
progressDone
Create FN
Create AC
G1Show Start Sequence
Create TP
Create BRA
IT-tasks
Businesstasks
Definition of Done - TP• IT Test Plan, light, created for Category
• Overall IT Test Scenarios in Test Execute
log at project portal
Volvo IT
Task boards
Business driven boardCategory Not
startedIn
progressDone
IT driven boardAcceptance
CriteriaNot
startedIn
progressDone
Create FN
Create AC
G1Show Start Sequence
Create TP
Create BRA
IT-tasks
Businesstasks
Definition of Done• Product Backlog Grooming is Done when
these results are Done. This means that Acceptance Criteria ticket(s) can be created and added to the IT board (Acceptance Criteria queue)
Volvo IT
Task boards
Business driven boardCategory Not
startedIn
progressDone
IT driven boardAcceptance
CriteriaNot
startedIn
progressDone
Create FN
Create AC
G1Show Start Sequence
Create TP
Create BRA
IT-tasks
Businesstasks
G1.3Press Export
button...
G1.2Press column
header...
Volvo IT
Task boards
Business driven boardCategory Not
startedIn
progressDone
IT driven boardAcceptance
CriteriaNot
startedIn
progressDone
Create FN
Create AC
G1Show Start Sequence
Create TP
Create BRA
IT-tasks
Businesstasks
G1.3Press Export
button...
G1.2Press column
header...
Coding
Test
ValidateAC
Coding
Test
ValidateAC
Volvo IT
Task boards
Business driven boardCategory Not
startedIn
progressDone
IT driven boardAcceptance
CriteriaNot
startedIn
progressDone
Create FN
Create AC
G1Show Start Sequence
Create TP
Create BRA
IT-tasks
Businesstasks
G1.3Press Export
button...
G1.2Press column
header...
Coding
TestValidateAC
Coding
Test
ValidateAC
All coding and test activities needed (sticky notes used for work tasks, icons used to show blocked work etc.)
Volvo IT
Task boards
Business driven boardCategory Not
startedIn
progressDone
IT driven boardAcceptance
CriteriaNot
startedIn
progressDone
Create FN
Create AC
G1Show Start Sequence
Create TP
Create BRA
IT-tasks
Businesstasks
G1.3Press Export
button...
G1.2Press column
header...
Coding
Test
Coding
Test
ValidateAC
ValidateAC
All coding and test activities Done. Acceptance Test can be performed
Volvo IT
Task boards
Business driven boardCategory Not
startedIn
progressDone
IT driven boardAcceptance
CriteriaNot
startedIn
progressDone
Create FN
Create AC
G1Show Start Sequence
Create TP
Create BRA
IT-tasks
Businesstasks
G1.3Press Export
button...
G1.2Press column
header...
Coding
Test
ValidateAC
ValidateAC
Coding
Test
Volvo IT
G1.2 & G1.3 Show start sequenceAcceptance Test performed
Volvo IT
Task boards
Business driven boardCategory Not
startedIn
progressDone
IT driven boardAcceptance
CriteriaNot
startedIn
progressDone
Create FN
Create AC
G1Show Start Sequence
Create TP
Create BRA
IT-tasks
Businesstasks
G1.3Press Export
button...
G1.2Press column
header...
ValidateAC
Coding
Test
ValidateAC
Coding
Test
Volvo IT
G1.2 & G1.3 Show start sequenceAcceptance Test performed
Volvo IT
Conclusion
· Customer and IT must collaborate closely together
· Well defined and visual way of working
· Product demands expressed as Acceptance Criterias
· Results in the shape of tested and running software
Volvo IT
Conclusion
· Customer and IT must collaborate closely together
· Well defined and visual way of working
· Product demands expressed as Acceptance Criterias
· Results in the shape of tested and running software
Work ongoing