Application Lifecycle Management
Articles
From One Expert to Another: Simon Baker In this interview, author, speaker, and agile tester Lisa Crispin speaks with Simon Baker, cofounder of Energized Work and recipient of the Gordon Pask award, about the approaches and tools his lab uses. |
||
Continuous Integration and the Automated Database Update Process Developers must have good feedback to ensure productivity. Most shops have a continuous integration (CI) build process that allows the developer to quickly know if a build failed, and some shops have an automatic deploy of the CI build to provide website feedback. Lance Lyons writes about an approach to automating the update of databases in a CI environment. |
Lance Lyons
July 14, 2011 |
|
Communication and Cooperation When Implementing CM and ALM If you have been involved with any technology-related efforts, then you will instantly recognize how often teams struggle with effective collaboration, communication, and cooperation. This article covers several key “people” issues that you should consider when implementing CM and ALM strategies. |
||
Branching to Distraction Branching can be an effective solution for managing change, enabling parallel development and improved productivity. But, working on a branch is a distraction and can decrease agility, productivity, and code robustness. Learn when the value of working on a branch outweighs the cost. |
||
Factor in Coworkers' Personalities When Implementing ITIL/ITSM There are many people who do not like structure. Application lifecycle management (ALM), and, even more so, IT infrastructure library (ITIL) as a framework, touch some people's buttons as being just too much structure. In this article, Leslie Sachs examines the personality factors that you need to be aware of when implementing ALM and ITIL/IT service management (ITSM). |
||
How to Use ALM for a Comprehensive Software and Systems Development Lifecycle Bob Aiello explains that ALM and ITIL provide considerable guidance that can help you implement a comprehensive software and systems development lifecycle. Your organization would benefit from implementing these best practices, especially if you need to meet regulatory requirements or perhaps pass an internal audit once in a while. |
||
Four Agile Tips to Eliminate Rework in Application Development Your applications need to meet business needs, overcome complex processes, and provide instant results to customers. And, ideally, they’ll require minimal rework on your part. The first step to success is requirements definition. Here, Filip Szymanski offers some tips from agile methods that will improve your requirements—even if you haven’t otherwise adopted agile. |
||
Ten Capabilities that ALM Tools Must Support Joe Farah writes that next generation ALM tools must not interfere with development by adding overhead. Instead, they must help to increase efficiencies and productivity of all roles as part of the agile backbone. Here is a list of capabilities that ALM tools must support in an increasingly agile world. |
||
The Needs and Growth for ALM Tools and Techniques After defining ALM and looking at the entire lifecycle, teams can begin deciding which tools to utilize to close the gap that often forms between development and operations. Learn how to avoid disruptions by choosing tools that can work across the entire lifecycle. |
||
Personality Factors That Influence Core Build and Release Management Practices Leslie Sachs discusses the key people skills essential to appreciating how and which personality factors most impact one's ability to successfully implement core build and release management practices. |