|
Ways to Implement Agile without Breaking the Bank 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.
|
|
|
Eight Mistakes that Prevent DevOps Success DevOps is more than just a buzzword; it’s about delivering value to customers faster and more reliably. Jonathan Thorpe explains eight mistakes that can dramatically increase cycle time and slow the flow of releases to customers, which is counter to the goals of DevOps.
|
|
|
Essential Methods for Agile Project Success Mark Balbes presents a framework for agile project management’s critical techniques. These techniques are required for successful agile development, where rapid requirements changes can be followed through with rapid development changes.
|
|
|
Overcoming the Fractured Development Cloud The IT industry is abuzz with conversations regarding continuous delivery, DevOps, and cloud development—and with good reason. Advances in agile software development methods, the integration of these practices into both on-premise and public clouds, and the emergence of end-to-end cloud platforms have been shown to cut development cycles by as much as half, greatly improve quality, and reduce costs. Even though this is an unbelievably exciting time, we need to work together on the issue of the “fractured cloud.”
|
|
|
The Agile Success Factor: Continuous Integration Kirk Knoernschild discusses the subtle though significant ways that continuous integration can be leveraged—from helping to align IT with the business to enforcing architectural constraints—and shows that this fundamental aspect of agility is the defining and necessary element of a truly agile development experience.
|
|
|
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.
|
|
|
Virtual Hudson Build System: The Rest of The Story The second half of this Hudson-adoption case study sees the team working through some challenges and setbacks. Do they meet their goals? Find out how this virtualization journey ends.
|
|
|
Virtual Hudson Continuous Build Environments: Out with the Old A continuous build may be a great idea, but it takes more than a great idea to be successful. In this article, Tony Sweets describes his personal experience with difficult build servers and his organization's move toward a continuous build.
|
|
|
Agile ALM—Opposites Attract Agile and ALM are two terms that you don’t often see side by side. To most developers, agile means team interaction, customer collaboration, dynamism, and responsiveness to change. In contrast, ALM seems to imply the opposite of agile, with echoes of rigid procedures, inflexibility, and top-down process control. But are the agile and ALM approaches as contradictory as they first appear to be?
|
|
|
When is Open Source not Enough? Open source CI tools have been immensely popular, but are they the perfect fit for your operation? Answer these seven questions to quickly assess if you should upgrade to an enterprise-class CI environment.
|
|