This is an original blog created by Esther Kanagaratnam. Defines my understanding of requirements gathering , the various documents involved and visuals in effective "requirements gathering".The growing technical world is so demanding that "documentation" can be difficult at all times. Content is dynamic and ever changing, user requirements can be less defined and more widen. A simple request to add "module" to website might seem easy to the business , but this requires adequate time to Scope, Define, and interpret business requirements into functional requirements.
An innovative approach to documentation. During my couple of years working within the web industry, I could see that "complex documentation" is complicated and long winded. Hours spent writing large Business requirements to change a specific are on a site or application is very time consuming.
Even though documentation is very important. I could see the value of incorporating all requirement gathering, signoff into one document. Providing the business a hierarchical understanding, giving the development team technical insight.
An innovative approach to documentation. During my couple of years working within the web industry, I could see that "complex documentation" is complicated and long winded. Hours spent writing large Business requirements to change a specific are on a site or application is very time consuming.
Even though documentation is very important. I could see the value of incorporating all requirement gathering, signoff into one document. Providing the business a hierarchical understanding, giving the development team technical insight.