Recently I was brainstorming with a highly competent tester based in Bangalore, India [a rare breed out here] and we stumbled on a startling fact. Requirement gathering and tracking methods have remained largely static for a long time. The delivery models in India with respect to QA and process are reminiscent of the late 90’s.
These are some of the facts that we ascertained:
- The most prolific and commonly used requirement tracking tool in the Indian IT service sector is…….. “Microsoft Word”.
- Every stakeholder/developer/tester in a project has a personal copy of the requirement document resident in his inbox.
- Requirement changes are often not centrally held/ distributed.
- Requirement discussions/ freeze is effected after multiple rounds of talks with the onsite customer/coordinator.
Software systems today have reached a stage of “critical complexity” where it is imperative that we hold requirements in a central repository. There core reason for no advances in this segment is because our internet non-savvy IT community is oblivious to the concepts of web2.0 and the “collaborative internet”.
The version of the internet as we have it today has moved towards distributed applications with added focus on communities,collaboration and harnessing collective intelligence.
The benefits this can provide to requirement tracking are the following:
- Use Web 2.0 principles to build requirement tracking tools on the “internet platform”.
- Provide features within the app like forums [to start discussion threads], chat enabling for real time gap resolution, wikis for public bulletin boards.
- The feature rich UI capabilities of internet based applications can provide “mind map” like interfaces for provide a structural organization for requirements.
- This would provide the benefit of greater usability and clarity compared to “referring to section 1.1.3 (a) or 1.2.4 (b)” to track requirements.
Requirements are the most critical pieces of information in the IT sector…. Information management is a science that Internet gurus are trying to perfect and they are the forerunners. So its only logical to adopt their practices in “managing” our information rather than stick to “Pubic library model of requirement tracking and analysis”.
If you enjoyed this post, make sure you subscribe to my RSS feed!
