Requirements Practice - Maveric Systems


Published on

The focus of requirements management is shifting away from the high cost of defect detection and fixing to defect prevention by improving the quality of requirements management process. Maveric provides assurance in Requirements Management through adoption of structured tools, methodologies, industry best practices and consultants with deep domain knowledge. Maveric offers end-to-end services in the Requirements Assurance practice.

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Requirements Practice - Maveric Systems

  1. 1. © 2013. Maveric Systems Limited Requirements Assurance This presentation and supporting material is owned by Maveric Systems and is for sole use of intended audience only. The presentation may contain content that is confidential or proprietary and may not be distributed or copied without the permission of Maveric Systems.
  2. 2. © 2013. Maveric Systems Limited 2 Our Lifecycle Assurance Business Requirement Definition and Management Requirements Validation, Functional Specs & Signoff Design Development & Unit Testing System Integration Testing Non-functional Tests & UAT, Training & Ops readiness Go Live REQUIREMENTS ASSURANCE APPLICATION ASSURANCE PROGRAM ASSURANCE Our assurance-only business model combines upstream defect prevention with robust downstream defect detection and risk management services
  3. 3. © 2013. Maveric Systems Limited 3 Requirements Assurance We Assure defect prevention by significantly enhancing Requirements Quality through ▸ Domain centric approach ▸ Usage of structured methodologies and templates ▸ Deep knowledge of current regulatory trends and proven expertise performing Analysis/Design for large Financial-services engagements
  4. 4. © 2013. Maveric Systems Limited 4 Requirements Assurance – Service Portfolio Requirements Definition & Management Requirements Validation Program Health Check
  5. 5. © 2013. Maveric Systems Limited 5 Practice Overview Structure ▸ Practice Leader with rich industry experience. Primarily involved in engagement governance , stake holder management and mentor team members Associate Consultants Consultants Senior Consultants Principal Sub Vertical Capital markets Risk & Compliance Retail Banking Cards Corporate Banking ▸ Subject Matter Experts ▸ Lead Engagements ▸ Lead small teams in projects ▸ Assist in running workshops ▸ Trained in domain areas and tools ▸ Business Analysis
  6. 6. © 2013. Maveric Systems Limited 6 Training Programs Domain Business Analysis Consulting Skills Industry Certifica- tions Project Specific Training Banking and Financial Services ▸ Requirements Definition and Management ▸ Requirements gathering tools and techniques ▸ Consulting models ▸ Managing customer expectations ▸ Service excellence ▸ CBAP ▸ FRM ▸ CFA ▸ CAMS ▸ NCFM ▸ Train on Skill sets aligned with project objectives ▸ Impart necessary application knowledge – Conducted collaboratively with the customer
  7. 7. © 2013. Maveric Systems Limited 7 ▸ Maveric is an “Assurance only” Business model – Requirements to Release ▸ Experienced Consultants with strong domain knowledge of banking & understanding of regulatory framework ▸ Experienced in conducting structured ‘Requirements Validation’ with business stakeholders gained from execution of numerous UAT projects and standalone RV engagements ▸ Usage of structured methodologies, templates and checklists Maveric Differentiators
  8. 8. © 2013. Maveric Systems Limited Our Service Offerings
  9. 9. © 2013. Maveric Systems Limited 9 Activities Requirements Definition & Management Conduct stakeholder interviews and gather requirements Conduct follow-up meetings/ workshops for clarifications and refinement Conduct walkthrough of Requirements Specifications Document ▸ Conduct stakeholder interviews/workshops for requirements gathering ▸ Document and publish workshop notes for approval ▸ Analyze requirements and identify gaps for clarifications and follow-up ▸ Produce draft Requirements Specifications ▸ Documentation of inconsistencies in rationale, sources and conditions ▸ Refine Requirements Specifications Document through corrective action ▸ Ensure bi-directional traceability of requirements ▸ Conduct playback session of Requirements Specifications Document to stakeholders for validation, approval and sign off Deliverable Requirements Elicitation Requirements Elaboration Requirements Validation ▸ Draft Requirements Specifications Document ▸ Requirements Specifications Document ▸ Approved Requirements Specification Document for baselining
  10. 10. © 2013. Maveric Systems Limited 10 Criteria ▸ The BRDs pertain to enhancements done to existing applications, hence any new NFR should be called out explicitly ▸ The assumptions section of the BRD should clearly state that existing NFRs would suffice in the absence of explicitly stated NFRs Requirements Validation Criteria Definition Metric Cohesiveness All parts of a requirement should be together No of dependent requirements not cohesive Consistency All requirements have the same level of detail. No contradictions between individual requirements No of conflicting requirements Completeness Requirements have to be fully developed No of requirements not complete Traceability Each requirement is essential for the solution and be traceable to a stakeholder No of requirements that cannot be traced back to stakeholders Testable Should be capable of being validated by designing test cases to check if the solution meets the requirements No of requirements without ‘Acceptance Criteria’ being defined Unambiguous Devoid of terms open to interpretation (like fast, new, etc.) No of open ended requirements Criteria for assessment of Business Requirement Document (BRDs) Criteria for assessment of Non Functional Requirements (NFRs)
  11. 11. © 2013. Maveric Systems Limited 11 Program Health Check ▸ A diagnostic approach to finding underlying causes that can result in program failures ▸ A three step process involving: 1. Structured data collection and analysis 2. Identification of problem areas 3. Roadmap and recommendations ▸ Deliverables: A Health Check Assessment Report that » Highlights specific issues and risks in the program » Suggests remedial action that needs to be taken to address these issues and risks » Provides a comprehensive roadmap that identifies the interventions required
  12. 12. © 2013. Maveric Systems Limited Case Studies
  13. 13. © 2013. Maveric Systems Limited 13 Requirements Validation Business Context Project Objectives & Maveric Approach Value Adds & Business Impact ▸ A large global bank was in need of a full fledged Requirements Validation service, as there was a lack of formal review of business requirements and functional/ Non functional specifications, particularly by test teams who often have no involvement in review/or Signoff. This lead to 1. Risk of rework due to poor requirements 2. Increased costs of defect removal where defects due to poor requirements were found late in development cycle e.g., SIT/UAT Project Objectives ▸ Develop an offshore/onshore service model for requirements validation ▸ Business requirements documents and functional/Non- functional specifications to be assessed against defined criteria Maveric Approach ▸ Review of BRDs/FSDs against defined criteria namely Correctness, Unambiguity, Completeness, Consistency, Traceability, Cohesiveness Review documents and produce report/defect scorecards Value Adds ▸ ‘Validation Checklist’ used for review of BRDs/FSDs ▸ Acceptance criteria agreed upon and documented ▸ Clear governance model put in place for project execution Business Impact ▸ Improved requirements ,reduced need for rework thereby saving cost and time ▸ Reduced opportunity for misinterpretation ▸ Enabled cross project comparison of document quality through standardized ‘Quality scorecard’ ▸ Testable and traceable requirements made testing more efficient and effective at finding defects
  14. 14. © 2013. Maveric Systems Limited 14 Business Context Project Objectives & Maveric Approach Value Adds & Business Impact ▸ A leading bank based in KSA (offering Consumer Banking, Private Banking and Investment Management services) wanted to migrate from a legacy transaction processing system to a core banking system in order to improve Time to Market for new product launch and reduce the total cost of ownership Project Objectives ▸ Complete Requirements Analysis and Fit/Gap Analysis ▸ De-risk post implementation risks arising due to incorrect requirements implementation or missed requirements Maveric Approach - A phased approach to deliver: ▸ AS-IS Functionality Documentation ▸ Requirements Specifications Document with bi-directional traceability ▸ Detailed Functional Specifications for Gaps in Product features vis-à- vis requirements Value Adds ▸ ‘Domain Checklist’ used for each Line of Business to ensure requirements capture was comprehensive and accelerated ▸ Acceptance Criteria agreed upon and documented in Requirements Specification Document ▸ End-to-end Requirements Management services for implementation from requirements definition to testing Business Impact ▸ Improved requirements, reduced need for rework thereby saving cost and time ▸ Reduced opportunity for misinterpretation ▸ Testable and traceable requirements made testing more efficient and effective at finding defects Requirements Management
  15. 15. © 2013. Maveric Systems Limited 15 Program Health Check Business Context Project Objectives & Maveric Approach Value Adds & Business Impact ▸ A leading bank in the Middle East initiated a major IT Transformation program to streamline its various lines of business – Retail, Corporate and Wealth management with a program outlay exceeding USD 45 million Project Objectives ▸ Streamline business processes, improve productivity and accelerate time to market for new products launches ▸ Offer a wider range of products and best in class banking experience to its growing customer base through cross sell opportunities and a 360 degree customer view across portfolio Maveric Approach ▸ Developed Evaluation ▸ Tools & Strategy (questionnaire, random sampling ) ▸ Gathered all critical document s about the program from start to current status including; Program Plan, strategy documents, escalation history, risk assessment documents Value Adds ▸ Development of Pain Points/ Heat map chart across major breakdown areas ▸ Roles & Responsibilities matrix was redefined ▸ Review of Risk and criticality under various segments – Business, Implementation, Program and Operations ▸ Evaluation of Strategies for outcomes and continuity based on the current plan ▸ Implementation road map was provided with potential benefits Business Impact ▸ An Integrated War Room team was introduced for program recovery ▸ Program Steering Committee was reconstituted to monitor progress of implementation
  16. 16. © 2013. Maveric Systems Limited Thank You