Only by creating a relationship based on trust can agile coaches be effective in aiding teams with an agile adoption. Joel Bancroft-Connors says the best start is actually to do nothing. Spend time observing the team first. This helps you understand the people and processes, which will help you determine the best course of action.
At the core of agile is the need to effectively communicate and interact with your team members, so it's important for all roles to practice soft skills. However, there is nothing soft about them. Soft skills are probably the most challenging thing you can focus on in your technical career. Rather than struggle to improve by yourself, develop these skills through collaboration.
Education is a vital ingredient in transformations, and it should be one of the first steps you take in moving to agile. Regardless of anyone’s level of agile experience, everyone should go through the same training because the real value of training isn't the lesson plan; it's the shared experience. Everyone across teams having the same foundation is essential.
The leaders in an organization play a key role in making a team's agile change journey sustainable. Managers have to understand the team culture, address the real problems, and commit to undergoing self-transformation first before transforming others. Ledalla Madhavi outlines her process for coaching teams starting a successful agile journey.
Scaling agile across a large, enterprise organization is different from dealing with just a handful of teams. Though you have the same key ingredients, there are several recipes for how to put those ingredients together. Enter The Agile Coach’s Transformation Cookbook. You can whip up an organization-wide agile transformation by finding your own recipe for success.
There is no question that agile has gone mainstream. If you aren't already using at least some agile methods, you soon will be. TechWell took a look at which topics the growing agile community cares most about and put together a list of the most popular AgileConnection stories and interviews of 2016. From failing Scrum teams and successful agile communication to facilitating feedback and simplifying user stories, we've curated the content you need to read as we head into a new year.
When teams are transitioning to agile, making so many changes all at once can be hard. But just like with your health, in order to see progress, you have to commit, and when something starts working, you have to keep it up. Following this prescription should cure a team's agile ills and get its program on the road to recovery.
The experience of implementing agile in a company of thousands of employees differs widely from that of a company of hundreds. Although the risks can be greater, the rewards can be, too. If you work in a small company that is interested in transitioning to an agile workflow, consider these strategies for implementing agile in small organizations.
The core of the Scrum framework for managing product development is the three key roles: ScrumMaster, product owner, and the development team. This triad is what makes Scrum so successful—when it works. However, it is the absence of these three roles that is the root cause of the majority of unsuccessful adoptions.
It’s the distinctions between agile and traditional software development approaches, as well as the adaptability of testers in these very different environments, that makes agile testing different from traditional testing. Agile demands more from its testers, and, in turn, it values them more, too. Let’s look at five main things that make an agile tester’s life different from that of a traditional tester.