Agile India: Working without Product Owner

The document provides guidance on building an early prototype of a core loop for a product. It emphasizes choosing the right team and tools to build and iterate the prototype quickly. It also highlights potential speed bumps to avoid, such as using the wrong team, becoming too perfectionist about design, over-engineering the prototype, or making the core activity unappealing. The document stresses testing prototypes to form habits from the ground up.

A/B Testing - In data we trust

Pedro Marques

This document discusses A/B testing and provides advice for conducting A/B tests. It notes that A/B testing was originally used in pharmaceutical testing but is now commonly used by websites to test different versions of pages or features. The document emphasizes defining key performance indicators, testing hypotheses with proper sample sizes and durations, and not assuming causation from correlations in results. It cautions that A/B testing requires data analysis and should not kill creativity.

4 Steps Toward Scientific A/B Testing

Janessa Lantz

MVP Design Hacks: Sprint 7

This document provides guidance on iterating a design based on customer insights from early adopters. It recommends turning job stories derived from early adopters into an updated design. It also provides resources on background reading, viewing, iteration shortcuts using tools like Keynote and Balsamic, and templates to update the minimum viable product canvas and core solution loop. Potential iteration speedbumps are identified such as false pivots or discomfort with the customer discovery process.

Agille Testing Meetup 1

Nathan Bain

This document summarizes the agenda and discussion at an Agile Testing meetup group. It introduces the purpose of the group as a place for testers to share experiences and learn new skills in Agile Testing. Key topics discussed include the benefits of testing earlier in the development cycle using automated tools. A demonstration was given of a keyword driven web testing solution using WebDriver and FitNesse. Attendees then shared challenges with testing in Agile and ideas for future meetup activities.

The document describes an experiment conducted by a software development team where they worked without a dedicated Product Owner for 3 months. In the experiment, the team was directly responsible for interacting with customers and prioritizing work. After the experiment, the team found that they were able to deliver more while being more customer-focused without a Product Owner acting as a proxy between them and customers. The team also realized they did not need the Product Management Expert to be present at all planning meetings to understand customer priorities. After a year of working without a Product Owner, the team was recognized as the "Best Team in Corporate R&D".

Lean Responsive

Josh Jeffryes

MVP Design Hacks: Sprint 5

A/B Testing - In data we trust

Pedro Marques

4 Steps Toward Scientific A/B Testing

Janessa Lantz

MVP Design Hacks: Sprint 7

Agille Testing Meetup 1

Nathan Bain

Machine Learning 101 for Product Managers by Amazon Sr PM

Webinar: How to be More Effective Data-Driven PM by fmr Groupon Sr PM

e-Portfolio Presentation

Evan Letzter

The document describes how the author introduced themselves to HTML, CSS, and JavaScript in order to create a keyword scoring tool for an SEO agency. They used tutorials from W3Schools and answers from Stack Overflow forums and Google searches to learn the necessary skills over 10+ hours. They created the first version of the tool and presented it to executives at the agency, who approved of the final product. The author gained experience with three new technical skills and learned how best to learn new concepts through this process.

Qual vs. Quant: Using data to Build Better Products

uxpin

Conceptual Machine Design | BP Automation

Steven Tyler

Ideas & execution

Fahad Ahmad

Turning ideas into real products requires tenacity, patience and discipline to execute on the idea. The entrepreneur builds a system around the idea that allows it to mature into a real product. Ideas are common, but execution is what matters most. There are three key qualities of effective execution: processes must be repeatable, efficient, and reliable. Without reliable, repeatable and efficient processes, scaling the business is impossible.

Operations-Driven Web Services at Rent the Runway

Camille Fournier

Agile Nightmares

unbrand

This document lists common problems and nightmares that can occur on Agile projects. Some of the issues discussed include clients not wanting to use Agile, having too short of a timeline, clients demanding specifications, disagreements over feature scope, dependencies between stories causing delays, and clients repeatedly requesting changes late in the project. The document provides advice on how to potentially address each issue, such as getting buy-in from clients on using Agile early, setting clear expectations on the project parameters and what can be changed, and prioritizing more risky work earlier on.

What does it mean to be a test engineer?

Andrii Dzynia

