agile | TechWell


Group of game pieces with one left behind Leave No Tester Behind

Creating comprehensive automated tests within a sprint can be a challenge. If the testers don't finish the automation and the rest of the team moves on, testers get left behind and can't catch up. You need some techniques to keep everyone together and ensure that all essential work is accomplished—including test automation.

Hans Buwalda's picture
Hans Buwalda
Agile team talking about their struggles Build Stronger Agile Teams by Getting Real about Mental Health

How much more effective would our teams be if we created an environment that was psychologically safe enough to be honest about how we're feeling? Mental health can be difficult to talk about, but we can use the agile frameworks of standups and retrospectives as a blueprint to share with our teams. Here's how to speak up.

Jenna Charlton's picture
Jenna Charlton
An agile acrobat holds himself perpendicular to a wall An Agile Mindset Teaches the Lessons We Need for COVID-19

Since we can't control the COVID-19 situation besides following safety protocols, and updates change almost daily, our circumstances necessitate agility from everyone, from employees to company leads. Let’s look at the practical agility lessons COVID-19 is teaching us and why an agile mindset is even more important now.

Bharathan Venkateswaran's picture
Bharathan Venka...
Software engineer looking at her computer monitors and integrating code Code Integration: When Moving Slowly Actually Has More Risk

Many decisions about code branching models are made in the name of managing risk, and teams sometimes pick models that make integration harder in the name of safety. Moving slowly and placing barriers to change can seem safer, but agile teams work best when they acknowledge that there is also risk in deferring change.

Steve Berczuk's picture
Steve Berczuk
Agile team coming up with three-point estimate for a project 3 Questions for Easier, Less Stressful Project Estimates

In agile development, the idea of precise estimates is unrealistic. But estimates are needed to inform decision-makers about whether it's worth solving a problem as it is currently understood. It sounds counterintuitive, but instead of asking for one estimate of cost and schedule, ask for three. Here's why it's more useful.

Payson Hall's picture
Payson Hall
Looking at code through eyeglasses Fearless Refactoring, Not Reckless Refactoring

Fearless refactoring is the agile concept that a developer should be able to incrementally change code without worrying about breaking it. But it's not believing that you don't need a safety net to detect and correct defects quickly when changes are made—that's just reckless. Here's how to avoid reckless refactoring.

Jeffery Payne's picture
Jeffery Payne
Basketball player playing defense Defensive Design Strategies to Prevent Flaky Tests

Flaky tests could be the result of issues in the code, but more often they are due to assumptions in the test code that lead to non-relatable results. There are many reasons that tests can fail intermittently, and some can be easily avoided by applying good defensive design strategies. It's all about making your code agile.

Steve Berczuk's picture
Steve Berczuk
Repeating geometric pattern Achieve Repeatable Builds with Continuous Integration

Continuous integration is essential to provide the feedback needed to keep a team’s code agile. One crucial aspect to a successful CI process is a repeatable build. There are two parts to maintaining a repeatable build: the idioms and practices to define it, and the feedback cycle to maintain it. Here's what you need.

Steve Berczuk's picture
Steve Berczuk