Collaboration: At the Extremities of Extreme
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Mark Levison on May 13, 2008
Integrating Testers into the team is an oft repeated Agile mantra, but we don't spend much time thinking about what it means or how to do it.
What is the role of testers on the team? To:
Compiled from (Cem Kaner, Johanna Rothman (pdf), and Jonathan Kohl).
Testing as part of an Agile team is quite different experience than most are used to. As Jonathan Kohl, co-founder of Kohl Concepts, notes: "The difference is that on an agile project, we find the important bugs faster. We are more involved with testing throughout development. Now that the developers are doing rigorous work themselves with solid automated unit tests, the products I test are much more robust."
Antony Marcano, Independent agile testing consultant, talks about the lessons he's learned:
On Simon Baker's team, co-founder of Energized Work, the developers write most of the acceptance tests. This frees the testers to do Exploratory Testing, work with the Product Owner to connect with the customer and help the team understand the users (not just the stories). Developers work on vertical slices (small parts of stories) that satisfy specific acceptance criteria. When the slice is complete the developer works with the tester to explore the slice and understand the acceptance test. The team treats defects as a stop the line event. Either the developer fixes it in the next slice or if its no longer under development a defect task is created. The defect task becomes the highest priority task for the team. Testers find that although they use the same skills, they spend a lot more time collaborating with peers and less time filing bugs.
Transforming Software Delivery: An IBM Rational Case Study
Case Study: IBM's Agile Transformation
Five Key Practices to Agile ALM
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
No comments
Watch Thread Reply