Continuous Quality - Moving Beyond Bug Reports

•Download as PPTX, PDF•

1 like•312 views

In 2015, I ran a workshop at TestBash Brighton entitled "Supercharging Your Bug Reports" (also available in webinar format on the Ministry of Testing Dojo). In that class, I outlined some of the key components of an effective bug report, with the goal of helping testers to become better advocates for problems in their workplace. Fast-forward to 2017, and my world (and beliefs) have changed. I've been working in some fast-paced environments with highly-productive teams, where life moves at a pace which is largely incompatible with "traditional" bug reporting processes. How do you effectively act as a champion for quality when one of your most visible forms of communication is taken away? In this talk, I'll share stories of my transition: how I had to adapt, the approaches that I chose to take, and evaluate how my 2017 outlook on bug reporting compares to my previous vision.

CONTINUOUS
QUALITY Moving beyond
bug reports
TODO: REPLACE TERRIBLE BORING TITLE SLIDE WITH SOMETHING INTERESTING

Enterprise
Distributed
across
timezones
Infrequent
releases
Server/desktop
architecture
Bug Review
Committees
Requirement
documents

“Neil is some kind of Navy
SEAL tester who’s decided
to take this class”

Agile /
kanban
Frequent
releases
Short
projects
Challenging
deadlines
Regulatory
pressures
Marketing
campaigns

BUGS…
• Difference between
perceived and desired
• Something that bugs
somebody who matters
• A threat to value
• (Problems, defects, issues)
• A snapshot of information
• A placeholder for conversation
• Communicate within team
• Surface info to stakeholders
• To guide decisions
BUG REPORTS…
If a bug isn’t written in a bug report… it’s still a bug!

ZERO-TOLERANCE BUG POLICY
• YAGNI – If not now, then not later either!
• Deal with mess as it arises
• Avoids “bug tennis”
• Weekly code-freeze for release: tackle what little remains
• BUT: Hard if external parties (clients, support) want involvement

THE TOOLS TO FIX IT YOURSELF
• Domain knowledge
• Understanding of codebase/standards
• Know your personal limitations
• Know what your team is comfortable with
• Show the fix to the developer (keep the feedback cycle)
++positivity;
++respect;
++gratitude;
--blame_game;
++credibility;

GET INVOLVED EARLIER
• Get the team thinking about testing (and testability) early
• Reduce feedback/cycle time
• Dev and test, complementing each other, working in harmony

As close to the code as
you can get
Mob Programming
(Woody Zuill)
Shared expertise
Better understanding
of what’s been tested

PRACTICAL AUTOMATION
• Doesn’t have to be a fully autonomous solution!
• Small scripts/tool/helpers
• Automate the pain points of daily life
• Lower cost (only needs to be as good as the job it’s serving)
• Recognise opportunities to practice
• Seek forgiveness, not permission

LOGGING AND MONITORING
• “Free testing”!
• Not just useful for support/ops
• Rich supply of information
• Make it queryable
• Some teams do all of their testing this way
• Reliance depends on risk appetite

"environment":"prod"
claimAmount is missing

METRICS
• Bug counts are a lousy metric
• Get qualitative information
• Interview team members
• What’s going well, what’s going badly
• Ask your testers what challenges they face
• “But that takes time and effort…” - Good!
• “But that’s difficult to scale…” – Don’t over-manage!
• Hire great people. Trust them. Support them.

A MANIFESTO FOR CONTINUOUS QUALITY
• Encourage easier communication
• Highlight problems
• Reveal value (and threats to value)
• Get involved earlier
• Arm yourself with tools/knowledge to work alongside developers
• Make bold and courageous choices
• Deliver quality software quicker
(a work-in-progress!)

THANKS FOR LISTENING!
@neilstudd @ScreenTesting

The document discusses incorporating user experience (UX) design into an Agile development methodology. It outlines the key parts of Agile like user stories, backlogs, and sprints. It then provides three principles for combining UX and Agile: iterate by making mistakes faster, scale by doing more with less, and simplify by keeping things "good enough." Specific tactics are described like using Sprint Zero to get ahead, prioritizing work, and embracing failures to find solutions. The importance of the UX designer's mindset and role on an Agile team is emphasized.

Agile Impact 2018: Feature Experimentation

Thomas Rothe

Experimentation, as the gold standard to measure new product initiatives, has become an indispensable component of product development cycles in the online world. The ability to automatically collect user interaction data online has given companies an unprecedented opportunity to run many experiments at the same time, allowing them to iterate rapidly, fail fast, and deliver the highest user value. In this talk, i spoke about the approach of experimentation and how it fits into the development process of products. http://agileimpact.id/ #AICON18

Sechs Jahre Erfahrungen mit Scrum & Tools - eine Retrospektive

mkloss

This document reflects on the author's six years of experience using Scrum tools and discusses how their perspective on tools has evolved over time. Initially tools were seen as very useful, but the author later felt something was missing when relying solely on tools. Through experimenting with different approaches like using a physical wall and spending time together in person, the author found teams interacted more and had fewer misunderstandings. However, tools may still have a role to play, especially for distributed teams, but the focus should be on the team rather than the tools.

Pavel Kamyshov "Team Health Check" Kyiv PM Club

