...
Goal for the sprint:
deliver, test, demo defined increment of function; customer has tested and accepted the results.
Actions:
Follow the development of the assigned to sprint user stories
Track the progress in Sprint board
Make sure team is logging time on daily basis
Check with customer the progress at standups
Prepare a Demo for the developed functionality during the week 3
Document all bugs and changes in JIRA on base of customer feedback
Make sure customer is testing during the agreed period of time and provide feedback in JIRA
Schedule a retrospective
Plan next Sprint together with customer
Assign change requests/bugs to the upcoming sprints and access the impact on timeline/budget
Checklist for Feature sprints:
All tasks are tracked in JIRA.
Sprints are running as planned.
Customer performs testing, provides feedback and sings off the results of the sprint in written form.
Weekly status reports are prepared.
Project is running within defined time and budget.
The testing time and bugfixing time is included into the planning.
The buffer between sprints is planned.
All defects and changes are tracked in JIRA.
You team is booking time on weekly basis.
The customer confirm acceptance in written form during after each sprint.
Your engineering team creates a brief release notes after each sprint and add those in public Confluence.
A good Project Manager:
Has backlog with user stories, tasks and estimations for all tasks.
Has planned sprints with column „ready for revision“
Submits weekly status reports.
Each part of implementation is documented in JIRA.
Customer is doing testing and leaves comments in JIRA.
Keeps the budget in budget tool on the paper and aware how it is used.
Knows about all parts of the project.
Communicates the risks before hand and mitigates them.
Collaborates with the CSM on any issues that arises.
Submits timesheets at the end of the month.
Makes sure that the time is booked in Tempo according to the estimations and planning.