Plenty of companies want to be agile and go through the motions but are not really agile. An agile assessment allows you to evaluate how teams or even organizations are doing in their agile journey. But like any useful tool, there is no shortage of assessment options available. Here are the acceptance criteria to look for and a framework for using an agile assessment.
The greatest use for agile in business is in changing how you tackle problems and projects. Rather than defining the whole project and setting a “way forward,” an agile approach takes things much more iteratively. That means meeting as a team on a frequent and regular basis to share problems and successes, then making improvements as needed—being retrospective.
In agile development, a bloated backlog results from teams accumulating huge lists of requirements, usually in the form of user stories. Retaining every possible story for building the product weighs down the backlog while squeezing (or obscuring) the highest-value stories. The best way to help minimize this risk is to optimize the time spent defining and refining the product priorities.
Agile is not a state of doing; it’s a state of being. Adopting business models on value and learning how to make teams autonomous are both necessary steps to reap the benefit of agility.
- Hamel, Gary. “The Why, What, and How of Management Innovation.” Harvard Business Review . February 2006. . https://hbr.org/2006/02/the-why-what-and-how-of-management-innovation.
- Rutgers School of Arts and Sciences. “Thomas A. Edison Papers.” The Edisonian, Volume 9, Fall 2012. http://edison.rutgers.edu/newsletter9.html.
- Critchfield, Sara. “How to Push Your Team to Take Risks and Experiment.” Harvard Business Review . March 9, 2017. https://hbr.org/2017/03/how-to-push-your-team-to-take-risks-and-experiment.
The Agile Manifesto contains values to guide teams toward developing better software. But its directives are also about leadership—influencing culture and creating an organization where people can collaborate to meet the needs of their customers. Here are seven lessons the Agile Manifesto can teach us about leadership.
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.
Test automation is one of several key technical enablement practices that allow teams to be more successful in their agile journey. Although there are many test practices and automation tools available for software development teams to leverage, few are targeted to data-related development...
When software development teams work in waterfall environments, traditional performance management programs can help encourage personal development and innovation. However, Tina Rusnak says that when organizations move to agile, measuring performance takes on a new form that often causes...
Many approaches to implementing agile focus primarily on the adoption of common practices at the team level. While this focus on practices is important, recognizing that agile is a set of overarching values and principles is also important. Adopting agile “at scale” in organizations often...
The Internet of Things (IoT) will be a $1.7 trillion market by 2020. Don MacIntyre explains how agile is being used in Internet of Things systems—often combined with mobile and cloud technologies. Don reviews how agile is successfully being used today in a wide range of development...