Rob has more than thirty years of management experience, leading teams of software development professionals. A well-respected member of the software engineering community, Robert has managed, trained and mentored thousands of top professionals. He often speaks at conferences & writes on software engineering, testing, management, and internationalization. Author of I am a Bug!, the popular testing children’s book, Robert is an adjunct prof at McGill University & runs the consultancy AmiBug.Com
Friday 13.00 - 13.50 in: Keyboard Cat
Whiteboarding for Testers, Developers and Customers too
Rob Sabourin, AmiBug.com
How can testers spend more time doing productive testing and waste less effort preparing "useless" project documentation? Whiteboarding techniques enable powerful communication and collaboration without all the paperwork. Rob Sabourin has used whiteboarding to help identify technical risks, better understand user needs and to focus testing on what really matters to business stakeholders.
Whiteboards can be used to communicate between testers, developers and customers. Whiteboarded block diagrams can visulaize technical risk. Whiteboarded fault models can highlight failure modes. Testers can elicit usage scenarios directly from customers using story boards diagrams.
Rob Sabourin shows how simple whiteboarding strategies help testers learn, help testers design tests and help testers estimate their activities.
Whiteboarding allows testers to collaborate with developers, customers and other testers to solve complex problems.
Rob share his experiences whiteboarding of all sorts of visual models: block diagrams, time sequences, story boards, state models, control flows, data flows and mind maps to name a few.
What is the Big Message?
Whiteboard for Powerful communication and collaboration without the need for heavy documentation
What are the Practical Take Aways?
Testers can use whiteboards to
Identify technical risks
Understand user requirements
Focus testing on what really matters
What is the Wow?
whiteboarding leads to improved tester
Wednesday 10.00 - 16.30 in: TBA
This tutorial takes place at Øredev on Wednesday and requires special registration. Please register normally for the Øredev conference. In addition, please send an e-mail to firstname.lastname@example.org.
Dealing with Software Project Turbulence
Turbulent development projects experience almost daily requirements changes, user interface modifications, and the continual integration of new functions, features, and technologies. Keep your testing efforts on track while reacting to changing priorities, technologies, and user needs. This interactive workshop offers a unique set of tools to help you cope with—and perhaps even flourish in—what may seem to be a totally chaotic environment. Practice dynamic test planning, test idea development and test triage.
Getting Ready for Almost Anything They Can Throw at You
Learn to identify, organize, and prioritize your testing “ideas”. Adapt the testing focus as priorities change. Decide on purpose—what not to test not just because the clock ran out!
Real Techniques Proven in Real Projects
Just-In-Time Testing (JIT) approaches are successfully applied to many types of software projects—commercial off-the-shelf applications, agile and iterative development environments, mission-critical business systems, and just about any Web application. Real examples demonstrate how JIT testing either replaces or complements more traditional approaches. Examples are drawn from insurance, banking, telecommunications, medical, and other industries. The course is packed with interactive exercises in which students work together in small groups to apply JIT testing concepts.
Who Should Attend
This course is appropriate for anyone who works in fast-paced development environments, including test engineers, test managers, developers, QA engineers, and all software managers.
1-Day Course Outline
Testing as soon as possible
Testing as late as possible
Basis for Just-In-Time testing
Be prepared-what you need
Exercise: Nature of Testing
Test ideas-what to test
Usage scenarios and data
Requirements and design documents
Capabilities and domains
Exercise: Creative test idea generation
Focus Planning and Prioritization
What not to test
Consequences and benefits of skipping
Consequences of implementing
Adapting to project context for triage
Exercise: Testing triage practice session