InfoQ Homepage ALM Content on InfoQ
-
Towards Agile CMMI Level 3: Requirement Development and Verification
This article shows how to do requirement development in agile environments, covering concepts and offering examples of how an agile team could run a CMMI for Development SCAMPI to become appraised at a targeted level 3 for the areas of requirements development and verification.
-
Interview and Book Review of The Technical and Social History of Software Engineering
Capers Jones wrote the book The Technical and Social History of Software Engineering in which he provides an overview of the evolution of information technology and software development. InfoQ interviewed Capers about advancements and events in software engineering and the effects that they have had on our society.
-
DevOps @ large investment bank
This article is part of the “DevOps War Stories” series. In each issue we hear what DevOps brings to a different organisation, we learn what worked and what didn’t, and chart the challenges faced during adoption. This time a very personal story on introducing a DevOps mindset at a large bank. In particular how the automation of configuration and release management processes enabled collaboration.
-
Implementing Software Lifecycle Integration (Part Two)
In this article we focus on the practical steps a software delivery professional should take in implementing an end-to-end software delivery process. The three basic steps are prioritizing needs, team building, and measuring results.
-
Book Review: Vagrant up and running
Mitchell Hashimoto released his book "Vagrant up and running" which covers everything from basic Vagrant usage to extending its functionality. In seven chapters he explains every aspect of Vagrant - from staring a default VM to extending it via plug-ins.
-
The Case for Software Lifecycle Integration
For many years, software delivery has been treated as an ancillary business process; a business process that, though costing the organization a considerable amount of money, does not have the structure, rigor, or focus of other enterprise business processes such as supply chain management, financial management, and even talent management.
-
Managing Build Jobs for Continuous Delivery
The number of jobs in a continuous integration tool can range from a few to several thousand, all performing various functions. There is an approach to manage these jobs in a more efficient manner.
-
Evaluating Agile and Scrum with Other Software Methodologies
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.
-
Interview and Book Review: Enterprise Software Delivery
"Enterprise Software Delivery" is the latest book by Alan W. Brown, and is a must-read guide for anybody concerned with the development and delivery of software in a large organisation.
-
Automated Builds: How to Get Started
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.
-
Integrated ALM Tools Are Fundamental to Success
The typical software delivery project captures requirements numerous times, describes tests in multiple places, is indiscriminate of what is in a particular build, and often requires a large amount of analysis to know who is doing what and why. Dave West looks at the problems this causes and argues for holistic, integrated ALM approach.
-
Automated Builds: The Key to Consistency
If there's one thing software developers are good at, it's automating things that used to be done manually. Making life easier for everyone by letting computers handle tedious repeatable tasks, allowing people to focus on what matters to them is what we’re here for. However, development teams often neglect the one audience that would benefit the most - themselves.