PASI Support - Operational Update tracking and administration
As operational updates progress through the various states, the following activities are required to track the items through to deployment to Production. The Release Priority spreadsheet is to be updated on a regular basis to ensure the correct state and tags are noted and the features are reflected in the correct release/ iteration.
| State | Action | Assign To | tfs tag |
|---|---|---|---|
| New | Review feature, check for completeness, i.e. iteration path (should be PASI/Backlog) date raised, who raised the feature, attach any emails, screen shots, etc. | ||
| New | Add feature to the Scheduling Agenda and the details to the PASI Release Priority spreadsheet, stored in the Release Planning folder in SharePoint. If agreed in the scheduling meeting to go forward update tag, add to estimate agenda | To be Estimated | |
| Needs Business Review | Used when the item should not go forward, for any reason. Further work required before proceeding with the next step. | ||
| Ready for Review | Once the item is estimated, add to the Scheduling Agenda for the Business Reason and Impact to be reviewed. Present at the next Triage, if approved to submit, update tfs item | Project Manager | To be Submitted |
| Ready for Review | Once the item is submitted, update tfs tag | Waiting for Funding | |
| Ready for Requirements | Has been approved for funding. Now ready for scheduling to a release. When it is scheduled to a release, in the spreadsheet, move the row for that tfs item to the Release tab. | Assigned BA | Approved |
| In Requirements | A business analyst is assigned and gathers requirements. If needed, the business analyst will create a business level design document. | ||
| Ready for Assessment | Assigned BA adds tasks. The change will remain in this state until all impacts have been assessed, and addressed with impacted systems / stakeholders. | ||
| *Task | Perform Business Impact Assessment. The design is assessed for business impacts / alignment by the Student Records Business Support Team. | Business Support Team Lead | |
| *Task | Perform GOA System Impact Assessment. The completed business design is reviewed for system integration impacts, both with systems within the Government of Alberta, and external to the GOA. | Business Analyst | |
| *Task | Perform Vendor Impact Assessment. The design is assessed for any vendor SIS impacts. | SIS Vendor Lead | |
| Ready for Development | Assessment is completed, ready and assigned to a developer. Assigned BA adds tasks. | Assigned Developer | |
| *Task | System Test Case Creation. | Assigned BA | |
| *Task | System Test Case Review. | Assigned Developer | |
| *Task | BA Implementation Review. Impact document is prepared for the Service Now CHG ticket. | BA who Submits the Service Now CHG | |
| *Task | UAT Handoff Preparation. | Assigned BA | |
| *Task | UAT Skeleton Creation. | UAT Coordinator | |
| *Task | UAT Skeleton Review. | Assigned BA | |
| *Task | Wiki Updates. | Assigned BA | |
| In Development | The developer(s) are making the necessary changes to the system, and completing their unit testing of the solution. | ||
| Ready for Release | The developers have completed their activities and the changes are ready to be incorporated into a PASI release. Typically, the change will remain in this state until all/most of the changes for the release have been completed in order to ensure testing of the release addresses the release as a whole. There are times when a feature (isolated from the rest of the features) is made available for testing in advance in order to streamline the testing workload. | ||
| In QA | The quality assurance team is completing system testing and regression testing of the change/release. | QA Tester | |
| Ready for UAT | System testing of the change/release is complete and is ready for user acceptance testing. At this point, it is expected that the change is working as per the documented requirements. | ||
| In UAT | The changes/release are being User Acceptance Tested by designated users. This activity is coordinated by the UAT Coordinator within the Student Records Business Support Team. | UAT Coordinator | |
| Ready for Production | UAT of the changes/release is complete and signed-off by the business based on the UAT activities completed. | ||
| Done | The changes/release has been implemented into production and development activities are now complete. | ||
| Removed | This state indicates that the requested change is no longer required and has been removed from the backlog. |