Lviv Startup Club

The document describes a Team Health Check model used at EPAM to monitor team health and identify issues. Key aspects include anonymized surveys of individuals every 3 months, tracking trends over time across various topics like work environment, growth opportunities, and satisfaction. Previous issues like demotivation and failed sprints were addressed. The checks identified top problems like code quality, process suitability, and satisfaction. Initiative groups then worked to reverse negative trends in these areas. Pitfalls to avoid include not sharing or acting on results and making the checks performative rather than meaningful.

Exploratory testing

Aleksis Tulonen

This document discusses exploratory testing and provides definitions and concepts related to testing. It defines testing, quality, bugs, and why we test. It then discusses exploratory testing and how it is about continuous learning. Elements of exploratory testing discussed include test design, careful observation, critical thinking, diverse ideas, and rich resources. Specific techniques like session-based testing, heuristics, oracles, and fractals are also covered. The importance of context and skills like communication, courage, and self-esteem for testers are emphasized.

[HCMC STC Jan 2015] Developing an Offshore Context-Driven Testing Team

Ho Chi Minh City Software Testing Club

Ho Chi Minh City Software Testing Conference January 2015 Software Testing in the Agile World Website: www.hcmc-stc.org Author: Lee Hawkins With a growing product portfolio and limited capacity to expand in Melbourne, the opportunity arose to build a testing capability in the Dell office in Zhuhai, in the Guangdong province of China. He's been working closely with this growing team of young inexperienced testers for the last two years. Collaborating with this enthusiastic offshore team has been a three-way challenge: dealing with cultural differences, overcoming the language barrier, and challenging the traditional software testing status quo. In this presentation, he will share his personal experience of collaborating with these young testers to develop a performance & creative context-driven testing team - the first time this had been attempted within this office in China. By sharing this experience, he hopes to highlight areas where offshore teams themselves can help those working with them, particularly across significant cultural divides.

Becoming a Salesforce.com Technical Architect

Steven Herod

This document provides guidance on conducting a usability study. It outlines the schedule, expectations for participants, and guidelines for running test sessions. Participants will be divided into groups of 3, with one person acting as the user and two observing. As a user, they will complete tasks while thinking aloud, and observers will take notes on successes, obstacles, and areas of confusion. After each task the group will switch roles. The goal is to evaluate the design and identify ways to improve the user experience.

Cheap'n'easy usability

Paul Canning

This document provides guidance on how to conduct low-cost or "discount" usability testing. It notes that usability testing does not require specialized expertise and can be done by following some basic steps. Such testing involves observing users complete simple tasks on a website or prototype and noting where they succeed or fail. While confronting at times, these tests can help identify usability issues and save costs compared to not testing. The document recommends starting with 5-7 test participants and observing each other conduct tests before analyzing the results for common problems and user feedback.

Trust Me, I'm An Architect

Keir Bowden

amccormick_conference_talk

Andy McCormick

Andy McCormick's development team experienced a flood that damaged their office. They were able to continue working remotely using cloud-based tools like Jira and HipChat. After cleaning up the office, they moved back within a month without losing workflow. McCormick recommends identifying current issues, evaluating cloud options, getting team buy-in, testing options, making a decision, planning rollout with leadership and accountability, communicating the reasons for change, and documenting decisions to onboard new employees and survive future disruptions.

Intro to Lean UX with UserTesting

Carlos González de Villaumbrosia

This document provides an introduction to Lean UX and UserTesting. It defines UX and Lean UX, discusses the benefits of user testing such as increased revenue and decreased costs, and outlines the UserTesting process including defining objectives, writing tasks, analyzing results, and using metrics and notes. UserTesting allows remote, unmoderated usability testing of digital products through video recordings of testers interacting with designs. The document provides tips for effective user testing through UserTesting.

Usability Testing Basics: Remote and In-Person Studies

UXPA International

This document provides an agenda and overview for a workshop on getting started with usability testing. The workshop will include introductions, presentations on measurements and testing, and activities for planning test logistics and interacting with participants. It will cover why usability testing is important, common myths, and tips for getting started. Participants will learn about planning and preparing for tests, recruiting profiles, scripts, test materials, facilitating sessions, and reporting results. The goal is to help attendees understand the basics of usability testing and conduct initial tests.

Usability testing tips for UX Designers

David Hamill

This document provides tips for usability testing from a usability specialist at Skyscanner. Some key tips include: - Conduct small, frequent usability tests with around 6 participants rather than large lab studies - There is no single best way to do usability testing and you have to sacrifice aspects of the process - Remember that participants are not like real users in the way they will use the product - Expect that the initial design will have problems and be prepared to iterate based on test findings

Rethinking UX Research - Design4Drupal 2014 keynote presentation

Perfetti Media

How do you really know what your users want? How do you ensure your designs work for your prospects and customers? How can you be confident that your design changes improve your site? There are those that believe that user research must be a complex and scientific process that takes a lot of time, money, and resources. However, in the real world, most designers and developers don't have the luxury to spend weeks and months on their user research. It's possible to get useful results without the time-consuming expense of traditional user research methods. In this presentation, Christine Perfetti will share proven strategies and techniques for successfully integrating UX research into your process. You'll learn how to answer essential design questions using methods that take only a day—and sometimes only 10 minutes!

