Related Content
 |
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. |
|
 |
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. |
|
 |
6 Ways to Build Strong Relationships on Your Project Team When you form a new team to tackle a major project, the project's success hinges not just on the technical savvy of the team members, but also—and especially—on how well the team members get along. How everyone communicates and collaborates can make or break your project. Here's how to build strong team relationships. |
|
 |
To Be a Good Leader, Become a Better Servant Wanting to serve others—not wanting them to serve you—is one of the best signs of an effective leader. Being a leader is also not about doing more of the work or being the most technical person on your team. Rather, it's actually about giving up some of your work to help others grow. Here's what else good leaders do. |
|
 |
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. |
|
 |
Testers as Disciplinarians As testers, are we disciplinarians? We shouldn't fall into the trap of controlling quality or becoming quality police. Instead, we should be true facilitators of quality, enabling the product team to own it in their own right at every stage. Isn’t this what teachers do, too, in the learning process? What is our role? |
|
 |
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. |
