The Latest
Scrumdamentalism[magazine] It's been said that, over time, charismatic movements often evolve to become "bureaucratic"—focused on a set of standardized procedures that dictate the execution of the processes within the movement. Has Scrum evolved to this point or is there still a place for agility in our processes? |
||
IDEs and Build Scripts[magazine] Teams benefit from using both IDEs like Eclipse and integration tools like Maven. Steve Berczuk discusses the risks that can occur when IDEs and build scripts diverge, and provides guidelines for keeping the two consistent, so that teams can be more productive. |
||
It Takes a Village[magazine] Pair programming is an Agile practice that has been shown to greatly improve code quality without a huge increase in development time. This article explains the ins and outs of pair programming and some things you need to consider before you tell team members to grab a partner and get programming. |
||
Software Longevity Testing: Planning for the Long Haul[magazine] How long do you let your software run during testing? An increasing number of software applications are intended to run indefinitely, in an always-on operating environment. And yet, few test plans include more than a brief memory leak test case. Learn how to test for problems due to the passing of time and problems due to cumulative usage. |
||
The Whos and Wheres of Stakeholder Requirements[magazine] Whether you're working on a collocated or a distributed team, it's important to take stakeholder requirements into account: "Who" are they and "where" are they located? In this article, Mary Gorman offers some tips to help you narrow the gap between thinking and acting globally and locally. |
||
Rescuing a Captive Project[magazine] Allowing an individual to hold a project hostage to his knowledge and expertise is bad for the project and for the team. Fiona Charles describes one captive project and shows how it could have been remedied. |
||
Food for Thought[magazine] Ideas about testing can come from many different and unexpected sources, including reductionism, agronomy, cognitive psychology, mycology, and general systems. Michael feasts on Michael Pollan's "The Omnivore's Dilemma" and finds much to whet the tester's appetite for learning about how things work. |
||
A Manager's Role in Agile Development: The Light Bulb Moment[article]
Video
Michele Sliger shares stories about how agile adoption has affected people like you and how it has changed individuals—their perceptions of agile, their leadership styles, and even their personal lives. |
||
The Cost of Coexistence[article] Some organizations want to make the transition to agile, but aren't ready to trade in their old ways overnight. They'd rather spend some time getting to know agile—letting it coexist alongside already established, traditional methodologies. In this article, Michele Sliger and George Schlitz explain that such coexistence is possible, but that there is a cost of coexistence of which all organizations should be aware. |
||
Software as a Service: What You Need to Know[presentation] Many familiar products, including email, instant messaging, search, and e-commerce sites, are actually implemented as services rather than PC-installed software. |
Ibrahim El Far, Microsoft Corporation
|
|
How Others See You: Seeking Personal Feedback[presentation] Has this ever happened to you? You've just finished an important presentation. |
Esther Derby, Esther Derby Associates Inc
|
|
Five Test Automation Fallacies that Will Make You Sick[presentation] Five common fallacies about test automation can leave even the most experienced test and development teams severely ill. If allowed to go unchallenged, these beliefs will almost guarantee the death of an automation effort. |
Douglas Hoffman, Software Quality Methods, LLC.
|
|
Communicating the Meaning Inside the Metrics[presentation] Measurement data is supposed to help you make better decisions; yet, the information provided under the term "metrics" is often confusing, obscure, or irrelevant to those who need it most. |
Terry Vogt, Booz Allen Hamilton
|
|
Creating Habitable Code[presentation] A major challenge for software organizations is to create software that can continue to adapt and change over time-a codebase the team can live with "forever." Jeffrey Fredrick and Paul Julius review the concepts and features of CruiseControl |
Jeffrey Fredrick, Independent Consultant
|
|
A Solid Foundation for Quality Improvement[presentation] Many managers look to formal techniques-requirements reviews, code inspection, and testing-to improve the quality of their software. While these techniques are valuable, they only evaluate the state of quality rather than improve it. |
Jason Bryant, Schlumberger Information Solutions
|