Related Content
 |
Make Your Security Testing More Agile Security practices traditionally have followed a waterfall model, adding security testing on at the end. Organizations need to coach their security programs and testers to prioritize analysis and risk, much like we do with agile stories, to better incorporate security defects with other feature work along the way. |
|
 |
What’s Your “Size” of Agile? There are approaches to agile that sound great on paper, but will they really be the best choice for your team in practice? Instead of standardizing on any form of agile, think about the results you want. Why not create the environment that works best for you? There's more than one way to do agile. |
|
 |
Breaking Down Your Development and Testing Walls Testing earlier assures better quality. But maybe most important, things like agile and DevOps—which encourage that you shift your testing left and allow for more collaboration between different parts of your team—have broken down the walls that previously separated testers for the rest of the organization. |
|
 |
Finding the Bottlenecks in the Agile and DevOps Delivery Cycle To achieve incremental software development and continuous feedback, you need to eliminate the tasks that create bottlenecks, which hinder the flow of development. A chain is no stronger than its weakest link, and identifying these “weak links” is a critical step toward achieving agility and increasing efficiency. |
|
 |
Continuous Testing: New Improvements on an Old Idea The concept behind continuous testing is far from new, but what’s different now is that software development practices have evolved to a point where developers are embracing testing as part of their responsibilities. Testing is slowly moving from being an “event” to an activity throughout the development lifecycle. |
|
 |
In Praise of Failure Failure is measured by expectations. If we aim to be perfect, or set the expectation that only perfection is acceptable, we risk losing opportunities to get valuable feedback. Creating an expectation of perfection can lead to stagnation, not success. Instead, view failure as a learning experience. |
|
 |
Before You Can Eliminate Agile and DevOps Bottlenecks, You Need to Identify Them Agile and DevOps, which now dominate software development, lean on continuous integration, continuous testing, and continuous deployment. Because of that, anything that might break this iterative and continuous cycle could throw everything out of whack and stunt your team’s growth. |
|
 |
Think Small: Break Down User Stories for Agile Success The entire agile team needs to be involved in a continuous process of identifying ways to simplify work, right up until a story is complete. Smaller stories ensure that development work is rapid and trackable. Mitch Goldstein details how to focus on breaking stories down into a more estimable, “digestible” size. |
