Goal for the sprint: detailed and cleaned Solution backlog in JIRA allocated to Sprints; all internal project systems are set.
Set up and prepare the Pfx application for starting the developmentsprepare production system to the Cutover and have a technical Go-Live plan in place.
Actions:
Making Make sure that all user stories are clearly defined with acceptance criteria and are allocated to Sprints
Revisit the sprint and project timeline after user story refinement
Provide support and work with customer on data interfaces
Plan and prepare Setup Sprint including stand ups and demo calls
Prepare a protocol about the agreed points during the foundation week that customer should confirm in written form
Make sure that the customer has provided the sample data that is sufficient for starting the configuration.
Make sure that the sample data has been sent to Pfx team (manual – small real data set).
Make sure that tables in Pfx for uploading the data are ready.
Make sure that customer has access to the QA partition and know how to access the application.
Assure that acceptance criteria for feature Sprint #1 are confirmed by Pfx and Customer and uploaded in JIRA.
Artifacts:
DEV partition (SA/CE should have credentials)
QA partition (SA/CE should have credentials)
Checklist for Preparation sprint:
JIRA is set up with tasks and time estimations (check the budget in SoW so estimations do not step over it).
Customer has access to JIRA and knows how to use the system.
You agree on the timeline for the project, and it is documented in communication with customer.
The sprints or timeframe for implementation is revised.
The user stories and data interfaces specified for being developed (including non-functional user stories).
The team resources are available during the sprints.
You scheduled a weekly call with the customer for the project updates.
You watched the budget used on this stage and manage it within performance corridor.
You keep Project Confluence page up to date
The Configuration sprint is planned and will kick off right after Preparation sprintUAT has finished and you have the acceptance protocol signed.
Prepare Cutover planning - the template will help.
Assure the resources availability on Pfx and customer side
Prepare an exact and comprehensive (list of logics, jobs, tables etc...) environment update plan for Production (based on experience with previous update of QA environment). In case our operations team need to do actions (e.g. set up a new instance, or copy an instance) please take the lead time they need for these actions into account - this can be up to one week.
Revision of the documented implementations
Training for super users
Artifacts:
Checklist for Cutover:
The Go/No Go Live meeting took place and the decision for solution sign off has been provided.
The solution has been signed off to be deployed in production. If not, plan additional sprint and estimate time/budget impact.
The cutover plan has been prepared and agreed by Pfx and Customer.
The PROD partition is prepared and customer has access to the partition.
The technical Go Live date is scheduled and resources are allocated.