| |
On great agile teams, conflict is constant and welcomed by all as a catapult to higher performance. It is about human beings working together, day after day, in the maelstrom of constant collaboration and change. In this turbulence, how can teams chart a course through conflict and turn it into a force for greatness? Lyssa Adkins reveals a conflict model that helps you do just that, walking you through five levels of conflict from "Problem to Solve" to "World War," with each step finely tuned to view conflict in a deeply human and humane way.
| |
| |
Agile software processes vary in detail, depth, impact, and endurance as much as painting styles like graffiti differ from Baroque or Impressionist art. What can artists teach us about successful agile transitions, and what can past agile transitions teach us about styles that endured or faded away? Joshua Kerievsky maps agile transitions to art styles and identifies elements that lead to success or failure, offering an excellent perspective on the art of agile transitioning and what style(s) will work best for you.
| |
| |
Testers make decisions every day that are just as irrational as those made by the managers about whom they complain. In this video, James Lyndsay presents his view of tester bias, such as: why we so often labor under the illusion of control, how we lock onto the behaviors we're looking for, and how two testers can use the same evidence to support opposing positions.
| |
| |
Manual testing is the best way to find the bugs most likely to bite users badly after a product ships. However, manual testing remains a very ad hoc, aimless process. At a number of companies across the globe, groups of test innovators gathered in think tank settings to create a better way to do manual testing--a way that is more prescriptive, repeatable, and capable of finding the highest quality bugs. The result is a new methodology for exploratory testing based on the concept of tours through the application under test. In short, tours represent a more purposeful way to plan and execute exploratory tests. James Whittaker describes the tourist metaphor for this novel approach and demonstrates tours taken by test teams from various companies including Microsoft and Google. He presents results from numerous projects where the tours were used in critical-path production environments. Learn about the collection of test tours, test cases, and bugs from these case studies and recommendations for using tours on your own products.
| |
| |
Even with the best tools and processes in the world, if your staff is not focused and productive, your testing efforts will be weak and ineffective and your finished product will reflect this. Retired Marine colonel and long-time test consultant Rick Craig describes how using the Marine Corps Principles of Leadership will help you become a better leader and, as a result, a better test manager or tester.
| |
| |
Ray Arell read an agile project management book on a long flight to India, and, like all good reactionary development managers, he was sold. But the agile/Scrum adoption was not without strain on development, test, and other QA practices. Join Ray on a retrospective of what went right and, more importantly, what went wrong. If agile is in your future, come discover what you're in for, traps to avoid, and how to be successful. If you're not ready for agile, you'll learn some new approaches that can be applied to traditional processes.
| |
| |
Because agile teams are supposed to be self-organizing, many of the "classic" management tasks are no longer important or even appropriate. 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. Learn about the transformations of managers who clearly recall their "light bulb moment," the moment when they realized what their new identities would be in the agile development world.
| |
| |
Are we, in our rush to be "agile," losing sight of what's really important? Shouldn't our dilemma be whether we are creating software our customers value? If your processes and tools deliver software that your customers value, does it matter how "agile" you are? In this video, Jonathan Kohl looks at why and for whom we develop software, what our end users and team members value, and the difference between tools and processes that create value and those that distract from it.
| |
| |
In this video from the STAREAST 2009 Interactive Lounge, Michael Bolton takes a look at two subjects--a 17th century debate over the air pump and the difference between experience and experiments--and how they relate to the software testing of today and tomorrow.
| |
| |
In this video from STAREAST 2009, tester and author James Bach talks about the context-driven school of software testing, his latest book, and how both the history of ideas and the discovery of oxygen can be connected to software testing.
| |
| | | |