Related Content
 |
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. |
|
 |
Creating a Community of Testers Many teams are divided by product or feature, with only one dedicated tester per team. How do you learn and grow in your career when you’re disconnected from your peers? One solution is to create your own community of testers that spans the organization. Here are some ideas to start and facilitate a Quality Guild. |
|
 |
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. |
|
 |
Transitioning to Testing: The Qualities We Should Be Looking For Testing is an accessible career choice for people who don't come from the typical paths into a tech job. Previous jobs and formal education should matter less than the abilities to observe, identify risks, and report that information. How can we change our interview processes to highlight these skills and mindset? |
|
 |
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. |
|
 |
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. |
|
 |
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. |
|
 |
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. |
