Reval - What is Left on Reval MVP on the RHS
Post MVP: Connections (7 to 10 Iterations?)
Exception Queue (1 to 2 iterations)
Disconnected Filter (1 to 2 iterations)
Post MVP
To Do: GMC Refresh
To Do: Manually adding connection
Reporting
Send data to NDW
Permissions & Roles (2 to 3 Iterations)
Data Migration (2 to 3 Iterations)
To Do: Scripts / JFDI
To Do: Local Office Permissions (DBCs)
Monitoring & Logging Levels (1 to 2 Iterations)
All (1 Iterations)
To Do: Trigger
To Do: User management (keycloak)
Hidden (2 Iterations)
Connection
To Do:Secure
To Do: Concern
Connected Filter (1 to 2 iterations)
To Do: Action
To Do: View
To Do: Cognito
To Do: Trigger
Notifications
To Do: View
Sync
To Do: Remove
Tech Debt (1 to 2 Iterations)
To Do: View
Concerns (2 to 3 Iterations)
To Do: View disconnected (not data migration)
Recommendations (1 to 3 Iterations)
To Do: New Project / ETL?
GMC
To Do: Adding
Hide/Ignore
To Do: Integration Service
TCS
Error Handling (reporting to slack)
Implementation
To Do: Recommendation
Archiving
To Do: Missing dates
Stage and prod the same/What is deployed in both environment? Terraform?
To Do: View Document for individual trainee
To Do: Mapping
To Do: Trigger
Excpetions
To Do: GMC Status
To Do: Concerns
Sending too much
Un-Hide
GMC
Filtering
To Do: TCS Refresh
To Do: GMC Client
Searching
To Do: Save Concern
To Do: GMC Sync
To Do: Core
To Do: Import to staging
GMC
TCS
To Do: Searching
To Do: Connections
Success
To Do: Front End
TCS
To Do: Connection
Failure
Trigger
To Do: Recommendations
Caching/ES (2 to 4 Iterations)
Sync
In Progress Rabbit
In Progress SQS
Trigger
To Do: Connections
In progress: GMC
In Progress: TCS
To Do: History
In Progress: Reading from TCS
In Progress: Reading from GMC
To Do: Updating the same index from TCS and GMC
To Do: Manual trigger
To Do: Scheduled Triggering
Connections (2 to 3 Iterations)
All Filter
To Do: Add- Connected
To Do: Remove- Disconnected
To Do: Populate ES Index
To Do: View
Logging level
Control autogenerated logging
TIS common upload
Possibility of more bugs
To Do: Possibility of more bugs
To Do: Review and Implement confluence page permissions and Roles
Testing on stage
Check in both environments what has been terraformed
Assumptions
Assumption#1 - current team of 3 throughout
Assumption#2 - rest of the team will not be in a position to help out for the next 12 months
Assumption#3 - team of 3 will either not realistically be able to work on multiple elements in parallel, or if they are, that this will result in each element needing to take longer overall (negating the time estimate benefits of working on things in parallel). Splitting up and working on different sections in parallel vs tackling sections as a team (of 3 plus DevOps) consecutively makes current estimations quite difficult.
Assumption#4 - the business will continue to insist on a relatively high level of fidelity of the MVP proposed
Assumption#5 - the business will not agree to reduce the scope of the MVP
Assumption#6 - the business will not allow us to release the currently defined "MVP" incrementally (eg, Recommendations first, then Concerns, then Connections, etc)