As agile principles and practices receive greater organizational exposure, business teams are embracing certain aspects of agility that were traditionally reserved for technology teams. This article details the experiences of a group of people with business roles who have adopted some agile methods and how their teams have benefitted.
The traditional ways of finding employees are changing. If you want to get a role that will make you happy to contribute to the team, you need to rethink the way you apply for roles. If you are the resource manager, change how you recruit. This article focuses on the qualities you should be exemplifying or looking for if you want to form a team with an agile mindset.
Usually noise has a negative connotation, but in this sense, noise means something that increases the team progress (i.e., velocity) and output (i.e., quality). Chaos is the negative side of noise and decreases velocity. Teams should know the importance of agile noise and handle the chaos in a right way at the time of transformation. Let’s explore agile noise and its benefits.
When it comes to transitioning to agile, if a team only goes off what it's heard from other teams and doesn't take a class or read any books about the process, misconceptions can abound. And that leads to problems. Read on to have three common agile myths debunked and to learn why agile is a cultural change, not just a project management framework.
The fable of stone soup is often told as a lesson about cooperation in times of scarcity. Mike Edwards has used an approach based on this allegory to help teams make steps toward improving themselves and the way they work, especially when it comes to shifting to new methodologies such as agile and Scrum.
An employee may become indispensable through arrogance or happenstance. These employees can cause bottlenecks and often prevent others, as well as themselves, from learning and growing professionally. "Firing" these indispensable employees sets your team free to work even when the expert is not available.
Simply putting a handful of developers together and calling it a “team” doesn’t cut it. There’s a better, more analytical approach to team assembly that results in more cohesive teams, faster ramp-up times to peak velocity, and improved innovation, business outcomes, and value.
Agile teams are supposed to take responsibility for how they work and how they learn. But what if you need to jump-start that learning? Agile transformation is about making this happen rather than waiting for it to happen. You need to get your team to learn the technical side of agile, and soon. Here are some effective approaches.
Agile pods are small custom agile teams, ranging from four to eight members, responsible for a single task, requirement, or part of the backlog. This organizational system is a step toward realizing the maximum potential of agile teams by involving members of different expertise and specialization, giving complete ownership and freedom, and expecting the best quality output.
Do your managers truly own their decision making or are they only "empowered" to come to you for approval of every idea and dollar spent? If you don't trust your team leaders to make decisions, how can you expect stakeholders to? Setting boundaries and defining expectations are two ways to empower managers and encourage initiative, giving them the opportunity to gain your trust.