What BUFR (big up-front requirements) is useful for
Type: (Anti-)Rules
Gist
How to use the BUFR approach in order to hinder change, to avoid focus on business value, to create thrashing, to facilitate no longer valid requirements and to create high risk.
Principles and Notes
R1: Try to find, document and analyse all requirements for a non-trivial system development before you do anything else
Related Pages
- being agile on offshoring projects
- go agile, enterprise wide
- stripping user stories for incremental development
If you want to know more about a topic, simply tag the article with a 'morePlease' or 'examplesPlease' tag!
page_revision: 3, last_edited: 1228325376|%e %b %Y, %H:%M %Z (%O ago)
