Historical data is a key resource for judging the effectiveness of software process improvement methods and also for calibrating software estimation accuracy. In this article, Capers Jones compares Agile and Scrum with a sample of contemporary software development methods using several standard metrics.
The first part of this series discussed some of the benefits of automating your build and deployment processes. In this article, we will take a common example of a corporate web application for a fictional financial institution, and walk through fully automating their build process.
The software business has moved from ancillary to mission critical. This teams must start thinking about how to best integrate their delivery disciplines, creating a holistic integrated ALM approach. 2
If there's one thing developers are good at, it's automating things that used to be done manually. However, development teams often neglect the one audience that would benefit the most - themselves.
Last time we looked at Lean ALM from a high level perspective. This article Dave West builds on that by discussing how one can gradually introduce Lean ALM to established teams.
We examine what organizations can learn from Lean thinking in transforming ALM from an inflexible, expensive, dogmatic approach to one more able to reduce waste and deliver measurable value.
In Part 2 of our MSBuild series look at using the CI server Jenkins. We choose Jenkins because it supports a wide variety of projects, making it ideal for heterogeneous environments. 7
In this first of a two-part series, Mustafa Saeed Haji Ali looks at implementing a continuous integration system using MSBuild and Jenkins, an extendable continuous integration server. 8
InfoQ met with Microsoft's Jason Zander to discuss the arrival of Visual Studio 2012 and to take a look at what developers can expect from the product in the future.
Laila Lotfi explains how using automated error reporting results in greater customer trust, higher renewal rates, lower maintenance costs, and fewer opportunities for the competition. 2
Manually testing mobile apps slows down development, leaves a huge margin for error, and ultimately lowers the team’s ability to release quality software. Dan Bartow hopes to offer something better.