Requirement/Gaps Template

  Requirements Management  

Format: Evaluation Assessment / Log

This template can be used to gather requirements and gaps during product walk-through sessions or in any requirement discussion session. This template can be used in all kinds of projects where requirements and gaps can be classified according to the business unit and (if required) can be further drilled down to sub-units. It is most apt for core banking transformation projects where requirements come from all participants from all business units. Once the PWT sessions or requirement discussions are done and development takes over, it’s difficult to trace back a requirement to the individual member who raised it. It's very important to trace back the requirement so that it can be understood in detail and can be discussed for development purposes.

Categorization or classification of requirements also helps in rationalization or prioritization of requirements and gaps when it comes to the cost of development. Requirements /Gaps per business unit/sub-unit can be easily filtered and shared with respective units for prioritization of requirement items. This template is an important part of the SDLC process, where requirements from this template will be traced and tracked back to RS (Requirement Specs) >> FS (Functional Specs) >> DS (Design Specs) docs.

How to use this template?

• Column A – Requirement tracking number; suitable convention can be used as per the requirement
• Column B – All participating business units can be captured under this column (Audit & Compliance, Branch Operations, Branch Banking, etc.)
• Column C – This column can be used for further sub-units under the main business unit
• Column D – Team member/participant who has raised this requirement during the session
• Column E – Module highlight specific to application
• Column F – Detail of the requirement
• Column G – Priority attached to the requirement
• Column H – Date on which this requirement is implemented
• Column I – Sub-product specific to application
• Column J – Country can be captured for multi-country projects, or if participating members are from different countries
• Column K – Status of the requirement
• Column L – Application vendor remarks (if applicable)
• Column M – Any specific comments or remarks to be captured

People who downloaded this item also downloaded . . .