SPA Conference session: Style and Taste in Writing FIT Documents | |||
| One-line description: | Hands-on tutorial to refactor some poorly written FIT tables into something clearer | ||
| Session format: | Tutorial (75 mins) [read about the different session types] | ||
| Abstract: | FIT is a framework that comes in various guises (Fit, Fitnesse, Fitlibrary), and can be used in different ways. The core principle behind writing FIT documents is to promote better communication between the stakeholders of a system. By using FIT, we can get our customers more involved in the design and specification. With the help of FIT documents, we will collaborate more closely and evolve a better shared understanding. As the system evolves, the collective set of FIT documents will provide a living specification - the place that everyone refers back to, to understand what the system actually does. In principle, using FIT is a good thing, but in practice we find that some teams struggle to use FIT documents effectively. In this tutorial we will introduce some concrete examples of poor FIT style, and get the participants to refactor these examples to improve them. | ||
| Audience background: | Required: a basic understanding of agile software development Useful but not essential: some prior experience with FIT documents. This session is relevant to anyone involved in software development, especially testers, business analysts, product owners, programmers, etc. | ||
| Benefits of participating: | - gain an understanding into how to write FIT documents that communicate well - learn what pitfalls to avoid when applying FIT in practice | ||
| Materials provided: | - Introductory slide presentation. - For the exercises, some poorly written example FIT documents, and our proposed improved versions - FIT in practice slide presentation. | ||
| Process: | 00 - 10 mins: Introduction, including a brief introduction to FIT, and example driven development in general. 11 - 60 mins: Laptops required. Work through a series of exercises. For each exercise, we will give the participants one or two FIT documents, and ask the participants to work in pairs to refactor the tables into something clearer. Each exercise is focused on a specific aspect of FIT document style. After each exercise we will present our proposed refactored document(s) and discuss. 61 - 75 mins: FIT in practice. We will wrap up the session with a short presentation covering some of the practical pitfalls to avoid when applying FIT in practice. This is based on our real experience of using FIT on several projects, some successful, some not so successful. | ||
| Detailed timetable: | See process | ||
| Outputs: | No outputs planned | ||
| History: | Steve & I gave a talk-only version of this session at JavaZone 2007. | ||
| Presenters | |||
| 1. Mike Hill Mandu Limited |
2. Steve Freeman M3P Ltd |
3. | |