Five UX Myths to Avoid

Bonny Colville-Hyde

Soft Launch Planning and Management | Dylan Tredrea

Jessica Tams

1. Soft launches are different from regular live operations and require specific strategies to maximize learning. 2. It is important to take risks and make big changes during soft launches to learn as much as possible, as learnings accumulate over multiple tests and most soft launches fail. 3. Proper soft launch planning includes preparing server-side controls, operations plans, and qualitative feedback channels to support high-risk, high-reward experiments that could potentially "break" the game.

Fast then Faster - a Retrospective on Retrospectives

Atlassian

So, you’re agile. You’ve got a healthy backlog, you understand your team’s velocity, and you’re holding retrospectives. You’re in a good place – right? Maybe not. You may have a handle on the quality of your stories & their output, but what about that of your team and those around you? Or your agile processes themselves? Retrospectives are a great way to get feedback, but they are often both undervalued and underutilized as a tool for improvement. Agile gets you fast, but retrospectives get you faster. We’ll walk you through what good and bad retrospectives look like, how to tell when they’re failing, and (more importantly) how to uncover what's lurking behind bias, ego, and protocol. If you’re in doubt if this session is for you, suggest a team under pressure skips the retrospective this week, and see just how quickly they drop the most important part of the agile cycle! Products covered: JIRA Software, Confluence, Bitbucket, Bamboo, Fisheye / Crucible

DevOps - Successful Patterns

Creationline,inc.

Alex Vinyar is an enterprise architect with 18 years of automation experience who provides on-site consulting engagements to help companies assess their infrastructure and workflows, implement DevOps practices, and train teams. He has worked with many large companies to help them start their DevOps journeys. Some key lessons he has learned include getting executive sponsorship to provide resources and protection for changes, starting with a small initial project, controlling the impact of changes, appointing internal champions, using metrics to prove value, taking care of employees, understanding that culture change takes time, and regularly demoing successes and failures to build community.

Agile - A failure story

Miki Lior

- The company "SellALot" was struggling with low quality deliveries, missed deadlines, and siloed development teams in 2010 when using an undisciplined "monster methodology". - In 2012, unhappy clients, repeating bugs, and an unsatisfied CEO prompted the company to consider changing their development process to improve collaboration, reduce gaps between development and testing, and create more realistic plans and estimates. - They adopted Agile/Scrum practices like JIRA for collaboration and ALM processes with 2-week iterations to avoid long development cycles. This helped improve coordination between teams. - By 2014, a frustrated team and slow feature delivery led the company to fully adopt Agile practices like short user

The 5 Biggest Productivity Blockers (And How to Fix Them)

Atlassian

The document provides frameworks for addressing 5 common productivity blockers: prioritization, time management, communication, ability to focus, and burnout. For prioritization, it recommends the Eisenhower matrix and Rule of 5 techniques. For time management, it contrasts approaches for "makers" and "managers" and recommends the Pomodoro technique. For communication, it advocates the 30/60/90 feedback framework. For focus, it suggests limiting notifications and changing locations. And for burnout, it stresses limiting decisions and learning to say no.

Event tech 101 -- Online Webinars with Adobe Connect

Adam Schrecengost

http://www.fsnnetwork.org/event-management-and-technology-considerations After reviewing this presentation, the audience will be familiar with: --The best circumstances under which to host an online event --Key steps in planning such an event successfully --Required personnel and roles --Top audio-visual tips for successfully hosting the event In collaboration with the TOPS Knowledge Management Team, Adam Schrecengost from KDAD takes participants through a high level overview of some technology considerations to think about when planning a hybrid (in person and virtual combined) or online event.

Startup Operating Systems

Dean Haritos

The document discusses operations systems for startups. It emphasizes building well-defined systems before hiring teams to ensure work is done predictably and efficiently. Key principles outlined include treating all internal customers well, managing by exception to focus on problems, solving each problem only once, and using "trim tabs" or minimal adjustments to influence outcomes. The document also provides templates and examples for defining department processes and product roadmaps.

Software demo Skills for Business Analysts

Heather L. Cole (J.D)

Are you deploying technology and need to show executives what you have built? Then you must learn demonstration skills! Increase end user adoption and executive engagement by wowing your audience with your presentation skills. If you have IBM Cognos, Host Analytics, SAP, Oracle, or any software, it's time to let it shine in your presentations. I share my 25+ years of experience demonstrating software, so you look like a rock star.

Startup Engineering Flashpoint Batch 3 Better Startups Faster

merrickfurst

This document provides an overview of the Startup Engineering curriculum offered through Georgia Tech's Flashpoint program. It summarizes the program's goals of reducing startup risks through experiments and testing hypotheses to validate business models and product assumptions. Key aspects covered include identifying and prioritizing different risk categories, conducting inner loop experiments to disprove theories, and focusing on metrics that affect funding and pitching abilities rather than technical processes. The timeline outlines the weekly workshops, events, and expectations for mentor participation throughout the 3-month batch program.

The Usability of Usability

Andrew Chak

