Whiteboarding—for Testers, Developers, and Customers, Too
•Download as PPTX, PDF•
0 likes•352 views
How can testers spend more time doing productive testing and waste less time preparing "useless" project documentation? Rob Sabourin employs whiteboarding techniques to enable faster, easier, and more powerful communication and collaboration—without all the paperwork. Rob uses whiteboarding to help identify technical risks, understand user needs, and focus testing on what really matters to business stakeholders. Whiteboard block diagrams visualize technical risk to stakeholders. Whiteboard fault models highlight failure modes to developers and testers. Testers can elicit usage scenarios directly from customers using storyboard diagrams. Rob shows how simple whiteboarding strategies help testers learn new concepts, design better tests, and estimate their activities. Rob shares his experiences whiteboarding all kinds of visual models: time sequences, block diagrams, storyboards, state models, control flows, data flows, and mind maps. Save time and avoid the pain of back-and-forth or written document reviews that testers, developers, customers, and users often come to despise.
Report
Share
Report
Share
Recommended
Unlocking Innovation in Your Organization
According to a recent study, more than 60 percent of CEOs cite the need to discover innovative ways of managing their organization’s structure, finances, people, and strategies as their top priority. In order to compete in the 21st century, organizations must rethink how they function—they must adapt or die. Derek Neighbors shows you how to meld chaos, creativity, and collaboration within your organization to unlock innovation. Learn how to balance fun and excellence to achieve results while redefining your organization's culture. Many models try to explain what complex systems might look like or how to determine what kind of culture an organization may need. Walk away with real-life stories of how teams, organizations, and even cities are transforming themselves for the future. Apply what you learn to your own product, team, and organization as Derek helps you learn how to evolve for the future.
Creating Dissonance: Overcoming Organizational Bias toward Software Testing
Overcoming organizational bias toward software testing can be a key factor in the success of your testing effort. Negative bias toward testing can impact its perceived value—just as inaccurate positive bias can set your team up for failure through mismanaged expectations. A structured approach to identifying, understanding, and overcoming bias is an integral part of any successful enterprise testing strategy. Keith Klain describes the origins of organizational bias and what it means for your testing effort, including what the test team and the industry do—and don’t do—to support those perceptions. He explores what you can do to identify your particular organization’s bias toward testing, how it evolved, evidence of those attitudes, and what you can do to change perceptions. Through case studies, Keith shares his successes and failures in navigating and running change programs focused on software testing and discusses the obstacles he’s encountered—and overcome.
Collaboration Techniques: Forgotten Wisdom and New Approaches
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 and productively with customers, programmers, business analysts, writers, trainers, and pretty much everyone in the business value chain. Testers and managers have many touch points of collaboration: 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 describe how collaboration worked on several agile projects, giving critiques of what worked well, where problems could arise, and additional aspects to consider. Join Rob and Dot to look at examples from agile projects and how forgotten but proven “ancient” techniques can be applied to your own collaboration, such as entry and exit criteria, role diversity, risk-based objectives, checklists, cross-checking, and root cause analysis. Bring your own stories of collaboration—good and bad—and see how forgotten wisdom can help improve today’s practices.
Group Interaction Patterns: The Keys for Highly Productive Teams
Development teams often fail to recognize the complex group interactions and multi-person relationships that are critical to build and maintain a highly productive team. Instead, they adopt follow-the-crowd practices such as stand up meetings or Kanban boards without understanding the underlying fundamentals. Michael Wolf introduces group interaction patterns of highly productive development teams to provide a framework for understanding group interactions and a vocabulary for discussing ways to improve. Michael demonstrates a simple tool-based on nine keystone patterns-that you can use to observe and understand your team members' interactions. He shares case studies that illustrate successes, failures, and turnarounds he's observed and explores how they relate to the different group interaction patterns. Join Michael to see how identifying your group's interaction patterns can suggest actions to develop highly productive-and happier-teams in your organization.
The Evolution of Agile: Dealing with the Growing Pains
Agile development has evolved into a lifecycle that not only affects the IT department but the overall business as well. Forward-thinking enterprises recognize this and benefit from the software efficiency that agile development delivers. Through real-world examples, Jonathan Thorpe explains how enterprises can improve their agile success. Discover how successful global enterprises are applying the principles of agile development beyond just software development to a level where it affects entire business groups. Jonathan describes the evolution of agile and discusses why organizations are feeling growing pains as the methodology grows from the IT department to the business level. Learn how agile methodologies can be applied to business analysis, release management, and other IT processes to ensure applications are being delivered to customers on time and on budget. Are you ready to ensure your entire organization is truly agile?
Red Beads: A New Tool for Managing Software Projects
Warning! Warning! Managing software projects may be accompanied by continued bouts of nausea-brought on by unmet expectations, process churn, late deliveries, and worse. In their attempt to conquer these problems, many managers stiffen their resolve, create stricter schedules, and install rigid processes to guide development from inception to production. Howard Deiner demonstrates that better results come from fundamental changes in the way managers and the organization approach problems. Drawing on W. Edward Deming’s "14 Obligations of Management," Howard reprises (with volunteers from the audience) Deming's famous Red Bead Experiment on its 30th anniversary and draws conclusions about how our approach to problem-solving affects our day-to-day work. Expect to get up on your feet and have a lot of fun "working" in a simulation of a modern workday environment, leading and managing the development efforts. Leave with new, meaningful insights that will inspire you to make changes to improve the work life for yourself and those around you.
Exploring Usability Testing
It is not enough to verify that software conforms to requirements by passing established acceptance tests. Successful software products engage, entertain, and support the users' experience. While goals vary from project to project, no matter how robust and reliable your software is, if your users do not embrace it, business can slip from your hands. Rob Sabourin shares how to elicit effective usability requirements with techniques such as story boarding and task analysis. Together, testers, programmers, and users collaborate to blend the requirement, design, and test cycles into a tight feedback loop. Learn how to select a subset of system functions to test with a small group of users to get high value information at low cost. Learn how usability testers can take advantage of naïve questions from novice users as well as the tunnel vision and bias of domain experts. Rob shares examples of usability testing for a variety of technologies including mobile and web based products.
Software Security Goes Mobile
Erik Costlow says that, as more and more business is transacted on mobile platforms, securing the applications and data that run on them is a business imperative. Developers and their managers are asked to make key decisions regarding data caching, authorized permissions, authentication requirements on the backend, and safe coding practices—all of which contribute to the protection of their organization’s intellectual property. However, hackers have taken advantage of a knowledge gap to develop creative attacks against mobile applications. Becoming more common is “intent spoofing” in which hackers write a special application that targets an existing app on the Android platform and directs it to take malicious actions. Erik guides you through the steps you can take—use of two-factor authentication, code analysis, and obfuscation—to protect your intellectual property and your customers’ data against these and other potential threats.
Recommended
Unlocking Innovation in Your Organization
According to a recent study, more than 60 percent of CEOs cite the need to discover innovative ways of managing their organization’s structure, finances, people, and strategies as their top priority. In order to compete in the 21st century, organizations must rethink how they function—they must adapt or die. Derek Neighbors shows you how to meld chaos, creativity, and collaboration within your organization to unlock innovation. Learn how to balance fun and excellence to achieve results while redefining your organization's culture. Many models try to explain what complex systems might look like or how to determine what kind of culture an organization may need. Walk away with real-life stories of how teams, organizations, and even cities are transforming themselves for the future. Apply what you learn to your own product, team, and organization as Derek helps you learn how to evolve for the future.
Creating Dissonance: Overcoming Organizational Bias toward Software Testing
Overcoming organizational bias toward software testing can be a key factor in the success of your testing effort. Negative bias toward testing can impact its perceived value—just as inaccurate positive bias can set your team up for failure through mismanaged expectations. A structured approach to identifying, understanding, and overcoming bias is an integral part of any successful enterprise testing strategy. Keith Klain describes the origins of organizational bias and what it means for your testing effort, including what the test team and the industry do—and don’t do—to support those perceptions. He explores what you can do to identify your particular organization’s bias toward testing, how it evolved, evidence of those attitudes, and what you can do to change perceptions. Through case studies, Keith shares his successes and failures in navigating and running change programs focused on software testing and discusses the obstacles he’s encountered—and overcome.
Collaboration Techniques: Forgotten Wisdom and New Approaches
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 and productively with customers, programmers, business analysts, writers, trainers, and pretty much everyone in the business value chain. Testers and managers have many touch points of collaboration: 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 describe how collaboration worked on several agile projects, giving critiques of what worked well, where problems could arise, and additional aspects to consider. Join Rob and Dot to look at examples from agile projects and how forgotten but proven “ancient” techniques can be applied to your own collaboration, such as entry and exit criteria, role diversity, risk-based objectives, checklists, cross-checking, and root cause analysis. Bring your own stories of collaboration—good and bad—and see how forgotten wisdom can help improve today’s practices.
Group Interaction Patterns: The Keys for Highly Productive Teams
Development teams often fail to recognize the complex group interactions and multi-person relationships that are critical to build and maintain a highly productive team. Instead, they adopt follow-the-crowd practices such as stand up meetings or Kanban boards without understanding the underlying fundamentals. Michael Wolf introduces group interaction patterns of highly productive development teams to provide a framework for understanding group interactions and a vocabulary for discussing ways to improve. Michael demonstrates a simple tool-based on nine keystone patterns-that you can use to observe and understand your team members' interactions. He shares case studies that illustrate successes, failures, and turnarounds he's observed and explores how they relate to the different group interaction patterns. Join Michael to see how identifying your group's interaction patterns can suggest actions to develop highly productive-and happier-teams in your organization.
The Evolution of Agile: Dealing with the Growing Pains
Agile development has evolved into a lifecycle that not only affects the IT department but the overall business as well. Forward-thinking enterprises recognize this and benefit from the software efficiency that agile development delivers. Through real-world examples, Jonathan Thorpe explains how enterprises can improve their agile success. Discover how successful global enterprises are applying the principles of agile development beyond just software development to a level where it affects entire business groups. Jonathan describes the evolution of agile and discusses why organizations are feeling growing pains as the methodology grows from the IT department to the business level. Learn how agile methodologies can be applied to business analysis, release management, and other IT processes to ensure applications are being delivered to customers on time and on budget. Are you ready to ensure your entire organization is truly agile?
Red Beads: A New Tool for Managing Software Projects
Warning! Warning! Managing software projects may be accompanied by continued bouts of nausea-brought on by unmet expectations, process churn, late deliveries, and worse. In their attempt to conquer these problems, many managers stiffen their resolve, create stricter schedules, and install rigid processes to guide development from inception to production. Howard Deiner demonstrates that better results come from fundamental changes in the way managers and the organization approach problems. Drawing on W. Edward Deming’s "14 Obligations of Management," Howard reprises (with volunteers from the audience) Deming's famous Red Bead Experiment on its 30th anniversary and draws conclusions about how our approach to problem-solving affects our day-to-day work. Expect to get up on your feet and have a lot of fun "working" in a simulation of a modern workday environment, leading and managing the development efforts. Leave with new, meaningful insights that will inspire you to make changes to improve the work life for yourself and those around you.
Exploring Usability Testing
It is not enough to verify that software conforms to requirements by passing established acceptance tests. Successful software products engage, entertain, and support the users' experience. While goals vary from project to project, no matter how robust and reliable your software is, if your users do not embrace it, business can slip from your hands. Rob Sabourin shares how to elicit effective usability requirements with techniques such as story boarding and task analysis. Together, testers, programmers, and users collaborate to blend the requirement, design, and test cycles into a tight feedback loop. Learn how to select a subset of system functions to test with a small group of users to get high value information at low cost. Learn how usability testers can take advantage of naïve questions from novice users as well as the tunnel vision and bias of domain experts. Rob shares examples of usability testing for a variety of technologies including mobile and web based products.
Software Security Goes Mobile
Erik Costlow says that, as more and more business is transacted on mobile platforms, securing the applications and data that run on them is a business imperative. Developers and their managers are asked to make key decisions regarding data caching, authorized permissions, authentication requirements on the backend, and safe coding practices—all of which contribute to the protection of their organization’s intellectual property. However, hackers have taken advantage of a knowledge gap to develop creative attacks against mobile applications. Becoming more common is “intent spoofing” in which hackers write a special application that targets an existing app on the Android platform and directs it to take malicious actions. Erik guides you through the steps you can take—use of two-factor authentication, code analysis, and obfuscation—to protect your intellectual property and your customers’ data against these and other potential threats.
STARCANADA 2013 Keynote: Lightning Strikes the Keynotes
Throughout the years, Lightning Talks have been a popular part of the STAR conferences. If you’re not familiar with the concept, Lightning Talks consists of a series of five-minute talks by different speakers within one presentation period. Lightning Talks are the opportunity for speakers to deliver their single biggest bang-for-the-buck idea in a rapid-fire presentation. And now, lightning has struck the STAR keynotes. Some of the best-known experts in testing—Jon Bach, Michael Bolton, Fiona Charles, Janet Gregory, Paul Holland, Griffin Jones, Keith Klain, Gerard Meszaros, and Nate Oster—will step up to the podium and give you their best shot of lightning. Get ten keynote presentations for the price of one—and have some fun at the same time.
Exploding Management Myths
We’ve all heard management “nuggets” such as “make people come to you with solutions, nut just problems,” or “training time is wasted time,” or my favorite, “work smarter.” But how are you supposed to do that, especially if you may not have received any management training, or if your gut is telling you what you’re doing might not be working? Johanna Rothman explains that much of what you have heard about management is myth—based not on evidence, but on ideas dating from the Industrial Revolution. However, many myths have a germ of truth. If you would like to learn about these germs—the kinds of training that are useless and the kinds that are useful, how to really work smarter, how to help people develop solutions when they are stuck—the kind of management that empowers knowledge workers, join Johanna in exploding management myths.
Structural Testing: When Quality Really Matters
Jamie Mitchell explores an underused and often forgotten test technique—white-box testing. Also known as structural testing, this technique requires some programming expertise and access to the code. Using only black-box testing, you could easily ship a system having tested only 50 percent or less of the code base. Are you comfortable with that? For mission-critical systems, such low test code coverage is clearly insufficient. Although you might believe that the developers have performed sufficient unit and integration testing, how do you know that they have achieved the level of coverage that your project requires? Jamie describes the levels of code coverage that the business and your customers may need—from statement coverage to modified condition/decision coverage. He explains when you should strive to achieve different code coverage target levels and leads you through examples of pseudocode. Even if you have no personal programming experience, understanding structural testing will make you a better tester. So, join Jamie in this code-diving session.
Enhancing Developer Productivity with Code Forensics
Imagine an engineering system that could evaluate developer performance, recognize rushed check-ins, and use that data to speed up development. “Congratulations Jane. You know this code well. No check-in test gate for you.” Anthony Voellm shares how behavioral analysis and developer assessments can be applied to improve productivity. This approach was motivated by today's test systems, tools, and processes that are all designed around the premise that “all developers are created equal.” Studies have shown developer error rates can vary widely and have a number of root causes—the mindset of the developer at the time the code was written, experience level, amount of code in a check-in, complexity of the code, and much more. With Digital Code Forensics, a set of metrics that can evaluate developers, Anthony demonstrates how even modest applications of this approach can speed up development. Discover and use the cutting edge of engineering productivity.
A UX Strategy for Persona Research
Research into your users’ personas can provide deep insights into their needs and validate your product design. This research doesn’t have to take months; it can often be done in two weeks, during sprint 0. Unfortunately, many companies using agile methods don’t invest in personas and a UX strategy because they think they have no time or believe they already know enough about their users. We typically spend months to years developing a software product. Don’t we owe it to our users and ourselves to devote some time to researching and understanding them? Nellie LeMonier describes persona research methods and techniques for conducting quick guerrilla research. She discusses how to ensure your research results are shared throughout the software team so that everyone has a common understanding of what your users care about and what they need. Nellie uses case studies to illustrate the benefits and consequences for projects conducted both with and without persona research. Join Nellie to get a UX strategy for your project!
Mob Programming: A Whole Team Approach
Teamwork is an important component of agile software development. We all agree that teamwork must be nurtured and grown in our organizations. But what does it mean to work as a team in the world of software development? How can we encourage our “teams” to truly work “as a team?” Woody Zuill and his team at Hunter Industries have found tremendous benefits following the whole team approach they call Mob Programming. Everyone works together at the same time, in the same space, on the same problem, and at the computer—every day, eight hours a day! How can this possibly work? Woody explores the whole team concept and shows the specific practices his team uses for communication, collaboration, coding, and accelerated learning in their daily software development work. Learn how Woody and his team discovered this highly productive practice, see what it looks like, and take home some ideas you can use in to your software development work.
Implementing Cloud-Based DevOps for Distributed Agile Projects
Cloud-based development, delivery, and deployment environments are the future of IT operations. Thomas Stiehm shares the hard-learned lessons of setting up and running cloud-based solutions that implement DevOps for geographically distributed agile projects. Thomas describes how to best leverage the cloud to enable your teams to use it effectively. Learn why cloud software delivery is different from traditional software delivery environments, and how to optimize your platform and team to get the most out of the cloud. Geographically-distributed software delivery teams are now the norm for large projects, and the cloud is a perfect enabler to level the playing field for your distributed teams and to give them all the same ability to achieve high productivity. Since the road to the cloud isn’t always paved, learn many of the trade-offs that must be made to implement cloud-based delivery and discover the situations that will derail a move to cloud-based development.
Scaling Your Tests: Continued Change Without Fear
Agile teams move faster when cycle times are short and code deployments are frequent. To release often, a robust suite of automated tests is a must-have. Tests are the safety net that enables fearless change. Throughout a software system's lifespan, its test suite grows, evolves, and decays. Left unchecked, test execution times increase and non-deterministic failures erode confidence. Ultimately, the test suite that once served as a change-enabler becomes an anchor, grinding progress to a halt. Scaling a test suite is complex and difficult—and vital to successful organizations. Drawing from experience in the trenches, Ryan Scott describes real-world examples of how and why test suites can become burdensome and shares solutions for keeping your test suites tidy. Ryan explores techniques for test parallelization and code restructuring that his company used to decrease the execution time of its test suites by more than 90 percent while more than tripling the number of tests. Take back new ways to fearlessly scale your agile testing.
Seven Deadly Habits of Dysfunctional Software Managers
As if releasing a quality software project on time were not difficult enough, poor management dealing with planning, people, and process issues can be deadly to a project. Presenting a series of anti-pattern case studies, Ken Whitaker describes the most common deadly habits-and ways to avoid them. These seven killer habits are mishandling employee incentives; making key decisions by consensus; ignoring proven processes; delegating absolute control to a project manager; taking too long to negotiate a project's scope; releasing an "almost tested" product to market; and hiring someone who is not quite qualified-but liked by everyone. Whether you are an experienced manager struggling with some of these issues or a new software manager, you'll take away invaluable tips and techniques correcting these habits-or better yet, avoiding them altogether. As a bonus, every attendee will receive a copy of Ken's full-color 7 Deadly Habits comic .
Trends in Big Data Testing
The Big Data has three unique characteristics—Volume, Velocity, and Variety. Today’s big data applications are growing dramatically. We must process data ever more quickly so we can respond to events as they happen, and that data is arriving from an ever wider array of channels, sensors, and formats. Stefano Rizzo explains that the main challenges of testing big data by little agile teams, beside the apparent contradiction, are related to testing individual components vs. testing the big product, traceability, and organizing massive amounts of test data vs. minimal testing with spreadsheets, and testing the final products of development vs. test-driven development. After reviewing these challenges, Stefano shares practices and tools to address both testing Big Data and managing the Testing of Big Data—the huge amount of data coming from massive and continuous testing practices.
Testers in Agile Teams—Isolation or Collaboration?
What exactly are testers doing as organizations evolve from waterfall lifecycles to iterative, incremental agile approaches? Agile transitions, rather than fostering collaboration, often lead to isolation, role confusion, and fear. Many testers are left out in the cold. Agile testers face existential challenges: Is it enough that programmers test their own code? Must testers become programming experts? Do we still need business analysts or subject matter experts? Test evangelist Rob Sabourin explores an exciting vision for testers and demonstrates how they can take a role in acting as guiding lights to the entire team. Rob shares real-life examples of testers becoming trusted advisors and confidants to product owners, acting as customer advocates and guardians of the user experience. He explains how testers can drive critical design decisions early, using risk models to expose emergent architectures. Testing skills, knowledge, and wisdom apply in a plethora of circumstances so testers can take the driver’s seat—in every step of the agile transition.
Testing Lessons from the Land of Make Believe
Rob Sabourin has discovered testing lessons in Sesame Street, the Simpsons, the Looney Tunes gang, the Great Detectives, Dr. Seuss, and many other unlikely places, but this year he journeys to the Land of Make Believe. Rob's grandchildren Jane and Suzy draw him into the Land of Make Believe. Every visit is a new adventure. By leaving reality for the realm of play, Rob has discovered many simple truths and clever strategies for solving stubborn technical, management, and people-related software testing problems. An imaginary tea party teaches role playing, simulation, re-focusing, and test leadership. Imaginary messes suggest powerful environment virtualization strategies. Are you robust enough to romp around the playground? Can you bake mud pies with variability, combinations, and permutations? Who can enter the land of make believe without the blessing of beautiful princesses whose whimsical authority demonstrates adapting to stakeholder value systems? Open the tickle chest to discover storyboards, affinity analysis, test design, scenarios, and attacks. Join Rob to wander into the wonderful Land of Make Believe. See if the imagination of Jane and Suzy inspires you with powerful testing ideas.
Exploring Usability Testing
It is not enough to verify that software conforms to requirements by passing established acceptance tests. Successful software products engage, entertain, and support the users' experience. Goals vary from project to project, but no matter how robust and reliable your software is, if your users do not embrace it, business can slip from your hands. Rob Sabourin shares how to elicit effective usability requirements with techniques such as story boarding and task analysis. Together, testers, programmers, and users collaborate to blend the requirement, design, and test cycles into a tight feedback loop. Learn how to select a subset of system functions to test with a small group of users to get high value information at low cost. Learn how usability testers can take advantage of naïve questions from novice users as well as the tunnel vision and bias of domain experts. Rob shares examples of usability testing for a variety of technologies including mobile and web-based products.
Testing in the Dark
Isn't it amazing? Stakeholders drop software on our desks and expect us to test it—without any requirements, design, or product knowledge whatsoever. About the only clear thing is the absurd and unrealistic deadline. We are expected to bend over backward, spread magic pixie dust, and heroically test quality into a product we have never heard of before. But testing in the dark is not impossible, and as Rob Sabourin shows, it can even be a very valuable and fun experience. Learn strategies to emerge from a murky fog into clear, meaningful quality insights. Leverage unlikely sources about what stakeholders care about and what users really need the software to do. Rob introduces you to methods of reconnaissance-style, charter-driven, and session-based exploratory testing and helps you provide meaningful estimates to stakeholders with minimal hard information about the software under test. Rob shares recent experiences testing in the dark on chaotic and turbulent projects, turning his product ignorance into a testing superpower. Join Rob’s quest to find important bugs fast while testing in the dark—and you, too, will see the light!
Testing Lessons Learned from Monty Python
And now for something completely different. Monty Python's Flying Circus revolutionized comedy and brought zany British humor to a worldwide audience. However, buried deep in the hilarity and camouflaged in its twisted wit lie many important testing lessons—tips and techniques you can apply to real world problems to deal with turbulent projects, changing requirements, and stubborn project stakeholders. Rob Sabourin examines some of the most famous Python bits—“The Spanish Inquisition” telling us to expect the unexpected, “The Dead Parrot” asking if we should really deliver this product to the customer, “The Argument” teaching us about bug advocacy, “Self Defense against Fresh Fruit” demonstrating the need to pick the right testing tool, and a host of other goofy gags, each one with a lesson for testers. Learn how to test effectively with persistence, how to make your point with effective communication, and how to clarify project goals and requirements.
Encuesta Ambysoft - IT Project Success 2013
Encuesta Ambysoft sobre la tasa de éxito/fracaso de proyectos TI de noviembre 2013
The Tester’s Role in Agile Planning
All too often testers passively participate in agile planning. And the results? Important testing activities are missed, late testing becomes a bottleneck, and the benefits of agile development quickly diminish. However, testers can actively advocate customer concerns while helping to implement robust solutions. Rob Sabourin shows how testers contribute to estimation, task definition, and scoping work required to implement user stories. Testers apply their elicitation skills to understand what users need, exploring typical, alternate, and error scenarios. Testers can anticipate cross story interference and the impact of new stories on legacy functionality. Rob discusses examples of how to break agile stories into test-related tasks. He shares experiences of transforming agile testers from passive planning participants into dynamic advocates of effective trade-offs, addressing the product owners’ critical business concerns, the teams’ limited resources, and the software projects’ technical risks. Join Rob to explore test infrastructure, test data, non-functional attributes, privacy, security, robustness, exploration, regression, business rules, and more.
The Tester's Role in Agile Planning
If testers sit passively through agile planning, important testing activities will be missed or glossed over. Testing late in the sprint becomes a bottleneck, quickly diminishing the advantages of agile development. However, testers can actively advocate for customers’ concerns while helping the team implement robust solutions. Rob Sabourin shows how testers contribute to the estimation, task definition, clarification, and the scoping work required to implement user stories.
Failing and Recovering
Do you ever feel you have lost confidence in your own abilities? Why does this happen? Isabel Evans spends a lot of time painting. Someone once commented, “Why are you doing this, when you are not very good at it?” And gradually she stopped drawing and painting, after being intimidated by a conventional vision of what good art should look like. At the same time, she experienced a parallel loss of confidence in her professional abilities. Attempting creative pursuits like drawing and painting is essential to cognitive, emotional, creative abilities and she began to understand the correlation between her creative activities and her confidence. Making errors, being wrong, failing – that is a generous gift we receive when we practice outside our skill level. By staying in a comfort zone and repeating successes, we stagnate. As Isabel started to create again she thought “I don’t feel good at it, I do feel good doing it” The difference was that she was learning, having ideas and the act of re-engaging with failure, together with the comradeship of friends and colleagues, including at Women Who Test, Isabel has regained her confidence in her professional abilities, and been able to reboot her career and joy. Join Isabel to share a journey from self-perceived failure, to recovery and renewed learning.
Instill a DevOps Testing Culture in Your Team and Organization
The DevOps movement is here. Companies across many industries are breaking down siloed IT departments and federating them into product development teams. Testing and its practices are at the heart of these changes. Traditionally, IT organizations have been staffed with mostly manual testers and a limited number of automation and performance engineers. To keep pace with development in the new “you build it, you own it” environment, testing teams and individuals must develop new technical skills and even embrace coding to stay relevant and add greater value to the business. DevOps really starts with testing. Join Adam Auerbach as he explains what DevOps is and how it relates to testing. He describes how testing must change from top to bottom and how to access your own environment to identify improvement opportunities. Adam dives into practices like service virtualization, test data management, and continuous testing so you can understand where you are now and identify steps needed to instill a DevOps testing culture in your team and organization.
Test Design for Fully Automated Build Architecture
Imagine this … As soon as any developed functionality is submitted into the code repository, it is automatically subjected to the appropriate battery of tests and then released straight into production. Setting up the pipeline capable of doing just that is becoming more and more common and something you need to know about. But most organizations hit the same stumbling block—just what IS the appropriate battery of tests? Automated build architectures don't always lend themselves well to the traditional stages of testing. In this hands-on tutorial, Melissa Benua introduces you to key test design principles—applicable to organizations both large and small—that allow you to take full advantage of the pipeline's capabilities without introducing unnecessary bottlenecks. Learn how to make highly reliable tests that run fast and preserve just enough information to let testers and developers determine exactly what went wrong and how to reproduce the error locally. Explore ways to reduce overlap while still maintaining adequate test coverage. Take back ideas about which test areas could benefit from being combined into a single suite and which areas could benefit most from being broken out altogether.
System-Level Test Automation: Ensuring a Good Start
Many organizations invest a lot of effort in test automation at the system level but then have serious problems later on. As a leader, how can you ensure that your new automation efforts will get off to a good start? What can you do to ensure that your automation work provides continuing value? This tutorial covers both “theory” and “practice”. Dot Graham explains the critical issues for getting a good start, and Chris Loder describes his experiences in getting good automation started at a number of companies. The tutorial covers the most important management issues you must address for test automation success, particularly when you are new to automation, and how to choose the best approaches for your organization—no matter which automation tools you use. Focusing on system level testing, Dot and Chris explain how automation affects staffing, who should be responsible for which automation tasks, how managers can best support automation efforts to promote success, what you can realistically expect in benefits and how to report them. They explain—for non-techies—the key technical issues that can make or break your automation effort. Come away with your own clarified automation objectives, and a draft test automation strategy to use to plan your own system-level test automation.
More Related Content
Viewers also liked
STARCANADA 2013 Keynote: Lightning Strikes the Keynotes
Throughout the years, Lightning Talks have been a popular part of the STAR conferences. If you’re not familiar with the concept, Lightning Talks consists of a series of five-minute talks by different speakers within one presentation period. Lightning Talks are the opportunity for speakers to deliver their single biggest bang-for-the-buck idea in a rapid-fire presentation. And now, lightning has struck the STAR keynotes. Some of the best-known experts in testing—Jon Bach, Michael Bolton, Fiona Charles, Janet Gregory, Paul Holland, Griffin Jones, Keith Klain, Gerard Meszaros, and Nate Oster—will step up to the podium and give you their best shot of lightning. Get ten keynote presentations for the price of one—and have some fun at the same time.
Exploding Management Myths
We’ve all heard management “nuggets” such as “make people come to you with solutions, nut just problems,” or “training time is wasted time,” or my favorite, “work smarter.” But how are you supposed to do that, especially if you may not have received any management training, or if your gut is telling you what you’re doing might not be working? Johanna Rothman explains that much of what you have heard about management is myth—based not on evidence, but on ideas dating from the Industrial Revolution. However, many myths have a germ of truth. If you would like to learn about these germs—the kinds of training that are useless and the kinds that are useful, how to really work smarter, how to help people develop solutions when they are stuck—the kind of management that empowers knowledge workers, join Johanna in exploding management myths.
Structural Testing: When Quality Really Matters
Jamie Mitchell explores an underused and often forgotten test technique—white-box testing. Also known as structural testing, this technique requires some programming expertise and access to the code. Using only black-box testing, you could easily ship a system having tested only 50 percent or less of the code base. Are you comfortable with that? For mission-critical systems, such low test code coverage is clearly insufficient. Although you might believe that the developers have performed sufficient unit and integration testing, how do you know that they have achieved the level of coverage that your project requires? Jamie describes the levels of code coverage that the business and your customers may need—from statement coverage to modified condition/decision coverage. He explains when you should strive to achieve different code coverage target levels and leads you through examples of pseudocode. Even if you have no personal programming experience, understanding structural testing will make you a better tester. So, join Jamie in this code-diving session.
Enhancing Developer Productivity with Code Forensics
Imagine an engineering system that could evaluate developer performance, recognize rushed check-ins, and use that data to speed up development. “Congratulations Jane. You know this code well. No check-in test gate for you.” Anthony Voellm shares how behavioral analysis and developer assessments can be applied to improve productivity. This approach was motivated by today's test systems, tools, and processes that are all designed around the premise that “all developers are created equal.” Studies have shown developer error rates can vary widely and have a number of root causes—the mindset of the developer at the time the code was written, experience level, amount of code in a check-in, complexity of the code, and much more. With Digital Code Forensics, a set of metrics that can evaluate developers, Anthony demonstrates how even modest applications of this approach can speed up development. Discover and use the cutting edge of engineering productivity.
A UX Strategy for Persona Research
Research into your users’ personas can provide deep insights into their needs and validate your product design. This research doesn’t have to take months; it can often be done in two weeks, during sprint 0. Unfortunately, many companies using agile methods don’t invest in personas and a UX strategy because they think they have no time or believe they already know enough about their users. We typically spend months to years developing a software product. Don’t we owe it to our users and ourselves to devote some time to researching and understanding them? Nellie LeMonier describes persona research methods and techniques for conducting quick guerrilla research. She discusses how to ensure your research results are shared throughout the software team so that everyone has a common understanding of what your users care about and what they need. Nellie uses case studies to illustrate the benefits and consequences for projects conducted both with and without persona research. Join Nellie to get a UX strategy for your project!
Mob Programming: A Whole Team Approach
Teamwork is an important component of agile software development. We all agree that teamwork must be nurtured and grown in our organizations. But what does it mean to work as a team in the world of software development? How can we encourage our “teams” to truly work “as a team?” Woody Zuill and his team at Hunter Industries have found tremendous benefits following the whole team approach they call Mob Programming. Everyone works together at the same time, in the same space, on the same problem, and at the computer—every day, eight hours a day! How can this possibly work? Woody explores the whole team concept and shows the specific practices his team uses for communication, collaboration, coding, and accelerated learning in their daily software development work. Learn how Woody and his team discovered this highly productive practice, see what it looks like, and take home some ideas you can use in to your software development work.
Implementing Cloud-Based DevOps for Distributed Agile Projects
Cloud-based development, delivery, and deployment environments are the future of IT operations. Thomas Stiehm shares the hard-learned lessons of setting up and running cloud-based solutions that implement DevOps for geographically distributed agile projects. Thomas describes how to best leverage the cloud to enable your teams to use it effectively. Learn why cloud software delivery is different from traditional software delivery environments, and how to optimize your platform and team to get the most out of the cloud. Geographically-distributed software delivery teams are now the norm for large projects, and the cloud is a perfect enabler to level the playing field for your distributed teams and to give them all the same ability to achieve high productivity. Since the road to the cloud isn’t always paved, learn many of the trade-offs that must be made to implement cloud-based delivery and discover the situations that will derail a move to cloud-based development.
Scaling Your Tests: Continued Change Without Fear
Agile teams move faster when cycle times are short and code deployments are frequent. To release often, a robust suite of automated tests is a must-have. Tests are the safety net that enables fearless change. Throughout a software system's lifespan, its test suite grows, evolves, and decays. Left unchecked, test execution times increase and non-deterministic failures erode confidence. Ultimately, the test suite that once served as a change-enabler becomes an anchor, grinding progress to a halt. Scaling a test suite is complex and difficult—and vital to successful organizations. Drawing from experience in the trenches, Ryan Scott describes real-world examples of how and why test suites can become burdensome and shares solutions for keeping your test suites tidy. Ryan explores techniques for test parallelization and code restructuring that his company used to decrease the execution time of its test suites by more than 90 percent while more than tripling the number of tests. Take back new ways to fearlessly scale your agile testing.
Seven Deadly Habits of Dysfunctional Software Managers
As if releasing a quality software project on time were not difficult enough, poor management dealing with planning, people, and process issues can be deadly to a project. Presenting a series of anti-pattern case studies, Ken Whitaker describes the most common deadly habits-and ways to avoid them. These seven killer habits are mishandling employee incentives; making key decisions by consensus; ignoring proven processes; delegating absolute control to a project manager; taking too long to negotiate a project's scope; releasing an "almost tested" product to market; and hiring someone who is not quite qualified-but liked by everyone. Whether you are an experienced manager struggling with some of these issues or a new software manager, you'll take away invaluable tips and techniques correcting these habits-or better yet, avoiding them altogether. As a bonus, every attendee will receive a copy of Ken's full-color 7 Deadly Habits comic .
Trends in Big Data Testing
The Big Data has three unique characteristics—Volume, Velocity, and Variety. Today’s big data applications are growing dramatically. We must process data ever more quickly so we can respond to events as they happen, and that data is arriving from an ever wider array of channels, sensors, and formats. Stefano Rizzo explains that the main challenges of testing big data by little agile teams, beside the apparent contradiction, are related to testing individual components vs. testing the big product, traceability, and organizing massive amounts of test data vs. minimal testing with spreadsheets, and testing the final products of development vs. test-driven development. After reviewing these challenges, Stefano shares practices and tools to address both testing Big Data and managing the Testing of Big Data—the huge amount of data coming from massive and continuous testing practices.
Viewers also liked (10)
STARCANADA 2013 Keynote: Lightning Strikes the Keynotes
STARCANADA 2013 Keynote: Lightning Strikes the Keynotes
Enhancing Developer Productivity with Code Forensics
Enhancing Developer Productivity with Code Forensics
Implementing Cloud-Based DevOps for Distributed Agile Projects
Implementing Cloud-Based DevOps for Distributed Agile Projects
Seven Deadly Habits of Dysfunctional Software Managers
Seven Deadly Habits of Dysfunctional Software Managers
Similar to Whiteboarding—for Testers, Developers, and Customers, Too
Testers in Agile Teams—Isolation or Collaboration?
What exactly are testers doing as organizations evolve from waterfall lifecycles to iterative, incremental agile approaches? Agile transitions, rather than fostering collaboration, often lead to isolation, role confusion, and fear. Many testers are left out in the cold. Agile testers face existential challenges: Is it enough that programmers test their own code? Must testers become programming experts? Do we still need business analysts or subject matter experts? Test evangelist Rob Sabourin explores an exciting vision for testers and demonstrates how they can take a role in acting as guiding lights to the entire team. Rob shares real-life examples of testers becoming trusted advisors and confidants to product owners, acting as customer advocates and guardians of the user experience. He explains how testers can drive critical design decisions early, using risk models to expose emergent architectures. Testing skills, knowledge, and wisdom apply in a plethora of circumstances so testers can take the driver’s seat—in every step of the agile transition.
Testing Lessons from the Land of Make Believe
Rob Sabourin has discovered testing lessons in Sesame Street, the Simpsons, the Looney Tunes gang, the Great Detectives, Dr. Seuss, and many other unlikely places, but this year he journeys to the Land of Make Believe. Rob's grandchildren Jane and Suzy draw him into the Land of Make Believe. Every visit is a new adventure. By leaving reality for the realm of play, Rob has discovered many simple truths and clever strategies for solving stubborn technical, management, and people-related software testing problems. An imaginary tea party teaches role playing, simulation, re-focusing, and test leadership. Imaginary messes suggest powerful environment virtualization strategies. Are you robust enough to romp around the playground? Can you bake mud pies with variability, combinations, and permutations? Who can enter the land of make believe without the blessing of beautiful princesses whose whimsical authority demonstrates adapting to stakeholder value systems? Open the tickle chest to discover storyboards, affinity analysis, test design, scenarios, and attacks. Join Rob to wander into the wonderful Land of Make Believe. See if the imagination of Jane and Suzy inspires you with powerful testing ideas.
Exploring Usability Testing
It is not enough to verify that software conforms to requirements by passing established acceptance tests. Successful software products engage, entertain, and support the users' experience. Goals vary from project to project, but no matter how robust and reliable your software is, if your users do not embrace it, business can slip from your hands. Rob Sabourin shares how to elicit effective usability requirements with techniques such as story boarding and task analysis. Together, testers, programmers, and users collaborate to blend the requirement, design, and test cycles into a tight feedback loop. Learn how to select a subset of system functions to test with a small group of users to get high value information at low cost. Learn how usability testers can take advantage of naïve questions from novice users as well as the tunnel vision and bias of domain experts. Rob shares examples of usability testing for a variety of technologies including mobile and web-based products.
Testing in the Dark
Isn't it amazing? Stakeholders drop software on our desks and expect us to test it—without any requirements, design, or product knowledge whatsoever. About the only clear thing is the absurd and unrealistic deadline. We are expected to bend over backward, spread magic pixie dust, and heroically test quality into a product we have never heard of before. But testing in the dark is not impossible, and as Rob Sabourin shows, it can even be a very valuable and fun experience. Learn strategies to emerge from a murky fog into clear, meaningful quality insights. Leverage unlikely sources about what stakeholders care about and what users really need the software to do. Rob introduces you to methods of reconnaissance-style, charter-driven, and session-based exploratory testing and helps you provide meaningful estimates to stakeholders with minimal hard information about the software under test. Rob shares recent experiences testing in the dark on chaotic and turbulent projects, turning his product ignorance into a testing superpower. Join Rob’s quest to find important bugs fast while testing in the dark—and you, too, will see the light!
Testing Lessons Learned from Monty Python
And now for something completely different. Monty Python's Flying Circus revolutionized comedy and brought zany British humor to a worldwide audience. However, buried deep in the hilarity and camouflaged in its twisted wit lie many important testing lessons—tips and techniques you can apply to real world problems to deal with turbulent projects, changing requirements, and stubborn project stakeholders. Rob Sabourin examines some of the most famous Python bits—“The Spanish Inquisition” telling us to expect the unexpected, “The Dead Parrot” asking if we should really deliver this product to the customer, “The Argument” teaching us about bug advocacy, “Self Defense against Fresh Fruit” demonstrating the need to pick the right testing tool, and a host of other goofy gags, each one with a lesson for testers. Learn how to test effectively with persistence, how to make your point with effective communication, and how to clarify project goals and requirements.
Encuesta Ambysoft - IT Project Success 2013
Encuesta Ambysoft sobre la tasa de éxito/fracaso de proyectos TI de noviembre 2013
The Tester’s Role in Agile Planning
All too often testers passively participate in agile planning. And the results? Important testing activities are missed, late testing becomes a bottleneck, and the benefits of agile development quickly diminish. However, testers can actively advocate customer concerns while helping to implement robust solutions. Rob Sabourin shows how testers contribute to estimation, task definition, and scoping work required to implement user stories. Testers apply their elicitation skills to understand what users need, exploring typical, alternate, and error scenarios. Testers can anticipate cross story interference and the impact of new stories on legacy functionality. Rob discusses examples of how to break agile stories into test-related tasks. He shares experiences of transforming agile testers from passive planning participants into dynamic advocates of effective trade-offs, addressing the product owners’ critical business concerns, the teams’ limited resources, and the software projects’ technical risks. Join Rob to explore test infrastructure, test data, non-functional attributes, privacy, security, robustness, exploration, regression, business rules, and more.
The Tester's Role in Agile Planning
If testers sit passively through agile planning, important testing activities will be missed or glossed over. Testing late in the sprint becomes a bottleneck, quickly diminishing the advantages of agile development. However, testers can actively advocate for customers’ concerns while helping the team implement robust solutions. Rob Sabourin shows how testers contribute to the estimation, task definition, clarification, and the scoping work required to implement user stories.
Similar to Whiteboarding—for Testers, Developers, and Customers, Too (8)
Testers in Agile Teams—Isolation or Collaboration?
Testers in Agile Teams—Isolation or Collaboration?
More from TechWell
Failing and Recovering
Do you ever feel you have lost confidence in your own abilities? Why does this happen? Isabel Evans spends a lot of time painting. Someone once commented, “Why are you doing this, when you are not very good at it?” And gradually she stopped drawing and painting, after being intimidated by a conventional vision of what good art should look like. At the same time, she experienced a parallel loss of confidence in her professional abilities. Attempting creative pursuits like drawing and painting is essential to cognitive, emotional, creative abilities and she began to understand the correlation between her creative activities and her confidence. Making errors, being wrong, failing – that is a generous gift we receive when we practice outside our skill level. By staying in a comfort zone and repeating successes, we stagnate. As Isabel started to create again she thought “I don’t feel good at it, I do feel good doing it” The difference was that she was learning, having ideas and the act of re-engaging with failure, together with the comradeship of friends and colleagues, including at Women Who Test, Isabel has regained her confidence in her professional abilities, and been able to reboot her career and joy. Join Isabel to share a journey from self-perceived failure, to recovery and renewed learning.
Instill a DevOps Testing Culture in Your Team and Organization
The DevOps movement is here. Companies across many industries are breaking down siloed IT departments and federating them into product development teams. Testing and its practices are at the heart of these changes. Traditionally, IT organizations have been staffed with mostly manual testers and a limited number of automation and performance engineers. To keep pace with development in the new “you build it, you own it” environment, testing teams and individuals must develop new technical skills and even embrace coding to stay relevant and add greater value to the business. DevOps really starts with testing. Join Adam Auerbach as he explains what DevOps is and how it relates to testing. He describes how testing must change from top to bottom and how to access your own environment to identify improvement opportunities. Adam dives into practices like service virtualization, test data management, and continuous testing so you can understand where you are now and identify steps needed to instill a DevOps testing culture in your team and organization.
Test Design for Fully Automated Build Architecture
Imagine this … As soon as any developed functionality is submitted into the code repository, it is automatically subjected to the appropriate battery of tests and then released straight into production. Setting up the pipeline capable of doing just that is becoming more and more common and something you need to know about. But most organizations hit the same stumbling block—just what IS the appropriate battery of tests? Automated build architectures don't always lend themselves well to the traditional stages of testing. In this hands-on tutorial, Melissa Benua introduces you to key test design principles—applicable to organizations both large and small—that allow you to take full advantage of the pipeline's capabilities without introducing unnecessary bottlenecks. Learn how to make highly reliable tests that run fast and preserve just enough information to let testers and developers determine exactly what went wrong and how to reproduce the error locally. Explore ways to reduce overlap while still maintaining adequate test coverage. Take back ideas about which test areas could benefit from being combined into a single suite and which areas could benefit most from being broken out altogether.
System-Level Test Automation: Ensuring a Good Start
Many organizations invest a lot of effort in test automation at the system level but then have serious problems later on. As a leader, how can you ensure that your new automation efforts will get off to a good start? What can you do to ensure that your automation work provides continuing value? This tutorial covers both “theory” and “practice”. Dot Graham explains the critical issues for getting a good start, and Chris Loder describes his experiences in getting good automation started at a number of companies. The tutorial covers the most important management issues you must address for test automation success, particularly when you are new to automation, and how to choose the best approaches for your organization—no matter which automation tools you use. Focusing on system level testing, Dot and Chris explain how automation affects staffing, who should be responsible for which automation tasks, how managers can best support automation efforts to promote success, what you can realistically expect in benefits and how to report them. They explain—for non-techies—the key technical issues that can make or break your automation effort. Come away with your own clarified automation objectives, and a draft test automation strategy to use to plan your own system-level test automation.
Build Your Mobile App Quality and Test Strategy
Let’s build a mobile app quality and testing strategy together. Whether you have a web, hybrid, or native app, building a quality and testing strategy means (1) knowing what data and tools you have available to make agile decisions, (2) understanding your customers and your competitors, and (3) testing your app under real-world conditions. Jason Arbon guides you through the latest techniques, data, and tools to ensure the awesomeness of your mobile app quality and testing strategy. Leave this interactive session with a strategy for your very own app—or one you pretend to own. The information Jason shares is based on data from Appdiff’s next-gen mobile app testing platform, lessons from Applause/uTest’s crowd, text mining hundreds of millions of app store reviews, and in-depth discussions with top mobile app development teams.
Testing Transformation: The Art and Science for Success
Technologies, testing processes, and the role of the tester have evolved significantly in the past few years with the advent of agile, DevOps, and other new technologies. It is critical that we testing professionals evaluate ourselves and continue to add tangible value to our organizations. In your work, are you focused on the trivial or on real game changers? Jennifer Bonine describes critical elements that help you artfully blend people, process, and technology to create a synergistic relationship that adds value. Jennifer shares ideas on mastering politics, maneuvering core vs. context, and innovating your technology strategies and processes. She explores how new processes can be introduced in an organization, what the role of organizational culture is in determining the success of a project, and how you can know what tools will add value vs. simply adding overhead and complexity. Jennifer reviews critically needed tester skills and discusses a continual learning model to evolve your skills and stay relevant. This discussion can lead you to technologies, processes, and skills you can stake your career on.
Implement BDD with Cucumber and SpecFlow
We’ve all been there. We work incredibly hard to develop a feature and design tests based on written requirements. We build a detailed test plan that aligns the tests with the software and the documented business needs. And when we put the tests to the software, it all falls apart because the requirements were changed without informing everyone. Mary Thorn says help is at hand. Enter behavior-driven development (BDD), and Cucumber and SpecFlow, tools for running automated acceptance tests and facilitating BDD. Mary explores the nuances of Cucumber and SpecFlow, and shows you how to implement BDD and agile acceptance testing. By fostering collaboration for implementing active requirements via a common language and format, Cucumber and SpecFlow bridge the communication gap between business stakeholders and implementation teams. In this workshop, practice writing feature files with the best practices Mary has discovered over numerous implementations. If you experience developers not coding to requirements, testers not getting requirements updates, or customers who feel out of the loop and don’t get what they ask for, Mary has answers for you.
Develop WebDriver Automated Tests—and Keep Your Sanity
Many teams go crazy because of brittle, high-maintenance automated test suites. Jim Holmes helps you understand how to create a flexible, maintainable, high-value suite of functional tests using Selenium WebDriver. Learn the basics of what to test, what not to test, and how to avoid overlapping with other types of testing. Jim includes both philosophical concepts and hands-on coding. Testers who haven't written code should not be intimidated! We'll pair you up to make sure you're successful. Learn to create practical tests dealing with advanced situations such as input validation, AJAX delays, and working with file downloads. Additionally, discover when you need to work together with developers to create a system that's more easily testable. This tutorial focuses primarily on automating web tests, but many of the same concepts can be applied to other UI environments. Demos and labs will be in C# and Java using WebDriver. Leave this tutorial having learned how to write high-value WebDriver tests—and stay sane while doing so.
Ma 15
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Eliminate Cloud Waste with a Holistic DevOps Strategy
Chris Parlette maintains that renting infrastructure on demand is the most disruptive trend in IT in decades. In 2016, enterprises spent $23B on public cloud IaaS services. By 2020, that figure is expected to reach $65B. The public cloud is now used like a utility, and like any utility, there is waste. Who's responsible for optimizing the infrastructure and reducing wasted expenses? It’s DevOps. The excess expense, known as cloud waste, comprises several interrelated problems: services running when they don't need to be, improperly sized infrastructure, orphaned resources, and shadow IT. There are a few core tenets of DevOps—holistic thinking, no silos, rapid useful feedback, and automation—that can be applied to reducing your cloud waste. Join Chris to learn why you should include continuous cost optimization in your DevOps processes. Automate cost control, reduce your cloud expenses, and make your life easier.
Transform Test Organizations for the New World of DevOps
With the recent emergence of DevOps across the industry, testing organizations are being challenged to transform themselves significantly within a short period of time to stay meaningful within their organizations. It’s not easy to plan and approach these changes considering the way testing organizations have remained structured for ages. These challenges start from foundational organizational structures and can cut across leadership influence, competencies, tools strategy, infrastructure, and other dimensions. Sumit Kumar shares his experience assisting various organizations to overcome these challenges using an organized DevOps enablement framework. The framework includes radical restructuring, turning the tools strategy upside down, a multidimensional workforce enablement supported by infrastructure changes, redeveloped collaborations models, and more. From his real world experiences Sumit shares tips for approaching this journey and explains the roadmap for testing organizations to transform themselves to lead the quality in DevOps.
The Fourth Constraint in Project Delivery—Leadership
All too often, the triple constraints—time, cost, and quality—are bandied about as if they are the be-all, end-all. While they are important, leadership—the fourth and larger underpinning constraint—influences the first three. Statistics on project success and failure abound, and these measurements are usually taken against the triple constraints. According to the Project Management Institute, only 53 percent of projects are completed within budget, and only 49 percent are completed on time. If so many projects overrun budget and are late, we can’t really say, “Good, fast, or cheap—pick two.” Rob Burkett talks about leadership at every level of a team. He shares his insights and stories gleaned from his years of IT and project management experience. Rob speaks to some of the glaring difficulties in the workplace in general and some specifically related to IT delivery and project management. Leave with a clearer understanding of how to communicate with teams and team members, and gain a better understanding of how you can be a leader—up and down your organization.
Resolve the Contradiction of Specialists within Agile Teams
As teams grow, organizations often draw a distinction between feature teams, which deliver the visible business value to the user, and component teams, which manage shared work. Steve Berczuk says that this distinction can help organizations be more productive and scale effectively, but he recognizes that not all shared work fits into this model. Some work is best handled by “specialists,” that is people with unique skills. Although teams composed entirely of T-shaped people is ideal, certain skills are hard to come by and are used irregularly across an organization. Since these specialists often need to work closely with teams, rather than working from their own backlog, they don’t fit into the component team model. The use of shared resources presents challenges to the agile planning model. Steve Berczuk shares how teams such as those providing infrastructure services and specialists can fit into a feature+component team model, and how variations such as embedding specialists in a scrum team can both present process challenges and add significant value to both the team and the larger organization.
Pin the Tail on the Metric: A Field-Tested Agile Game
Metrics don’t have to be a necessary evil. If done right, metrics can help guide us to make better forward-looking decisions, rather than being used for simply managing or monitoring. They can help us identify trade-offs between options for what to do next versus punitive or worse, purely managerial measures. Steve Martin won’t be giving the Top Ten List of field-tested metrics you should use. Instead, in this interactive mini-workshop, he leads you through the critical thinking necessary for you to determine what is right for you to measure. First, Steve explores why you want to measure something—whether it’s for a team, a portfolio, or even an agile transformation. Next, he provides multiple real-life metrics examples to help drive home concepts behind characteristics of good and bad metrics. Finally, Steve shows how to run his field-tested agile game—Pin the Tail on the Metric. Take back this activity to help you guide metrics conversations at your organization.
Agile Performance Holarchy (APH)—A Model for Scaling Agile Teams
A hierarchy is an organizational network that has a top and a bottom, and where position is determined by rank, importance, and value. A holarchy is a network that has no top or bottom and where each person’s value derives from his ability, rather than position. As more companies seek the benefits of agile, leaders need to build and sustain delivery capability while scaling agile without introducing unnecessary process and overhead. The Agile Performance Holarchy (APH) is an empirical model for scaling and sustaining agility while continuing to deliver great products. Jeff Dalton designed the APH by drawing from lessons learned observing and assessing hundreds of agile companies and teams. The APH helps implement a holarchy—a system composed of interacting organizational units called holons—centered on a series of performance circles that embody the behaviors of high performing agile organizations. Jeff describes how APH provides guidelines in the areas of leadership, values, teaming, visioning, governing, building, supporting, and engaging within an all-agile organization. Join Jeff to see what the APH is all about and how you can use it in your team and organization.
A Business-First Approach to DevOps Implementation
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Databases in a Continuous Integration/Delivery Process
DevOps is transforming software development with many organizations adopting lean development practices, implementing continuous integration (CI), and performing regular continuous deployment (CD) to their production environments. However, the database is largely ignored and often seen as a bottleneck in the DevOps process. Steve Jones discusses the challenges of database development and why many developers find the database to be an impediment to the CD process. Steve shares the techniques you can use to fit a database into the DevOps process. Learn how to store database code in a version control system, and the differences between that and application code. Steve demonstrates a CI process with SQL code and uses automated testing frameworks to check the code. Steve then shows how automated releases with manual gates can reduce the stress and risk of database deployments while ensuring consistent, reliable, repeatable releases to QA, UAT, and production.
Mobile Testing: What—and What Not—to Automate
Organizations are moving rapidly into mobile technology, which has significantly increased the demand for testing of mobile applications. David Dangs says testers naturally are turning to automation to help ease the workload, increase potential test coverage, and improve testing efficiency. But should you try to automate all things mobile? Unfortunately, the answer is not always clear. Mobile has its own set of complications, compounded by a wide variety of devices and OS platforms. Join David to learn what mobile testing activities are ripe for automation—and those items best left to manual efforts. He describes the various considerations for automating each type of mobile application: mobile web, native app, and hybrid applications. David also covers device-level testing, types of testing, available automation tools, and recommendations for automation effectiveness. Finally, based on his years of mobile testing experience, David provides some tips and tricks to approach mobile automation. Leave with a clear plan for automating your mobile applications.
Cultural Intelligence: A Key Skill for Success
Diversity is becoming the norm in everyday life. However, introducing global delivery models without a proper understanding of intercultural differences can lead to difficulty, frustration, and reduced productivity. Priyanka Sharma and Thena Barry say that in our diverse world, we need teams with people who can cross these boundaries, communicate effectively, and build the diverse networks necessary to avoid problems. We need to learn about cultural intelligence (CI) and cultural quotient (CQ). CI is the ability to relate and work effectively across cultures. CQ is the cognitive, motivational, and behavioral capacity to understand and respond to beliefs, values, attitudes, and behaviors of individuals and groups. Together, CI and CQ can help us build behavioral capacities that aid motivation, behavior, and productivity in teams as well as individuals. Priyanka and Thena show how to build a more culturally intelligent place with tools and techniques from Leading with Cultural Intelligence, as well as content from the Hofstede cultural model. In addition, they illustrate the model with real-life experiences and demonstrate how they adapted in similar circumstances.
Turn the Lights On: A Power Utility Company's Agile Transformation
Why would a century-old utility with no direct competitors take on the challenge of transforming its entire IT application organization to an agile methodology? In an increasingly interconnected world, the expectations of customers continue to evolve. From smart meters to smart phones, IoT is creating a crisis point for industries not accustomed to rapid change. Glen Morris explains that pizzas can be tracked by the minute and packages at every stop, and customers now expect this same customer service model should exist for all industries—including power. Glen examines how to create momentum and transform non-IT-focused industries to an agile model. If you are struggling with gaining traction in your pursuit of agile within your business, Glen gives you concrete, practical experiences to leverage in your pursuit. Finally, he communicates how to gain buy-in from business partners who have no idea or concern about agile or its methodologies. If your business partners look at you with amusement when you mention the need for a dedicated Product Owner, join Glen as he walks you through the approaches to overcoming agile skepticism.
More from TechWell (20)
Instill a DevOps Testing Culture in Your Team and Organization
Instill a DevOps Testing Culture in Your Team and Organization
Test Design for Fully Automated Build Architecture
Test Design for Fully Automated Build Architecture
System-Level Test Automation: Ensuring a Good Start
System-Level Test Automation: Ensuring a Good Start
Testing Transformation: The Art and Science for Success
Testing Transformation: The Art and Science for Success
Develop WebDriver Automated Tests—and Keep Your Sanity
Develop WebDriver Automated Tests—and Keep Your Sanity
Eliminate Cloud Waste with a Holistic DevOps Strategy
Eliminate Cloud Waste with a Holistic DevOps Strategy
Transform Test Organizations for the New World of DevOps
Transform Test Organizations for the New World of DevOps
The Fourth Constraint in Project Delivery—Leadership
The Fourth Constraint in Project Delivery—Leadership
Resolve the Contradiction of Specialists within Agile Teams
Resolve the Contradiction of Specialists within Agile Teams
Pin the Tail on the Metric: A Field-Tested Agile Game
Pin the Tail on the Metric: A Field-Tested Agile Game
Agile Performance Holarchy (APH)—A Model for Scaling Agile Teams
Agile Performance Holarchy (APH)—A Model for Scaling Agile Teams
A Business-First Approach to DevOps Implementation
A Business-First Approach to DevOps Implementation
Databases in a Continuous Integration/Delivery Process
Databases in a Continuous Integration/Delivery Process
Turn the Lights On: A Power Utility Company's Agile Transformation
Turn the Lights On: A Power Utility Company's Agile Transformation
Recently uploaded
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Elevating Tactical DDD Patterns Through Object Calisthenics
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
A tale of scale & speed: How the US Navy is enabling software delivery from l...
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Essentials of Automations: The Art of Triggers and Actions in FME
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
GraphRAG is All You need? LLM & Knowledge Graph
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Epistemic Interaction - tuning interfaces to provide information for AI support
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Elizabeth Buie - Older adults: Are we really designing for our future selves?
Elizabeth Buie - Older adults: Are we really designing for our future selves?
Securing your Kubernetes cluster_ a step-by-step guide to success !
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Removing Uninteresting Bytes in Software Fuzzing
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
The Metaverse and AI: how can decision-makers harness the Metaverse for their...
The Metaverse is popularized in science fiction, and now it is becoming closer to being a part of our daily lives through the use of social media and shopping companies. How can businesses survive in a world where Artificial Intelligence is becoming the present as well as the future of technology, and how does the Metaverse fit into business strategy when futurist ideas are developing into reality at accelerated rates? How do we do this when our data isn't up to scratch? How can we move towards success with our data so we are set up for the Metaverse when it arrives?
How can you help your company evolve, adapt, and succeed using Artificial Intelligence and the Metaverse to stay ahead of the competition? What are the potential issues, complications, and benefits that these technologies could bring to us and our organizations? In this session, Jen Stirrup will explain how to start thinking about these technologies as an organisation.
DevOps and Testing slides at DASA Connect
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
UiPath Community Day Dubai: AI at Work..
Welcome to the first live UiPath Community Day Dubai! Join us for this unique occasion to meet our local and global UiPath Community and leaders. You will get a full view of the MEA region's automation landscape and the AI Powered automation technology capabilities of UiPath. Also, hosted by our local partners Marc Ellis, you will enjoy a half-day packed with industry insights and automation peers networking.
📕 Curious on our agenda? Wait no more!
10:00 Welcome note - UiPath Community in Dubai
Lovely Sinha, UiPath Community Chapter Leader, UiPath MVPx3, Hyper-automation Consultant, First Abu Dhabi Bank
10:20 A UiPath cross-region MEA overview
Ashraf El Zarka, VP and Managing Director MEA, UiPath
10:35: Customer Success Journey
Deepthi Deepak, Head of Intelligent Automation CoE, First Abu Dhabi Bank
11:15 The UiPath approach to GenAI with our three principles: improve accuracy, supercharge productivity, and automate more
Boris Krumrey, Global VP, Automation Innovation, UiPath
12:15 To discover how Marc Ellis leverages tech-driven solutions in recruitment and managed services.
Brendan Lingam, Director of Sales and Business Development, Marc Ellis
Video Streaming: Then, Now, and in the Future
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Recently uploaded (20)
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
Elevating Tactical DDD Patterns Through Object Calisthenics
Elevating Tactical DDD Patterns Through Object Calisthenics
A tale of scale & speed: How the US Navy is enabling software delivery from l...
A tale of scale & speed: How the US Navy is enabling software delivery from l...
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
Secstrike : Reverse Engineering & Pwnable tools for CTF.pptx
Secstrike : Reverse Engineering & Pwnable tools for CTF.pptx
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Epistemic Interaction - tuning interfaces to provide information for AI support
Epistemic Interaction - tuning interfaces to provide information for AI support
Elizabeth Buie - Older adults: Are we really designing for our future selves?
Elizabeth Buie - Older adults: Are we really designing for our future selves?
Securing your Kubernetes cluster_ a step-by-step guide to success !
Securing your Kubernetes cluster_ a step-by-step guide to success !
FIDO Alliance Osaka Seminar: FIDO Security Aspects.pdf
FIDO Alliance Osaka Seminar: FIDO Security Aspects.pdf
Assure Contact Center Experiences for Your Customers With ThousandEyes
Assure Contact Center Experiences for Your Customers With ThousandEyes
The Metaverse and AI: how can decision-makers harness the Metaverse for their...
The Metaverse and AI: how can decision-makers harness the Metaverse for their...
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024
Whiteboarding—for Testers, Developers, and Customers, Too
- 1. Whiteboarding Robert Sabourin President AmiBug.Com, Inc. Montreal, Canada rsabourin@amibug.com January 16, 2014 © Robert Sabourin, 2012 Slide 1 AmiBug.Com, Inc.
- 2. Whiteboarding • Robert Sabourin , Software Evangelist • President • AmiBug.Com Inc. • Montreal, Quebec, Canada • rsabourin@amibug.com • www.amibug.com January 16, 2014 © Robert Sabourin, 2012 Slide 2 AmiBug.Com, Inc.
- 3. Whiteboarding January 16, 2014 © Robert Sabourin, 2012 Slide 3 AmiBug.Com, Inc.
- 4. Whiteboarding January 16, 2014 © Robert Sabourin, 2012 Slide 4 AmiBug.Com, Inc.
- 5. Whiteboarding January 16, 2014 © Robert Sabourin, 2012 Slide 5 AmiBug.Com, Inc.
- 6. Whiteboarding What is Whiteboarding? Collaboration Coordination Conceptualization January 16, 2014 © Robert Sabourin, 2012 Slide 6 AmiBug.Com, Inc.
- 7. Whiteboarding Collaboration Get together Join forces Cooperate January 16, 2014 © Robert Sabourin, 2012 Slide 7 AmiBug.Com, Inc.
- 8. Whiteboarding Coordination Organize Manage Align January 16, 2014 © Robert Sabourin, 2012 Slide 8 AmiBug.Com, Inc.
- 9. To Do Whiteboarding January 16, 2014 © Robert Sabourin, 2012 Slide 9 AmiBug.Com, Inc.
- 10. Kanban Whiteboarding January 16, 2014 © Robert Sabourin, 2012 Slide 10 AmiBug.Com, Inc.
- 11. Homeban Whiteboarding January 16, 2014 © Robert Sabourin, 2012 Slide 11 AmiBug.Com, Inc.
- 12. Homeban Whiteboarding January 16, 2014 © Robert Sabourin, 2012 Slide 12 AmiBug.Com, Inc.
- 13. Whiteboarding Conceptualization Generate ideas Design Visualize January 16, 2014 © Robert Sabourin, 2012 Slide 13 AmiBug.Com, Inc.
- 14. Web Globalization Whiteboarding January 16, 2014 © Robert Sabourin, 2012 Slide 14 AmiBug.Com, Inc.
- 15. Web Globalization Whiteboarding January 16, 2014 © Robert Sabourin, 2012 Slide 15 AmiBug.Com, Inc.
- 16. Web Globalization Whiteboarding January 16, 2014 © Robert Sabourin, 2012 Slide 16 AmiBug.Com, Inc.
- 17. Compare Design Alternatives Whiteboarding January 16, 2014 © Robert Sabourin, 2012 Slide 17 AmiBug.Com, Inc.
- 18. Mind Maps Tony Buzan January 16, 2014 © Robert Sabourin, 2012 Slide 18 AmiBug.Com, Inc.
- 19. Scenario Based Testing January 16, 2014 © Robert Sabourin, 2012 Slide 19 AmiBug.Com, Inc.
- 20. User Mind Map Whiteboarding January 16, 2014 © Robert Sabourin, 2012 Slide 20 AmiBug.Com, Inc.
- 21. Buying a Book Usage Scenarios January 16, 2014 © Robert Sabourin, 2012 Slide 21 AmiBug.Com, Inc.
- 22. Story Board Whiteboarding January 16, 2014 © Robert Sabourin, 2012 Slide 22 AmiBug.Com, Inc.
- 23. January 16, 2014 © Robert Sabourin, 2012 Slide 23 AmiBug.Com, Inc.
- 24. January 16, 2014 © Robert Sabourin, 2012 Slide 24 AmiBug.Com, Inc.
- 25. January 16, 2014 © Robert Sabourin, 2012 Slide 25 AmiBug.Com, Inc.
- 26. Social Networking Usage Scenarios January 16, 2014 © Robert Sabourin, 2012 Slide 26 AmiBug.Com, Inc.
- 27. January 16, 2014 © Robert Sabourin, 2012 Slide 27 AmiBug.Com, Inc.
- 28. Scenario Based Testing January 16, 2014 © Robert Sabourin, 2012 Slide 28 AmiBug.Com, Inc.
- 29. Scenario Based Testing January 16, 2014 © Robert Sabourin, 2012 Slide 29 AmiBug.Com, Inc.
- 30. Scenario Based Testing January 16, 2014 © Robert Sabourin, 2012 Slide 30 AmiBug.Com, Inc.
- 31. Scenario Based Testing January 16, 2014 © Robert Sabourin, 2012 Slide 31 AmiBug.Com, Inc.
- 32. Scenario Based Testing January 16, 2014 © Robert Sabourin, 2012 Slide 32 AmiBug.Com, Inc.
- 33. Scenario Based Testing January 16, 2014 © Robert Sabourin, 2012 Slide 33 AmiBug.Com, Inc.
- 34. Scenario Based Testing January 16, 2014 © Robert Sabourin, 2012 Slide 34 AmiBug.Com, Inc.
- 35. Scenario Based Testing January 16, 2014 © Robert Sabourin, 2012 Slide 35 AmiBug.Com, Inc.
- 36. Test Design Failure Mode Analysis January 16, 2014 © Robert Sabourin, 2012 Slide 36 AmiBug.Com, Inc.
- 37. Failure Mode Analysis Failure Mode and Effects Analysis Create block diagram List classes of users Find elements which can fail Create usage/failure table Rank potential failure impacts January 16, 2014 © Robert Sabourin, 2012 Slide 37 AmiBug.Com, Inc.
- 38. Failure Mode Analysis Create block diagram Blocks Connector • System Elements • Processes • Subsystems • Logical relationships • Physical relationships • Process invocations January 16, 2014 © Robert Sabourin, 2012 Slide 38 AmiBug.Com, Inc.
- 39. Failure Mode Analysis List classes of users Who are the users? What are they doing? Classes Personas Context January 16, 2014 © Robert Sabourin, 2012 Slide 39 AmiBug.Com, Inc.
- 40. Failure Mode Analysis Find elements which can fail • Break • Constrained • Slow • ABEND • Crash January 16, 2014 © Robert Sabourin, 2012 Slide 40 AmiBug.Com, Inc.
- 41. Failure Mode Analysis Create usage/failure table •Scenarios •Interesting blocks January 16, 2014 © Robert Sabourin, 2012 Slide 41 AmiBug.Com, Inc.
- 42. Failure Mode Analysis Rank potential failure impacts S4 – Cosmetic • User can accomplish the task with some inconvenience January 16, 2014 S3 – S2 – Work around No Work around • User can accomplish task by working around the problem • User cannot accomplish some tasks S1 – Show stopper • User cannot accomplish any tasks © Robert Sabourin, 2012 S0 – No Impact • User can accomplish the task Slide 42 AmiBug.Com, Inc.
- 43. Wrap-O-Matic Failure Mode Analysis January 16, 2014 © Robert Sabourin, 2012 Slide 43 AmiBug.Com, Inc.
- 44. Failure Modes Whiteboarding January 16, 2014 © Robert Sabourin, 2012 Slide 44 AmiBug.Com, Inc.
- 45. Failure Mode Analysis January 16, 2014 © Robert Sabourin, 2012 Slide 45 AmiBug.Com, Inc.
- 46. Failure Mode Analysis January 16, 2014 © Robert Sabourin, 2012 Slide 46 AmiBug.Com, Inc.
- 47. Prize Server Failure Mode Analysis January 16, 2014 © Robert Sabourin, 2012 Slide 47 AmiBug.Com, Inc.
- 48. Failure Mode Analysis Prize Manageme nt Interface Prize Status Reporter January 16, 2014 Prize Table Prize Server Game Server Prize Spinner Game Server System Elements © Robert Sabourin, 2012 Slide 48 AmiBug.Com, Inc.
- 49. Failure Mode Analysis Users Prize Administrator Database Administrator Auditor Player January 16, 2014 © Robert Sabourin, 2012 Slide 49 AmiBug.Com, Inc.
- 50. Game Server Prize Spinner S1 S0 S0 S0 Prize Administrator Change prize dates S3 S0 S1 S0 S0 S0 Prize Administrator Change prize amounts S3 S0 S1 S0 S0 S0 Prize Administrator Stop prizes S3 S0 S1 S0 S0 S0 Prize Administrator Start prizes S3 S0 S1 S0 S0 S0 S0 S0 S1 S0 S0 S0 S0 S0 S1 S0 S0 S0 Database Administrator Prize Server S0 Scenario Prize Table S1 User Prize Status Reporter Add prize Prize Management Interface Prize Administrator Prize System Failure Modes Failure Mode Analysis What if the process fails? Report prize status Database Administrator Modify prize status Auditor View prize schedule S0 S3 S1 S0 S0 S0 Auditor View prizes awarded S0 S3 S1 S0 S0 S0 Auditor View prizes remaining S0 S3 S1 S0 S0 S0 Player Spin for prize S0 S1 S1 January 16, 2014 S0 © Robert Sabourin, 2012 S1 Slide 50 S1 AmiBug.Com, Inc.
- 51. Thank You • Questions? January 16, 2014 © Robert Sabourin, 2012 Slide 51 AmiBug.Com, Inc.