SOFTWARE DEVELOPMENT | devops
In a digital transformation context
Customer Experience, Business Models, Operational Processes, all need the support of a modern software architecture. In Agile Systems GmbH we work with the Java-based Spring Framework. This helps us support our clients in delivering as quickly and reliably as possible according to the target product roadmap or story mapping.
agile software development
As described by Accenture Technologies in 2019, the “cloud is the execution platform“.
No other architecture can match the flexibility, resilience, scalability and agility as the cloud. And no other architecture can use this paradigm as the microservices architectures.
If your business is still developing so-called monolithic applications, you are losing out on the agile approach to software development.
Furthermore, if your company is creating apps from scratch, chances are it is also missing out on the API Economy.
With around 16,690 API freely available the next logical step in improving your team’s transformational capabilities is to reuse software that others have already programmed.
In his article “What’s driving APIs in Automotive“, Alan G. from IBM explains that “By 2020, 90% of cars are expected to feature built-in connectivity, up from just 10% today with an estimated 210 million connected cars hitting the road over the next few years.” This is only possible, of course, via APIs.
More specific to your digitalization project:
- Are there any APIs that are relevant to your project, which you could use immediately?
- What API architecture and strategy is currently available at your company?
- Can you integrate your company’s architecture, strategy and APIs into your current project?
By answering these basic questions, you will start your digital transformation journey from a much higher vantage point.
But yes, sometimes your team has to program. To remain agile, you need to focus on doing it as fast and as error-free as possible – in, you guessed it – an agile fashion.
Should you wait at the end of the sprint to package your code base into a deliverable product? Or should you deliver your product as fast as your Devs finish testing them?
This is a business decision as not all the clients need to see all the improvements all the time. Sometimes due to marketing planning (or due to Service Management considerations) your agile team needs to wait not only at the end of the sprint, but even it has to wait until the planned release date.
Whatever your strategy might be, the tools for a rapid digital transformation are there for you to use. Test Driven Development, Pair Programming, etc. You just need to understand how these mechanism fit your company and your specific project.
At Agile Systems, we use the Jenkins Framework to support our client’s DevOps:
Needless to say: The fastest you can deliver quality code to your company or customers, the better positioned you are to reach your digital transformation’s goals. With the immense availability of cloud solutions and methodologies, whether you wait or constantly update your code base, is up to you.