Agile Development Methods
 |
Choose Continuous Integration over Branching for Faster Feedback Continuous integration is the best way to get feedback often on the state of your project. Running automated builds and tests after each integration improves reliability and predictability. Consequently, using task and feature branches, while useful in some cases, can be a distraction and delay getting information. |
|
 |
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. |
|
 |
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. |
|
 |
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. |
|
 |
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. |
|
 |
Tester Contributions to Scrum Conversations Scrum is one of the most popular paths to agile, but testers sometimes join this framework as an afterthought and aren’t quite sure how they fit into the development flow. Scrum is more than answering three daily questions, and testers are in a position to understand the project better than anyone else on the team. |
|
 |
The Software World Is Changing—Are You Willing to Change with It? The software landscape is changing. Processes are becoming quicker and leaner, but instead of re-evaluating some of our traditional practices, we sometimes try to make them fit where they don't belong. This holds back continuous improvement. If you want change, you first need to be willing to change. |
- 1 of 49
- ››