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. |
|
 |
The Problem with the People-Management Bell Curve Conforming team performance evaluations to a tidy bell curve is a simple, quantitative solution to the challenging problem of rating employee performance. However, it doesn’t work. It’s unrealistic (not to mention counterproductive) to force-fit employee evaluations to the curve when that doesn't reflect their work. |
|
 |
One-on-Ones: A Framework for Feedback Regular one-on-one meetings between a manager and employee are a forum to provide safe, timely feedback. They can be short or longer, but you should discuss successes, challenges, and how to improve. Having a framework for the conversation helps you make sure that the meetings don’t routinely become chat sessions. |
|
 |
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. |
|
 |
Why Choose Containerization? Containers have been adopted by many organizations. Docker is the most popular and has become the standard containerization platform, though there are others. But why use containerization? What are the advantages that spurred its adoption? Let’s look at some of the factors that govern the choice of containerization. |
