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.
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
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
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)