{"id":21572,"date":"2017-02-14T07:27:30","date_gmt":"2017-02-14T13:27:30","guid":{"rendered":"https:\/\/blog.planview.com\/value-stream-integration\/"},"modified":"2017-02-14T07:27:30","modified_gmt":"2017-02-14T13:27:30","slug":"value-stream-integration","status":"publish","type":"post","link":"https:\/\/blog.planview.com\/value-stream-integration\/","title":{"rendered":"Value Stream Integration"},"content":{"rendered":"
<\/figure>\n

Every business is now a digital business – if you’re not then you’re vulnerable to disruption. Traditional business models, infrastructures and operations are in a flux as software continues to usurp and transform the status quo. Look at Airbnb and hotels, Uber and taxis, Netflix and films, Amazon and retail…you get the picture. The message is clear: keep up or be left behind. Or to paraphrase organizational theorist Geoffrey Moore: “Innovate or die!”.<\/p>\n

Most CIOs are acutely aware of this state-of-play and are under pressure to optimize their organization’s software delivery process. Many are investing in new staff, tools and processes to drive Agile and DevOps initiatives and are often encouraged (and given false hope) by initial success – especially at a local level. Then they try to scale and become stuck. There’s too many tools, people and disciplines. The toolchain is fragmented and their transformations are failing.<\/p>\n

Why does this happen? The problem is that best-of-breed Agile and DevOps tools don’t work together, creating friction in the way stakeholders interact. This causes manual work that increases cost, reduces velocity, frustrates team members, all the while making it difficult for management to have the visibility and traceability that they so desperately need to make key business-decisions.<\/p>\n

Organizations continually adopt new tools to improve the individual disciplines they serve – test automation, requirements management, agile planning, DevOps and the like. By using these tools, stakeholders create work specifically for collaborating with their colleagues. But that collaboration is compromised precisely because each of these disciplines are using different, unintegrated tools.<\/p>\n

\"Fragmented<\/p>\n

Furthermore, managers want to see metrics and dashboards for real-time status reports so they optimize a process and\/or ensure compliance. However, with a fragmented toolchain it is nearly impossible to obtain a holistic view. And everyone knows that the only way to improve a process is to look at it holistically.<\/p>\n

What can be done? The key is to integrate the value stream.<\/p>\n

\n

Value Stream: Sequence of activities required to design, produce, and provide a specific good or service, and along which information, materials, and worth flows – Business Dictionary[1]<\/a> <\/strong><\/em><\/p>\n<\/blockquote>\n

When we talk about an integrated value stream in software delivery, we mean bringing together the tools across the software development lifecycle to radically improve team effectiveness and project visibility which allows you to:<\/p>\n