Value stream management principles have helped organizations across the globe leverage lean strategies to optimize their software development processes. However, the benefits from effectively managing value streams are not limited to only software. Value streams exist all around us whether we realize it or not. The goal of this blog post is to help explain how value stream management works in the context of software delivery by applying VSM concepts to an activity we experience every day.
It’s difficult to manage your value streams effectively if you can’t see them, can’t comprehend them, or aren’t aware of them. What helps — value stream mapping, making work visible, implementing the Kanban method, and a value stream manager. In an organization, different people have different views of the value streams, and potentially conflicting improvement objectives, it is important to share one vision of these streams and align on improvement goals. In this post, we will focus on getting a shared understanding of the streams.
OKR is an approach that organizations of varying sizes use to measure the ongoing health of their processes and align efforts up and down the organizational hierarchy around important improvement opportunities. You might think OKR is a relatively new approach; however, it has been around for decades. The truth of the matter is that scaling Lean-Agile practices requires organizations to evolve the way progress is measured. So instead of focusing only on completion of projects, OKRs help organizations set goals in a trackable manner — tying your project goals to business objectives and measuring the results against the overall objective.
In ConnectALL’s Ultimate Guide to Lean Metrics in Value Stream Management, you’ll learn about the history of VSM and how IT leaders have adapted fundamental lean concepts from over 70 years ago to software delivery today. We’ll take you down a journey of why organizations have adopted multi-tooling strategies in their value streams and why business intelligence platforms are a must-have requirement. We’ll also explore common synchronization patterns between the world’s most popular and widely used application lifecycle management (ALM) and Agile planning tools. Most importantly, this guide is designed to prompt action within your organization.
ConnectALL has helped companies solve simple problems, from synchronizing bugs from Azure DevOps to Micro focus ALM, to much more complex digital transformation efforts involving mergers, acquisitions, and spin-offs of business units. With that, our professional services team has helped these companies visualize their tools, people, and processes across those software value streams – while providing actionable recommendations to improve both software delivery speed and quality. Although every organization is unique, we have recorded and documented a common scenario faced by organizations running ServiceNow, Micro Focus ALM, and Atlassian Jira that we will share in this blog post.
Originally published on SDTimes.com There are a few definitions of “value stream management” floating around out there. Most seem pretty good, but they are necessarily very broad and maybe vague. That’s because value stream management is a very broad concept. Given the hype around these 3 words, and how it’s often shortened to 2 words, there is a lot of confusion. Maybe it will help if we discuss what value stream management isn’t. So, let’s first look at the way Chris Condo of Forrester described it at the virtual VSM DevCon that took place in July: “A combination of people, process, and technology …
Since 1941, America has officially celebrated “the Fourth of July” – better known as Independence Day -with loud fireworks, jam-packed concerts, parades, family picnics, barbeques, and sparklers. Celebrating 4th of July is like apple pie in America. But did you know that long before 1941, Americans unofficially celebrated the 4th of July? More specifically, on July 2nd, 1776, the Continental Congress voted in favor of declaring independence from England. Only two days later, on July 4th, the delegates across each of the 13 colonies adopted the “Declaration of Independence” – famously drafted by Thomas Jefferson. Fast forward 244 years and …
A well-known failure mode for business process automation is to automate a broken process. The same goes for tooling up Value Stream Management (VSM).