Scrum with it’s few artefacts, roles and meetings is already fun. The documentation task for most developers and testers is still just boring. Because of this, documentation seldom serves as it’s intended purpose. It is rarely complete, up to date or clear enough to avoid misunderstandings. So you don’t trust documentation, do you? If you can get hold of the people who you know what the software is doing, you ask them instead. Nowadays Behaviour driven development (BDD) makes documentation not only for developers more fun, but also serves as a trust building documentation. Further, it helps to clarify the intent of the story or requirement before implementation starts and validates it continuously after it is released. Sounds impossible? In this track we make the BDD concept of a Living Documentation a reality. We share with you our experiences about the methods and tools which support the notion of BDD and provide practical guidance about which tools are best suited for your context. We will be also happy to share with you the premiere of our open source suite testIT LivingDoc, a BDD solution for Atlassian Confluence and the successor of the popular but almost dead GreenPepper.

1. PIMP MY SCRUM
DOCUMENTATION FUN FOR SCRUM TEAMS
11.11.2015 ANIS BEN HAMIDENE
ANDREAS FALK

2. Our Mission: Fixed Quality
for moving Targets
Agile Quality Engineering
15.06.20162

3. PIMP MY SCRUM
DOCUMENTATION FUN FOR SCRUM TEAMS

4. WHAT?
HOW?
max. 30 days
Every 24 hours
Scrum Big Picture

6. What is Agile?
http://agilemanifesto.org/
Individuals and interactions over processes and tools
Working software over
Customer collaboration over contract negotiation
Responding to change over over following a plan
15.06.20166
comprehensive documentation

7. 15.06.20167

9. WHY?
REASONS FOR FAILING DOCUMENTATION

10. Unclear Goals
• What shall it be used for?
• Feature documentation
• Technical documentation
• Requirements
• User documentation
• Support
• …

11. Business
experts
Developer
Tester
Architect
Requirement
Management Tool
Models
Deliverables
Source Code
Test scripts
Bug
reports
Document
ation
Test
Specification
Different formats and repositories
15.06.201611

12. Unclear Roles & Responsabilities
15.06.201612

13. HOW?
TIPS FOR SUSTAINABLE DOCUMENTATION

14. Tips for sustainable documentation
15.06.201614
• Define the goals for the documentation and share them
• Adopt agile principles
• YAGNI
• Inspect and Adapt
• Fix quality
• Definition Of Done
• Face 2 Face communication

15. Tips for sustainable documentation
15.06.201615
• Build a central glossary for domain terms!

16. Product Owner
Business experts
Developer
Architects
Tester
Single
source
of truth
User should be able
to add DVDs to a
shopping cart
Register as “user1”
Go to “/catalog/search”
Enter “Ice Age”
Click “Search”
Click “Add to Cart”
Click “View Cart”
Verify “Cart” contains
“Ice Age”
Customer customer = new
Customer();
Order order = new
Order(customer);
newOrder.AddDVD(
Catalog.Find(“Ice Age”) );
Make the Documentation accessible and centralized

17. Seperate Requirement Specifications from
Feature Documentation
User Story
Change
Short living
Goal: Planing &
Doing
Feature
Specification
Final state
Long living
Goal: Documentation
& Validation
DavidEvans–effectiveUserStories

18. Business Goals
Scope
(Product Backlog,
User Stories)
Specification
with examples
Executable
specification
Living
documentation
Key
Examples
Try Specification By Example

19. Try Specification By Example

20. Integrate Documentation Tasks into Lifecycle
Specification
Workshop
Impact
Analysis
Observe
& Learn
Go Live!
Review
Sprint
Planning
Session
Based
Testing
Continuous
Validation
Product
Backlog
Living
Documentation
Business
Expert
Product
Owner
Enduser
Tester
Developer
Automate
test
examples
Refine
Develop
Finalize
Story

21. Think about BDD Tools
• Different format
• Table based
• Text based
• Script based
• etc.
• Known Tools
• testIT LivingDoc
• FitNesse (fitnesse.org)
• JBehave (jbehave.org)
• Robot Framework (code.google.com/p/robotframework)
• Cucumber (cukes.info)
• Concordion (concordion.org)

22. 15.06.201622

23. GreenPepper / LivingDoc History
15.06.2016 LivingDoc23
GP Version 1.0 GP Version 1.1… GP Version 3.0 LivingDoc V.1.0
 2006
 Initial Release
 Greenpepper
Server
 Confluence Plugin
 2007
 Eclipse Plugin
 Maven Plugin
 Improved
documentation
 2015
 „GreenPepper 4.0“
 Confluence 5.x plugin
 Eclipse 4.x plugin
https://github.com/testIT-LivingDoc/testit-livingdoc
 2012
 Last GreenPepper
release
 Confluence 4.x
plugin

24. LivingDoc – Architecture and Components
15.06.2016 LivingDoc24
Remote
Agent
ServerCore

25. LivingDoc – Executable specifications using Confluence
15.06.2016 LivingDoc25
LivingDoc Interpreters
Fixture code (Java)
System under Test
Specification
(Confluence WIKI + LivingDoc Plugin)
+
+
+ Executable
Specification


26. LivingDoc – Developing fixtures with Eclipse 4 Plugin
15.06.2016 LivingDoc26

27. LivingDoc – Workflow (1)
15.06.2016 LivingDoc27
1. Create specification (Product Owner, Tester, Developer)

28. LivingDoc – Workflow (2)
15.06.2016 LivingDoc28
public class GreeterFixture {
private String message;
public String greeting () {
return "hello " + this.message;
}
public void setMessage(String message) {
this.message = message;
}
}
2. Implement Fixture Code (Developer)

29. LivingDoc – Workflow (3)
15.06.2016 LivingDoc29
3. Execute specification (Product Owner, Tester)

30. HELLO WORLD DEMO

31. LivingDoc – Evolve a “Real World” living documentation
15.06.2016 LivingDoc31
Reference documentation (Getting started, guides, …)

32. TIME TRACKER DEMO

33. UI TEST DEMO

34. LivingDoc – Stay Tuned for Release (1)
15.06.2016 LivingDoc34
Soon to be released on
https://github.com/testIT-LivingDoc/testit-livingdoc

35. LivingDoc – Stay Tuned for Release (2)
15.06.2016 LivingDoc35
Stay tuned on http://blog.novatec-gmbh.de
or follow @NT_AQE

36. GO AHEAD!
CREATE A LIVING DOCUMENTATION
WITH

37. THANK YOU FOR YOUR ATTENTION
WWW.NOVATEC-GMBH.DE/EN
aqe.novatec-gmbh.de
@NT_AQE
blog.novatec-gmbh.de