Test engineering is hard, even harder than software development. Being test engineer puts you in a wider context, with no clear boundaries. You have to find those by yourself. This requires courage. Courage to take action, courage to make mistakes. As a test engineer, you do mistakes every day. You do them so often that sometimes you feel you can predict the future. Scientific explanation to this phenomena is patterns recognition. It is an ability of our brain to match the information from a stimulus with information retrieved from memory. Defect prevention is hard. Together with technical skills one have to develop high social awareness. Working on safety nets never was so important, different types of checks on different levels to make sure software is reliable and serves its purpose to the variety of everyday use-cases. We know that life is so complex and sometimes complicated which makes it impossible to predict all possible outcomes and scenarios. But striving for excellence never was so important as nowadays in such an open, transparent and competitive environment. Goal of my talk will be to show you my everyday job as a test engineer. Not only how to look for defects, but how to prevent them from happening. Not only how to automate tests(noun), but how to build safety nets to minimize end-user impact. Not only how to inform testing status but how to influence quality on company level.

what's blocking our way

tanvir afzal

DrupalCon 2013 Making Support Fun & Profitable

Promet Source

Doing the Impossible: Implementing New TestComplete Framework for Windows App...

SmartBear

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

Learn Unit Testing and Improve Sexual Performance

Bill Shelton

How to write Great Requirements

Greg Thomas

Developer Night - Opticon18

Optimizely

Software Project Estimation Survival Guide

michaelcummings

CMs presentation March 2010

eBusiness Champions

The document discusses content management systems (CMS) and bespoke website solutions. It provides information on what a CMS is and when they are needed. It then discusses bespoke CMS solutions, how they work, example websites, and factors to consider like costs and choosing a supplier. The document also summarizes open source CMS options, what open source means, common pros and cons, and how to choose the right open source solution.

DDD Europe: Breaking Illusions with Testing (keynote)

The document discusses how testers break illusions about code by finding issues and areas for improvement. It provides examples of illusions such as code doing what it's intended, the product meeting requirements, and the development process supporting changes. The document advocates for an exploratory testing approach using heuristics to poke at the system until problems are uncovered. It also emphasizes the importance of a learning mindset when testing and discovering new ways the system could be improved.

ATAGTR Keynote: I have a rock in my shoe - Navigating Improvement

The document discusses navigating improvement at work and changing more than we think is possible. It provides tips for naming discomfort, sharing work, dealing with rejection of ideas, and turning failures into learning opportunities. Specific problems mentioned include long release testing times, testing queues, and meeting expectations. Corresponding solutions proposed include more frequent releases, exploratory testing, test automation, discussing testing earlier, and explaining/stretching rules and expectations.

Stilnest.com: Wie beste Magento-Shop-Performance für zufriedene Kunden sorgt

Dynatrace

SEETest: Making Teams Awesome

This document contains snippets from Maaret Pyhäjärvi's website about testing and quality assurance. It discusses topics like making customers and teams awesome, the importance of learning, taking risks, and viewing one's role as a catalyst for change, conscience for quality, cheerleader for others, and critical thinker. It emphasizes focusing on generativity over just productivity and caring about work over personal credit. The document promotes concepts like thinking systemically, having a growth mindset, and assuming positive intent from others.

What's hot

Machine Learning 101 for Product Managers by Amazon Sr PM

Webinar: How to be More Effective Data-Driven PM by fmr Groupon Sr PM

e-Portfolio Presentation

Evan Letzter

Qual vs. Quant: Using data to Build Better Products

uxpin

Conceptual Machine Design | BP Automation

Steven Tyler

Ideas & execution

Fahad Ahmad

Operations-Driven Web Services at Rent the Runway

Camille Fournier

Agile Nightmares

unbrand

What does it mean to be a test engineer?

Andrii Dzynia

what's blocking our way

tanvir afzal

DrupalCon 2013 Making Support Fun & Profitable

Promet Source

Doing the Impossible: Implementing New TestComplete Framework for Windows App...

SmartBear

Agile - A failure story

Miki Lior

Learn Unit Testing and Improve Sexual Performance

Bill Shelton

How to write Great Requirements

Greg Thomas

Developer Night - Opticon18

Optimizely

Software Project Estimation Survival Guide

michaelcummings

CMs presentation March 2010

eBusiness Champions

What's hot (18)

Machine Learning 101 for Product Managers by Amazon Sr PM

Webinar: How to be More Effective Data-Driven PM by fmr Groupon Sr PM

e-Portfolio Presentation

Qual vs. Quant: Using data to Build Better Products

Conceptual Machine Design | BP Automation

Ideas & execution

Operations-Driven Web Services at Rent the Runway

Agile Nightmares

What does it mean to be a test engineer?

what's blocking our way

