MinneBar Notes - Translating Geek: Executable Documentation
by Robert Fischer - 1000-1050
- The Pragmatic Programmer - if you are repeating tasks, automate them.
- How can we translate customer specs and requirements to documentation?
- FIT - Framework for integrated testing
- Story Test - Based on Unit Test idea
- Customer produces expectations and communicates them to a developer
- Hopefully it is documented for future reference - if it’s not documented it’s hard to expect people to understand or know if they followed the idea as originally discussed.
- Story Test
- Translations must be made from Expectations to Story Tests. Can be translated by developers, QA, customer.
- Has Criteria (done or not done)
- ‘Like This’ doesn’t work as well for criteria as boolean
- If you have criteria to satisfy for the story, you can say how many have been satisfied when reporting progress.
- Gives a common language between developers and business people.
- Especially userful if trust is a concern with customers; no expectation that anything done will actually do what was requested. Helps build trust up.
- Related to the story test, may be several tests for a Story Test.
- End result (surprise!)