Related Content
 |
Signs Your Organization Isn't Ready for DevOps Organizations struggling to see tangible benefits after adopting DevOps practices often have only slapped together a few tools instead of making the required changes. Many aren’t really embracing DevOps at all. Here are three signs to help you determine if your organization isn’t quite ready yet to practice DevOps. |
|
 |
Drafting the Right Software Professional for Your Fantasy Team Teams are systems made up of individuals with different strengths and weaknesses. When people are cooperating on a team—whether in software development or football—sometimes those strengths and weaknesses can be complementary, and other times they can be out of alignment. Be sure to draft the player your team needs. |
|
 |
Continuous Security in Agile Development "Continuous" gets mentioned a lot in agile and DevOps, but one area that often doesn’t get enough attention is how to continuously build, test, and deliver secure applications. Just like for quality, you can’t test security in, so you need to have a plan for how to build it in. Here are some tips on how to do that. |
|
 |
Aesop and Agile: A Moral for Effective Teamwork When a manager sees a problem on their team, they often want to act quickly to correct it. But if you take a “fix it” mentality too far, while you might get past the initial impediment, you have done little to help the team work better in the future. Let's look at another approach, based on one of Aesop's Fables. |
|
 |
Integrating Threat Modeling into Agile Development Threat modeling helps you determine where to focus your security testing efforts when building your app. But people often wonder how it can fit into their existing agile software development process. Here are three things you can do to integrate threat modeling into your agile workflow, either early on or mid-project. |
|
 |
The Good, the Practical, and the Expedient When a process isn't working, you'll have to make a choice that will help move things along. However, some choices are less about inspecting and adapting than about getting things done quickly, and that incurs risk. To manage this risk you need to be aware of the differences between "practical" and "expedient." |
|
 |
Alleviate Employees’ Stress through One-on-Ones Simply having one-on-ones because they’re expected is not enough to realize their potential. To make one-on-ones effective, as the manager, you’ve got to be available, prepared, and engaged. It has to be more than a one-way status update. Here's how to use these meetings to promote trust, growth, and creativity. |
|
 |
Do’s and Don’ts for Having a Technical Lead on a Scrum Team Technical leads can be useful, both within the dev team and as a go-between. But is that a good idea on a Scrum team, which should be self-organizing? There is nothing wrong with having a technical lead on your team, as long as the role doesn’t impede the team. Here's where a tech lead can help or hurt a Scrum team. |
