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

By Topic

Agile Development Methods

Agile Development Stories
Agile team made of different people all bumping fists How Embracing Differences Makes More Robust Agile Teams

On any team, there are bound to be some differences. But even though work styles may differ from what you expect, they may not be problematic simply because they are different. Before making assumptions about what a teammate is doing or why, just ask to find out. Their differences may bring a helpful new perspective.

Steve Berczuk's picture
Steve Berczuk
Stacy Kirk DevOps Transformations for QA Teams: A Slack Takeover with Stacy Kirk

Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. QA architect an agile coach Stacy Kirk, founder of QualityWorks Consulting Group LLC and nodeqa.io, hosted this Slack takeover and discussed improving teams by implementing DevOps practices.

Kelly McGee's picture
Kelly McGee
"Does not equal" sign Agile Is Not the Same as DevOps

Agile and DevOps are two terms that are often confused with each other and sometimes used interchangeably. But they are not the same idea. While both improve software performance, these concepts are actually quite different. Let's look at their definitions, origins, and principles, as well as using each in practice.

Deepak Vohra's picture
Deepak Vohra
Plants scaling larger 5 Mistakes to Avoid When Implementing Agile at Scale

Businesses are increasingly hopping on the agile bandwagon, but ensuring effective adoption of agile practices throughout the organizational hierarchy is easier said than done. To ensure that your agile transformation doesn’t get stuck in limbo and is scaled successfully, you need to steer clear of these common errors.

Vinati Kamani's picture
Vinati Kamani
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