req42 Documentation
52 tips how to use the req42 template.

  • Home
  • About req42
  • A - Tips on req42 Sections
  • B - Tips on Documentation
  • C - Tips on req42 & Agility
  • D - Tips on Clean Start
  • E - Tips on req42 & Tools
  • F - Frequently Asked Questions (FAQs)
  • All tips
  • All keywords
  • Contact

B - Tips on Documentation


Tip B-01: Designate a responsible person.

  • #docu-gardener

Tip B-02: Document sparingly ('less is of more').

  • #documentation
  • #lean

Tip B-03: Clarify appropriateness and need through early feedback.

  • #documentation
  • #lean

Tip B-04: Always explain and communicate top-down, work differently as needed.

  • #top-down

Tip B-05: Focus on benefits rather than functionality.

  • #style

Tip B-06: Always put usefulness before principles.

  • #style

Tip B-07: Separate volatile and permanent documentation.

  • #docu-gardener

Tip B-08: Avoid redundancy in your requirements documentation, if possible.

  • #redundancy

Tip B-09: Establish a positive attitude towards documentation.

  • #documentation

Tip B-10: Document from your readership's point of view.

  • #documentation

  • Imprint & Privacy
© 2023 b-agile & agile-experts. Powered by Jekyll & TtskchTheme, created by Per Starke Web Development, generated 10. Sep. 23