Share on facebook
Share on twitter
Share on linkedin
project management
Value Stream Management
Issue management tools like Jira usually now provide an integrated way to manage requirements, tasks, and defects. Typically they also provide search functionality, agile boards, customisable workflows, and sometimes, time-tracking. However, they are increasingly being used as a tool to measure the value stream management of a software development organisation.
 

Value Stream Mapping

Value stream management is not a new technique, it has its origins in value stream mapping, like many process improvement techniques. It is a recognised part of the Six Sigma technique. In essence it is a lean-based approach to mapping the value added by different parts of the software development process, and to identify waste, and then manage it.

As issue management tools track the states of different types of work, they therefore provide a proxy for measuring where work is within a larger process. 

Value stream map, metrics & dashboards

One example metric is the time that issues spend on average in each state. When this is compared between components, products and teams, it can provide useful insight to where inefficiencies are rooted. You can add various “time in state” charts to your various dashboards to see how long different tests, issues or other types of tracked ticket are spending in different statuses. You can also see how this changes over time.

Perhaps you would need to include other key performance indicators KPIs, let us know how we can help your business leaders, at neuro we are looking to the future by combining multiple data sets from across the toolchain with multiple machine learning models to provide far-reaching insights into the technology supply chain.

If you are wondering why you would want to do this – a key principle of lean is “just-in-time” working. The less time things spend between elaboration and business feedback in production – the more efficient you are!

Zero-waste software development - an engine for growth
The economics of software development have fundamentally changed. Cheap credit is less available, resource costs are increasing and skilled technology professionals are in short supply. At a time when demand for technology has never been greater, companies and their senior leadership are increasingly challenged in their technology delivery and digital transformations. This short paper focuses on how organisations can achieve cost and value transparency, reduce waste and close the gap between high-performing competitors by increasing agility and resilience while driving down the cost of building and delivering software – zero-waste software development.
Combining Automation with a Human Touch: How to Harness Value Stream Management to Assess Technology Vendors
In today's digital age, companies heavily rely on technology vendors to deliver cutting-edge solutions and support their operations. Ensuring the performance and value delivery of these vendors is crucial to maintaining a competitive edge and providing exceptional customer experiences. One easy and powerful way to do this is through the application of Value Stream Management (VSM). This article explores how companies can leverage VSM to measure vendor performance and drive continuous improvement to reduce cost and waste.
How neuro makes commit risk predictions
Every developer has heard of Git. Originally authored by Linus Torvalds in 2005 to track the development of the Linux kernel, Git has become the go to version control system for 99.99% of development teams on the planet. With such widespread adoption, it seems obvious that everyone from heads of development to testing and quality specialists would be making the most out of the mountains of git data generated during the software development cycle. This, however, isn’t the case.
Value Stream Management
Issue management tools like Jira usually now provide an integrated way to manage requirements, tasks, and defects. Typically they also provide search functionality, agile boards, customisable workflows, and sometimes, time-tracking. However, they are increasingly being used as a tool to measure the value stream management of a software development organisation....
Zephyr Dashboards on an Agile Project.
WHY IS A ZEPHYR DASHBOARD USEFUL ON AN AGILE PROJECT? Before explaining the importance of a Zephyr dashboard on an agile project, we must know what the requirements are for the perfect agile environment. The most important concepts that define today’s software world are the speed of keeping up with...
Dragonfly Quality Engineering Toolchain Report 2021
This survey of software practitioners identifies some key trends in the quality engineering toolchain.

Supporting content

data driven testing

Zero-waste software development – an engine for growth

The economics of software development have fundamentally changed. Cheap credit is less available, resource costs are increasing and skilled technology professionals are in short supply. At a time when demand for technology has never been greater, companies and their senior leadership are increasingly challenged in their technology delivery and digital transformations. This short paper focuses on how organisations can achieve cost and value transparency, reduce waste and close the gap between high-performing competitors by increasing agility and resilience while driving down the cost of building and delivering software – zero-waste software development.
Broken chain

Combining Automation with a Human Touch: How to Harness Value Stream Management to Assess Technology Vendors

In today's digital age, companies heavily rely on technology vendors to deliver cutting-edge solutions and support their operations. Ensuring the performance and value delivery of these vendors is crucial to maintaining a competitive edge and providing exceptional customer experiences. One easy and powerful way to do this is through the application of Value Stream Management (VSM). This article explores how companies can leverage VSM to measure vendor performance and drive continuous improvement to reduce cost and waste.

How neuro makes commit risk predictions

Every developer has heard of Git. Originally authored by Linus Torvalds in 2005 to track the development of the Linux kernel, Git has become the go to version control system for 99.99% of development teams on the planet. With such widespread adoption, it seems obvious that everyone from heads of development to testing and quality specialists would be making the most out of the mountains of git data generated during the software development cycle. This, however, isn’t the case.