Kirk J. Hargreaves

Management Consultant @Optimus SBR

Requirements Elicitation: Employing user stories, acceptance criteria, and process flows to ensure requirements documentation is gather in a clear, concise and atomic manner\\\\n\\\\nData Collection: Capturing the mandatory information during the small business loan application / origination process with respect to the consumer’s demographic identities\\\\n\\\\nRecordkeeping: Ensuring collected customer data is properly stored in the applicable repositories and shielded from the adjudicators during the underwriting process, curbing discriminatory judgments\\\\n\\\\nRegulatory Reporting: Correlating collected customer data to the expected coding as dictated by the regulatory filing instruction guide\\\\n\\\\nRegulatory Compliance: Ensure applicant–provided data is properly handled and procedural ‘firewalls’ are in place to shield the protected demographic information from loan adjudicators – enforcing the bank’s Risk Management model and enhancing data privacy\\\\n\\\\nFuture-State Process Mapping: Drawing comparisons between current process and target-state environments to ensure a seamless transition of data flow post implementation\\\\n\\\\nRequirements Socialization: Presenting both business and technology requirements to senior leadership and maintaining evidence\\\\n\\\\nTraceability: End-to-end referencing of precedents/dependencies throughout the requirements documentation catalogue, ensuring alignment between stakeholder needs, project objectives, and target deliverables\\\\n\\\\nData Requirements: Capturing data points, managing system data elements and converting the information into a coded dataset as expected by the regulatory body upon annual filing\\\\n\\\\nDevelopment and Rollout: Act as a supporting role during joint requirements sessions with solutions architects, business systems analysts and quality assurance thought-out the lifecycle of the project\\\\n \\\\n\\\\n \\\\n \\\\n\\\\n \\\\n