days
0
-35
-6
hours
-1
0
minutes
-1
-9
seconds
-3
-2
search
The road to SDM

Software Delivery Management: New Mindset

Anders Wallgren
software delivery
© Shutterstock / William Potter

SDM (Software Delivery Management) pulls together under one umbrella all the teams, tools, information sources and processes that relate to the delivery of software. This post by Anders Wallgren is part one in a series about SDM.

Innovation and mindset can take a while to evolve. It was the case with social media, wireless communications and the Internet of Things.

Software delivery is a good example of a concept that’s ready to stand on its own. As software becomes more integral to companies and to society at large, the way it’s designed, built and distributed have evolved. Today, the delivery process is far more sophisticated than it used to be, with more resources in the mix and more moving parts. After years of looking at aspects of the software delivery process as separate pieces, people are thinking differently about how all the pieces fit together.

That change in thinking is putting momentum behind the creation of a new IT category called Software Delivery Management (SDM). SDM pulls together under one umbrella all the teams, tools, information sources and processes that relate to the delivery of software. It aims to eliminate inefficiencies that have cropped up along the way and help create a more value-driven process, aligning organisations’ resources toward a common set of goals.

SEE ALSO: Turning binary thinking into better software development

The Road to SDM

For decades people divided IT into two basic camps – hardware and software. The categories were analysed largely in terms of output. Experts tracked how many computer boxes a big integrated manufacturer like IBM or Digital Equipment Corp made or how many software disks Microsoft spun off its production lines. Companies had their own methods of getting products out the door. Management techniques like TQM helped guide these processes, but little outside attention was paid to specific steps companies took along the way.

All of this changed as software itself started to evolve. The internet, smartphones and more versatile operating systems opened up the software market to everybody. Software producers – manufacturers and individual companies alike – spent a lot of cycles working to perfect aspects of the software delivery process. Companies created teams to research, scope, develop, engineer, produce, integrate, test, market and sell software apps. They applied a variety of tools to accomplish specific tasks and implemented processes like continuous integration and continuous delivery (CI/CD) to help streamline the engineering functions.

These advancements brought software to where it is today – companies are delivering apps quickly and updating them often. Operations teams are collaborating with developers, and organisations are doing their best to anticipate customer needs and institute quality control mechanisms. Software is achieving things never thought possible.

Stashed in siloes

But the delivery process isn’t perfect. Too often, pieces are separated from each other. Tools don’t work together. Teams don’t talk to each other enough. Information is stashed in silos that one side of the organisation isn’t sharing with another. Data that does get shared hasn’t been updated.
Disconnects like these cause ripple effects throughout the organisation. Projects get delayed. Apps get delivered with bugs and/or vulnerabilities. Developers find themselves overworked, restarting initiatives because they didn’t have the information they needed to do it right the first time. Executives get frustrated that teams aren’t delivering on their goals.

The disconnects can’t really be blamed on a particular team, tool or misplaced plan. They’re the fault of the overall process itself. A development team might be doing a great job with a top-quality tool and a well-thought-out plan. But if the product development group supplied developers with out-of-date information and a testing tool doesn’t integrate with a tracking database, the project will run into problems.

SEE ALSO: Software development trends: Top tools and methodologies

All processes connected

What’s needed is a new category that looks at software delivery from a holistic vantage point. Everything connects with everything. Software Delivery Management (SDM) provides those connections. It outlines a set of pillars to unify data, insights, processes and functions – aligning organisations around a common set of goals.

In upcoming blogs, we’ll look more closely at how SDM works, what kinds of benefits it can provide and how it can generate true business value for an organisation.

Author
Anders Wallgren
Anders Wallgren is vice president, technology strategy at CloudBees. Anders brings with him over 30 years of in-depth experience designing and building commercial software. Prior to joining CloudBees, Anders held executive positions at Electric Cloud, Aceva, Archistra and Impresse. Anders also held management positions at Macromedia (MACR), Common Ground Software and Verity (VRTY), where he played critical technical leadership roles in delivering award-winning technologies such as Macromedia’s Director and various Shockwave products.

Leave a Reply

avatar
400