To document or not to document ...
Abstract
Once you've elicited your requirements, they are inside your head.
This is not the ideal situation as there exist no techniques to pull them out of your brain whenever they are needed.
You need to document your requirements so they are accessible whenever someone needs them.
In this session you will discover how you can document your requirements and keep them alive in the most useful way, depending on your development model and your stakeholders.
About Bert Fabry
Agile Coach, CTGEvolving from a programming background, Bert Fabry has been active for over 15 years in project management & analysis. Since adopting agile, he has been a pragmatic agile advocate who tries to find value in everything he sees and does.
About Wim Decoutere
Learning & Development Expert, CTGWim Decoutere started his testing career at CTG Belgium over 12 years ago and has been testing at a number of companies ever since, mostly in the financial sector. He’s passionate about teaching and feels at home when standing in front of a class room. Recently he became a full-time trainer, coaching and teaching about the wonderful world of testing, but also ISTQB, IREB, test design techniques, soft skills, etc.
As a veteran youth instructor with a passion for learning theories and people management, Wim is constantly looking for new ideas to improve his own performance and that of the entire testing team.
