Feature-Driven Development: Documentation, Data-Conversion and Deployment (Chapter 14)
Requirements Change Management: If features increase by 10% either scope, schedule
or budget will have to give by 10% to compensate.
Up to 10% can usually be absorbed without too much extra effort.
End User Documentation:Look to:
- Embed helpful information into spare space and panels in the user interface so that it is immediately available to a user.
- Use tooltips/flyover help to display truncated information in full, to explain icons and to briefly display more pertinent details of items quickly.
- Ensure information/warning and error messages are helpful and have an easy to use mechanism to display further explanation of the message including examples.
- Check context sensitive help is written at a useful level of granularity.
- Enable on-line guides and tutorials to easily be published as printed manuals.
Data Conversion: Look for:
- Business data
- Reference data
- Configuration data
Clean data at the source; do not propagate data errors and omissions.
Convert paper-based data into an intermediate electronic form in parallel with
feature development and create programs to convert to final electronic form
once all required features are complete.
Deployment: Start it early. Practice on partial systems, creating pilot schemes.
Repeat training at regular intervals adding new training on new features.