At our Customer Day in the UK I was approached by a number of people expressing a desire for an alternative to the “rip & replace” ALM generation. Like many organizations, they have existing investments in various application development and lifecycle tools, and have been struggling to get them all to work together for quite some time.
For much of them, the driver is not simply the replacement of one tool with another, but the increasing need to accommodate modern development practices, to more efficiently leverage globally distributed teams, and to simplify complex processes and technologies across the application development lifecycle, while leveraging some of their existing investments.
Then last week at a Customer Advisory Board meeting I heard, on multiple occasions, an organization’s desire to seek an alternative practitioner tool – requirements management or quality assurance tool, while maintaining an orchestrated product development process that enables rather than penalizes an evolution of individual practitioner tools.
And in terms of visibility, customers are seeing the value in an orchestrated ALM dashboard that can capture data from one or more practitioner tools, displaying both data and process KPI metrics.
I sense an increasing realization by our customers and prospects that ALM is becoming an instance of the practice of business process management, through which software delivery is automated through common workflows and practitioner tools -implementing methods, activities and change management in an orchestrated flow of software development and delivery.
That is what we’ve been focused on here at Serena, of course. If you’ll forgive me for pointing to some marketing material, we’ve encapsulated our view in the following presentation. Let me know what you think.