We’ve begun work on the update to the Magic Quadrant for ALM. We are subtly shifting our terminology for the market from Application Lifecycle Management to Application Development Lifecycle Management. We feel this is a more accurate depiction of what the tools in this space are focused on.
Participants this year all have at least 200 active customer installations, $5M per year in revenue. These vendors are also actively brought up by our clients on calls and thus have created some recognition at the enterprise level. There are many other products in the market that are effective for specific roles or at the project level, our goal is to look at tools that are effective at scale and most of the vendors being covered have installations with 1000 or more users.
We will be using the same criteria as the prior edition of the MQ. We will however, have an additional use case for product development which supports the 2011 Maverick research by Matt Hotle on the shift from Projects to Products.
We will also update several surrounding documents and are working on pieces around the market sub-segments.
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
The Gartner Top 10 Strategic Technology Trends for 2016
Strategic technology trends are rapidly changing disruptive trends with significant potential for enterprise impact over the next three...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.