Timeline and Schedule
Overview
This document outlines the timeline and schedule for the Slate to Banner integration testing project. Each phase is broken down into tasks with start and end dates to ensure smooth execution and timely completion.
Project Timeline
Phase | Start Date | End Date |
|---|---|---|
Front-End User Testing | January 6 | January 8 |
Admissions Process Testing | January 9 | January 14 |
Data Mapping Validation | January 15 | January 24 |
Detailed Schedule
1. Front-End User Testing
Objective: Validate the functionality and usability of the application interface.
Key Tasks
Develop Testing Personas: January 6 – January 7
Prepare Test Cases and Feedback Forms: January 7 – January 8
Assign Testers to Personas: January 8
Execute Testing: January 8 – January 8
Analyze Feedback and Report Results: January 9
2. Admissions Process Testing
Objective: Ensure workflows, checklist assignments, and notifications function correctly.
Key Tasks
Design Test Workflows: January 9 – January 10
Review Checklist Rules: January 10 – January 11
Conduct System Email Testing: January 12
Execute End-to-End Workflow Tests: January 13
Finalize Admissions Process Feedback: January 14
3. Data Mapping Validation
Objective: Verify data accuracy between Slate and Banner.
Key Tasks
Review Data Mapping Documents: January 15 – January 17
Test Data Imports and Exports: January 18 – January 20
Validate Field Mappings: January 21 – January 23
Resolve Integration Issues: January 24
Deliver Final Report: January 24
Milestones
Key Milestones
Milestone | Date |
|---|---|
Personas and Test Cases Finalized | January 8 |
Front-End Testing Completed | January 8 |
Admissions Testing Completed | January 14 |
Data Mapping Validation Completed | January 24 |
Final Testing Report Delivered | January 24 |
Dependencies and Risks
Dependencies
Access to Slate Staging Environment: Required by January 8.
Complete Data Mapping Documents: Finalized by January 15.
Availability of Testers: Assigned by January 8.
Risks
Risk: Delayed access to the staging environment.
Mitigation: Coordinate with IT early to ensure readiness.Risk: Staff unavailability during testing phases.
Mitigation: Identify backup testers and prioritize critical workflows.
Key Contacts
Role | Name | Contact Info |
|---|---|---|
Test Lead | Gabriela Lozanova | |
IT Support | James Moran |