10. 4 Balanced Metrics for Tracking Agile Teams
Whatever your feelings on metrics, organizations will expect them for your team. You don't want to measure only one aspect to the detriment of other information, but you also don't want to measure too many things and scatter your team's focus. Here are four metrics that balance each other out and help gauge an agile team's productivity, work quality, predictability, and health. By Joel Bancroft-Connors
[Read the article]
9. An Agile Approach to Software Architecture
For an organization transitioning to agile development, creating software architecture isn’t incompatible with your new processes. Consider the principles in the Agile Manifesto, involve team members who will be using the architecture in its development, and reflect and adapt often, and you will end up with an architecture that meets the needs of your team and your enterprise. By Gene Gotimer
[Read the article]
8. Delivering Value with Agile and #NoEstimates
#NoEstimates is a challenge to the traditional thinking that estimation is essential to agile development. Ryan Ripley believes there are more interesting tools available to help us determine what value is and when we could realize it, while still staying aligned with the businesses and customers we serve. Learn some other ways to deliver value to your customers. By Ryan Ripley
[Read the article]
7. 6 Steps to a Successful DevOps Adoption
Implementing DevOps practices can significantly accelerate software releases while still assuring applications meet quality objectives. But DevOps can’t be bought, bolted on, or just declared. If you’re considering a move to a DevOps delivery model, here are six approaches for ensuring a successful DevOps adoption within an organization. By Alan Crouch
[Read the article]
6. The Transparency Experiment: Improving Accuracy and Predictability in Scrum
Using the iterative and incremental agile development framework Scrum should help manage product development, but some teams still have difficulty delivering features in a predictable manner. This organization decided to address the mismatch between what was being committed and what was accomplished by doing an experiment in work transparency. By Darin Kalashian, Chris Jalbert, Rahul Jain
[Read the article]
5. Has Continuous Deployment Become a New Worst Practice?
Software development has been moving toward progressively smaller and faster development cycles, and continuous integration and continuous deployment are compressing delivery times even further. But is this actually good for businesses or their users? Just because you can deploy to production quickly and frequently, should you? By John Tyson
[Read the article]
4. 8 Keys to Transforming into a High-Performance Agile Team
Following an agile process alone will not guarantee your teams will be high performers. Teams undergo various challenges while transforming into a highly productive team. This article looks at the areas where teams generally struggle in adopting agile principles and the typical root causes for those struggles, as well as eight behaviors that can help drive teams toward greater success. By Uday Varma
[Read the article]
3. Estimating Cost of Delay in Agile Projects with Time-Value Profiles
The cost of delay for releasing a product can be due to many factors, but that value loss can seem like an abstract concept. Attaching hard numbers to a release timeline in the form of a time-value profile helps the development team and business stakeholders have a conversation about how long they have to build a product and when it would be best to enter a market. By Allan Kelly
[Read the article]
2. Agile Managers: Trust Your Team and Encourage Innovation
In order to fully embrace agile and create an environment where individuals want to work together as a team, managers have to move from a role of dictation to one of direction and mentorship. Instead of making all the decisions, managers need to trust their team members and empower them to solve problems on their own, innovate, and fail—or succeed. By Lisa Rich, Mic Riley
[Read the article]
1. Why DevOps Still Needs Release Management
Release management is still critical in a DevOps environment. You likely will just have to change your current process. You will no longer need to track implementation or back-out plans as part of change orders; you just need to be able to track the application, its components, and its promotion schedule. The key to maintaining these change orders is automation. By Adam Auerbach
[Read the article]
Top AgileConnection Interviews of 2017
Transitioning from Waterfall to Agile Using DevOps: An Interview with Mark Levy
Why Test Automation Is Important for Agile Data Teams: An Interview with Cher Fox
Trust Your Testing Team and Stop Leading from the Front: An Interview with Bob Galen
Identify Bottlenecks in Your Agile and DevOps Processes: An Interview with Tanya Kravtsov