Sometimes, they just don’t get it. We’re just trying to do the right thing here. Isn’t our success dependent on our users being able to shop, buy, apply or contact us through our web site or app? So if we’re dependent on our users, shouldn’t we at least involve them somehow in the design process? Not so easy. For some of “those” people, design is easy. Don’t we already know what the problem is and what design we can use to fix it? Can’t we just leverage best practices? Why do we even need to test the design if we’re experts? No one ever says these things, right? In the real world, user-centered design and usability is ironically, not that easy to adapt. It’s counterintuitive because it’s such hard work to make things easy. What we have to do is to make what we do easy to understand and easy to choose. This session may not change your reality, but by sharing in some lessons learned, hopefully you’ll have the tools to help change some minds.

Top 15 reasons to choose qa testing as career

JanBask Training

Supercharging your bug reports

Neil Studd

Are you having trouble getting your bug reports fixed? It could be that you’ve yet to master the craft of bug reporting. It’s a common assumption that bug reports are easy to create, but a well-crafted bug report requires more than innate ability. In this practical workshop, Neil will share his experiences (good and bad!) from ten years of bug reporting, and show how you can supercharge your bug reports: First presented at the 2015 TestBash Workshop Day: http://www.ministryoftesting.com/training-events/testbash-workshop-day/

Hands on Usability Testing (Jonathan Rubin)

uxpa-dc

What's hot

DrupalCon Austin: UX Bootcamp workshop

Perfetti Media

Cheap'n'easy usability

Paul Canning

Trust Me, I'm An Architect

Keir Bowden

amccormick_conference_talk

Andy McCormick

Intro to Lean UX with UserTesting

Carlos González de Villaumbrosia

Usability Testing Basics: Remote and In-Person Studies

UXPA International

Usability testing tips for UX Designers

David Hamill

Rethinking UX Research - Design4Drupal 2014 keynote presentation

Perfetti Media

Five UX Myths to Avoid

Bonny Colville-Hyde

Soft Launch Planning and Management | Dylan Tredrea

Jessica Tams

Fast then Faster - a Retrospective on Retrospectives

Atlassian

DevOps - Successful Patterns

Creationline,inc.

Agile - A failure story

Miki Lior

The 5 Biggest Productivity Blockers (And How to Fix Them)

Atlassian

Event tech 101 -- Online Webinars with Adobe Connect

Adam Schrecengost

Startup Operating Systems

Dean Haritos

Software demo Skills for Business Analysts

Heather L. Cole (J.D)

Startup Engineering Flashpoint Batch 3 Better Startups Faster

merrickfurst

The Usability of Usability

Andrew Chak

Top 15 reasons to choose qa testing as career

JanBask Training

What's hot (20)

DrupalCon Austin: UX Bootcamp workshop

Cheap'n'easy usability

Trust Me, I'm An Architect

amccormick_conference_talk

Intro to Lean UX with UserTesting

Usability Testing Basics: Remote and In-Person Studies

Usability testing tips for UX Designers

Rethinking UX Research - Design4Drupal 2014 keynote presentation

Five UX Myths to Avoid

Soft Launch Planning and Management | Dylan Tredrea

Fast then Faster - a Retrospective on Retrospectives

DevOps - Successful Patterns

Agile - A failure story

The 5 Biggest Productivity Blockers (And How to Fix Them)

Event tech 101 -- Online Webinars with Adobe Connect

Startup Operating Systems

Software demo Skills for Business Analysts

Startup Engineering Flashpoint Batch 3 Better Startups Faster

The Usability of Usability

Top 15 reasons to choose qa testing as career

Similar to Continuous Quality - Moving Beyond Bug Reports

Supercharging your bug reports

Neil Studd

Hands on Usability Testing (Jonathan Rubin)

uxpa-dc

Cas2010 to-track-defects-or-not-to-track-defects-that-is-the-question

Agile Spain

This document discusses different perspectives on tracking defects in Agile development and proposes an alternative approach. It argues that defects should be treated like user stories with estimates and tests rather than using separate tracking tools. Within a sprint, any issues found should be visible on the task board as tests to be fixed. This maintains visibility while avoiding separate backlogs. The document shares a case study where this approach worked well but faced challenges with remote visibility and lack of automation. It concludes defects are best addressed by tracking tests, not bugs, and prioritizing visibility and automation.

DaKiRY_BAQ2016_QADay_Дмитро Стеценко "One Man Band"

Dakiry

This document provides advice for software testers working alone on projects. It discusses what software testing involves, who the key stakeholders are, and expectations managers and developers have of testers. It emphasizes the importance of communication and understanding the domain. The document provides tips for testers on planning testing activities, keeping stakeholders informed, educating managers, and proposing process improvements. Testers are advised to study the product, communicate regularly in a way stakeholders prefer, and work collaboratively to resolve issues and improve processes over time.

Agile for Me- CodeStock 2009

Adrian Carr

This document provides an overview of Agile software development. It begins by defining Agile as a project management process that encourages frequent inspection and adaptation. It then discusses some common Agile practices like Scrum and eXtreme Programming. The Agile Manifesto values individuals and interactions, working software, customer collaboration, and responding to change. Finally, it provides advice for different roles on how Agile can benefit them and their work.

From defect reporting to defect prevention

BestBrains

