Agile Development Stories & Trends | TechWell
Development Agile Test & Quality Assurance Project Management Requirements
CM & ALM Devops Cloud Mobile People & Teams

By Topic

Agile Development Methods

Agile Development Stories
Software team in a meeting The Myth of Too Many Scrum Meetings

A common complaint in organizations adopting Scrum is that Scrum has too many meetings. However, people may not be considering all the time they spent meeting before Scrum—and how effective that time really was. As long as you keep meetings focused, people should waste less time in meetings than they did before Scrum.

Steve Berczuk's picture
Steve Berczuk
Agile team having a productive meeting Getting the Most out of Your Agile Meetings

One of the most common complaints of any software team during a retrospective is the issue of too many meetings. Agile ceremonies can provide a lot of value to the team, but only when they're done correctly. Here are four ways to get the most out of meetings, avoid wasting time, and gain value for everyone involved.

Alan Crouch's picture
Alan Crouch
Red apple fitting in with green apples Making Testing Work within Your Sprints

A common problem for Scrum teams is having a good understanding of what work is complete by the end of the sprint. Teams often end with a few items coded but not fully tested, but since the goal of a sprint is to have a deliverable increment of work, skipping tests isn’t a good idea. Here's how you can fit them in.

Steve Berczuk's picture
Steve Berczuk
Looking upward at trees in a forest Scrum Can Help You See the Forest and the Trees

In project management, it's easy to focus on details to the extent that you lose track of the larger goal. Scrum can help you identify flaws and gaps, and skipping or trivializing Scrum events will just hide the fact that there are things you need to improve. Finding problems is something to be celebrated, not hidden.

Steve Berczuk's picture
Steve Berczuk
Person on a skateboard When Transitioning to Agile, Let Value Be Your Guide

When making a transition to agile, it’s important to get a common understanding of what you’re trying to do, of how things are currently done, and of the definition of done. In a value stream analysis, you can identify where major chunks of time are being spent (and why), and then start prioritizing based on value.

Owen Gotimer's picture
Owen Gotimer
Two agile team members exchanging feedback in a retrospective 6 Ways to Share Negative Feedback in a Retrospective

Negative feedback has the greatest potential to help people change in areas that can have a lasting impact. But sharing negative experiences and criticism can often be a challenge and may cause more harm than good. Here are six tips for sharing negative experiences effectively and building trust along the way.

Alan Crouch's picture
Alan Crouch
Sign saying "You got this" next to a laptop Brain Hacks to Engineer an Agile Transformation

When we are presented with a decision, the subconscious determines what we’re most emotionally comfortable with, then fills in the gaps to justify choosing it. In other words: Our brains lie to us. Then how can we ever get out of our comfort zone? Believe in change and take an agile approach to incremental adoption.

Chris Murman's picture
Chris Murman
A watch with the second hand moving fast The Agile Culture You Need for Faster Pull Requests

Is your process for pull requests compromising your team's agility? You can structure your changes in a way that facilitates more rapid feedback, but even then it is still possible to have a slow integration time if people don’t review pull requests promptly. Mechanics are part of it, but culture also matters.

Steve Berczuk's picture
Steve Berczuk