Related Content
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. |
||
Making the Switch from Quality Assurance to Quality Engineering The quality engineering approach differs from QA in that quality teams partner with business users and product managers to better understand requirements and to catch problems as products are being built—not after the fact. There are two pillars to building a true quality engineering organization: culture and process. |
||
The Developer’s Role in Testing and Quality Of course a developer's primary job is to produce good code, but there's also a lot they can do to contribute to quality and test their code before it gets to a tester. Code quality techniques help developers write better code, more thoroughly understand their changes, and avoid builds with many easy-to-find problems. |
||
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. |
||
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. |
||
Beware the Bad Apple: 3 Types to Watch for on a Team We all know some obvious personality types that can be less than ideal to work with. However, there are other personality traits you may want to beware of as well. Although these characteristics may seem perfectly harmless on the surface, in excess they can be just as dangerous to a project as the more glaring types. |