|
Six Behaviors to Consider for an Agile Team If you've been tasked with creating an agile team, first consider what differentiates an agile team from a non-agile team. In this column, Johanna Rothman highlights six behaviors of people on successful agile teams that candidates for an agile team should possess.
|
|
|
Us Against Them How well does creating an opposing force serve to deliver on shared objectives within the same organization? A stronger argument may be to teach both business stakeholders and delivery personnel to reach across organizational boundaries to share not only the vision but also the methods used to achieve it.
|
|
|
Broken Windows, Broken Projects A social experiment in the ‘80s found “Vandalism can occur anywhere once communal barriers are lowered by actions that seem to signal that 'no one cares.'" The same can be said for our software projects.
|
|
|
The System Behind The Behavior Most managers are familiar with using feedback and coaching to help people improve their performance at work. But those aren't the only tools managers have. Sometimes, the most effective way to change individual behavior is to change something in the system.
|
|
|
Is Your Agile Audit and Compliance Process Really Agile? In a previous column, George Schlitz proposed that process improvements, such as agile, require organizations to change process rules. Now George continues his review of agile in regards to compliance and auditing practices. What he's found is that changes to compliance and auditing rules may appear compatible, but the implementation process usually remains unchanged and conflicts with agile practices.
|
|
|
Taming Bug Reports and Defects: The Agile Way Software defects bug everyone. If your organization is like most and you have a large queue of defects waiting to be fixed, this session is for you. It's probably not realistic to think we'll get around to fixing all of these bugs; so, we need to consider another approach. Lisa Crispin explains how agile teams address defects and how you can apply an agile approach to defects whether or not your development approach is "agile." Explore with Lisa ways to deal with a giant pile-or database-of old bug reports and which of the many, available defect tracking systems to consider-if you need one at all. See examples of alternatives to traditional bug reporting and how to shift your team's mindset toward preventing bugs in the first place. Get new ideas for taming your backlog of defects and discover ways your team can work together to minimize or eliminate bug reports all together.
|
Lisa Crispin, ePlan Services, Inc.
|
|
Keys to a Successful Beta Testing Program Your company is ready to launch its new product. How will it perform under real-world conditions? Will it meet the needs and expectations of the users? Will it operate on all the platforms and configurations for which it was designed? With the future of the product, your company, and perhaps your job depending on the answers, beta testing is a great way to maximize your chances of success. Beta testing provides empirical metrics that prove or disprove that your product will meet clients’ expectations, providing you with input for necessary course corrections in the product. Rob Swoboda explains the process of beta testing as well as the key concepts needed to plan, execute, and evaluate a successful beta testing effort. Rob shares his insights into the practices he employs to design and manage high-priority beta test efforts and offers you the keys to succeed in your own beta test program.
|
Rob Swoboda, HomeShore Solutions
|
|
The Power of Risk Erik Boelen starts his risk-based testing where most others stop. Too often, risk-based test strategies are defined in the initial test plan and are never looked at or used again. Erik explores how a dynamic, living risk-based testing strategy gives testers a vital tool to manage and control testing activities and identify the infrastructure they need to perform these activities. Find out how to use your risk-based testing strategy as a tool for negotiations among the different stakeholders. Take on the important role of risk mediator for all of the parties in the project. The risk-based test strategy is a tool you can use to defend testing’s need for time and resources, especially when late delivery is possible. Use your risk-based strategy to drive and manage exploratory testing sessions.
|
Erik Boelen, QA Consult Services
|
|
Creating the Right Environment for Mobile Applications Testing Is your organization releasing applications that target multiple mobile devices, platforms, or browsers? If so, you have faced-or soon will face-the challenge of choosing and setting up a test environment for these devices and platforms. Nat Couture shows how to develop a cost-effective application test environment to mitigate the risks associated with deploying mobile applications. He shares his latest research on mobile devices, mobile platforms, and mobile browser usage, and explains in detail what you need to consider when choosing a test environment. Learn how to select a winning combination of device-specific simulation, platform-specific simulation, and browser-specific simulation-coupled with tests on the actual devices. Build a mobile device testing program that reduces cost, increases coverage, and helps achieve the level of confidence you need to release mobile applications into production.
|
Nat Couture, Professional Quality Assurance Ltd.
|
|
Enabling Agile Testing through Continuous Integration Continuous integration is one of the key processes that support an agile software development and testing environment. Sean Stolberg describes how a traditional software tester-transitioning to an agile development environment-put a continuous integration infrastructure in place. In doing so, he helped improve development practices and made possible his team’s transition to agile testing. Sean discusses his team’s initial motivations for adopting agile development practices and dives into the nuts-and-bolts implementation details. He shares their post-assessment of the implementation using Martin Fowler's “Practices of Continuous Integration” and concludes with a retrospective on implementing and promoting continuous integration within the context of agile testing. Find out how continuous integration can help improve your testing results and the quality of the software your team delivers.
|
Sean Stolberg, Pacific Northwest National Laboratory
|