TN PM Tutorial 4/30/13 1:00PM Collaboration Techniques: Combining New Approaches with Ancient Wisdom Presented by: Rob Sabourin, AmiBug.com Dorothy Graham, Software Test Consultant Brought to you by: 340 Corporate Way, Suite 300, Orange Park, FL 32073 888-268-8770 ∙ 904-278-0524 ∙ [email protected]∙ www.sqe.com
15
Embed
Collaboration Techniques: Combining New Approaches with Ancient Wisdom
In our increasingly agile world, the new buzzword is collaboration—so easy to preach but difficult to do well. Testers are challenged to work directly, effectively, efficiently, and productively with customers, programmers, business analysts, writers, trainers, and pretty much everyone in the business value chain. Many points of collaboration exist: grooming stories with customers, sprint planning with team members, reviewing user interaction with customers, troubleshooting bugs with developers, whiteboarding with peers, and buddy checking. Rob Sabourin and Dot Graham examine what collaboration is, why it is challenging, and how you can do it better. Join Rob and Dot to learn about forgotten but proven techniques, such as risk-based objectives, checklists, entry and exit criteria, diverse roles, cross-checking, and root cause analysis. These techniques can help you work more efficiently, improve your professional relationships, and deliver quality products. Bring your own stories of collaboration—good and bad—and see how forgotten wisdom can help improve today’s practices.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
TN PM Tutorial
4/30/13 1:00PM
Collaboration Techniques: Combining
New Approaches with
Ancient Wisdom
Presented by:
Rob Sabourin, AmiBug.com
Dorothy Graham, Software Test Consultant
Brought to you by:
340 Corporate Way, Suite 300, Orange Park, FL 32073
Rob Sabourin, P. Eng., has more than thirty years of management experience leading teams of software development professionals. A well-respected member of the software engineering community, Rob has managed, trained, mentored, and coached hundreds of top professionals in the field. He frequently speaks at conferences and writes on software engineering, SQA, testing, management, and internationalization. Rob wrote I am a Bug!, the popular software testing children's book; works as an adjunct professor of software engineering at McGill University; and serves as the principle consultant (and president/janitor) of AmiBug.Com, Inc. Contact Rob at [email protected].
Dorothy Graham In testing for more than thirty years, Dorothy Graham is coauthor of four books—Software Inspection, Software Test Automation, Foundations of Software Testing, and Experiences of Test Automation: Case Studies of Software Test Automation. Dot was a founding member of the ISEB Software Testing Board, a member of the working party that developed the first ISTQB Foundation Syllabus, and served on the boards of conferences and publications in software testing. A popular and entertaining speaker at conferences and seminars worldwide, she has been coming to STAR conferences since the first one in 1992. Dot holds the European Excellence Award in Software Testing. Learn more about Dot at DorothyGraham.co.uk.
Forgotten Wisdom from Ancient Testers • Collaboration has become a new testing cliché. But it is hard to do. Testers are challenged
to work directly with customers, programmers, business analysts and other stakeholders. They have less time with more at stake. They must apply skills outside their experience, knowledge and comfort zones.
• Dorothy Graham (Dot) and Robert Sabourin (RobSab) have fostered excellent collaboration applying wisdom of some ancient testing concepts, born in the dark ages of software engineering, methods from a forgotten era of turbulence, flakey technology and overtly ambitious project managers.
• “Static testing” practices like inspections, reviews and walkthroughs helped teams systematically learn, explore and evolve, by identifying concerns, and redirecting or refactoring development efforts as early as possible in lifecycles. Dot and Rob show how they have managed to capture excellence, identify weakness and learn from mistakes as part of testing tasks through interactions between team members, stakeholders and other unlikely contributors too.
• Understand client needs and values by grooming stories. Brainstorm with programmers about design solutions and associated technical risks. Pair up with programmers, to focus on what can break, with other testers to avoid rat holes and with domain experts to assess correctness. Use examples to anchor understanding and highlight differences.