Terry Wiegmann writes about how Microsoft Word's features, like its spelling and grammar checkers, can help one identify agile smells—those signs that something might be wrong. While we may want to minimize documentation and the use of Word, we can mentally use some of Word’s features to sniff out some whiffs of smells.
Marcia Rose Sweezey and Stefan Visuri explain two best practices that are defined for agile teams in their organization. Read on to discover how externalizing strings and conducting pseudo-language testing during each iteration and sprint will give you the most payback for the least investment.
Every time we look at the data, we perform an analysis that helps us make decisions—hopefully the right ones. In this article, Gil Zilberfeld describes a few traps where bug data misled him to make bad decisions. These traps are in the data itself, not the tools, and can lead us in the wrong direction.
In this roundup of noteworthy quotes from industry experts interviewed in 2013, read about what constitutes effective agile methods, the year in testing techniques, and why you shouldn't put too much trust in the latest and greatest tools.
Anthony Akins explains how he used agile methods to modify the way he mowed his lawn. Learn how any project can benefit from using an agile approach and how large projects can be broken down into smaller chunks, each complete and with value.
Have you heard the old maxim “What gets measured gets done”? Management expert Peter Drucker said it, and here, Bill Donaldson shows us how a smart manager uses visual management to apply measurement to change what gets done.
Kenneth Grant explains whether or not being agile is really as cheap for an organization as its proponents claim it to be. Agile’s relentless focus on business value and just-enough work can help teams identify waste—or poor return on investment (ROI) requirements—and gives them the opportunity to change it or leave it out all together.
Mariya Breyter explores the role of a ScrumMaster and whether or not one can work effectively when working remotely. If the ScrumMaster is not available to orchestrate product delivery, bridge any gaps, and remove any obstacles, a product will never be delivered—even worse, a wrong product will be delivered. In order to achieve this understanding, the ScrumMaster must show value to the team as a natural leader, no matter if he is onsite or remote.
Did you ever wonder if a team needs some prerequisites before transitioning to agile? In this true story, John Lynch shows us the story of a team who teetered on the brink of dysfunction and then was able to create its foundation so team members could begin their agile transition.
In order to be successful in the ring, a sumo wrestler needs to maintain a heavy body weight and at the same time be in peak physical condition. Just as these Japanese athletes have to find the right balance through a well thought-out combination of diet and training regimen, software development organizations need a balanced approach to implementing application architecture on agile projects.