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. |
|
 |
Does Agile Have Too Many Meetings? Because agile favors lots of short meetings, it may seem like they take up a lot more time. But when you compare it to time spent meeting in the pre-agile days, it's usually actually less. However, this doesn’t mean all meetings you attend are useful. Here are a few tips for deciding if all your meetings are necessary. |
|
 |
Defect Reporting: The Next Steps When a software defect is identified, best practices usually only pertain to the initial writing of the defect, not the tasks required to close it. Many factors can influence the tester's work. The solution is to add a “Next Steps” section that identifies the work remaining and the person responsible for completing it. |
|
 |
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. |
|
 |
Shifting Security Left: The Innovation of DevSecOps The more established a product is when it is first audited for security, the harder it will be to find the time to fix problems and to refactor the software. DevSecOps was created to get application security practices into the development process as early as possible, so we can use them from the beginning of a project. |
|
 |
3 Tactics to Stay Productive with an Agile Schedule The usual productivity tips apply best to those working in a typical office with typical hours. What if you don’t work within a structured schedule? How can you stay productive when work ebbs and flows or occurs outside the typical nine-to-five? Here are three ways to be productive when your schedule is unpredictable. |
