1. LogikFabrik
Relevant issues from Pragmatic Programmer

2. Chapter 7 Pragmatic Programmer
Before The Project
Chapter 7
Pragmatic Programmer

3. The Requirements Pit Tip 51: Don’t Gather Requirements – Dig for Them
Tip 52: Work with a User to Think Like a User
Tip 53: Abstraction Live Longer than Details
Tip 54: Use a Project Glossary

4. Overspecifying
Don’t be too specific. Good requirement documents remain abstract.
Requirements
Are NOT architecture
Are NOT design, NOR user interface
Are need

5. The Specification Trap
Tip 57: Some Things Are Better Done than Described
Seamless approach:specification and implementation are different aspects of the same process: each should flow directly into the next, with no artificial boundaries.

6. Pragmatic Teams