agile transition
 |
5 Tips for Making the Most of Your Agile Meetings People think agile entails too many meetings, but usually that complaint has nothing to do with the number of meetings, but rather the way they're run. New agile teams often do everything together because they think that’s what agile expects, but that's not true. Here are five tips to better run your agile meetings. |
|
 |
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. |
|
 |
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. |
|
 |
Thanks to Agile, You Can No Longer Be a Selfish Tester You achieve much greater things if you trust your testing team and focus on the entire software lifecycle rather than your own personal goals. Over the years, agile has made it difficult to be both selfish and successful as a tester. |
|
 |
3 Common Collaboration Problems for Teams Transitioning to Agile A shift toward working in smaller teams on tighter releases forces organizations adopting agile to rethink what successful delivery looks like. It can be a big change for those used to silos. Here are three key symptoms of agile teams that don’t have close collaboration—and some solutions you can implement to fix them. |
|
 |
3 Reasons Exploratory Testing Is Great for Agile Teams Specification-based testing is critical for determining whether a user story is “done done.” But that doesn’t ensure a positive user experience. Coherence, comprehension, and usability are beyond the scope of automated functional testing. Here are three reasons agile teams should embrace exploratory testing. |
