The automotive industry’s digital transformation has been incredibly dramatic, both on the road, with new cars packed with tech goodies, and on the factory floor, where the Internet of Things, robotics and artificial intelligence have been adding marked efficiencies to the way cars are produced.
On top of these more obvious developments, consumer trends have changed in that drivers are seeking new models of ownership. In fact, they may not seek ownership at all. Today’s drivers may take a bus to a train, then drive a rideshare vehicle 100 miles, drop off the vehicle and then take a metro in an urban area to their final destination. Automakers are finding the traditional model of simply building cars and shipping them to the dealer showroom has shifted as these consumer trends emerge.
All of this puts tremendous pressure on automakers and software shops to respond quickly to customer needs and services from competitive companies. Software shops need to use agile development techniques to meet these challenges. Here are three questions companies need to ask about how their software development groups can adapt to this new way of developing applications:
- What cultural shift is required? For years software shops at automakers operated much like the military, in a command and control, top-down model. Today, companies need to create flexible teams of workers from different disciplines who are involved in the software development from the start. For this to work, everyone must contribute and everyone has input into the final product. Former U.S. Naval Captain David Marquet has a famous presentation where he explains that, instead of simply instructing all the men on his submarine to blindly follow orders, he lets the sailors closest to the work make the decisions. The captain then only kept the final decision to fire a weapon at the top of the chain of command with him. These cultural changes earned his group high marks on inspections and he now runs a successful consulting business. Much can be learned from this approach in terms of getting all members of the team to contribute and not be afraid to make decisions. After all, the coders are the ones closest to the work.
- Is the organisation willing to change its organisational structure and procedures? In the past, software was developed in a step-by-step process and people from each group often didn’t have input into the new software until it was much too late. In an agile model, design, development, testing and operations are involved from the beginning and work out any concerns or issues before it gets to operations and everyone finds out that what was developed won’t work.
- What are the outcomes that organisations can realistically expect from agile development? By creating an agile development organisation, companies can stay flexible as requirements change while also improving time-to-market. Instead of rolling out complete products, software can be developed in smaller modules. This results in fewer bugs and modules that can be plugged in as the teams develop the products.
Companies often don’t know how to start to change their development organisations. They are too close to the operation and need a team of experienced consultant to get them to look at the organisation from a fresh angle. DXC has the experience with large global organisations to help you build development teams that can scale across your organisation, from the headquarters group to the most remote sites offshore.