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. |
||
How to Achieve Better Internal Communication Our methods of communicating are often on “autopilot.” Being more mindful of when and how we communicate can eliminate problems and strengthen internal relationships. There are several things that can be improved or implemented to increase trust and effective communication on any business team. Here are some ideas. |
||
Why We Need to Stop Calling Them Soft Skills People often focus on hard skills for career development, but soft skills are just as important—if not more. Soft skills require practice and they are crucial for professional success, so we should stop referring to interpersonal skills as soft. They’re hard, human skills, and they can set you apart in your job. |
||
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. |
||
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. |
||
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. |
||
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. |