The document discusses moving from a defect reporting approach in software testing to a defect prevention approach using lean principles. It notes that preventing defects from the beginning is more effective than finding faults later. The document encourages exploring testing earlier in the process, understanding the root causes of defects, and prioritizing removing those causes over manual regression testing. The overall message is that building quality into the software from the start leads to higher profitability than relying on later fault detection and fixing.

10 signs your testing is not enough

SQALab

The document discusses 10 signs that an organization's software testing may not be enough. These include having excessive production bugs, bugs found during user acceptance testing, growing bug counts over test cycles, not investing in testing compared to competitors, lacking clear criteria for what constitutes "enough" testing, testers advising against releasing software, weak prevention efforts like code reviews, lack of developer unit testing, frequently reduced testing periods causing deadline problems, and high tester turnover. The document advocates treating testing as risk management, increasing test reuse and automation, and addresses common challenges and questions around software testing.

DevOps for the sysadmin

Robert Nelson

Surviving as a Software Tester, Even in Difficult Circumstances

rrice2000

Ten proven ways to demotivate your team are outlined, including setting unreasonable goals, taking credit, and never giving praise. The document provides strategies for software testers to survive in difficult work circumstances, such as dealing with clueless managers, lack of resources, and ignored test findings. It emphasizes the importance of self-care, being proactive in one's career, and knowing when to leave a dysfunctional work environment.

Surviving as a Tester, Even in Difficult Circumstances with Randy Rice

TEST Huddle

Most test professionals have worked at some time or other in difficult organizations, dysfunctional cultures, and for unreasonable managers and stakeholders. This causes much internal stress and creates fear instead of creativity. While some fortunate testers work in fantastic and supportive organizations, Rice’s research with many testers indicate most of the problems in testing are “people problems.” In this webinar, Randy will describe the most common organizational issues that affect testers and will give some tips and strategies on how to survive through them. He will also discuss the difficult issue of knowing when to move on to a new organization, as well as how to map your own career growth.

New_ppt.pptx

vivekgupta751524

The document provides an overview of Dr. Glenn Stout's presentation on conducting user acceptance testing (UAT) for a new software system. He likens the UAT process to a chess game, where all involved parties can "win" if the right approach is taken. The presentation covers organizing people into roles to oversee different business processes or departments, defining communication processes and status meetings, and ensuring testers are properly trained. The goal is to have a structured yet simple testing methodology supported by the right tools.

Ericriesleanstartuppresentationforweb2

Edmund FOng

The document summarizes the key principles of the Lean Startup methodology for building startups. It discusses two tales of startups, one that failed spending $40M over 5 years by making assumptions without customer validation, and one called IMVU that shipped frequently and earned $10M in revenue in 2007. The Lean Startup methodology advocates continuous deployment, rapid A/B testing to validate hypotheses, and using the "Five Whys" technique to understand root causes of problems. Adopting these principles can help startups iterate quickly and reduce the risk of expensive failures.

Lean Startup 301

Lean Startup Co.

Aubrey Smith, Sparked Advisory In this training, we will build on the foundation established in Lean Startup 101 and 201 by delving into examples and cases of the Lean Startup concepts in action. Attendees of Lean Startup 301 will be exposed to cutting edge work from thought leaders and experts using Lean Startup in practice today — at startups and within the enterprise. Participation in this session is essential: You will be asked to help design an MVP and experiment to test critical Leap of Faith Assumption(s) in groups and will be encourage to share experiences. The session is designed to allow attendees to stretch their skills and to push one-another to ‘learn by doing’. The session will also include: Sample cases and live interviews with practitioners highlighting the application of core concepts; Exercises designed to bring the concepts to life and challenge participants to deepen their skills; Discussion of advanced topics such organizational culture and governance as well as industry-specific concepts such as using Lean Startup in heavily regulated markets. Thanks to Lean Startup Co.’s law firm, Orrick, for being the sponsor for this track.

Harnessing Your Product Manager Superpowers with Trello, Confluence, and Jira

Atlassian

Whether you're a product manager, product owner, or a cat herder, creating a stellar product takes skill. The list is endless—from aligning stakeholders to creating a clear vision and specifications, planning sprints, measuring success and everything in-between. In this session, we'll share how to extend the power and flexibility of Atlassian tools for your team. From inception, to planning, to building, learn the battle-tested tips from our own Atlassian teams to ensure that you not only build the product right, but also build the right product.

Things Could Get Worse: Ideas About Regression Testing

TechWell

Michael Bolton, DevelopSense Tester, consultant, and trainer Michael Bolton is the coauthor (with James Bach) of Rapid Software Testing, a course that presents a methodology and mindset for testing software expertly in uncertain conditions and under extreme time pressure. Michael is a leader in the context-driven software testing movement with twenty years of experience testing, developing, managing, and writing about software. Currently, he leads DevelopSense, a Toronto-based consultancy.

Lean thinking and the agile culture

Alejandro Claro Mosqueda

This document discusses lean thinking and agile principles for improving productivity. It promotes embracing change and continuous improvement over rigid plans. Key aspects covered include lean concepts like just-in-time production, eliminating waste, continuous flow, and respect for people. Agile principles emphasized include valuing individuals, interactions, and responding to change over rigid processes. Methodologies like Scrum, Kanban, and lean software development are presented as ways to apply these principles through iterative development, visualization, inspection, and adaptation.