DrupalCon 2013 Making Support Fun & Profitable

Doing the Impossible: Implementing New TestComplete Framework for Windows App...

Agile - A failure story

Learn Unit Testing and Improve Sexual Performance

How to write Great Requirements

Developer Night - Opticon18

Software Project Estimation Survival Guide

CMs presentation March 2010

Similar to Agile India: Working without Product Owner

DDD Europe: Breaking Illusions with Testing (keynote)

ATAGTR Keynote: I have a rock in my shoe - Navigating Improvement

Stilnest.com: Wie beste Magento-Shop-Performance für zufriedene Kunden sorgt

Dynatrace

SEETest: Making Teams Awesome

Agile Software Community of India

Practices Change - Moving to Delivering Continuously by Maaret Pyhajarvi at #...

Delivering continuously - easier said than done. As I joined my team delivering Windows Desktop products two years ago with the aspiration of implementing continuous delivery, I was told it cannot be done. It started from the fact that making a single release was five-day effort, and continued with “no user would allow us to deliver frequently”. Two years later, making a release takes us two hours and the way we work together looks very different. With the principle of fixing maintenance issues in the latest release has resulted in improved flow forward and savings of effort in supporting small number of releases. This talk goes through our lessons learned on the journey of shortening release cycles to a continuous daily flow. We’ve experienced three essentially different sets of practices, with the core difference coming from release frequency. The good place is when we deliver continuously. The soulsucking place is when we deliver on two week cadence. And the insane asylum is when we deliver just once at the end of the project. Think of it like this: a pool is not just a bigger bathtub. The things you can do in a pool are different to those you can do in a bathtub. While both are containers of water, they serve different purposes. It is the same with release frequency. While it is all still releases, the continuous ones enable different practices. More details: https://confengine.com/agile-india-2019/proposal/7961/practices-change-moving-to-delivering-continuously Conference link: https://2019.agileindia.org

Agile India: Practices Change - Moving to Delivering continuously

This document discusses moving from releasing software periodically to delivering continuously. It notes that while some software components are updated 20 times per day, the customer-facing parts are still released less frequently. Moving to more frequent releases requires changes to development, testing, product management, and other practices. Benefits include a reputation of flow without estimates, more focus on value over risk management, and enabling different practices.

Iterating on your idea

Shem Magnezi

- Analyze and implement feedback from your wireframes / mockup in order to create a working prototype/MVP for your product or service - Test the viability of individual features of your product or service - Create user flows and understand how customers will interact with your product or service - Determine the right software development methodology (traditional or waterfall vs agile) for your product or service

AADays Poland: Perfecting the Craft of Test Automation

The document discusses test automation and emphasizes the importance of clean code, collaboration between testers, developers and automators, and exploring diverse approaches beyond basic regression testing. Specifically, it notes that without clean code, test automation will not be effective. It also stresses creating understanding between testers, developers and automators, and that the landscape of test automation involves more than just usual techniques like regression testing.

Talentum: Testiautomaation tekemisen taito

The document discusses test automation and clean code. It notes that without clean code, all the test automation in the world will not save you. It advocates creating a mindshare between testers, test automators, and developers. It also discusses that the test automation landscape includes more than just the usual suspects like regression testing, and can include things like automation of the environment, disposable test automation, and model-based test automation.

Achieving Technical Excellence in Your Software Teams - from Devternity

Peter Gfader

Our industry has a problem: We are not lacking software methodologies, programming languages, tools or frameworks but we need great software engineers. Great software engineer teams build quality-in and deliver great software on a regular basis. The technical excellence of those engineers will help you escape the "Waterfall sandwich" and make your organization a little more agile, from the inception of an idea till they go live. I will talk about my experiences from the last 15 years, including small software delivery teams until big financial institutions. Why would a company like to be "agile"? How can a company achieve that? How can you achieve Technical Excellence in your software teams? What developer skills are more important than languages, methods or frameworks? This will be an interactive session with a Q&A at the end.

2010 08 19 The Lean Startup TechAviv

Eric Ries

The document discusses the Lean Startup methodology for building startups under conditions of extreme uncertainty. It advocates for building a minimum viable product and continuously validating hypotheses through customer experiments rather than fully planning products. Key techniques include rapid A/B testing, continuous deployment of code, and using metrics to guide product decisions rather than visions of predicted success. The goal is to maximize learning from customers with minimum resources to improve odds of achieving product-market fit.

HUSTEF '21 Keynote: Hands Off Exploratory Testing - Managing at Scale

