Another increment was just released! Up until now, you could play with only one predefined Product and one predefined Team. That would cover only tiny software shops. Now, with this release, a podium is set for larger organizations that are creating many products and have more teams working on those products.

The groundwork for creating an aggregate, holistic, view on how the teams, products, and the whole organization is making progress is now well underway. Linking users to teams is in the pipeline.

Three new metrics are also available in the Time to Market Key-Value Area: Lead Time, Cycle Time, and Release Frequency.

Lead Time

Lead Time measures the product’s teams time to deliver validated requirements to customers.

Cycle Time

Cycle time is the elapsed time from the moment a Product Backlog Item (PBI) is started until the work item is finished. Cycle time represents the elapsed time from the moment the team begins developing a vertical slice of functionality until that slice meets the Definition of Done and Acceptance Criteria.

Release Frequency

Organizations that have adopted agile software development are seeing much higher quantities of releases. With the increasing popularity of agile development, a new approach to software releases known as Continuous delivery is starting to influence how software transitions from development to a release.

With these three new metrics, the Time to Market sub-dashboard looks like the image below, but with the introduction of the goals the sub-dashboard will not be the same for every organization as teams will be choosing their set of metrics. The sub-dashboard will show a union, an aggregate across all teams and products.

Time to Market sub-dashboard

Agile Tools will have an educational value by having a description of each metric. Later on, the relationships between them will also promote the usage of a balanced set of them.

Goals

We will focus now on one major feature, and that is – setting goals!

The whole point of measuring is to get better at what you are doing.

One goal per team, one goal per product, and one goal per organization. Each of them – per quarter.

Each team will be able to select their metrics, and the importance of this can not be stressed enough! No command-and-control paradigm here where managers select measures for their subordinates. Also, a safe environment is a must.

The metrics are here to bring the attention of a team to start discussing possible techniques for improvement.

Setting goals and utilizing proper measurement techniques is the How part of the Agile journey your organization is or will be on.