Skip to main content

Gartner report: Microsoft takes the lead in the Application Lifecycle Management(ALM) space

According to a recent Garner report Microsoft takes the lead in the ALM space.

By virtue of its position in the market as a provider of key platforms and development tools, Microsoft acts as an overall thought leader in the ALM market. However, this breadth and a late start in the ALM market have caused its tools often to lag other products, although it is now introducing innovations. At this point, other than IBM, Microsoft offers the broadest set of ALM functionality in the market. The company tends to deliver new releases every 18 months, but generally needs to coordinate with key platform updates and initiatives. To make up for long development cycles, the product team uses the Microsoft Developer Network (MSDN) to deliver "Power Tools" and other early access software bits.

Microsoft has a broad customer base going from small or midsize businesses (SMBs) up to extremely large enterprises, and its largest sites have more than 10,000 users. Unlike all of the other tools in this Magic Quadrant, Microsoft's is the only one that tightly binds its versioning system to the rest of the ALM planning tool. The single product platform delivery may create functional overlaps with other tools already in your portfolio. Microsoft supports the Visual Studio product line in 13 languages (the second highest of the tools in this Magic Quadrant) and is pushing into cloud deployment for its Team Foundation Server (TFS).

Although Microsoft is one of the only vendors to cover all aspects of the SDLC, its greatest challenge has been support for non-Microsoft development. However, the company has made good strides with support for Eclipse and the ability to extend TFS with Java code. The greatest challenge comes in how to stitch together a mixed environment with developers on non-Microsoft platforms that may have a stack that includes other SCCMs and the steps required to weave this together. TFS is a strong system; however, if your organization doesn't use .NET or other Microsoft technologies, then this will not be your ALM product of choice. As deployment platforms shift to the cloud, this isn't just a Java and .NET issue, and Microsoft will need to continue to demonstrating a long-term commitment to support diverse platform user needs.

Microsoft's products support:

  • Requirements management
  • Project management
  • Quality management
  • Defect management
  • Build management
  • Release management
  • Lab management
  • Change management
  • Task management
  • Modeling

Figure 1.Magic Quadrant for Application Life Cycle Management

Source: Gartner (June 2012)

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...