CreditInfo (Barbados) - CIB Strategy: Phase 1

Credi-Check Modernization

The revamped Credi-Check platform will address existing functional issues and enhance user engagement by introducing features like consolidated profile management, debt tracking, and improved user authorization processes. The target audience includes CIB admins and subscribers requiring efficient credit information management.

 

Goals

Business Goals

  • Improve Usability: Enhance login and session management features to increase user satisfaction by 30%.

  • Streamline Data Management: Reduce data redundancy and improve the accuracy of reports by 40%.

  • Increase User Base: Attract 20% more businesses to the platform within the first year.

User Goals

  • Efficient navigation through credit reports and historical transaction data.

  • Seamless integration of new data management functionalities.

  • Enhanced security features to safeguard user credentials.

Non-Goals

  • Developing third-party integrations with external financial platforms.

  • Introducing new payment gateway systems.

 

 

User Stories

Personas:

  1. CIB Admin

    • As a CIB Admin, I want to add, edit, and manage user profiles easily, so that I can maintain up-to-date credit records efficiently.

  2. Subscriber

    • As a Subscriber, I want to generate comprehensive credit reports swiftly, so that I can make informed financial decisions.

 

 

Functional Requirements

Credit Reporting Portal (Priority: High)

  • Login Capability: Ensure secure and recoverable login features.

  • Logout Capability: Implement automatic session expiration after inactivity.

  • Search Capabilities: Allow detailed personal and business profile searches.

Inquiries Portal (Priority: Medium)

  • Subscriber to Subscriber: Add login and report generation capabilities.

  • Profile Details: Show comprehensive profile overviews with restricted subscriber information.

Error Handling and User Feedback (Priority: High)

  • Enhance error messages related to data retrieval and user inputs.

 

 

User Experience

Entry Point & First-Time User Experience

  • Users receive email instructions upon registration to set up accounts securely.

Core Experience

  • Step 1: User logs in using an email-enabled password setup.

    • Easy password reset on first login for enhanced security.

  • Step 2: Navigate to the credit reporting section for user-specific data retrieval.

    • Features error notifications and detailed search parameters.

Advanced Features & Edge Cases

  • Resolve broken features like the 'Run Collection Report' for accuracy.

 

 

Narrative

The new platform allows a CIB Admin, Laura, to manage credit data seamlessly. With improved search functionalities and user profile capabilities, she efficiently consolidates erroneous records and retrieves accurate financial assessments. Her organization sees a boost in credibility, leading to new partnerships and trust with clients.

 

 

Success Metrics

User-Centric Metrics

  • Reduce report generation errors by 50%.

  • Increase the number of logins by existing subscribers by 40%.

Business Metrics

  • Double the platform’s enrollment in the first quarter after the revamp.

  • Enhance customer retention rates by 30%.

Technical Metrics

  • Maintain uptime at 99.9%.

  • Errors in skip trace alerts are reduced by 60%.

 

 

Technical Considerations

Components

  • Implement robust APIs for search and reporting functionalities.

Integration Points

  • Maintain synchronization with existing admin systems without additional third-party tools.

Data Storage & Privacy

  • Secure all data compliant with legislative requirements, focusing on user permission levels.

Code Availability & Maintainability

  • Language & Tools Selection:

    • Strategy: Opt for widely-adopted programming languages and frameworks with abundant community and vendor support (e.g., Python, JavaScript frameworks).

    • Benefits: Leverage existing resources and expertise, reducing future learning curves and ensuring long-term support.

  • Version Control:

    • Strategy: Utilize a distributed version control system like Git with a robust branching strategy.

    • Benefits: Enables collaborative development, easy rollback, code review, and history maintenance.

  • Code Documentation & Commenting:

    • Strategy: Implement thorough in-line commenting and maintain an up-to-date documentation repository alongside code changes.

    • Benefits: Enhances understanding for current and future developers, facilitates onboarding.

  • Code Review Process:

    • Strategy: Establish a code review protocol that includes automated testing and peer review before merge.

    • Benefits: Ensures code quality, identifies potential issues early, and maintains code consistency.

  • Deployment & Development Environment:

    • Strategy: Use containerization (e.g., Docker) to create consistent development and deployment environments.

    • Benefits: Simplifies deployment, isolates dependencies, and enhances environment reproducibility.

  • Refactoring & Technical Debt Management:

    • Strategy: Regularly schedule refactoring sessions and track technical debt explicitly.

    • Benefits: Prevents codebase deterioration, improves performance, and aligns with evolving best practices.

  • Automated Testing & CI/CD:

    • Strategy: Implement Continuous Integration/Continuous Deployment pipelines with a focus on automated unit and integration tests.

    • Benefits: Ensures robust software with fewer bugs, accelerates release cycle, and reduces manual intervention.

  • End-of-Life Management:

    • Strategy: Regularly update third-party libraries and frameworks and plan for end-of-life replacements.

    • Benefits: Mitigates security risks, maintains compatibility, and ensures ongoing support.

 

 

Milestones & Sequencing

Project Estimate

  • TBD involves thorough testing and debugging phases.

Team Size & Composition

  • Medium Team: 3–5 total people including roles like Product Manager, Front-end Developer, and QA Tester.

Part 1: Initial Audit & Planning 

  • Key Deliverables: Identify broken features, plan revamp strategy.

  • Dependencies: Current system's operational review.

Part 2: Development & Testing

  • Key Deliverables: Implement enhancements, testing.

  • Dependencies: User testing and feedback loop.