This document discusses exploratory testing and managing testing at scale. It describes Maaret Pyhäjärvi's experience transitioning to exploratory testing and facilitating testing for multiple teams. Some key lessons learned include focusing on finding bugs and creating test automation, protecting testers' agency, limiting testing scope but extending it through networking, and using ideas like small continuous changes and automation to help guide testing at scale. The document emphasizes the importance of testing and encourages testers, programmers, and others to work together.

HOW TO INCREASE THE CHANCES OF DIGITAL STARTUP SUCCESS

leanstartuphh

Increase the chances of digital Startup success. In practice we will show how to Run startup and increase the chance of success. We will talk about pains of digital startups and ways to avoid critical problems. How to choose a team of developers and build interaction with them. Also how to manage and set up reporting of the development team. About presenter: Evgen Rybak ( https://www.linkedin.com/in/evgen-rybak-4569912/ ) is a Chief Technical Officer (CTO) in a Web-development company. He has a huge experience in Web-development and Product Management. Also Evgen has a very long experience working with digital startups.

Hellomeets - 15th November

Abhijeet Gaur

This document provides an overview of Abhijeet Gaur's career and experience in product management. It discusses his roles at companies like Google Pay, Amazon Pay, and Razorpay. It also outlines some key lessons and best practices for product managers, including using OKRs, data, communication, and learning on the job. Specific topics covered include writing good requirements documents, solving for uncertainty during product launches, and continuously learning as a product manager.

New AdWords Features You Shouldn't Ignore: 3 Experts Share Their Secrets

Hanapin Marketing

2010 04 28 The Lean Startup webinar for the Lean Enterprise Institute

Eric Ries

The document discusses myths and truths about Lean Startups. It dispels four common myths: that Lean means cheap, that it only applies to web/internet companies, that Lean Startups are small, and that they replace vision with data. It then provides an overview of Lean Startup principles like building a Minimum Viable Product, conducting rapid split tests, and achieving continuous deployment through small, frequent code releases.

Selling the Case for Accelerating Business Performance with Enterprise Colla...

Sameer Patel

So You Want to Rewrite That...

Camille Fournier

Building High-Growth Products with Jobs-to-be-Done

Jared Ranere, a Growth Partner at thrv, talked about how Jobs-to-be-Done answers questions like "what is a customer need?" "Who is your real competition?" and "What does it mean to be "satisfied?" in a way that aligns your development team around your customer. It also gives you precise, measurable customer needs, and helps you know if your feature idea will deliver customer satisfaction before your team writes a line of code.

Janna Bastow & James Mayes | Theme-based Roadmapping | ProductTank Toronto

Product Tank Toronto

We're excited to welcome Janna Bastow and James Mayes from Mind the Product to Toronto for this month's discussion. We'll be discussing how to move to a theme-based roadmap by 2017 and learning more about Mind the Product's global product community. Janna Bastow is co-founder of ProdPad, product management software that helps product managers build a product roadmap everyone understands and solve problems flexibly. She's also co-founder of Mind the Product, a global community of product managers, and the ProductTank series of meetups. She likes to inspire great product conversations by asking: “What problem are you trying to solve?” James lives at the intersection of Product, Startupsand Talent. As one of the Co-Founders of Mind The Product, he has specific remit now for partnerships throughout the product world in order to ensure the sustainability of the events. He’s always looking for new ways to add value to the community and while not always being a product person historically, loves the opportunity to experiment! James is a dad, gadget-geek, and frequent flyer. Thanks to Shopify for hosting us!

Similar to Agile India: Working without Product Owner (20)

DDD Europe: Breaking Illusions with Testing (keynote)

ATAGTR Keynote: I have a rock in my shoe - Navigating Improvement

Stilnest.com: Wie beste Magento-Shop-Performance für zufriedene Kunden sorgt

SEETest: Making Teams Awesome

Practices Change - Moving to Delivering Continuously by Maaret Pyhajarvi at #...

Agile India: Practices Change - Moving to Delivering continuously

Iterating on your idea

AADays Poland: Perfecting the Craft of Test Automation

Talentum: Testiautomaation tekemisen taito

Achieving Technical Excellence in Your Software Teams - from Devternity

2010 08 19 The Lean Startup TechAviv

HUSTEF '21 Keynote: Hands Off Exploratory Testing - Managing at Scale

HOW TO INCREASE THE CHANCES OF DIGITAL STARTUP SUCCESS

Hellomeets - 15th November

New AdWords Features You Shouldn't Ignore: 3 Experts Share Their Secrets

2010 04 28 The Lean Startup webinar for the Lean Enterprise Institute

Selling the Case for Accelerating Business Performance with Enterprise Colla...

So You Want to Rewrite That...

Building High-Growth Products with Jobs-to-be-Done

Janna Bastow & James Mayes | Theme-based Roadmapping | ProductTank Toronto

More from Maaret Pyhäjärvi

ATAGTR '20 Keynote: Building status

The document discusses Maaret Pyhäjärvi's career and testing philosophies. It highlights some of her "signature moves" including not having a product owner, holding space for quality and testing, pair and ensemble testing, and exploratory testing with automation as documentation. It also discusses different types of testers and how Maaret went from a junior tester to principal tester over her career while maintaining a 37.5 hour work week.

MoT Cork: Exploring Realities of Testing - From Theory to Practice

The document discusses Maaret Pyhäjärvi's work exploring realities of testing and moving testing practices from theory to real-world application. It notes she has spoken at around 40 conferences in 2021 on topics like tester expectations, behavioral-driven development, pair and ensemble programming/testing, exploratory testing, and testing in production. The document provides biographical information on Maaret Pyhäjärvi, including her role as the 2020 Most Influential Agile Testing Professional Person and links to connect with her.

Testing Voices '21 keynote: Testing Becoming Harder To BeValuable

The document discusses challenges that testers face as development practices have become more agile. Specifically, it notes that the cost of fixing defects is lower under agile but the cost of overengineering has increased. It also suggests that testers should get involved earlier, collaborate more with developers, and focus on learning and teaching skills rather than just finding bugs. Automation is important but must be integrated into continuous integration practices. The document advocates for techniques like holding space, telling stories of early value, and focusing communications on business needs rather than just the team.

TestJSConf: Go Find What We May Have Missed

The document discusses testing and how to build better teams. It advocates for an approach called ensemble testing that incorporates unit, service, UI, and other types of tests. It emphasizes the importance of feedback, understanding, and finding what others may have missed. Examples are provided of integrating different components and dealing with user expectations. The document also provides biographical information about Maaret Pyhäjärvi and how to connect with her.

SauceCon: It's More Complicated than THAT

1. The document discusses exploratory testing and provides examples of problems discovered through exploratory testing sessions, such as issues with logging in and out, session length, concurrency, and compatibility with different browsers and environments. 2. It promotes an approach of exploratory testing to "find what others may have missed" and provides tips for resultful testing through awareness of coverage. 3. The document is authored by Maaret Pyhäjärvi and includes information about her background and credentials in agile testing and exploratory testing.

TSQA: Something In The Way We Test

This document discusses exploratory testing and compares traditional test case-driven approaches to more contemporary exploratory approaches. It notes that test cases are better thought of as outputs that convey relevant information rather than inputs used to direct testing. The document also emphasizes that exploratory testing is a verb describing the active process of doing testing rather than a noun referring to pre-defined tests. It advocates for change-focused testing and shares examples of moving from traditional test documentation like test case documents to more lightweight charters and specifications.

ATAGTR: Targeting Errors Of Omission

The document discusses various topics related to software testing including: 1. The importance of considering errors of omission and actively searching for what others may have missed. 2. A 1-2-3 model for test coverage that includes code, requirements, results, environment, and data. 3. How pictures can convey different information than text and the value of visual modeling. 4. References to documentation on integer to Roman numeral conversion tests and reproducing a majority of production failures with unit tests.

Pivotal Moments, Pivotal Experiences

This document summarizes Maaret Pyhäjärvi's career journey and experiences in software testing and agile practices over several decades: - It begins in the late 1990s when she started in functional and localization testing in Finland, and began researching exploratory testing. - In the 2000s she worked as a senior tester, test manager, and principal tester while also teaching and researching testing methods at a university. She helped companies transform to agile practices. - Recent pivotal moments include advancing ensemble and pair programming practices for testing in 2014-2015, and unifying manual and automated testing in 2018 with her work on contemporary exploratory testing. - Throughout her career she has overcome challenges like public

Keynote at Sanae Beer.EX: The Automationist's Gambit

The document discusses exploratory testing and test automation. It advocates that exploratory testing and test automation should be used together, not separately. You cannot automate testing well without exploring features, and you cannot explore efficiently without some automated tests. The document also provides examples of how exploratory testing and test automation can inform and enhance each other when used as complementary techniques.

Testing Assembly: From Observations to Insights on Test Specialist Careers

This document discusses insights into becoming a test specialist and building a career in testing. It touches on topics like recognizing testing as a career path, gaining experience and education over time, learning from communities, dealing with imposter syndrome, taking on more responsibility, and balancing different skills like testing, programming, communication and learning. The overarching messages are that gaining experience, learning from others, developing confidence, and staying active in your learning and community can help one succeed in a career in testing.

Let's Do a Thing and Call it Foo

The document discusses computer programming concepts like foobar, foo, and bar which are used as placeholder names. It then discusses using computer-assisted software authorship (CASA) to generate code and tests. Finally, it discusses lessons learned from pair and ensemble testing including how fast exploratory testing can be, useful testing techniques like parametrized and approval tests, and challenges of domain testing.

Selenium Conf: Patterns to Whole Team Test Automation Transformation

The document discusses test automation transformation and lessons learned from a team's experience improving their test automation process. Some key points: - The team was able to improve test automation maturity and increase speed of releases, decrease time to release, and improve productivity, despite not having an explicit test automation strategy or careful tool selection. - Perceived success factors included whole team effort, expert team members, self-motivated team members, allowing time for learning, and choosing the right test tools and infrastructure. - An incremental approach, observing and optimizing processes, and an internal open-source community mindset also contributed to the team's success in improving their test automation capabilities.

AxiomSummit 2022: A Practitioner's Guide to Contemporary Exploratory Testing

A new generation of testing is emerging, led by testers who believe test automation is an inseparable part of how we do exploratory testing. Yes, you read that right: exploratory testing with test automation, and on unit, api, ui and e2e levels all at our reach with team collaboration. We work on acceptance criteria and examples in our short increments, yet people are at their most creative on what could go wrong when they use the product or a piece of the product as their external imagination. When we’re creative, we need to do things we can’t do by hand, using programming to extend our reach. When we’re learning, we need to take notes now and to keep for later, again using programming to replenish information we deem worthwhile. We want to work on exploring a category of bugs before implementing, and a category of bugs before releasing, and a category of bugs after releasing. Last year I worked with a team that was transforming from a traditional manual test case + test automation -based approach to contemporary exploratory testing. This year I work with another team that takes this style of testing further than we’ve taken it before with whole-team testing. Let’s learn from a practitioner’s examples of ideas leading into this, changes enabling this, and results we are seeing with contemporary exploratory testing.

MoT Sfax: Good Exploratory Testing Tactics for Taking Over Testing

The document discusses exploratory testing tactics for taking over testing. It provides over 20 different tactics, such as finding bugs that matter without writing bug reports, using mind maps to model systems, following code changes and documentation to test different aspects, and classifying test charters. It advocates for a contemporary approach to exploratory testing that combines both manual and automated testing, and emphasizes learning and agency.

Geekle QA: Automationist's Gambit

Programming Assignments in Tester Interviews

The document discusses programming assignments that are given during job interviews. It begins by sharing an experience from a recent interview where the expected assignment was to implement Roman numerals but the interviewee was surprised with a numbers to text conversion problem instead. It then provides the code for a function to convert integers to text from 0 to 999. The document discusses observations about test-driven development (TDD) and different focuses on teasing out solutions versus problems. It also considers internal versus external focus and explores modes for interview assignments like homework, during the interview, or open book. Lastly, it provides suggestions for doing interviewing with code problems better such as asking the interviewee how they would showcase skills and giving feedback during the session.

MoT Sarajevo: How to get better at Exploratory testing

This document discusses how to get better at exploratory testing through understanding, practice with feedback, and continuous growth (GROW). It emphasizes learning through experience and feedback, practicing a variety of techniques like pair and ensemble testing, and gaining leadership skills to continuously improve testing practices. The goal of exploratory testing is to find issues others may have missed through an interactive, learning-focused process.

EuroSTAR '21 Keynote: Automationist's Gambit

While we draw parallels to Queen's Gambit the series on Netflix and Software Testing, this talk is not about how substance abuse is like testing. Instead, the movie guides us to to its name and figuring out what is this gambit. With exploratory testing, we have the opening moves, the midpart and the end game. The start can be anything but it builds our platform for the end game. And while exploratory testing, automation is part of that way of staying in tune with learning to win in the end game.

AppiumLite Keynote: Many Hats to Make a Tester

Hands off Exploratory Testing - Managing Testing at Scale