Topic: agile

Agile Development Stories

The role of demonstration in a sprint review often takes on more importance than it should, even to the extent that some teams refer to the review as a demo. By focusing on the demo you risk having the team do all the talking, rather than a two-way conversation between the team and the stakeholders.

When adopting agile, organizations can be plagued with quality imbalance. Bob Galen found that all agile testing practices and activities can be grouped into three categories: development and test automation, software testing, and cross-functional team practices. He reviews these "pillars" of agile.

Bob Galen has noticed that when it comes to agile quality and testing practices, people tend to be either all in or under-practicing some techniques. But it is the interplay across practices that is most important for effectiveness. Here, he discusses his three pillars of agile quality and testing.

Self-organizing agile teams still need management, but they need a different kind of management from the autocratic style many teams in nonagile organizations have. A "post-heroic" leader is able to shift from an authoritative manner to a collaborative one as needed to optimize team performance.

We estimate to make decisions and to give an answer to the question, "When will this be done?" But estimation has limits, and trying to estimate too precisely in an agile project is wasteful. By driving the backlog based on priority, you can better deliver what is valuable to the business.

The classic discussion for agile estimation is about whether points or hours are better. But there is now a third option: a movement called #NoEstimates. It actually does involve estimation, but you break down work in priority order and estimate only when you know enough to estimate accurately.

Meetings are a crucial part of the communication process, but they endure a lot of ridicule. You can’t do away with them entirely—meetings are essential to an agile process like Scrum. Rather than avoiding all meetings, it’s better to work at making the times you meet with people more effective.

When teams self-organize to deliver software and solve problems, they can be more robust, effective, and directed. But this begs the question: If agile teams self-organize, do they really need managers? Yes, they do. Managers help create conditions that help teams thrive. Read on to find out how.

Some people in the software world feel that agile focuses too much on problems of the past. These people have moved on to what's being called post-agile, which shakes up the process. Johanna Rothman, however, thinks they're getting ahead of themselves—first, we need to keep working to achieve agile.

Many of us spend more time (and money) beefing up our technical skills when we could use guidance on developing soft skills. The Winter 2015 issue of Better Software should have just what you need to overcome organizational roadblocks in your quest for agile nirvana. Read on to see what's in it.