agile transition

[article]

Are You Agile? An Assessment Can Tell You

Summary:
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.

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.

About the author

[article]

How Businesses Stay Agile: The Art of Being Retrospective

Summary:
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.

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.

About the author

[article]

Streamline Your Agile Requirements by Avoiding Bloated Backlogs

Summary:
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.

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.

About the author

10 Things You Must Do to Become Truly Agile

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.

Better Software Magazine

References

  1. 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.
  2. Rutgers School of Arts and Sciences. “Thomas A. Edison Papers.” The Edisonian, Volume 9, Fall 2012. http://edison.rutgers.edu/newsletter9.html.
  3. 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.
[article]

7 Lessons Agile Can Teach Us about Leadership

Summary:
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.

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.

About the author

[article]

An Agile Approach to Software Architecture

Summary:
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.

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.

About the author

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.