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?
Scott Ambler explains how DevOps has grown within the agile community, and why he believes it will become an IT buzzword in 2012. DevOps uses agile's community-based teamwork and offers developers and those in operations a great way to make everyone's job easier.
If you have recently transitioned to an agile team, you may have questions about the differences between user stories and use cases, especially how they differ from tradition requirements writing. In this article, Charles Suscheck defines each of these requirements types and uses a running example to illustrate how they differ in a real-world setting.
In this second part of a two-part series, Mario Moreira explores the back-end disciplines of a lifecycle that establishes an ALM framework centering on customer value. If your organization has adopted agile and you are looking at building your ALM framework, consider an infrastructure and tooling that will help you establish and build customer value throughout the lifecycle.
In this excerpt from an interview recorded at this year's Better Software and Agile Development Practices East conferences, authors Bob Aiello and Jez Humble discuss the challenges and the rewards of instituting configuration management and DevOps practices.
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.
One of the hardest daily tasks developers, QA, ScrumMasters, and product owners encounter is effective communication with others. Sound implausible? According to many articles, research, and personal observations, the main cause of project failure is not technology or hardware, but inefficient communication stemming from lack of effective communication between team members, incomplete business analysis, imprecise requirements, and vaguely formulated business objectives.