EuroSTAR Software Testing Conference 2010 presentation on The Testers Toolbox by Graham Thomas. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Herman- Pieter Nijhof - Where Do Old Testers Go?TEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Where Do Old Testers Go? by Herman- Pieter Nijhof. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Michael Bolton - Heuristics: Solving Problems RapidlyTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Heuristics: Solving Problems Rapidly by Michael Bolton. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
The Snail Entrepreneur: The 7-year-old kid every startup should learn fromClaudio Perrone
Matteo faced a seemly impossible problem, but didn't give up. He used daddy's #PopcornFlow and pivoted. 17 options and 5 experiments later, he converged to success.
PopcornFlow is impacting businesses (large and small) but also families and kids.
If you like this story, please contribute to Matteo's cause.
A Rapid Introduction to Rapid Software TestingTechWell
You're under tight time pressure and have barely enough information to proceed with testing. How do you test quickly and inexpensively, yet still produce informative, credible, and accountable results? Rapid Software Testing, adopted by context-driven testers worldwide, offers a field-proven answer to this all-too-common dilemma. In this one-day sampler of the approach, Paul Holland introduces you to the skills and practice of Rapid Software Testing through stories, discussions, and "minds-on" exercises that simulate important aspects of real testing problems. The rapid approach isn't just testing with speed or a sense of urgency; it's mission-focused testing that eliminates unnecessary work, assures that the most important things get done, and constantly asks how testers can help speed up the successful completion of the project. Join Paul to learn how rapid testing focuses on both the mind set and skill set of the individual tester who uses tight loops of exploration and critical thinking skills to help continuously re-optimize testing to match clients' needs and expectations.
This document discusses various agile concepts including popcorn flow, jobs to be done, and continuous evolution. It describes how popcorn flow uses lightweight experiments to continuously evolve work and accelerate learning. It also discusses how focusing on the "jobs" customers need done rather than assumed wants can help create more valuable innovations and disrupt existing solutions. The overall message is that through approaches like popcorn flow and jobs to be done, organizations can continuously and rapidly improve their work and offerings to better meet customer needs.
When confronted with a problem, have you ever stopped and asked "why" five times? The Five Whys technique is a simple but powerful way to troubleshoot problems by exploring cause-and-effect relationships.
5 Whys: Originally developed by Sakichi Toyoda and used within the Toyota Motor Corporation during the evolution of its manufacturing methodologies, 5 Whys is a basic component of problem-solving. By asking ‘Why’ 5 times it encourages the problem solver to avoid assumptions and logic traps and trace the chain of causality from the effect seen through to a root cause. The real root cause should point toward a process that is not working well or does not exist.
Herman- Pieter Nijhof - Where Do Old Testers Go?TEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Where Do Old Testers Go? by Herman- Pieter Nijhof. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Michael Bolton - Heuristics: Solving Problems RapidlyTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Heuristics: Solving Problems Rapidly by Michael Bolton. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
The Snail Entrepreneur: The 7-year-old kid every startup should learn fromClaudio Perrone
Matteo faced a seemly impossible problem, but didn't give up. He used daddy's #PopcornFlow and pivoted. 17 options and 5 experiments later, he converged to success.
PopcornFlow is impacting businesses (large and small) but also families and kids.
If you like this story, please contribute to Matteo's cause.
A Rapid Introduction to Rapid Software TestingTechWell
You're under tight time pressure and have barely enough information to proceed with testing. How do you test quickly and inexpensively, yet still produce informative, credible, and accountable results? Rapid Software Testing, adopted by context-driven testers worldwide, offers a field-proven answer to this all-too-common dilemma. In this one-day sampler of the approach, Paul Holland introduces you to the skills and practice of Rapid Software Testing through stories, discussions, and "minds-on" exercises that simulate important aspects of real testing problems. The rapid approach isn't just testing with speed or a sense of urgency; it's mission-focused testing that eliminates unnecessary work, assures that the most important things get done, and constantly asks how testers can help speed up the successful completion of the project. Join Paul to learn how rapid testing focuses on both the mind set and skill set of the individual tester who uses tight loops of exploration and critical thinking skills to help continuously re-optimize testing to match clients' needs and expectations.
This document discusses various agile concepts including popcorn flow, jobs to be done, and continuous evolution. It describes how popcorn flow uses lightweight experiments to continuously evolve work and accelerate learning. It also discusses how focusing on the "jobs" customers need done rather than assumed wants can help create more valuable innovations and disrupt existing solutions. The overall message is that through approaches like popcorn flow and jobs to be done, organizations can continuously and rapidly improve their work and offerings to better meet customer needs.
When confronted with a problem, have you ever stopped and asked "why" five times? The Five Whys technique is a simple but powerful way to troubleshoot problems by exploring cause-and-effect relationships.
5 Whys: Originally developed by Sakichi Toyoda and used within the Toyota Motor Corporation during the evolution of its manufacturing methodologies, 5 Whys is a basic component of problem-solving. By asking ‘Why’ 5 times it encourages the problem solver to avoid assumptions and logic traps and trace the chain of causality from the effect seen through to a root cause. The real root cause should point toward a process that is not working well or does not exist.
This is a summary of the blogs by Eric Ries on the Five Whys at http://startuplessonslearned.blogspot.com/2008/11/five-whys.html. It was used for an internal presentation at Cogent Consulting. If Eric or anyone else thinks this should not be public I will take it down, but I hope I'll drive (a little) more traffic to his blog :-)
This document discusses reducing test case bloat. It defines test case bloat as having more test cases than can effectively be managed within the available time. The author recommends finding and removing unnecessary test cases through methods like prioritizing by importance, change-based filtering, and code coverage analysis. Barriers to reducing bloat include risk aversion, sunk costs, and cultural resistance to change. The author encourages testers to evaluate which test cases still provide value and to continuously refine test suites through pruning.
Witness wednesdays informing agile software development with continuous user...Rebecca Destello
In the startup world speed to market is everything.
This talk covers how it is possible to embed user insights into a rapid software development cycle by conducting usability studies that break the stereotype that "research takes too long."
Justin Marx and Rebecca Destello illustrate how to plan, conduct, analyze and inform development sprints in just one week with what famously became known as "Witness Wednesdays."
Justin Marx, Product Designer and Rebecca Destello, Manager, Research & Insights - both with Atlas Informatics.
The document discusses root cause analysis (RCA), a problem-solving method aimed at identifying the underlying causes of problems. RCA seeks to address root causes rather than superficial symptoms, in order to minimize the likelihood of recurrence. It should be performed systematically and conclusions backed by evidence. Examples demonstrate using the "5 Whys" technique to trace a problem back to its root cause by asking "Why?" in iterative steps. Criticism notes the difficulty of truly identifying a single root cause, and that addressing actionable causes may be more practical.
The document discusses the OODA (Observe, Orient, Decide, Act) loop, which is a model for decision making developed by military strategist John Boyd. It involves observing a situation, orienting oneself, making a decision, and taking action, then observing the results and repeating the process. The document provides examples of how the OODA loop applies to systems like thermostats, product development, and military strategy. It also discusses how organizations can get inside an opponent's decision cycle by pushing decision making down hierarchies and moving faster through the OODA loop.
It is well known that the decision-making process within companies presents some critical issues.
The purpose of this brief presentation is to adopt a decision model, starting from what was elaborated by John Boyd and which goes under the name of ‘’O.O.D.A. loop’’.
A Rapid Introduction to Rapid Software TestingTechWell
This document provides a summary of a presentation on Rapid Software Testing. The presentation was given by Michael Bolton of DevelopSense and covered the methodology and mindset of rapid software testing. It emphasizes testing software expertly under uncertainty and time pressure. The presentation defines rapid testing as testing more quickly and less expensively while still achieving excellent results. It compares rapid testing to other approaches like exhaustive, ponderous, and slapdash testing. The presentation also discusses principles of rapid testing, how to recognize problems quickly using heuristics, and testing rapidly to fulfill the mission of testing.
This document discusses effort estimation techniques for projects. It describes estimating as forming a judgment about the work required, and mentions common techniques like decomposition, expert judgment, analogy, and planning poker. It also covers risk identification and adding buffers to estimates and schedules to account for risks and uncertainties. Key points emphasized are estimating in hours or days, adding 25% to total costs for buffers, and that more estimation perspectives improve the accuracy and consensus of estimates.
Interface Design for Elearning - Tips and TricksJulie Dirksen
The document provides tips and guidelines for designing effective user interfaces for learning environments. It discusses principles of user interface design such as reducing extraneous cognitive load on users. Specific tips include using an F-shaped reading pattern to structure content, embedding instructions in the interface context, and testing designs with users. The key recommendation is that interface design should make tasks easy to complete while keeping users engaged in the learning process.
EuroSTAR Software Testing Conference 2010 presentation on Weekend Testing, Skilled Software Testing Unleashed by Ajay Balamnrugadas. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
General introduction to agile practices like Scrum and Kanban. Also covers what situations Agile is best at, what situations Agile doesn't help with, and what an Agile team should look like. This deck is a general intro to Agile for OpenSource Connections clients.
Presentation by Mike Rylander at Code4Lib 2007 in Athens, GA.
At PINES we have the luxury of a very supportive administrative team. Through trial and error over the last three years we have had the chance to glean a set of do's and don'ts for the building of a successful in-house development team and environment. We would like to share our experience in the hope that others may be able to duplicate our successes and avoid our missteps at all levels, from developers on up to management.
The document discusses context driven testing, which focuses on 7 principles: 1) the value of practices depends on context, 2) there are good practices in context but no best practices, 3) people are most important, 4) projects change unpredictably, 5) products must solve problems, 6) testing is challenging, and 7) judgment is needed. It provides examples of the principles in action like dangerous metrics and passed tests not ensuring problems won't occur. Context driven testing values individuals and interactions over processes, working software over documentation, and responding to change over plans. It believes in documentation and automation but communication and tools, respectively, are more important.
The document discusses the 3 E's of #NoEstimates in software development: Ethics, Empiricism, and Emergence. Regarding Ethics, it argues that estimates can encourage dishonesty and focusing on schedules over customer value. For Empiricism, it notes that estimates are often guesses rather than data-driven and that monitoring progress should focus on solving problems rather than hitting estimates. For Emergence, it discusses how requirements, designs, costs and values emerge through iterative development rather than being pre-determined by estimates.
The document discusses issues facing libraries and proposes strategies for addressing them. It focuses on the problems with current library software and promotes adopting the open source library system Evergreen as a solution. The summary promotes Evergreen by focusing on its cost-effectiveness and support model while addressing common concerns directors have about open source software.
Changing business of testing - Testing Assembly Helsinki 2014Vasco Duarte
Testing jobs will move to cheaper countries unless the role of testing changes. This is a trend that is happening already, we see large teams of testers being moved to other countries, simply because it is cheaper to do bad testing there!
Testing is a critical part of the product and software development process, and if we don't change its role it will slowly become obsolete. The fact is, that the traditional view of testing endangers testing jobs: now here, and later also in cheaper countries.
I propose a different view of testing. I propose that testing is about enabling business results, not just technical quality. I propose that the tester's job goes far beyond finding issues to track, but also finding users to acquire, finding methods to succeed in the software business. Testing in my view is about making businesses succeed, not about avoid failures in software.
In this presentation I'll describe how a very simple change can profoundly transform the role of testing in a way that it directly enables and supports our businesses! Testing is about making our businesses succeed!
The road ahead is not easy, and not every tester is ready to embrace this view of testing. But the road ahead is inevitable. And we have to start on that journey now!
10+ Testing Pitfalls and How to Avoid them PractiTest
Join Joel Montvelisky, PractiTest's chief solution architect in this webinar as he takes you through the common pitfalls of testing you need to be aware of and how to avoid them.
The document summarizes the agenda for the "Let's Test Context-Driven Software Testing Conference" in Stockholm, Sweden. The conference featured keynote speakers and tutorials on May 7-9, 2012 discussing context-driven testing approaches. Topics included stories-based testing, prioritizing bugs based on business impact, testing in unpredictable domains, moving beyond a pass/fail mindset, focusing on information over coverage metrics, and coaching other testers.
The document discusses moving from a defect reporting approach in software testing to a defect prevention approach using lean principles. It notes that preventing defects from the beginning is far more effective than finding faults later. It asks questions about the current state of testing and defect handling to determine opportunities to focus more on prevention activities like exploratory testing earlier and removing the root causes of defects.
This document discusses various cognitive biases that can affect testing, including anchoring bias, relativity bias, decoy effect, endowment effect, IKEA effect, confirmation bias, negativity bias, sunk costs fallacy, paradox of choice, and procrastination. It provides examples of how each bias could influence test planning, design, advocacy, estimation, negotiation, and other aspects of the testing process. The document concludes by acknowledging references used to research cognitive biases.
This document discusses formal methods in software engineering. It defines formal methods as mathematically-based techniques for specifying, developing, and verifying computer systems in a systematic way. Formal methods use formal logic to model systems and prove that models satisfy requirements. The document provides an example of applying formal methods to specify a water tank system that refills when low. Key steps include: 1) defining types and functions, 2) stating properties as logical statements, and 3) constructing proofs to show properties hold for all cases.
This is a summary of the blogs by Eric Ries on the Five Whys at http://startuplessonslearned.blogspot.com/2008/11/five-whys.html. It was used for an internal presentation at Cogent Consulting. If Eric or anyone else thinks this should not be public I will take it down, but I hope I'll drive (a little) more traffic to his blog :-)
This document discusses reducing test case bloat. It defines test case bloat as having more test cases than can effectively be managed within the available time. The author recommends finding and removing unnecessary test cases through methods like prioritizing by importance, change-based filtering, and code coverage analysis. Barriers to reducing bloat include risk aversion, sunk costs, and cultural resistance to change. The author encourages testers to evaluate which test cases still provide value and to continuously refine test suites through pruning.
Witness wednesdays informing agile software development with continuous user...Rebecca Destello
In the startup world speed to market is everything.
This talk covers how it is possible to embed user insights into a rapid software development cycle by conducting usability studies that break the stereotype that "research takes too long."
Justin Marx and Rebecca Destello illustrate how to plan, conduct, analyze and inform development sprints in just one week with what famously became known as "Witness Wednesdays."
Justin Marx, Product Designer and Rebecca Destello, Manager, Research & Insights - both with Atlas Informatics.
The document discusses root cause analysis (RCA), a problem-solving method aimed at identifying the underlying causes of problems. RCA seeks to address root causes rather than superficial symptoms, in order to minimize the likelihood of recurrence. It should be performed systematically and conclusions backed by evidence. Examples demonstrate using the "5 Whys" technique to trace a problem back to its root cause by asking "Why?" in iterative steps. Criticism notes the difficulty of truly identifying a single root cause, and that addressing actionable causes may be more practical.
The document discusses the OODA (Observe, Orient, Decide, Act) loop, which is a model for decision making developed by military strategist John Boyd. It involves observing a situation, orienting oneself, making a decision, and taking action, then observing the results and repeating the process. The document provides examples of how the OODA loop applies to systems like thermostats, product development, and military strategy. It also discusses how organizations can get inside an opponent's decision cycle by pushing decision making down hierarchies and moving faster through the OODA loop.
It is well known that the decision-making process within companies presents some critical issues.
The purpose of this brief presentation is to adopt a decision model, starting from what was elaborated by John Boyd and which goes under the name of ‘’O.O.D.A. loop’’.
A Rapid Introduction to Rapid Software TestingTechWell
This document provides a summary of a presentation on Rapid Software Testing. The presentation was given by Michael Bolton of DevelopSense and covered the methodology and mindset of rapid software testing. It emphasizes testing software expertly under uncertainty and time pressure. The presentation defines rapid testing as testing more quickly and less expensively while still achieving excellent results. It compares rapid testing to other approaches like exhaustive, ponderous, and slapdash testing. The presentation also discusses principles of rapid testing, how to recognize problems quickly using heuristics, and testing rapidly to fulfill the mission of testing.
This document discusses effort estimation techniques for projects. It describes estimating as forming a judgment about the work required, and mentions common techniques like decomposition, expert judgment, analogy, and planning poker. It also covers risk identification and adding buffers to estimates and schedules to account for risks and uncertainties. Key points emphasized are estimating in hours or days, adding 25% to total costs for buffers, and that more estimation perspectives improve the accuracy and consensus of estimates.
Interface Design for Elearning - Tips and TricksJulie Dirksen
The document provides tips and guidelines for designing effective user interfaces for learning environments. It discusses principles of user interface design such as reducing extraneous cognitive load on users. Specific tips include using an F-shaped reading pattern to structure content, embedding instructions in the interface context, and testing designs with users. The key recommendation is that interface design should make tasks easy to complete while keeping users engaged in the learning process.
EuroSTAR Software Testing Conference 2010 presentation on Weekend Testing, Skilled Software Testing Unleashed by Ajay Balamnrugadas. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
General introduction to agile practices like Scrum and Kanban. Also covers what situations Agile is best at, what situations Agile doesn't help with, and what an Agile team should look like. This deck is a general intro to Agile for OpenSource Connections clients.
Presentation by Mike Rylander at Code4Lib 2007 in Athens, GA.
At PINES we have the luxury of a very supportive administrative team. Through trial and error over the last three years we have had the chance to glean a set of do's and don'ts for the building of a successful in-house development team and environment. We would like to share our experience in the hope that others may be able to duplicate our successes and avoid our missteps at all levels, from developers on up to management.
The document discusses context driven testing, which focuses on 7 principles: 1) the value of practices depends on context, 2) there are good practices in context but no best practices, 3) people are most important, 4) projects change unpredictably, 5) products must solve problems, 6) testing is challenging, and 7) judgment is needed. It provides examples of the principles in action like dangerous metrics and passed tests not ensuring problems won't occur. Context driven testing values individuals and interactions over processes, working software over documentation, and responding to change over plans. It believes in documentation and automation but communication and tools, respectively, are more important.
The document discusses the 3 E's of #NoEstimates in software development: Ethics, Empiricism, and Emergence. Regarding Ethics, it argues that estimates can encourage dishonesty and focusing on schedules over customer value. For Empiricism, it notes that estimates are often guesses rather than data-driven and that monitoring progress should focus on solving problems rather than hitting estimates. For Emergence, it discusses how requirements, designs, costs and values emerge through iterative development rather than being pre-determined by estimates.
The document discusses issues facing libraries and proposes strategies for addressing them. It focuses on the problems with current library software and promotes adopting the open source library system Evergreen as a solution. The summary promotes Evergreen by focusing on its cost-effectiveness and support model while addressing common concerns directors have about open source software.
Changing business of testing - Testing Assembly Helsinki 2014Vasco Duarte
Testing jobs will move to cheaper countries unless the role of testing changes. This is a trend that is happening already, we see large teams of testers being moved to other countries, simply because it is cheaper to do bad testing there!
Testing is a critical part of the product and software development process, and if we don't change its role it will slowly become obsolete. The fact is, that the traditional view of testing endangers testing jobs: now here, and later also in cheaper countries.
I propose a different view of testing. I propose that testing is about enabling business results, not just technical quality. I propose that the tester's job goes far beyond finding issues to track, but also finding users to acquire, finding methods to succeed in the software business. Testing in my view is about making businesses succeed, not about avoid failures in software.
In this presentation I'll describe how a very simple change can profoundly transform the role of testing in a way that it directly enables and supports our businesses! Testing is about making our businesses succeed!
The road ahead is not easy, and not every tester is ready to embrace this view of testing. But the road ahead is inevitable. And we have to start on that journey now!
10+ Testing Pitfalls and How to Avoid them PractiTest
Join Joel Montvelisky, PractiTest's chief solution architect in this webinar as he takes you through the common pitfalls of testing you need to be aware of and how to avoid them.
The document summarizes the agenda for the "Let's Test Context-Driven Software Testing Conference" in Stockholm, Sweden. The conference featured keynote speakers and tutorials on May 7-9, 2012 discussing context-driven testing approaches. Topics included stories-based testing, prioritizing bugs based on business impact, testing in unpredictable domains, moving beyond a pass/fail mindset, focusing on information over coverage metrics, and coaching other testers.
The document discusses moving from a defect reporting approach in software testing to a defect prevention approach using lean principles. It notes that preventing defects from the beginning is far more effective than finding faults later. It asks questions about the current state of testing and defect handling to determine opportunities to focus more on prevention activities like exploratory testing earlier and removing the root causes of defects.
This document discusses various cognitive biases that can affect testing, including anchoring bias, relativity bias, decoy effect, endowment effect, IKEA effect, confirmation bias, negativity bias, sunk costs fallacy, paradox of choice, and procrastination. It provides examples of how each bias could influence test planning, design, advocacy, estimation, negotiation, and other aspects of the testing process. The document concludes by acknowledging references used to research cognitive biases.
This document discusses formal methods in software engineering. It defines formal methods as mathematically-based techniques for specifying, developing, and verifying computer systems in a systematic way. Formal methods use formal logic to model systems and prove that models satisfy requirements. The document provides an example of applying formal methods to specify a water tank system that refills when low. Key steps include: 1) defining types and functions, 2) stating properties as logical statements, and 3) constructing proofs to show properties hold for all cases.
Formal methods are mathematically based techniques for specifying, designing, and verifying software systems. Formal specifications precisely state what software should do without describing how. Formal verification rigorously proves an algorithm's correctness against a specification using logical rules. While formal methods reduce errors, the cost of full formalization is often prohibitive for industry; lightweight formal methods employing partial specification and focused analysis are alternatives.
#1 formal methods – introduction for software engineeringSharif Omar Salem
formal methods – introduction for software engineering
Part of formal class notes of the module "Formal Methods"
designed for software engineering students of BSc. level.
Building Cognitive Applications with Watson APIs Dev_Events
This document discusses building cognitive applications using Watson APIs. It provides an overview of cognitive computing and machine learning, as well as a demonstration of using the Watson Java SDK to analyze text tone. The document discusses problems that cognitive applications can help solve, how machine learning has advanced to help with non-deterministic problems, and examples of cognitive applications already in use. It also demonstrates a sample cognitive application for conversational skills that is built with Watson services and deployed to Bluemix.
Cognitive Computing and the future of Artificial IntelligenceVarun Singh
This document discusses cognitive computing and artificial intelligence. It defines cognitive computing as systems that learn from experience and instructions to mimic human cognition by synthesizing information, finding patterns rather than exact answers, and interacting naturally with humans. Specific examples discussed are IBM's Watson, which uses natural language processing and machine learning to answer questions and make complex decisions from vast amounts of data. The document also discusses concerns about the future risks of artificial intelligence, such as superintelligent systems that humans may not be able to control and could ultimately replace humans.
This document provides an overview of Neuro-Linguistic Programming (NLP) and discusses how it can be used to change behaviors and achieve desired outcomes. It examines how people think, feel, communicate and build relationships. Key concepts discussed include setting goals, establishing rapport, using sensory acuity for feedback, and reprogramming beliefs and physiology through techniques like anchoring. The document also discusses strategies for eliciting a person's process for achieving different states and the role of physiology in changing feelings and health.
This document provides techniques for effective communication and persuasion. It discusses listening actively, understanding language patterns, body language cues, and asking questions strategically. The key points are:
1. Active listening techniques like maintaining eye contact, pausing before responding, and paraphrasing help ensure understanding.
2. People communicate differently based on their sensory preferences (visual, auditory, kinesthetic). Matching these preferences aids connection.
3. Body language cues like eye movements and pupil size indicate mental processes and interest levels.
4. Questions are powerful tools for starting conversations, gaining information, building rapport, and motivating others when used strategically and with the right intention.
This blog post provides tools and frameworks to help trainees build confidence when handling selection days and persuading others. It includes stories, activities, and frameworks to help people reflect on their strengths and beliefs, communicate effectively using logical and emotional appeals, and answer interview questions focusing on situations, actions, results and lessons learned. Models discussed include Bloom's Taxonomy, strengthsfinder, 4MAT presentation structure, and the iSPARK mnemonic for "tell me a time when" questions. The post also cautions against making assumptions and provides tips to recognize them.
This document provides guidance on building confidence through understanding one's strengths, effective communication, and motivation. It includes stories, activities, and tools to help people reflect on their beliefs, identify strengths, construct persuasive messages tailored to different learning styles, manage anxiety, and stay motivated through reframing negative thoughts. The overall aim is to help trainees and teachers feel more focused, confident and skilled in achieving their goals.
This document provides tools and frameworks to help build confidence when communicating with others to achieve goals. It discusses understanding strengths, focusing on positive beliefs, using structured models like 4MAT to address different learning styles, and highlighting achievements using tools like iSPARK to answer "tell me about a time" questions in interviews. Stories are also provided as examples. The overall aim is to help the reader present themselves and their messages effectively.
SXSW - Diving Deep: Best Practices For Interviewing UsersSteve Portigal
While we know, from a very young age, how to ask questions, the skill of getting the right information from users is surprisingly complex and nuanced. This session will focus on getting past the obvious shallow information into the deeper, more subtle, yet crucial, insights. If you are going to the effort to meet with users in order to improve your designs, it's essential that you know how to get the best information and not leave insights behind. Being great in "field work" involves understanding and accepting your interviewee's world view, and being open to what they need to tell you (in addition to what you already know you want to learn). We'll focus on the importance of rapport-building and listening and look at techniques for both. We will review different types of questions, and why you need to have a range of question types. This session will explore other contextual research methods that can be built on top of interviewing in a seamless way. We'll also suggest practice exercises for improving your own interviewing skills and how to engage others in your organization successfully in the interviewing experience.
3 techniques for high quality communication on your agile teamsAndrea Chiou
The document summarizes a workshop on using techniques like Clean Language and Systemic Modeling to foster better communication on agile teams. The workshop covered listening exercises, using Clean setup to clarify goals, providing structured feedback, and modeling best practices. About 45 people attended the 4-5pm session, though no questions were asked at the end due to people needing to leave on time. The presenter was glad to get feedback and will offer another longer workshop on the same topics.
Yes, My Iguana Loves to Cha-Cha: Improv, Creativity and CollaborationSteve Portigal
Improv is not "stand-up comedy." It's a series of games with rules that offer huge degrees of freedom within a set of constraints. In these games we bring out a lot of basic, quickly understood and communicated rules of culture that are implicit, not explicit. The activities of design (collaboration, creativity, and design research, for starters) have interesting similarities with improv: All have in-the-moment aspects; we learn upon reflection; there's enormous unspoken interaction and there is often an "aha" moment. Design and improv also have important similarities: the need to collaborate and brainstorm, the importance of breakthrough thinking, the balance between process, structure, and unfettered creativity.
Playing with improv can make us more mindful of the power of listening, and can be harnessed to create a more collaborative work culture, as a way to develop one's own creativity, or to help warm up teammates and clients in workshops and design sessions. In this interactive presentation you will learn more about improv, listening, creativity, and how they all connect together to support one another. No iguanas will be harmed.
The Best Kept Secrets Of Great Communicators Reference ManualTiffany Siok
This document provides techniques for effective communication and persuasion. It discusses active listening skills like maintaining eye contact, paraphrasing, and asking follow up questions. It also covers nonverbal communication cues like eye movements and pupil dilation that provide insights into a person's thoughts. The document provides tips for starting conversations, asking questions, and matching a person's language preferences to improve understanding. The overall aim is to teach skills that improve conversations, persuasiveness, and relationships.
This document provides techniques for effective communication and persuasion. It discusses active listening skills like maintaining eye contact, paraphrasing, and asking follow up questions. It also covers nonverbal communication cues like eye movements and pupil dilation that provide insights into a person's thoughts. The document provides tips for starting conversations, asking questions, and matching a person's language preferences to improve understanding. The overall aim is to teach skills that improve conversations, persuasiveness, and relationships.
11 easy ways to finally overcome your fear of public speakingKhalid Abdullah
EIECC Aims & Objectives
The general aim of this program is designed to help motivate Muslims who speak English reasonably & fluently to lead in presenting Islam effectively to non-Muslims & spread the message of peace to the entire world.
The objectives of the program are such that on completion, participants should have:
• an improvement of the cross-cultural Islamic English Communication Competence
• learning a very powerful a new model of self-directed learning to continue learning after the workshops in teams
• a reasonable knowledge of Islamic terminology & jargon to refute misconceptions
• the basic ability to discuss Islamic concepts in English cross-culturally
• the ability to give short presentations on Islamic topics of their choice
• Ignition of the passion to lead in using English communication skills for presenting Islam
For applications like Learning and Leadership, we are especially interested in this part of Dependent Origination. We can call this The Process of Becoming.
For the purpose of investigating Learning as a process of Becoming, we will divide the stages a little differently.
We invest so much effort in proper use and understanding of language and terminology because the feedback loop between Consciousness and Name-and-Form is the most sensitive point in the Process of Becoming.
This document provides 7 exercises to improve public speaking skills for pitching business ideas: 1) Explain your idea simply to a child to practice concise language. 2) Practice small talk to build rapport before pitching. 3) Write out main points to ensure all key ideas are included. 4) Improve posture to boost confidence and engagement. 5) Experiment with different wording and phrasing to avoid sounding robotic. 6) Vary speech pacing to find the most effective style. 7) Record yourself to identify and address distracting mannerisms. The goal is to deliver pitches in a personable and compelling way through strong speaking abilities.
Leadership Without Authority - Scrum Master Week - Day 4Ilan Kirschenbaum
This document provides an overview of a workshop on agile practices for teams. It includes discussions on the role of the scrum master, building trust and accountability, overcoming team dysfunctions, delegation, feedback techniques, and challenges of distributed teams. The agenda covers establishing norms, defining responsibilities, creating a safe environment for experiments, assessing team dynamics, and techniques for effective communication across locations.
So many people are interested in the field of NLP and so many people are selling courses that it's hard to know where to start.
We're sharing this intro day for FREE and are happy to answer any questions to help you decide what course is best for you
www.nlpbirmingham.co.uk
This document outlines a brain training program consisting of several parts:
1. It begins with introductions and disclaimers about the program.
2. Part II defines key brain-related terms like neuroplasticity, neurogenesis, and cognitive reserve that are important for understanding brain training.
3. Later parts describe specific brain training exercises focused on skills like attention, brain speed, memory, and navigation that make up the brain training program.
An empathy workshop that addresses some practices that can help exhibit effective empathy. This is important for a project manager to truly understand the issue and any underlying emotions at hand before taking action or applying judgement.
This document outlines an agenda for a workshop on neuro-linguistic programming (NLP). It will cover the four pillars of NLP: rapport, outcome orientation, sensory acuity, and behavioral flexibility. These skills can help improve relationships, handle difficult people, resolve conflicts, and increase personal flexibility. The workshop will be a hands-on introduction to NLP concepts and techniques to help participants gain more control over their thoughts, feelings, actions, and lives.
Similar to Graham Thomas - The Testers Toolbox - EuroSTAR 2010 (20)
Why We Need Diversity in Testing- AccentureTEST Huddle
In this webinar Rasa (Testing capability lead for Denmark) and Matthias (EALA Testing capability lead) will share some of their own experiences why diversity matters, give insights into how Accenture as a global firm is promoting diversity and how we are in the process of changing our attitudes and processes to make all of this sustainable
Keys to continuous testing for faster delivery euro star webinar TEST Huddle
Your business needs to deliver faster. To accommodate, Development needs to introduce fewer changes but in a much more frequent cadence. This creates a challenge for test teams to keep up with the rapid pace of change without compromising on quality. Automation is paramount to the success or failure of Continuous Delivery, and Continuous Testing enables early and frequent quality feedback throughout the CI/CD pipeline.
In this webinar, Eran & Ayal will explore how to implement Continuous Testing to ensure high quality releases in a Continuous Delivery environment; including what to test and when to automate new functionality in order to optimize your efforts.
Why you Shouldnt Automated But You Will Anyway TEST Huddle
The document discusses automation in software testing. It begins by outlining common claims made about the benefits of automation, such as saving time and improving quality, but argues that these claims often don't hold true. Automation does not inherently save time, guarantee quality, or reduce resources needed. It also does not always save money when development, maintenance, and infrastructure costs are considered. The document provides a formula for determining when automation is worthwhile based on how many times a test case would need to be rerun manually. It concludes by acknowledging that, despite these drawbacks, organizations will still automate testing because it is exciting, managers demand it, and it benefits careers.
In this webinar Carsten will explore the role of the tester in a Scrum team. He will examine where the tester play an important role in Scrum and how you can contribute to a teams performance.
Leveraging Visual Testing with Your Functional TestsTEST Huddle
Designing and implementing (or selecting) the right automation strategy, for functional testing, with visual testing, can help your project with greater test coverage while improving test scalability
Big Data: The Magic to Attain New HeightsTEST Huddle
This document discusses how big data and data science can be used to attain new heights, likening it to magic. It provides an overview of Ken Johnston's background and experiences in data science. It then discusses six keys to a "big" magic show with big data: trying multiple times, addressing issues with over-counting, experimentation techniques like A/B testing, infrastructure for big data, tools and skills, and security, privacy and fraud protection. The document emphasizes the importance of an assistant to help the data scientist or data engineer with various tasks.
This talk suggests how we might make sense of the tools landscape of the near future, where the pressure to modernise processes and automate is greatest, and what a new test process supported by tools might look like.
Takeaways:
- We need to take machine learning in testing seriously, but it won’t be taking our jobs just yet
- We don’t need more test automation tools; today we need tools that capture tester knowledge
- Tools that that learn and think can’t work for testers until we solve the knowledge capture challenge.
View On-Demand Webinar: https://youtu.be/EzyUdJFuzlE
The document discusses Test Driven Development (TDD) and Test Driven Design. It uses the analogy of building a lightsaber and later a Death Star to illustrate the TDD process and benefits. Some benefits mentioned are better test coverage, less debugging, and better design. The document provides tips for practicing TDD including planning ahead, defining boundaries, taking small steps to pass each test, and maintaining discipline. It emphasizes trying TDD in a team and considering Behavior Driven Development (BDD) as well.
Scaling Agile with LeSS (Large Scale Scrum)TEST Huddle
In this webinar, Elad will cover the principles that the #LeSS framework has to offer in order to enable bug organisations to become agile.
View webinar recording - https://huddle.eurostarsoftwaretesting.com/resource/agile-testing/scaling-agile-less-large-scale-scrum/
Creating Agile Test Strategies for Larger EnterprisesTEST Huddle
Having difficulty creating an agile test strategy for your company? Let Testing Excellence Award winner, Derk-Jan de Grood, show you how it’s done
View webinar recording here - http://huddle.eurostarsoftwaretesting.com/resource/agile-testing/creating-agile-test-strategies-larger-enterprises/
3 key takeaways
- Do you know the meaning of your organisation, system, product?
- Can you deliver the important risks right away?
- How can you communicate about the (process and product) risks your dealing with?
View Webinar recording: https://huddle.eurostarsoftwaretesting.com/resource/test-management/is-there-a-risk/
Are Your Tests Well-Travelled? Thoughts About Test CoverageTEST Huddle
This document summarizes a presentation on test coverage given by Dorothy Graham. It uses an analogy of travel to different locations to explain what test coverage means and some caveats. Coverage refers to the relationship between tests and the parts of a system being tested, but achieving 100% coverage does not mean everything is tested. There are four caveats discussed: coverage only measures one aspect of testing, a single test can achieve coverage, coverage does not indicate quality, and it only applies to the existing system not missing pieces. The key recommendation is to ask "coverage of what?" when the term is used rather than assuming more coverage is always better.
Growing a Company Test Community: Roles and Paths for TestersTEST Huddle
Over the past three years, our company’s test team has grown from three lonesome testers to a community of nine – with more planned. Since we don’t see testers as “click monkeys”, but as valuable and integrated project members who bring a specific skill set to the table, it’s important for us to choose testers well and to train them in various areas so that they can contribute, grow and see their own career path within testing.
To structure to our internal tester training program, we have been developing role descriptions, education paths and career options for our testers, which I’d like to share with you in this webinar.
View webinar - https://huddle.eurostarsoftwaretesting.com/resource/webinar/growing-company-test-community-roles-paths-testers/
It’s the same argument again and again. One side says “team members should all be able to do everything, and the programmers should do their testing and all testers should be writing code”. The other side says “No, that can’t possibly work – programmers don’t know how to test, they don’t have the right mindset”. And on and on it goes.
http://huddle.eurostarsoftwaretesting.com/resource/webinar/need-testers-agile-teams/
In this webinar, Dave Haeffner (Elemental Selenium, USA) discusses how to:
- Build an integrated feedback loop to automate test runs and find issues fast
- Setup your own infrastructure or connect to a cloud provider
-Dramatically improve test times with parallelization
https://huddle.eurostarsoftwaretesting.com/resource/webinar/use-selenium-successfully/
Testers & Teams on the Agile Fluency™ Journey TEST Huddle
The document discusses the Agile Fluency model, which aims to help teams and testers improve their agile skills and practices over time. It describes a pathway with increasing levels of fluency that provide more benefits, including delivering value, optimizing value, and innovating. Reaching higher levels requires investments in training, coaching, and changing team structures and roles. The model can help organizations determine what level of fluency they need and what investments are required for testing teams to operate at that level.
Practical Test Strategy Using HeuristicsTEST Huddle
Key Takeaways
- See what makes a good test strategy
- Learn how to make a thorough test strategy
- Identify what is the ‘Heuristic Test Strategy Model’ is
- Develop a solid test strategy that fits fast
- Discover how diversification can help you to create a test strategy
Key Takeaways:
- A diagramming method that helps discuss roles
- A one page analysis heuristic for roles
- Why roles matter on projects
https://huddle.eurostarsoftwaretesting.com/resource/people-skills/thinking-through-your-role/
Key Takeaways:
- What will this release contain
- What impact will it have on your test runs
- How can you preserve your existing investment in tests using the Selenium WebDriver APIs, and your even older RC tests
- Looking forward, when will the W3C spec be complete
- What can we expect from Selenium 4
https://huddle.eurostarsoftwaretesting.com/
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
OpenID AuthZEN Interop Read Out - AuthorizationDavid Brossard
During Identiverse 2024 and EIC 2024, members of the OpenID AuthZEN WG got together and demoed their authorization endpoints conforming to the AuthZEN API
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Project Management Semester Long Project - Acuityjpupo2018
Acuity is an innovative learning app designed to transform the way you engage with knowledge. Powered by AI technology, Acuity takes complex topics and distills them into concise, interactive summaries that are easy to read & understand. Whether you're exploring the depths of quantum mechanics or seeking insight into historical events, Acuity provides the key information you need without the burden of lengthy texts.
AI 101: An Introduction to the Basics and Impact of Artificial IntelligenceIndexBug
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
2. Abstract
This workshop will take you on a magical journey through some very useful but mostly unknown tools for perception and comprehension which will aid you in your daily testing life.
Building on Graham’s previous work in the field, and his enthusiasm for the subject, this workshop will take you on a 90-minute journey of mind opening discovery, looking at 7 key but often overlooked tools.
The tools, and their techniques are easy, fun to learn, and very powerful to use. And they will help you in mastering testing in the industry’s currently very demanding transitionfrom that of a structured V-model history to a leaner, more agile and exploratory approach. 2
3. What we will look at
Gall-Peters Projection
a different but more accurate way to look at the world
Popper’s Theory of Testability
a powerful tool to scope testing
Mind Control
finally proof that your mind is not your own!
The Stroop Effect
a powerful mechanisms that can control your behaviour
The Necker Cube
what you see is not what I see!
The Spinning Dancer
the whole may look different to the individual parts
e-prime
how to communicate experience rather than judgement
3
5. Other types ofMis-representation?
Tube Map
A network diagram which bears very little relationship to where tube stations are actually situated
Critical Path Network
A common project tool that does not show actual duration or amount of effort required as a relative amount. Small and large are the same size, and time is distorted!
And we use these to control projects!
5
6. 2. Popper’s Theory of Testability
Falsifiabilityorrefutabilityis the logical possibility that an assertion can be shown false by an observation or a physical experiment. That something is "falsifiable" does not mean it is false; rather, thatifit is false, then this can be shown by observation or experiment. The term "testability" is related but more specific; it means that an assertion can be falsified through experimentation alone.
Are all swans white? If we find one single black swan, logic allows us to conclude that the statement that “All swans are white” is false.
6
7. 2. Popper’s Theory of Testability
How I have used this in the past
I had just carried out a review of testing in a large bank. When I reported back to management , one of the team stated “All of our projects have a test strategy”. To which I replied, “No, they don’t because I have found one that hasn’t!”.
The discussion continued –“Tell me which one?”.I said “Not until you provide me with a list of all of the projects, and all of their strategy documents, then I will tell you which one”.
I am still waiting for the list! I only had to find one. They had to show me everything!
How to use the Theory?
Wherever you see All, or Every, or None, or NeverYou only need one example to the contrary –You don’t have to prove everything
To help understand success and failure criteriaWhat will make it, and what will break it!
If you only have a short amount of time, how to target your testingAll transactions must complete in nseconds –target the ones least likely
7
8. 3. Mind Control
Group Questions
oThink of a vegetable
oThink of a flower
oThink of a colour
oThink of a tool
oA numberbetween 1 & 10
oA Software Testing Technique
Predictions8
9. 3. Mind Control
So Why is this important
I think it is important to understand that when we ask questions some people may be hard-wired to give certain answers.
We therefore have to think about the questions that we are asking, and the answers that we don’t want!
When you ask a question:-
Listento the answer. Is it actually the answer to your question?
Is it GroupThink? –The answer everybody has been told to say?
Is it just the lowest common denominator, e.g. Boundary Value Analysis?
How should you ask questions?
9
11. 4. The Stroop Effect
Your Eyes are more powerful than your Mouth! is hard-wired into our brains
We have been conditioned through evolution to respond to specific colours in certain ways:- . . . .
. . . .
11
13. 5. Necker Cube
So what did you see ?
Up and down ?
Left to Right ?
Switched from one to the other ?
When did the switch happen ?
It is a simple 4 frame animation.
There is no switch !
It is all in your brain !
It is important to understand that what you see is not what others see!
You may need to understand what they see
You may need to explain to them what you see
I have often had this experience as a Program Test Manager, where I have a program based view and the testers have a test centric team view, which may be opposites!
13
15. 6. The Spinning Dancer
You get a different view when you look at the whole to that when you look at the
individual parts
Don’t assume that your view is the only view!
Think of this as a process:
People in the different parts of the process see the process working differently
You need to understand the individual viewpoints
Example:
Defect Management system on a large testing program
Perceived bottleneck
Fixed the bottleneck, and it moved to another part of the process!
No overall process efficiency gain. It just looked different!
15
16. 7. E-Prime
E-Prime(short forEnglish-Prime, sometimes spelledE′) is a form of theEnglish languagein which the verbto bein all its forms does not exist. Thus, E-Primedoes not contain the words "be", "is", "am", "are", "was", "were", "been" and "being", nor does it contain their contractions "'m", "'s", and "'re". E-Primetherefore uses alternate means to express most statements which use thepassive voice, thus encouraging writers and speakers to clearly state an action'sagent.
How to communicate experience rather than judgement
“To be” prevents us from experiencing a shared reality; something we need in order to communicate in a sane way. If someone sees something completely different than another, our language prevents us from acknowledging the others point of view by limiting our perception to fixed states. For example, if I say “Star Wars is a ****** movie,” and my friend says, “Star Wars is not a ****** movie!” We have no shared reality, for in our language, truth lies in only one of our statements and we can forever argue these truths until one of us writes a book and has more authority than the other. If on the other hand I say, “I hated Star Wars,” I state my opinion as observed through my own senses. I state a more accurate reality by not claiming that Star Wars “is” anything, as it could “be” anything to anyone.
This sounds like rubbish? 16
17. 7. E-Prime
Lets Try it Out
http://www.manifestation.com/neurotoys/eprime.pl
It takes a while to get your head around it, but it helps you to write better English
It willimprove your communication
It willhelp others to more easily understand what you mean
Try it out when you have the time!
And before you ask I have E-Primedthis page and it doesn't contain any errors! 17
18. “To find fault is easy; to dobetter may be difficult”
Plutarch(c.46AD–c.120AD) Greek /Roman -historian, biographer, essayist
What did they know 2000 years ago that we don’t know now?
18
19. Action Plan
I would like you to start an Action Plan
Think of which techniques you could employ and
where
Do it now whilst it is fresh in your mind
Come up with at least 7 things to do
Visit my website where you can download a copy
of the slides – www.badgerscroft.com
So that you can use them yourselves
With your team
Refresh your memory in a couple of months
And maybe come up with some techniques of your
own that you could then share?
Gall-Peters Projection
Popper’s Theory of Testability
Mind Control
The Stroop Effect
The Necker Cube
The Spinning Dancer
e-prime
19
20. Contact Details
Graham Thomas
Independent Software
Testing Consultant
graham@badgerscroft.com
+44 7973 387 853
www.badgerscroft.com20