The business analyst (BA) has played a key role in software development. But within a modern agile context, the role of the BA is less clear, and there is some confusion as to whether the product owner role subsumes that of the traditional BA. Let’s look at the roles the BA can play with agile teams and how to fully leverage their expertise to supplement or augment that of the product owner.
Ambiguity abounds about value streams, so it’s good to clarify what they are, why they matter, and how to exploit them. It's important to help employees understand the organization's definition of value, to provide visibility on how business value is created, and to focus on the fast flow of value through the value streams. If everyone understands which direction to row the boat, they can steer toward it together.
Unfortunately, many retrospectives are not productive. It may be that the discussions are unfocused, not enough data was gathered to be helpful for analysis, or the team concentrates too much on issues they can’t control. Retrospectives should be a key part of an agile process for helping the team improve. Here are five tips that will help you have more valuable retrospectives.
You've heard of a minimum viable product, which has only enough features to create a working model and provide feedback for further development. If you want to get started on a new project quickly, Allan Kelly suggests assembling a minimum viable team—only a few people, with only the necessary skills. They begin work right away, with a small budget and tight feedback loops, driving down risk.
Just because a software team adopts agility doesn’t mean they’ll see results. Being flexible has its benefits, but ensuring that the team is given total responsibility to make decisions may be more important.
Most software developers are in either the agile or the waterfall camp. Agile is required to be competitive, but many enterprise processes still rely on waterfall practices for stability. They can coexist.
In this interview, Selena Delesie, an international leadership and transformation coach and trainer, explains how your team can find the soul of agile, why some agile teams lack creativity, and who on your team should become a leader.
In this interview, Adam Auerbach, the vice president of quality and DevOps engineering at Lincoln Financial Group, explains how major corporations can learn to take advantage of agile and quickly adjust to the speed it demands, as well as the methods he uses to implement enterprise agile.
In this interview, Isabel Evans, a quality and testing consultant, talks about the traits most often seen in effective leaders. She details different leadership styles that work best in different situations, how you can learn to lead agile teams, and what leaders can learn from the animal kingdom.
In this interview, Jessie Shternshus, the owner and founder of The Improv Effect, explains the similarities between agile development and improvisation. She details how, in both cases, team members need to learn how to support each other, build on work, and be comfortable with failure.
As agile practitioners, we constantly strive to better ourselves, our team, and our delivery. A great way to achieve this is simply being open to learning new ideas from other disciplines—including improvisation. Jessie Shternshus shares her story of realizing the uncanny similarities...
Aggressive timelines, scope creep, changing requirements, development delays, and the imperative to finish on the imposed timeline … how can you keep your team motivated and engaged when everything seems to go wrong? Larissa Rosochansky describes the major factors of team...
Do your developers and testers pair—and do it in the best ways? If you can answer yes, then you are among the fortunate ones who have a trusting environment where people have confidence in their work. Unfortunately, a large number of development shops don’t practice pairing in any form.
Are you having a difficult time finding female engineers to join your teams? Are you currently working on a project which seems to be going nowhere? Have you ever engaged in what you thought was customer-driven work only to later discover it was stakeholder-driven? When it comes to...