Fixing the Problems in Your Operations Problem-Solving Methods

SafetyChain Software

This document discusses problem solving methods for process manufacturers. It introduces a webinar on problem solving featuring two speakers: David Hicks, Vice President and Maintenance Excellence Practice Leader, and Tim Nickerson, Client Manager and Management System SME. The webinar will cover ensuring quality and compliance, maximizing throughput and yield, and optimizing labor and productivity using problem solving tools and the DMAIC methodology.

Mal12 qa tand-automatedtesting

andytinkham

This document discusses how testers can provide information to teams through risk-based testing and exploratory testing sessions of modern applications. It recommends identifying risks, prioritizing test cases based on risk, and conducting session-based exploratory testing to investigate risks. Automated testing tasks should leverage the computer's strengths rather than just automating human tests. Non-functional testing like performance and security should also be considered from the start. Developers can help testers by sharing testing infrastructure, reviewing automation code, and pairing on testing activities.

STARWEST 2013 - What Executive Value in Testing

Michael Kelly

Professional testers and test managers are feeling the pressures of low-cost competition and tools that claim to replace them through automation. So, how can test teams add more value to their projects and organization? In a recent survey of executives and testers, Mike Kelly and Jeanette Thebeau found major disconnects between what executives and testers believe are most important to the business. They explore new insights into the risks and concerns executives perceive and what you should do differently. In the survey, most testers believed that finding ways to cut operational costs was a low priority test objective, but executives listed operational cost reduction as a high value testing activity. On the flip side, testers believed that regulatory compliance was a high priority, while most executives reported compliance testing was a low priority. Join Mike and Jeanette to find new ways to help ensure the products you test solve the business problem, meet customer needs, reduce operational costs, scale easily as demand increases, and are built to quickly add new features over time.

Sage Summit 2012: Nerd, Geek and Gear Herding

Grant M Howe

This document provides an overview of a presentation on best practices for technical managers. It includes tips for managing technology selection such as preparing for meetings with solutions specialists, discussing requirements and desired outcomes, and comparing options. It also offers advice for handling emergencies like assembling the right response team and focusing on resolution over blame. Additionally, it suggests ways to motivate and reward technical staff like using public scoreboards and celebrating wins. The presentation concludes with a crowd-sourced Q&A where attendees can discuss real issues.

Similar to Continuous Quality - Moving Beyond Bug Reports (20)

Supercharging your bug reports

Hands on Usability Testing (Jonathan Rubin)

Cas2010 to-track-defects-or-not-to-track-defects-that-is-the-question

DaKiRY_BAQ2016_QADay_Дмитро Стеценко "One Man Band"

Agile for Me- CodeStock 2009

From defect reporting to defect prevention

10 signs your testing is not enough

DevOps for the sysadmin

Surviving as a Software Tester, Even in Difficult Circumstances

Surviving as a Tester, Even in Difficult Circumstances with Randy Rice

New_ppt.pptx

Ericriesleanstartuppresentationforweb2

Lean Startup 301

Harnessing Your Product Manager Superpowers with Trello, Confluence, and Jira

Things Could Get Worse: Ideas About Regression Testing

Lean thinking and the agile culture

Fixing the Problems in Your Operations Problem-Solving Methods

Mal12 qa tand-automatedtesting

STARWEST 2013 - What Executive Value in Testing

Sage Summit 2012: Nerd, Geek and Gear Herding

Recently uploaded

Presentation of the OECD Artificial Intelligence Review of Germany

innovationoecd

A Comprehensive Guide to DeFi Development Services in 2024

Intelisync

DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum. In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance. In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape. At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology. Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!

Nordic Marketo Engage User Group_June 13_ 2024.pptx

MichaelKnudsen27

Programming Foundation Models with DSPy - Meetup Slides

Zilliz

Digital Marketing Trends in 2024 | Guide for Staying Ahead

Wask

https://www.wask.co/ebooks/digital-marketing-trends-in-2024 Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.

Astute Business Solutions | Oracle Cloud Partner |

AstuteBusiness

Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe

Precisely

Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market. Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.

Taking AI to the Next Level in Manufacturing.pdf

ssuserfac0301

Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as: 1. How quickly AI is being implemented in manufacturing. 2. Which barriers stand in the way of AI adoption. 3. How data quality and governance form the backbone of AI. 4. Organizational processes and structures that may inhibit effective AI adoption. 6. Ideas and approaches to help build your organization's AI strategy.

Public CyberSecurity Awareness Presentation 2024.pptx

marufrahmanstratejm

Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...

saastr

Monitoring and Managing Anomaly Detection on OpenShift.pdf

Tosin Akinosho

Monitoring and Managing Anomaly Detection on OpenShift Overview Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices. Key Topics Covered 1. Introduction to Anomaly Detection - Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems. 2. Understanding Edge (IoT) - Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source. 3. What is ArgoCD? - Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices. 4. Deployment Using ArgoCD for Edge Devices - Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD. 5. Introduction to Apache Kafka and S3 - Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions. 6. Viewing Kafka Messages in the Data Lake - Learn how to view and analyze Kafka messages stored in a data lake for better insights. 7. What is Prometheus? - Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices. 8. Monitoring Application Metrics with Prometheus - Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system. 9. What is Camel K? - Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes. 10. Configuring Camel K Integrations for Data Pipelines - Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow. 11. What is a Jupyter Notebook? - Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text. 12. Jupyter Notebooks with Code Examples - Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.

