Hantering av värdeströmmar

Värdeflödeshantering (VSM) i programvaruleveranserna är en kritisk metod för att lyckas i dagens digitala landskap. Den systematiska metoden för att mäta och förbättra flödet hjälper organisationer att förkorta tiden till marknaden, öka genomströmningen och förbättra produktkvaliteten. Denna bloggkategori för VSM ger pedagogiska insikter, bästa praxis och råd från Planview och branschexperter om hur du kan ta itu med de begränsningar eller problem som du möter i livscykeln för leverans av mjukvara för att uppnå bättre affärsresultat.

CIOs – are you measuring the right DevOps data?

“When digital transformation is done right, it’s like a caterpillar turning into a butterfly. When done wrong, all you have is a really fast caterpillar.” – George Westerman, Principal Research Scientist with the MIT Sloan Initiative on the Digital Economy Has there been a more exciting yet challenging time to be a CIO? Bridging the...

How to minimize conflict in enterprise software delivery with value stream architecture

More features out the door, faster time to market, fewer defects, and shorter time to value: it’s widely accepted that you have to deliver better software products faster to gain that all important competitive edge. That’s why you’ve invested in DevOps, Agile, best-of-breed tools and specialist people, often to the tune of millions of dollars....

Are you drowning Jira and the rest of your software delivery stream?

“Any tool that has attempted to be ‘everything for everyone’ has failed miserably” – Dr. Mik Kersten, CEO and founder, Tasktop In the fable ‘The Man and The Wooden God’, the protagonist spends most of their life praying to a wooden idol for wealth and fortune to no avail. One day, in a fit of...

10 predictions and trends for enterprise software development and delivery in 2018

Predicting the future of enterprise software development and delivery can often feel like hammering Jell-O to a wall. The industry is a perpetually evolving beast, awash with nuance, relativity and disruption. Just when you think you’ve got your head around it all, new technology and ideas can gatecrash the party overnight. That said, we’ve dusted...

How to accommodate different processes in enterprise software delivery

“Nothing is permanent but change’ – Heraclitus In business, we all know if you’re standing still, you’re falling behind. We also know that asking people to change their ways is hard – especially in enterprise software delivery. Resistance from some of your best teams can be fierce, and the fallout can directly impact the quality...

The road to a unified automotive value stream

The phrase “software is eating the world” is ubiquitous across all industries, and the automotive sector is no different. Software is the main technology driving innovation in cars. Millions of lines of code underpin everything from our vehicle’s navigation systems and engine control to its power steering and airbag deployment. We’re basically driving mobile computers....

Fight Cultural Debt by Connecting Your Value Stream

“In a world where tools are a proxy for process, the disconnected worlds created by domain specific tools result in broken workflows, reduced visibility and obstructed collaboration.” The business world is often blissfully ignorant of how technology decisions can introduce ‘cultural debt’.  And when an organization takes on cultural debt unknowingly, the interest payments accumulate...

Every second counts – why you need Software Value Stream Integration today

“Each time you receive an email that describes a defect, or send one asking about a requirement, it costs a little bit of time and money, and introduces the opportunity for errors and omissions.” Connecting your best-of-breed tools for planning, building and delivering enterprise software is probably on your radar. Considering that nearly 50 percent of the...

How Software Development Metrics Can Improve Your Delivery Processes

Tasktalks is an engineering-focused podcast telling the stories of Tasktop’s engineering teams from internal practices to the day-to-day challenges they face. Imagine a world where there is only one way to develop software at scale. Imagine if everybody used the same tools, had the same team structure and processes, everything was done “by the book”....