Related Content
 |
Making Continuous Integration Work for You Many developers learn about using continuous integration to improve their deliverability speed and decrease the amount of effort needed to launch new features. Actually practicing continuous integration, however, is nowhere near as straightforward as it sounds. Here's how to get started in making CI work for you. |
|
 |
Rethink Your Strategy to Innovate Inexpensively Many companies avoid genuine innovation for fear of making potentially complex changes without producing measurable results. But you can start small with internal changes that have limited scope and that deliver prompt solutions, so there's less upfront investment—and less risk. Here's how to innovate inexpensively. |
|
 |
Implementing Continuous Delivery in the Federal Government Federal agencies generally have more regulation, slower processes, and a command-and-control style of bureaucracy. How does it work when trying to foster agility and implement a continuous delivery model? Gene Gotimer relates his experiences and challenges with encouraging a culture change in federal government. |
|
 |
3 Steps to Transformational Leadership for Business Agility Building your agile organization only starts with developing software in an agile way. The next step is transforming your business with a customer-focused embrace of agile across the entire enterprise. Managers who want a truly agile organization must lead with focus, steer from the edges, and change the system. |
|
 |
You Can’t Rush Agile Change Too often, organizations try to rush agile change. It is usually because they want to see the business benefits of agile as quickly as possible. Unfortunately, change doesn’t work like that—you can’t rush it. In fact, trying to change too fast often results in no change at all. Here are some examples to avoid. |
|
 |
How Failed Agile Transformations Can Still Have Value Not all agile transformations are successful in the same way; in fact, it’s possible to get tremendous value out of a failed attempt. A team that doesn't end up fully transitioning to an agile framework can still borrow some lessons from agile development methods to improve their processes. |
|
 |
Agile for Everything: Taking the Manifesto beyond Software The values of the Agile Manifesto, while written to apply to software, can form a basis for an adaptive approach to any project. Going from specific to general and inspecting and adapting along the way are great design ideas, no matter what you’re working on. Here's how to use feedback to take agile beyond software. |
|
 |
Why the Minimum Viable Product Matters The MVP brings tremendous value to a team’s ability to effectively implement agile practices. It also allows us to better understand what “value” actually means to our users and how context changes the meaning. Your MVP must move through your validation and release cycles while still being valuable to your users. |
