DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Zones

Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Generative AI has transformed nearly every industry. How can you leverage GenAI to improve your productivity and efficiency?

SBOMs are essential to circumventing software supply chain attacks, and they provide visibility into various software components.

Related

  • What They Don’t Teach You About Starting Your First IT Job
  • Improve Your Agile Processes With Artificial Intelligence
  • Feature Owner: The Key to Improving Team Agility and Employee Development
  • Agile Practices That Developers Can Use to Create Better Projects

Trending

  • Replacing Legacy Systems With Data Streaming: The Strangler Fig Approach
  • Modernize Your IAM Into Identity Fabric Powered by Connectors
  • Building V1 Gen-AI Products at Scale: Technical Product Patterns That Work
  • Jakarta EE 11 and the Road Ahead With Jakarta EE 12
  1. DZone
  2. Culture and Methodologies
  3. Agile
  4. Importance of KVI in Agile Projects

Importance of KVI in Agile Projects

If you feel like your Key Performance Indicators are no longer cutting it, read on to learn about a new system of estimating value.

By 
Arijit Sarbagna user avatar
Arijit Sarbagna
·
Aug. 10, 17 · Opinion
Likes (2)
Comment
Save
Tweet
Share
11.6K Views

Join the DZone community and get the full member experience.

Join For Free

Image title

More often than not you must have been through a phase in your Agile Software delivery life cycle, where people have questioned you about the KPI (Key Performance Indicators) and how you managed them. Well, they still exist - just the way "Scrum-Butt" also exists. Though the world has moved ahead, we realized that the questions posed by businesses are still the same (e.g. how to engage more customers, how to create better customer satisfaction, which segment needs to be pushed, how to deliver more with less etc. etc.) and hence we should still use the same age old KPIs. Dreadful - isn't it?So, it is high time that we wake up and realize that "Performance Indicators" don't necessarily deliver "Value." For example, if a team is delivering high (or huge) lines of codes, it doesn't necessarily mean they are delivering loads of business functionalities. From a different angle, if a team is not communicating the results of measurement and analysis activities to all relevant stakeholders, it doesn't necessarily mean they are not delivering value (perhaps they are just aiming at delivering a working piece of software)! And that is why the focus should shift to "Key Value Indicators," i.e. KVI.

What Is KVI?

As the name indicates, it stands for "Key Value Indicators." What does it mean actually? It simply refers to the parameters which, if measured, show how we are delivering better value our customers. For example, instead of measuring LoC (which doesn't add any value to the customer) within the KPI system, use "Build Stability" as a KVI (because a stable build indicates readiness for deployment, i.e. faster TTM). So, let's take an Agile Software Delivery Project for example. If we are working on this project, instead of measuring only the standard set of parameters like Burndown, Acceptance Ratio, etc., consider a holistic view and include items like:

  1. Release Burn Down Chart

  2. Sprint Burn Down Chart/Velocity

  3. User Story Acceptance Ratio (i.e. committed SP vs accepted SP)

  4. Build Quality Index

  5. Release Frequency

  6. Agile Practice Maturity

  7. Innovation Quotient

So What Exactly Changed?

If you noticed, we are changing the name to shift the focus from using a measure to understand what is happening (i.e. KPI), to a direction of identifying a means of improving value creation (i.e. KVI) for our customers. This is, essentially, the whole purpose of Agile Software Delivery - isn't it?

KVI Key Value Areas Objective
Release Burn Down Forecast and Planning Understand how to improve timeline.
Sprint Burn Down Forecast and Planning Understand how to improve timeline.
Story Acceptance Ratio Forecast and Planning;
Collaboration
How to improve communication and improve quality.
Build Quality TTM (Time to Market) Ensure stable build is available for quick release.
Release Frequency TTM (Time to Market)
Quicker Feedback Loop
Ensure integrated product could be released in quick intervals and customer feedback could be collected.


KPIs tend to get used in a Command and Control environment. I have seen many instances where it is not the case and they have my absolute respect! But otherwise, we should look for KVIs, which are more meaningful to our customers. 

At the end of the day, winners don't do different things,. they do things differently! 

agile Sprint (software development)

Opinions expressed by DZone contributors are their own.

Related

  • What They Don’t Teach You About Starting Your First IT Job
  • Improve Your Agile Processes With Artificial Intelligence
  • Feature Owner: The Key to Improving Team Agility and Employee Development
  • Agile Practices That Developers Can Use to Create Better Projects

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

ABOUT US

  • About DZone
  • Support and feedback
  • Community research
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • [email protected]

Let's be friends: