The Business Challenge
Issue Tracking and GAP Analysis is done via email and verbal communication.
This leads to communication gaps as well as an unscientific methodology being adapted.
The Enj Solution
The Testing function records a GAP in the system and sends it to the Project Manager.
If the GAP is accepted and after discussions for clarity, it is determined whether the same is a major one or not.
If it is, concurrent inputs are sought by the Project Manager from the Chief Architect (CA), the Chief Executive Officer (CEO), the Chief Operating Officer (COO) as well as the Chief Technical Officer (CTO).
Their views are then collated and a GAP analysis is categorized, scheduled and allocated.
If planning is not required, relevant development and delivery documentation is done.
The system is tested and once cleared is released to production.
Feedback is also given to the initiator of the gap.
On the other hand, if planning is required, acceptance criteria are prepared based on which test plans are created.
Further on the relevant development and delivery documentation is done and the workflow proceeds in the same way as the earlier case.
Scientific approach to product development.
Crystallized view of each and every GAP perceived in the system.
Ease of tracking of status of various GAPs - helps remove roadblocks.
Centralized repository of all GAPs- current and historic.
Concurrent development of Knowledge base.
Security issues are addressed.
Historical data is available for future reference.
Easy movement of documents.