Related Content
 |
Leave No Tester Behind Creating comprehensive automated tests within a sprint can be a challenge. If the testers don't finish the automation and the rest of the team moves on, testers get left behind and can't catch up. You need some techniques to keep everyone together and ensure that all essential work is accomplished—including test automation. |
|
 |
Code Integration: When Moving Slowly Actually Has More Risk Many decisions about code branching models are made in the name of managing risk, and teams sometimes pick models that make integration harder in the name of safety. Moving slowly and placing barriers to change can seem safer, but agile teams work best when they acknowledge that there is also risk in deferring change. |
|
 |
Building a DevOps Army As you scale DevOps, you need more team members who understand the fundamentals. You could bring in external folks, but they're expensive and in short supply, so start building your DevOps army now by training existing employees. Here's what testers, developers, and IT operations professionals each need to know. |
|
 |
Good Process, Bad Process “Process” is a word that seems to have a lot of baggage. Depending on whom you ask, process is either essential to delivering value, or something that gets in the way. But this is the wrong way to frame the issue. A process is not inherently good or bad; it's how you use it, and whether it's right for your situation. |
|
 |
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. |
|
 |
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. |
