Scrum project audit checklist

Below are some management best practices we use at Oxagile when implementing Scrum projects. Following these doesn't guarantee one wouldn't ever lose the game. Unexpected circumstances, we could not influence, happens daily. Still struggling them is a part of the job, as well as minimizing the impact. The chances to success however might arise, if some stuff would be considered beforehand.

Comments, questions - t.me/Roman_Kovalevsky

Customer:

• Vacation, sick leaves and day-offs notification rules are defined and approved with the customer.
• Any team's composition change is followed with customer's notification / approve.
• General team feedback is requested each 2 months.
• Budget report is sent once per agreed period.
• Budget forecast is sent once per month.
• Sprint report is sent at the end of sprint.
• Risks and dependencies are transparent, tracked and communicated to the customer.

Team:

• Personal meetings are held with every team member at least once per 2 months.
• All team members allocation is validated and confirm with Resource manager.

Development:

• Gitflow is set up, documented and used.
• There are enough environments for development and testing.
• If system is in production regular backups procedure is set up.
• Deployment guide is created and followed.
• Versions naming conventions is defined and followed.
• Each production release is accompanied by full system backup (DB, filesystem, etc) with ability to rollback fast.

Process:

• DOR and DOD are set up, documented and followed within Jira boards.
• Jira flow is set up and used.
• Jira dashboard is used.
• Meetings are held: Sprint planning, Daily Scrum, Grooming / Tech review, Sprint review, Retrospective.
• For big / long projects: Scrum of Scrums, Roadmap planning.
• All meetings are followed by meeting notes, action items are tracked.
• Release procedure is set up and documented.
• All releases are followed by meeting notes.
• UAT procedure is set up and documented.
• Stories are described in one manner, some agreed template is used.
• Standard Story Point is used.
• Task estimations does not exceed 12 hrs.
• Remaining estimate is updated for subtasks as soon as original estimate becomes outdated.
• For big / long projects: product documentation (requirements) is created and updated on a regular basis.

Planning:

• Delivery dates/milestones are defined, transparent, tracked and communicated to the customer. Scope of the deliveries is defined.
• There is enough prioritized stories for the next 2 sprints.
• Backlog stories are estimated in SP.
• Backlog cleaning is held at least once per month.