The other night I’ve been thinking of a way to manage features for my projects on a high level since I’m the type of person that think in pictures.
Basically what came to mind was to have a flow diagram with the features branching from each flow step. This gave me a good overview on progress and feature test coverage. It is also giving me a indication of when and where features overlap or when the are duplicated allowing me to limit extensive regression testing.
Some issues this might have are:
1) Time consuming to update. Solution: Use a dedicated requirements management tool that integrate into the process. But, updates should only happen once in the first day of the iteration assuming the team is following a strict iterative release model.
2) Space can be limited either by the amount of paper or the wall. Solution: Only list the high priority features that fill the business need.
3) Not environmentally friendly. Solution: Keep it digital either on the dashboard of the software package in #1 or a low energy TV set. Then again, the amount of energy the TV consumes will be higher than just to print the paper unless Amazon make large displays using their Kindle technology.
Nicolaas's space 