Related Content
Scrum Roles, Goals, and You The Scrum Guide specifies that there are three roles: product owner, developer, and ScrumMaster. It’s essential that a Scrum team have each of these roles to help it work well. But depending on how you implement the roles, you may end up hurting rather than helping your Scrum process. Focus on goals, not job titles. |
||
Why You Should Treat Tests as Products There's a case for treating some of your tests as products—project deliverables in their own right, created as a business investment. "Productizing" tests can show their value to management, but more importantly, it can help them contribute more effectively to the development lifecycle. Here are four steps to consider. |
||
3 Common Scrum Anti-Patterns and How to Fix Them For a Scrum team to operate successfully, the entire team must honor the Scrum values of commitment, courage, focus, openness, and respect. But it's easy to fall into practices that can erode trust and collaboration. Here are three common anti-patterns that emerge in Scrum, as well as the solutions to overcome them. |
||
3 Reasons Managers Struggle to Build Compatible Tech Teams Managers should try to find candidates who not only have the right technical skills, but also will ideally complement each other and be able to collaborate. But that’s not easy. Here are three main aspects managers struggle with when building compatible tech teams, so you can try to mitigate them and achieve harmony. |
||
2 Simple Ways to Improve Developer-Tester Relationships Supposedly there is a constant tension between developers and testers, like the roles of artist and art critic. They can’t exist without each other, and yet they can’t get along. It doesn't have to be that way! Here are two ways testers can reduce that feeling so that developers and testers can work better together. |
||
Plan for the Year the Agile Way The start of a new year always comes with new resolutions, goals, and a set of plans to grow in the future. The excitement and energy that a new start brings can rejuvenate a team. However, if you’re not careful, that same ambition can lead to failure. This year, adjust your strategy and plan in a more agile manner. |
||
The Curse of Rushed Requirements When development is outsourced, a documented baseline of expected functionality sets expectations for both the client and developer. Acknowledging that agile practices are flexible, beware the trap of rushing requirements just because you know they are going to change. It's still essential to be as accurate as you can. |
||
Top 10 TechWell Insights Stories of 2019 Career development was on many software practitioners' minds in 2019, as some of our top stories were about having a technical lead on a Scrum team and making the switch from quality assurance to quality engineering. Stories about new ideas such as DevOps and continuous testing also ranked high. Check out the roundup. |