Technology-driven companies, regardless of size and scale, are facing the increasing need to ship better code faster while meeting business requirements. This requires collaboration and interaction among the traditional information technology infrastructure library (ITIL), information technology service management (ITSM), and development teams for a truly agile organization to emerge.
James Sullivan explains popular agile frameworks and outlines their costs and benefits. If you're worried that you are at a place where you cannot make the sort of investments that these agile frameworks require, James is here to discuss foundational agile practices that can provide you key benefits without the costs associated with these kinds of agile brands.
In this first part of a two-part series, Mario Moreira writes that a reasonable application lifecycle management (ALM) product will have a common user interface for utilizing the ALM functionality. It will also include a meta-model and process engine to parse and share information across and amongst the various functions within the ALM framework. These technical needs must be accompanied by a strong business case for delivering higher customer value and new approaches for seamless integration.
DevOps puts the focus on automated application lifecycle management supporting development, test, integration, quality assurance (QA), user acceptance testing (UAT), and production. But, how do you develop DevOps, and how do you know when you have achieved success?
There are ever-growing ways to organize your project assets with public domain configuration management tools. There's a mistaken belief that these free software configuration management (SCM) alternatives can be just as powerful as leading commercial tools.
What happens when defects go unnoticed until it is too late? Mayank provides an insightful view of the true cost of not providing enough test coverage during a software development lifecycle. He also suggests some techniques to ensure that defects are identified and mitigated early.
When you think of configuration management, build automation and version control usually come to mind. Dave presents a perspective that shows the important role CM plays in the entire product and project lifecycle.
Steve Berczuk is a regular contributor to TechWell and StickyMinds and a principal engineer and ScrumMaster at Fitbit in Boston. In this interview, Steve discusses configuration management and agile, helpful tools, and how testing has evolved over the years with the rise of agile.
Joe Townsend has been working in the configuration management field for fifteen years and is a regular contributor to CMCrossroads. In this interview, Joe discusses how configuration management has changed over the years, the trouble with tools, and trends in IT.
We'd like to introduce the newly appointed editor of Better Software magazine, Ken Whitaker. Ken has a long history in software and is a great addition to the team. If you're interested in writing for Better Software, drop Ken a line. His contact info can be found in this interview
Robust configuration management (CM) practices are essential for creating continuous builds to support agile’s integration and testing demands, and for rapidly packaging, releasing, and deploying applications into production. Classic CM—identifying system components, controlling change...
Robust configuration management (CM) practices are essential for creating continuous builds to support agile’s integration and testing demands, and for rapidly packaging, releasing, and deploying applications into production. Classic CM—identifying system components, controlling changes...
Hans Buwalda shares his experiences and the strategies he's developed over the years for testing on very large projects. When “normal” testing practices are stressed on large projects, a multitude of innovative ideas and concepts emerge to support the industrial-strength practices such projects demand. Learn the significance of keyword automation on big test projects, how to design tests specifically for automation, and how to fit automation and scaling into your strategy. Hans explores how virtualization can help you leverage resources and how to deal with numerous versions and configurations common to large projects. Then, Hans points out the possibilities and pitfalls of outsourcing test automation. The information presented is based on his seventeen years of worldwide experience with testing and test automation, in testing projects that in some cases need to execute continuously for many weeks on numerous machines.
When Keith Klain took over Barclays Capital Global Test Center, he found an organization focused entirely on managing projects, managing processes, and managing stakeholders—the last most unsuccessfully.