80% of failures in IT projects come from poor requirements gathering. We focus strongly on getting a common ground of understanding between user, sponsor and project team.
We use a process built around responsibility and job roles in order to guarantee that all necessary stakeholders have their say.
Every job role has a unique perspective on what a system should and should not do. We all know that we should listen to the users, but what about.
- The administrators
- The business side, the value
- The legal or regulatory constraints
- The accountability required
- The workflow decided by the business
It all has to be captured in order to have a decent backlog of requirements to start a project. Gathering requirements is a discipline of bridging many peoples point of view.
And last but not least each requirement should be given a business value and an estimate of effort. Otherwise there is no guidelines as to what we should implement first.
| Next > |
|---|
