The Scrum health check is a simple tool to assess your current implementation of Scrum. This simple check can be done on a sprintly basis, especially for organisations undergoing transformation to Agile. Just answer the following questions under three keys areas, Scrum Roles, Scrum Ceremonies and Scrum Artefacts. It might be interesting to have the team go through this check at a retrospective.
Within the Scrum Framework three roles are defined: The Scrum Team, Scrum Master, and Scrum Product Owner. Each of these roles has a defined set of responsibilities and only if they fulfil these responsibilities, closely interact and work together they can finish a project successfully.
Scrum has four ceremonies that bring structure to each sprint: Sprint planning: A team planning meeting that determines what to complete in the coming sprint. Daily stand-up: Also known as a daily scrum, a 15-minute mini-meeting for the software team to sync. Sprint demo: A sharing meeting where the team shows what they’ve shipped in that sprint. Sprint retrospective
Scrum’s artifacts represent work or value in various ways that are useful in providing transparency and opportunities for inspection and adaptation. Artifacts defined by Scrum are specifically designed to maximize transparency of key information needed to ensure Scrum Teams are successful in delivering a “Done” Increment
Scrum Maturity Assessment
You are almost there. Our Agile experts will analyse your response and a detailed report will be sent to you soon. Please provide your contact details so that heathcheck report can be email. If you want to keep an eye on how your team is maturing, please subscribe to our services where you can track teams progress
Are all the Team members working full time for the Project?
Does the Team have the required skillset?
Are all the Team members co-located?
Are the Team motivated to work using Agile principles?
Have you engaged with an Agile coach?
Is the ScrumMaster full time on the Team?
Has the ScrumMaster been on any Scrum Master training?
Has the ScrumMaster performed the role on a previous project?
Does ScrumMaster remove impediments immediately?
Does ScrumMaster assign tasks to the team?
Is the Product Owner available full time or co-located?
Has the Product Owner attended any Product Owner training?
Does the Product Owner refrain from asking to add items to the Sprint (once Sprint has started)?
Is the Product Owner empowered to make decisions?
Is the Product Owner engaging with all the stakeholders?
Are the planning sessions time-boxed?
Is sprint planning meeting attended by the product owner, ScrumMaster and the entire Scrum team?
Do the team know what is intended to included in the next Sprint/release?
Are the stories in the Product Backlog sized?
Are the stories in the Product Backlog sized by the people who are going to do the work (or their representatives)?
Does everyone in the team attends daily standup?
Does scrum team give their update to Scrum Master or Product Owner
Does team highlight blockers or impediments during daily standups?
Does daily standup lasts less than 15 min?
Does team discuss their technical issue during daily standups?
Sprint Review & Retrospective
Are you having a review meeting at the end of every Sprint?
Are you having a Retrospective meeting every Sprint?
Do you take actions on issues identified in Sprint Retrospective meetings?
Do you only review stories which meet the Done definition during Review meetings?
Do all the Team members contribute to the Retrospective?
Do you have a Product Backlog?
Do the User Stories include acceptance criteria?
Is the Product Backlog continuously refined?
Is the Product Backlog continuously priortised?
Is the Product Backlog fully sized?
Does Product Owner clarifies the details of the product backlog items and their respective acceptance criteria?
Does team commits to user stories based on team velocity or sprint capacity?
Does Scrum Team understand the benefit of single tasking?
Does Scrum Team break user stories into tasks and estimate them in hours?
Does Sprint backlog include refinements of the Product backlog for future sprints?
Is Scrum board accessible to the whole Team?
Is Scrum board updated daily?
Is Sprint burndown up to-date?
Is the burndown chart visible to the whole Team?
Do you know your Team Velocity?
Provide your details
Company and/or Team Name
Any data collected through this website will be used for the purpose of improving our agile implementation services. Personal details will not be published or shared outside without respondent's express permission, in accordance with the principles of the Data Protection Act 1998. Are you content for Capri Consulting to contact you again in relation to improving our Agile Implementation related services?
Some required Fields are empty Please check the highlighted fields.
ITIL®, PRINCE2®, PRINCE2 Agile®, MSP®, M_o_R®, P3O®, MoP®, MoV® & RESILIA™ are registered trade marks of AXELOS Limited, used under permission of AXELOS Limited. All rights reserved.
The Swirl logo™ is a trade mark of AXELOS Limited, used under permission of AXELOS Limited. All rights reserved.