AWS Cloud Cost Optimization Presentation.pptx

HarisZaheer8

This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.

zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...

Alex Pruden

Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security. Paper Link: https://eprint.iacr.org/2024/257

Introduction of Cybersecurity with OSS at Code Europe 2024

Hiroshi SHIBATA

I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems. The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS. Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application. I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.

Dandelion Hashtable: beyond billion requests per second on a commodity server

Antonios Katsarakis

This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).

leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...

alexjohnson7307

JavaLand 2024: Application Development Green Masterplan

Miro Wengner

“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...

Edge AI and Vision Alliance

For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/ Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit. The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers. Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.

Skybuffer SAM4U tool for SAP license adoption

Tatiana Kojar

Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool. SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.

System Design Case Study: Building a Scalable E-Commerce Platform - Hiike

Hiike

Recently uploaded (20)

Presentation of the OECD Artificial Intelligence Review of Germany

A Comprehensive Guide to DeFi Development Services in 2024

Nordic Marketo Engage User Group_June 13_ 2024.pptx

Programming Foundation Models with DSPy - Meetup Slides

Digital Marketing Trends in 2024 | Guide for Staying Ahead

Astute Business Solutions | Oracle Cloud Partner |

Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe

Taking AI to the Next Level in Manufacturing.pdf

Public CyberSecurity Awareness Presentation 2024.pptx

Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...

Monitoring and Managing Anomaly Detection on OpenShift.pdf

AWS Cloud Cost Optimization Presentation.pptx

zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...

Introduction of Cybersecurity with OSS at Code Europe 2024

Dandelion Hashtable: beyond billion requests per second on a commodity server

leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...

JavaLand 2024: Application Development Green Masterplan

“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...

Skybuffer SAM4U tool for SAP license adoption

System Design Case Study: Building a Scalable E-Commerce Platform - Hiike

Continuous Quality - Moving Beyond Bug Reports

1. CONTINUOUS QUALITY Moving beyond bug reports TODO: REPLACE TERRIBLE BORING TITLE SLIDE WITH SOMETHING INTERESTING

3. IN THE BEGINNING…

4. Enterprise Distributed across timezones Infrequent releases Server/desktop architecture Bug Review Committees Requirement documents

7. “Neil is some kind of Navy SEAL tester who’s decided to take this class”

10. Agile / kanban Frequent releases Short projects Challenging deadlines Regulatory pressures Marketing campaigns

11.

12.

13.

14. CONTINUOUS QUALITY

15. bug?

16. BUGS… • Difference between perceived and desired • Something that bugs somebody who matters • A threat to value • (Problems, defects, issues) • A snapshot of information • A placeholder for conversation • Communicate within team • Surface info to stakeholders • To guide decisions BUG REPORTS… If a bug isn’t written in a bug report… it’s still a bug!

17.

18. ZERO BUGS

19. ZERO-TOLERANCE BUG POLICY • YAGNI – If not now, then not later either! • Deal with mess as it arises • Avoids “bug tennis” • Weekly code-freeze for release: tackle what little remains • BUT: Hard if external parties (clients, support) want involvement

20.

21. FIX IT YOURSELF

22. THE TOOLS TO FIX IT YOURSELF • Domain knowledge • Understanding of codebase/standards • Know your personal limitations • Know what your team is comfortable with • Show the fix to the developer (keep the feedback cycle) ++positivity; ++respect; ++gratitude; --blame_game; ++credibility;

23.

24.

25. “…But that’s not testing!”

26.

27. GET INVOLVED EARLIER

28. GET INVOLVED EARLIER • Get the team thinking about testing (and testability) early • Reduce feedback/cycle time • Dev and test, complementing each other, working in harmony

29.

30. As close to the code as you can get Mob Programming (Woody Zuill) Shared expertise Better understanding of what’s been tested

31. PRACTICAL AUTOMATION

32. PRACTICAL AUTOMATION • Doesn’t have to be a fully autonomous solution! • Small scripts/tool/helpers • Automate the pain points of daily life • Lower cost (only needs to be as good as the job it’s serving) • Recognise opportunities to practice • Seek forgiveness, not permission

33.

34.

35.

36.

37. LOGGING AND MONITORING

38. LOGGING AND MONITORING • “Free testing”! • Not just useful for support/ops • Rich supply of information • Make it queryable • Some teams do all of their testing this way • Reliance depends on risk appetite

39. "environment":"prod" claimAmount is missing

40.

41. METRICS AND NUMBERS

42. METRICS • Bug counts are a lousy metric • Get qualitative information • Interview team members • What’s going well, what’s going badly • Ask your testers what challenges they face • “But that takes time and effort…” - Good! • “But that’s difficult to scale…” – Don’t over-manage! • Hire great people. Trust them. Support them.

43. IF I COULD GO BACK…

