Metrics /OKR for the IT operations team working in Agile

Last post 11:15 am May 5, 2020 by Xander Ladage

1 reply

05:49 am May 5, 2020

Hi All,

Would like to know if any one is using OKR for IT support.

If so, could you please share some of the OKR that fits for Incident (l2 and l3 support) and CR and PBI .

Secondly, Would like to know what other metrics we can use apart from MTTR and Cycle time for faster time to market and to improve NPS.

Thanks,

Kavitha K

Xander Ladage

11:15 am May 5, 2020

I am not really clear on your question and do not explicitly use OKR, but OKR and Scrum could be a close fit. Objectives in OKR can be seens as Sprint Goals, and the measurable Key results can be seens as PBI's. On a larger scale, Objectives can be "the product", and the Key Resuts are the sprint Increments, which are in turn measurable. So designing your Scrum implementation around this, you can make this fit yourself.

If you want to learn more about metrics, I can encourage you to read

Actionable Agile Metrics for Predictability (An Introduction) by Daniel Vacanti

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.