44. A MANIFESTO FOR CONTINUOUS QUALITY • Encourage easier communication • Highlight problems • Reveal value (and threats to value) • Get involved earlier • Arm yourself with tools/knowledge to work alongside developers • Make bold and courageous choices • Deliver quality software quicker (a work-in-progress!)

45. THANKS FOR LISTENING! @neilstudd @ScreenTesting

Editor's Notes

Announced yet or not? Feedback please! (Both good and bad)
In the beginning
Early part of career
Scheming: Keeping test ideas to myself, to “catch out” developers. Perpetuating the divide
Oracles/heuristics Talking about testing Generating test ideas = testing is a skill which can be learned, developed
the James Bach RST Online comment, persuading me to focus on my advocacy skills
persuaded me to focus on my advocacy skills, the workshop/dojo (still the best theory material i've built). When getting workshop material reviewed, at least one reviewer mentioned a more lightweight approach - I did have one slide ("you may not need that bug") but acknowledged it wasn't where I was at right then.
When getting workshop material reviewed, at least one reviewer mentioned a more lightweight approach - I did have one slide ("you may not need that bug") but acknowledged it wasn't where I was at right then.
Since then - Amido, CTM, ZPG. Three strong agile/kanban shops. Some of the challenges, eg hard deadlines (marketing campaigns & regulatory requirements; one week sprints) mean that traditional, verbose bug reports are outdated (list why).
Something that I'm good at being taken away! Mental challenge to adjust. [Oracle] Holding onto things you’re good at, or avoiding things you don’t know, holding back the team
More pragmatic approach to quality Continuous testing? Continuous breathing?
Cloud / mind map? WHAT IS A BUG REPORT? A snapshot of information, to communicate with team/stakeholders, to guide decisions. A lot of that is possible without writing stuff down. A pragmatic approach to quality
Example from Supercharging, the dense bug (with fix suggestion) that nobody read.
TITLE SLIDE: YAGNI / ZERO BUGS
YAGNI - if it's not important enough to fix now, will it really be later? Current team has < 30 bugs in JIRA (rest is stories/tasks) because we don't tend to carry forward, and if we finish sprints early (or Thu PM code freeze) then devs are pushed towards the bug backlog. (Different if there are clients involved, especially if they have final say over defect prioritisation - CBRE)
https://devblog.songkick.com/experimenting-with-a-zero-bug-policy-3281490dbc8b
No time to file a bug report! In a tough situation – “good enough” is enough
Chris Kenst http://www.kenst.com/2017/04/testers-dont-be-afraid-to-make-production-changes/
SUBMITTING MY OWN PULL REQUESTS - finding a small bug in a story I'm testing - if I can identify root cause, AND fix it in code, AND test my fix as well as I would somebody else's, that reduces the admin time in bug reports.
The ultimate TDD – Tester Driven Development! When I left CTM – “I didn’t realise you were a tester” If I add a feature myself – that’s fine but (JB) then I am adopting a developer role.
Get involved earlier
PARTICIPATING IN CODE REVIEWS. I can read better than I can write! It doesn't hurt to be able to pick up some of the lingo. Example where we changed a SQL query and I identified that the new query would break existing functionality, without having to run it to prove it. Now I'm a formal part of the CR process! AND – it shouldn’t be my job to spot it, why wasn’t there a unit test to catch this plus - as someone who's not working with the code as much as developers, if I can't grasp what the code's doing, a newcomer to the team might struggle too.
Date/time knowledge (“this is simple” – “Hold my beer”) Plenty of room for a tester in this scenario
scripted tools don't have to be a fully autonomous solution, but they can automate the pain points of our day-to-day jobs, making it easier to deliver valuable information which humans can use to make decisions.
http://techjobs.comparethemarket.com/blog/automation-testing-pragmatic-approach Can’t fully automate (differences are not necessarily problems) Automate the time-consuming part (comparing two documents, highlighting differences) Leaves the human free to focus on the part which needs greater thought (unstructured analysis)
Learned about: Slack bots and how they communicate Creating and managing a Heroku instance The value of writing your own logging
https://xkcd.com/1205/ Gives good ballpark figures 5 years might be a bit long for a typical company’s ROI Doesn’t include the time to support the solution
Logging/monitoring = free testing
Another team broke our contract We spotted it before they did Helped them write the tests to stop it happening again
Sending requests for price comparisons to dozens of insurers Log when we get an error back, automated alert if error rate is high We tell them about problems in their own systems before they’ve spotted them – building credibility
Metrics/numbers?
Thinking back to the bug nobody read - what would I do differently now? Discuss with developers (how easy/viable is the suggested fix). Discuss with stakeholders (do they care). At that point, either fix it or write a one-liner (ok two lines, remind reader why it matters).
With 1wk sprints, as long as nothing has a major knock-on for users, it can be fixed quickly with little impact ..caveats? Conclusion Bring back round to continuous quality
Thanks – Q&A (now, after, pub) Twitter

Continuous Quality - Moving Beyond Bug Reports

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Continuous Quality - Moving Beyond Bug Reports

Similar to Continuous Quality - Moving Beyond Bug Reports (20)

Recently uploaded

Recently uploaded (20)

Continuous Quality - Moving Beyond Bug Reports

Editor's Notes