Agile testing for distributed teams and large orgsJanet Gregory
Some of the challenges and ideas for improving communication, testing practices that can help, and suggestions for adapting to the changes necessary to be successful in an agile world.
The document discusses challenges with agile testing in large enterprises and across distributed teams. It outlines some of the common challenges such as bureaucracy, multiple concurrent projects, and dependencies between teams. The document then provides several key testing practices that can work across teams, such as coordinating test planning, creating a shared test matrix, and using examples and tests to develop a common language. It emphasizes the importance of transparency between teams by sharing information and dependencies to reduce blame and ensure everyone understands the shared goals.
This document summarizes Janet Gregory's work promoting agile testing practices. It notes that she has been involved with agile teams since 2000 and has authored books and online courses on agile testing. The document discusses how testing should be a shared responsibility of the whole team. It emphasizes that testing provides feedback to improve quality, not just find bugs, and explains practices like examples, acceptance test-driven development, and exploratory testing that involve the whole team in testing activities.
A Whole Team Approach to Quality in Continuous Delivery - Lisa CrispinEqual Experts
Watch the video at https://www.equalexperts.com/expert-talks/a-whole-team-approach-to-quality-in-continuous-delivery/
It’s not uncommon for teams practicing, or moving towards, continuous delivery to face a growing backlog of customer-reported bugs and struggle to maintain their deployment cadence. If a team has testers, the testers may be expected to continue with their same testing activities, without any thought as to how those can be fit into CD. Teams without testing specialists often struggle with insufficient coverage from their automated regression tests, and they may miss serious problems entirely because of inadequate exploratory testing.
How can teams build confidence to release small changes so frequently? It’s not just about testing, it’s about finding ways to build quality into the product. This interactive session will introduce:
• a pipeline visualization exercise teams can do to find ways to fit in all testing activities, including manual ones, and shorten feedback loops
• using a test suite canvas to determine the minimum automated tests needed
• ways testing specialists help teams prevent defects and transfer testing skills across the team
This is a session for everyone on the software delivery team, who may or may not have experience with continuous delivery and deployment.
SPEAKER:
Lisa Crispin
Lisa Crispin is the co-author, with Janet Gregory, of three books: Agile Testing
Condensed: A Brief Introduction, More Agile Testing: Learning Journeys for the Whole Team, Agile Testing: A Practical Guide for Testers and Agile Teams; the LiveLessons Agile Testing Essentials video course, and “The Whole Team Approach to Agile Testing” 3-day training course offered through the Agile Testing Fellowship.
Lisa was voted by her peers as the Most Influential Agile Testing Professional Person at Agile Testing Days in 2012. She is co-founder with Janet of Agile Testing Fellowship, Inc.
Please visit www.lisacrispin.com, www.agiletestingfellow.com, and www.agiletester.ca for more.
Lisa is currently a Fellow Quality Owner at OutSystems, helping with the observability practice.
Using your testing mindset to explore requirementsJanet Gregory
Workshop from Agile Testing Days USA, Boston 2018 Janet Gregory and Ardita Karaj. Using different ideas to create your product backlog - understanding your ecosystem and using exploratory test charters to drive experimentation to your get to your learning releases.
The document discusses holistic testing in DevOps. It emphasizes testing early in collaboration with customers to help prevent defects. It also discusses testing throughout the deployment pipeline from development to production, including testing releases and using monitoring to observe and learn. The goal is to optimize the entire process from concept to delivering value to customers through continuous testing, delivery, learning and improvement.
The Whole Team Approach to Quality in Continuous Deliverylisacrispin
Lisa shares her teams' experiences with making a team commitment to quality and learning ways to build it in and fit all testing activities into continuous delivery.
Agile testing for distributed teams and large orgsJanet Gregory
Some of the challenges and ideas for improving communication, testing practices that can help, and suggestions for adapting to the changes necessary to be successful in an agile world.
The document discusses challenges with agile testing in large enterprises and across distributed teams. It outlines some of the common challenges such as bureaucracy, multiple concurrent projects, and dependencies between teams. The document then provides several key testing practices that can work across teams, such as coordinating test planning, creating a shared test matrix, and using examples and tests to develop a common language. It emphasizes the importance of transparency between teams by sharing information and dependencies to reduce blame and ensure everyone understands the shared goals.
This document summarizes Janet Gregory's work promoting agile testing practices. It notes that she has been involved with agile teams since 2000 and has authored books and online courses on agile testing. The document discusses how testing should be a shared responsibility of the whole team. It emphasizes that testing provides feedback to improve quality, not just find bugs, and explains practices like examples, acceptance test-driven development, and exploratory testing that involve the whole team in testing activities.
A Whole Team Approach to Quality in Continuous Delivery - Lisa CrispinEqual Experts
Watch the video at https://www.equalexperts.com/expert-talks/a-whole-team-approach-to-quality-in-continuous-delivery/
It’s not uncommon for teams practicing, or moving towards, continuous delivery to face a growing backlog of customer-reported bugs and struggle to maintain their deployment cadence. If a team has testers, the testers may be expected to continue with their same testing activities, without any thought as to how those can be fit into CD. Teams without testing specialists often struggle with insufficient coverage from their automated regression tests, and they may miss serious problems entirely because of inadequate exploratory testing.
How can teams build confidence to release small changes so frequently? It’s not just about testing, it’s about finding ways to build quality into the product. This interactive session will introduce:
• a pipeline visualization exercise teams can do to find ways to fit in all testing activities, including manual ones, and shorten feedback loops
• using a test suite canvas to determine the minimum automated tests needed
• ways testing specialists help teams prevent defects and transfer testing skills across the team
This is a session for everyone on the software delivery team, who may or may not have experience with continuous delivery and deployment.
SPEAKER:
Lisa Crispin
Lisa Crispin is the co-author, with Janet Gregory, of three books: Agile Testing
Condensed: A Brief Introduction, More Agile Testing: Learning Journeys for the Whole Team, Agile Testing: A Practical Guide for Testers and Agile Teams; the LiveLessons Agile Testing Essentials video course, and “The Whole Team Approach to Agile Testing” 3-day training course offered through the Agile Testing Fellowship.
Lisa was voted by her peers as the Most Influential Agile Testing Professional Person at Agile Testing Days in 2012. She is co-founder with Janet of Agile Testing Fellowship, Inc.
Please visit www.lisacrispin.com, www.agiletestingfellow.com, and www.agiletester.ca for more.
Lisa is currently a Fellow Quality Owner at OutSystems, helping with the observability practice.
Using your testing mindset to explore requirementsJanet Gregory
Workshop from Agile Testing Days USA, Boston 2018 Janet Gregory and Ardita Karaj. Using different ideas to create your product backlog - understanding your ecosystem and using exploratory test charters to drive experimentation to your get to your learning releases.
The document discusses holistic testing in DevOps. It emphasizes testing early in collaboration with customers to help prevent defects. It also discusses testing throughout the deployment pipeline from development to production, including testing releases and using monitoring to observe and learn. The goal is to optimize the entire process from concept to delivering value to customers through continuous testing, delivery, learning and improvement.
The Whole Team Approach to Quality in Continuous Deliverylisacrispin
Lisa shares her teams' experiences with making a team commitment to quality and learning ways to build it in and fit all testing activities into continuous delivery.
Get testing bottlenecks out of your pipelineslisacrispin
When teams move towards continuous delivery and deployment, how do they manage the manual stages in their deployment pipeline? This talk gives some techniques to visualize pipelines, identify bottlenecks, find ways to remove them.
Introduction into testing in large and distributed organizations that are practicing agile methods. Ideas, practices and tools to help develop open communication, deal with cultural differences both within an organization and across continents specifically related to testing activities.
Creating Agile Test Strategies for Larger EnterprisesTEST Huddle
Having difficulty creating an agile test strategy for your company? Let Testing Excellence Award winner, Derk-Jan de Grood, show you how it’s done
View webinar recording here - http://huddle.eurostarsoftwaretesting.com/resource/agile-testing/creating-agile-test-strategies-larger-enterprises/
This document introduces the A3 problem solving process. The A3 process provides a structured approach to address complex problems involving multiple causes across an organization. It involves planning to understand the current and target conditions, analyzing root causes, developing countermeasures through experiments, checking the results, and acting on lessons learned. An example is provided of using the A3 process to address an increase in serious defects found in code releases. The example walks through planning, root cause analysis identifying potential causes like insufficient testing time and large stories, developing countermeasures like weekly backlog grooming and test automation, and checking for results like reduced defects.
This document discusses Agile testing principles and practices. It defines Agile as valuing individuals and interactions over processes, working software over documentation, customer collaboration over contract negotiation, and responding to change over following a plan. It describes typical Agile team roles including the Agile Coach, Tester, Developer, and Product Owner. It then discusses Agile testing principles such as continuous feedback, delivering value, face-to-face communication, simplicity, and continuous improvement. The document outlines the Plan, Run, Evaluate, Improve steps of Agile testing and emphasizes the importance of continuous feedback and learning. It concludes that an Agile testing mindset is customer-focused, collaborative, and passionate about timely delivery of business value.
I presented this deck at a recent team meeting. This is a perpetual topic at every company I worked for. Having worked at early stage startups, fast growing unicorns, and IBM, I've got a sense of different kinds of speeds over the last 10 years. There 4 different kinds of speeds. The great companies are fast in all the speeds: Google, Facebook, Amazon, Tencent, Alibaba.
The document discusses challenges with the traditional waterfall process and separating testing from development in Agile. It advocates for a whole team approach where testers and developers collaborate throughout the sprint. Specification workshops are recommended to develop shared understanding. Automation and living documentation are presented as ways to prevent bugs. Quality is defined by how the software performs for users rather than bug counts. Measuring what matters to the business, rather than low level risks, is advised.
KAA How to get your Good agile teams to GreatDavid Hawks
The document provides tips for getting an agile team from good to great by focusing on outcomes over outputs, allocating time to incremental improvements to reduce technical debt, and limiting work in progress to focus on finishing projects instead of starting new ones in order to deliver value earlier. The presentation also discusses building trust, handling conflicts constructively, establishing team values and policies, and developing team members' breadth and depth of skills.
Dr. house would be a great product managementTautvydas Gylys
If product management goal is to increase the accuracy of company bets and if discovery is the process of doing that, why we spend so little time in comparison to taking care of delivery. Here I'm sharing insights from House MD and first steps we take @Trafi to change that.
The document discusses design sprints, which are a 5-day process to go from an idea to a tested prototype. It involves stages of understanding the problem, diverging on ideas, converging on a solution, prototyping, and user testing. The author discusses having conducted several successful design sprints across web and mobile products that significantly improved metrics like conversions, engagement, and growth. Key lessons are to properly prepare with data, stakeholders, and tools and to fully involve different teams to iterate quickly based on learnings.
Do you trust your developers to release on their own? Do you sleep well if they did? Do you know what is your next step?
High velocity development requires us to adopt continuous integration workflows, which means our reliance on manual QA has to drop significantly. For Quality Assurance Engineers it means we need to learn how to build effective automation strategy based on our resources.
During this talk we’ll look into exact steps you can use to define your product’s strategy in order to sleep well while your automation rocks.
PDCA, which stands for Plan, Do, Check, Act/Adjust, has provided a structure for process improvement for decades. Originally created by Dr. W. Edwards Deming, PDCA is an easy-to-follow method that works in any industry and on any process. Tune in to our 1-hour introductory webinar to get a primer on how this model can help you in your quest to explore root causes, improve processes and get results!
Test Strategy-The real silver bullet in testing by Matthew EakinQA or the Highway
This document provides an overview of creating a testing strategy. It begins with explaining why a testing strategy is important, as testing accounts for a large portion of IT budgets. It then discusses the key questions a testing strategy should answer: what to test, where to test, when to test, how to test, and who will test.
The document outlines a process for creating a testing strategy, including assessing the current state, defining a future vision, and creating a roadmap to get from the current to future state. It provides examples of what to include under each section of the strategy, such as system architecture under "what to test" and test environments under "where to test". Overall, the document provides guidance on developing a
Testing is Not a 9 to 5 Job - talk by industry executive Mike LylesApplitools
** FULL WEBINAR RECORDING: https://youtu.be/IC6ul_-PLj8 **
Find your hire power: Learn what managers look for when hiring (and firing...) testers.
Being an expert tester is no different. While the art and craft of testing and being a thinking tester is something that is built within you, simply going to work every day and being a tester is not always enough.
Each of us can become “gold medal testers” by practicing, studying, refining our skills, and building our craft.
In this webinar, we will evaluate extracurricular activities and practices that will enable you to grow from a good tester to a great tester.
Listen to this webinar, and enjoy these key takeaways:
** Inputs from testing experts on how they improve their skills
** Suggestions for online training and materials, which should be studied
** How to leverage social media to interact with the testing community
** Contributions you can make to the testing community to build your name as a leading test engineer
The document discusses lessons learned from implementing lean and agile approaches in three different products or organizations: Microsoft Windows CE.Net Platform Builder, Adobe Revel, and Spotify. For each product, both positive and negative lessons are outlined, such as isolating the effort as an experiment and being careful of early success for Windows, and balancing autonomy and collaboration for Spotify.
This document outlines potential causes of failure for a game development project based on a fishbone diagram. Key factors identified include lack of risk planning, overconfidence in the team's abilities, lack of market research on similar products or sales specialists for the business-to-business market, low budget, and entering a new market without sufficient preparation. Proper testing was also not conducted due to inaccurate project planning and oversight.
Workshop given at Agile Testing Days 2017 together with Lisa Crispin: "Testing in a Continuous World - How to Continuously Learn for Successful Continuous Delivery"
Abstract:
Nowadays users are quite used to getting product updates every other day. Many teams want to release updates to production more frequently, but they’re struggling to complete testing activities and fear that they might deliver big bugs instead of valuable features. Continuous delivery of reliable software is a huge challenge.
Many teams already develop their products in small chunks, but how does testing and quality fit into this fast-paced scenario? How can we not only continuously deliver, but continuously provide value to our users?
Elisabeth and Lisa have worked in teams who struggled to have testing fully integrated, being able to only release once every few weeks. They’ve also experienced highly collaborative teams who could easily deliver multiple times a day to quickly validate if they added value. What's your situation, can you keep up with testing and release frequently?
In this hands-on workshop, participants will have a chance to practice techniques that can help teams feel confident releasing more frequently. We will facilitate activities in which participants will come up with new experiments to help shorten feedback cycles, make sure all essential types of testing are done continually, and fit testing into the continuous world. Let's share experiences and develop custom solutions for your specific scenarios together!
WEBINAR: How to Flip the Conventional Lean Six Sigma Classroom Approach and G...GoLeanSixSigma.com
Are your Lean Six Sigma training efforts stale? Does your training approach need a facelift? Are you interested in changing your training approach to ensure students have better recall and retention of the material? Do you want to increase your rate of real world application and get better process improvement results? Then this 1-hour Leadership webinar is for you. We’ll provide the method and helpful examples of “Flipped Classrooms” so you can flip your own training and reap the rewards.
https://goleansixsigma.com/webinar-flip-conventional-lean-six-sigma-classroom-approach-get-better-results/
Testing in modern times a story about quality and value - agile testing dev ...Huib Schoots
In agile and especially DevOps approaches the motto is: automated everything! Companies like Facebook claim they do not have testers at all. Microsoft only has SDET (software development engineers in Test), other companies are T-shaping developers to do the testing. New kid on the block is AI and machine learning, that will definitely replace testing I hear people claim. What is really happening globally? Do we no longer need testers? Can we actually automate everything? How can we make valuable software for our clients?
In this presentation I will address questions like:
* Do we need testing? And if so: why is testing important?
* What is the business case of testing?
* Can developers also test? And if so: do we still need testers?
* How can we create quality software?
GDG Cloud Southlake #5 Eric Harvieux: Site Reliability Engineering (SRE) in P...James Anderson
Eric Harvieux, an SRE on Google's Customer Reliability Engineering (CRE) team, will talk to us about Site Reliability Engineering (SRE) in Practice, including a panel discussion with Fidelity, Home Depot, Sabre, and Google SRE Practitioners. We hope to hear how real-life SRE is different than the books.
Get testing bottlenecks out of your pipelineslisacrispin
When teams move towards continuous delivery and deployment, how do they manage the manual stages in their deployment pipeline? This talk gives some techniques to visualize pipelines, identify bottlenecks, find ways to remove them.
Introduction into testing in large and distributed organizations that are practicing agile methods. Ideas, practices and tools to help develop open communication, deal with cultural differences both within an organization and across continents specifically related to testing activities.
Creating Agile Test Strategies for Larger EnterprisesTEST Huddle
Having difficulty creating an agile test strategy for your company? Let Testing Excellence Award winner, Derk-Jan de Grood, show you how it’s done
View webinar recording here - http://huddle.eurostarsoftwaretesting.com/resource/agile-testing/creating-agile-test-strategies-larger-enterprises/
This document introduces the A3 problem solving process. The A3 process provides a structured approach to address complex problems involving multiple causes across an organization. It involves planning to understand the current and target conditions, analyzing root causes, developing countermeasures through experiments, checking the results, and acting on lessons learned. An example is provided of using the A3 process to address an increase in serious defects found in code releases. The example walks through planning, root cause analysis identifying potential causes like insufficient testing time and large stories, developing countermeasures like weekly backlog grooming and test automation, and checking for results like reduced defects.
This document discusses Agile testing principles and practices. It defines Agile as valuing individuals and interactions over processes, working software over documentation, customer collaboration over contract negotiation, and responding to change over following a plan. It describes typical Agile team roles including the Agile Coach, Tester, Developer, and Product Owner. It then discusses Agile testing principles such as continuous feedback, delivering value, face-to-face communication, simplicity, and continuous improvement. The document outlines the Plan, Run, Evaluate, Improve steps of Agile testing and emphasizes the importance of continuous feedback and learning. It concludes that an Agile testing mindset is customer-focused, collaborative, and passionate about timely delivery of business value.
I presented this deck at a recent team meeting. This is a perpetual topic at every company I worked for. Having worked at early stage startups, fast growing unicorns, and IBM, I've got a sense of different kinds of speeds over the last 10 years. There 4 different kinds of speeds. The great companies are fast in all the speeds: Google, Facebook, Amazon, Tencent, Alibaba.
The document discusses challenges with the traditional waterfall process and separating testing from development in Agile. It advocates for a whole team approach where testers and developers collaborate throughout the sprint. Specification workshops are recommended to develop shared understanding. Automation and living documentation are presented as ways to prevent bugs. Quality is defined by how the software performs for users rather than bug counts. Measuring what matters to the business, rather than low level risks, is advised.
KAA How to get your Good agile teams to GreatDavid Hawks
The document provides tips for getting an agile team from good to great by focusing on outcomes over outputs, allocating time to incremental improvements to reduce technical debt, and limiting work in progress to focus on finishing projects instead of starting new ones in order to deliver value earlier. The presentation also discusses building trust, handling conflicts constructively, establishing team values and policies, and developing team members' breadth and depth of skills.
Dr. house would be a great product managementTautvydas Gylys
If product management goal is to increase the accuracy of company bets and if discovery is the process of doing that, why we spend so little time in comparison to taking care of delivery. Here I'm sharing insights from House MD and first steps we take @Trafi to change that.
The document discusses design sprints, which are a 5-day process to go from an idea to a tested prototype. It involves stages of understanding the problem, diverging on ideas, converging on a solution, prototyping, and user testing. The author discusses having conducted several successful design sprints across web and mobile products that significantly improved metrics like conversions, engagement, and growth. Key lessons are to properly prepare with data, stakeholders, and tools and to fully involve different teams to iterate quickly based on learnings.
Do you trust your developers to release on their own? Do you sleep well if they did? Do you know what is your next step?
High velocity development requires us to adopt continuous integration workflows, which means our reliance on manual QA has to drop significantly. For Quality Assurance Engineers it means we need to learn how to build effective automation strategy based on our resources.
During this talk we’ll look into exact steps you can use to define your product’s strategy in order to sleep well while your automation rocks.
PDCA, which stands for Plan, Do, Check, Act/Adjust, has provided a structure for process improvement for decades. Originally created by Dr. W. Edwards Deming, PDCA is an easy-to-follow method that works in any industry and on any process. Tune in to our 1-hour introductory webinar to get a primer on how this model can help you in your quest to explore root causes, improve processes and get results!
Test Strategy-The real silver bullet in testing by Matthew EakinQA or the Highway
This document provides an overview of creating a testing strategy. It begins with explaining why a testing strategy is important, as testing accounts for a large portion of IT budgets. It then discusses the key questions a testing strategy should answer: what to test, where to test, when to test, how to test, and who will test.
The document outlines a process for creating a testing strategy, including assessing the current state, defining a future vision, and creating a roadmap to get from the current to future state. It provides examples of what to include under each section of the strategy, such as system architecture under "what to test" and test environments under "where to test". Overall, the document provides guidance on developing a
Testing is Not a 9 to 5 Job - talk by industry executive Mike LylesApplitools
** FULL WEBINAR RECORDING: https://youtu.be/IC6ul_-PLj8 **
Find your hire power: Learn what managers look for when hiring (and firing...) testers.
Being an expert tester is no different. While the art and craft of testing and being a thinking tester is something that is built within you, simply going to work every day and being a tester is not always enough.
Each of us can become “gold medal testers” by practicing, studying, refining our skills, and building our craft.
In this webinar, we will evaluate extracurricular activities and practices that will enable you to grow from a good tester to a great tester.
Listen to this webinar, and enjoy these key takeaways:
** Inputs from testing experts on how they improve their skills
** Suggestions for online training and materials, which should be studied
** How to leverage social media to interact with the testing community
** Contributions you can make to the testing community to build your name as a leading test engineer
The document discusses lessons learned from implementing lean and agile approaches in three different products or organizations: Microsoft Windows CE.Net Platform Builder, Adobe Revel, and Spotify. For each product, both positive and negative lessons are outlined, such as isolating the effort as an experiment and being careful of early success for Windows, and balancing autonomy and collaboration for Spotify.
This document outlines potential causes of failure for a game development project based on a fishbone diagram. Key factors identified include lack of risk planning, overconfidence in the team's abilities, lack of market research on similar products or sales specialists for the business-to-business market, low budget, and entering a new market without sufficient preparation. Proper testing was also not conducted due to inaccurate project planning and oversight.
Workshop given at Agile Testing Days 2017 together with Lisa Crispin: "Testing in a Continuous World - How to Continuously Learn for Successful Continuous Delivery"
Abstract:
Nowadays users are quite used to getting product updates every other day. Many teams want to release updates to production more frequently, but they’re struggling to complete testing activities and fear that they might deliver big bugs instead of valuable features. Continuous delivery of reliable software is a huge challenge.
Many teams already develop their products in small chunks, but how does testing and quality fit into this fast-paced scenario? How can we not only continuously deliver, but continuously provide value to our users?
Elisabeth and Lisa have worked in teams who struggled to have testing fully integrated, being able to only release once every few weeks. They’ve also experienced highly collaborative teams who could easily deliver multiple times a day to quickly validate if they added value. What's your situation, can you keep up with testing and release frequently?
In this hands-on workshop, participants will have a chance to practice techniques that can help teams feel confident releasing more frequently. We will facilitate activities in which participants will come up with new experiments to help shorten feedback cycles, make sure all essential types of testing are done continually, and fit testing into the continuous world. Let's share experiences and develop custom solutions for your specific scenarios together!
WEBINAR: How to Flip the Conventional Lean Six Sigma Classroom Approach and G...GoLeanSixSigma.com
Are your Lean Six Sigma training efforts stale? Does your training approach need a facelift? Are you interested in changing your training approach to ensure students have better recall and retention of the material? Do you want to increase your rate of real world application and get better process improvement results? Then this 1-hour Leadership webinar is for you. We’ll provide the method and helpful examples of “Flipped Classrooms” so you can flip your own training and reap the rewards.
https://goleansixsigma.com/webinar-flip-conventional-lean-six-sigma-classroom-approach-get-better-results/
Testing in modern times a story about quality and value - agile testing dev ...Huib Schoots
In agile and especially DevOps approaches the motto is: automated everything! Companies like Facebook claim they do not have testers at all. Microsoft only has SDET (software development engineers in Test), other companies are T-shaping developers to do the testing. New kid on the block is AI and machine learning, that will definitely replace testing I hear people claim. What is really happening globally? Do we no longer need testers? Can we actually automate everything? How can we make valuable software for our clients?
In this presentation I will address questions like:
* Do we need testing? And if so: why is testing important?
* What is the business case of testing?
* Can developers also test? And if so: do we still need testers?
* How can we create quality software?
GDG Cloud Southlake #5 Eric Harvieux: Site Reliability Engineering (SRE) in P...James Anderson
Eric Harvieux, an SRE on Google's Customer Reliability Engineering (CRE) team, will talk to us about Site Reliability Engineering (SRE) in Practice, including a panel discussion with Fidelity, Home Depot, Sabre, and Google SRE Practitioners. We hope to hear how real-life SRE is different than the books.
Good agile / Bad agile: Proving the value of Agile to a skeptical organizationAlan Albert
Is Agile worth it?
What value can being Agile bring to your organization?
Done right, Agile software development methodologies can help your organization deliver greater value to customers and other stakeholders more efficiently and with reduced risk.
Done wrong, Agile methodologies become an endlessly iterating feature factory, facing an ever-growing backlog.
In this interactive session, attendees discussed:
- How to identify what’s most valuable to build next
- How to ensure that the features you build are not just functional, but used and valued
- How to measure and effectively communicate the value that you create
Led by Alan Albert of MarketFit, this session at Agile Vancouver explored theory, examples, and exercises showing how to unlock the power of discovering, creating, and communicating value.
Presented at Ford's 2017 Global IT Learning Summit (GLITS)Ron Lazaro
Presentation Details: The best way to think about product discovery is to think about it in relation to product delivery. It's not possible to build a product without doing both discovery and delivery. Discovery encompasses all the activities that we do to decide what to build. It includes all the decisions we make to decide what to build next, whereas delivery is all the activities we do to write code, package releases, ship products. It's how we deliver value to our customers.
Key takeaway for the participants will be to help them understand the difference between Product Discovery and Product Delivery and how to apply techniques in doing both.
Id camp x dicoding live : persiapan jadi software engineer hebat 101DicodingEvent
Apakah seorang software engineer hebat adalah yang menguasai banyak bahasa pemrograman? Yang serba semua bisa? atau yang menguasai teknologi kekinian? Walaupun setiap individu memiliki standar hebat yang berbeda-beda tergantung dengan goals, passion, dan career path yang akan diambil. Tapi satu yang pasti untuk menjadi software engineer yang hebat ada cara dan langkah yang bisa dipelajari. Apa saja tips dan cara yang bisa kita lakukan untuk menjadi software engineer yang hebat? Hal ini akan kita bahas tips oleh Sidiq Permana (Co-Founder dan CIO - Nusantara Beta Studio) pada Dicoding LIVE x IDCamp dengan tema "Persiapan Jadi Software Engineer Hebat 101".
This document discusses how to grow a culture of quality in software development. It begins by defining quality as meeting customer needs and defining a culture of quality as having quality as the highest priority across teams. It then addresses common misconceptions about testing and quality assurance. The document advocates defining a quality narrative for how quality is perceived and measured in an organization. It provides an example of transforming a quality narrative from seeing quality assurance as a regulatory burden to advocates for quality. Key strategies discussed for growing a quality culture include empowering teams, engaging them in quality discussions, finding allies, speaking the language of the business, and continuously improving processes. The overall message is that developing a quality culture is a ongoing journey.
User Experience Measurement and Analysis: Perception TestingElementive
In this presentation learn about what perception testing is, see examples of perception tests and how you can use them to measure and improve your business.
LTK - FC - Supply Chain - Startup Challenge v3.pdfjeroen_tjepkema
Slides from our session at the FC Supply Chain event. It contains a short introduction into Lean Startup and innovation within FrieslandCampina, as well as 3 exercises for quickly deconstructing a complex challenges into experiments
How to Run Product Discovery Experiments in FinTechProduct School
The document discusses how to run successful product discovery experiments in FinTech. It covers identifying problems through customer research, creating testable hypotheses, designing experiments to validate hypotheses, and learning from experiment results. Specifically, it provides an example of running an experiment to test the hypothesis that mortgage brokers can access a virtual mortgage assistant via mobile app to get advice on suitable products for clients. The experiment would measure how often the assistant provides the right product recommendation and the reduction in calls to advisors. The document emphasizes the importance of experimentation for establishing a data-driven culture and de-risking investments by validating problems and solutions.
The document discusses the challenges of measuring progress in software development compared to manufacturing. Some key points:
- Software products are less standardized than manufactured goods, making it difficult to define metrics and measure improvements.
- Common metrics like lines of code and story points are arbitrary and don't accurately measure quality or velocity.
- Defect counts are an imperfect measure of quality as defects vary and there are long feedback loops.
- The document advocates measuring "waste" - non-productive time for engineers - as a better indicator of whether an organization is improving over time. Reducing waste through process improvements could show true gains in performance.
Huib Schoots Testing in modern times - a story about Quality and Value - Test...FiSTB
Huib introduces himself as an experienced IT professional with over 25 years of experience in roles such as developer, tester, consultant, manager, trainer, and coach. He currently works as a managing consultant and senior consultant focused on quality and testing.
The document discusses testing and quality, noting that quality is defined by the value provided to stakeholders rather than conformance to requirements. Testing is described as evaluating a product through experience and exploration to build understanding.
It emphasizes the importance of learning for both individuals and organizations. High-performing teams and organizations are able to learn continuously and adapt their processes accordingly. Continuous learning is key for developing complex software products and keeping up with changing needs.
Rev Up Your Lead Engine With Predictive ScoringMarketo
Check out this LaunchPoint presentation featuring data from Lattice, MuleSoft, and FireEye, to discover how to rev up your marketing engine with the power of predictive lead scoring!
This document provides an orientation for experts joining the Rover Expert Program powered by Directly. It outlines the key aspects of the Directly app such as the dashboard, answering questions, customer ratings, rewards, and resources for experts. Experts are encouraged to introduce themselves, start answering questions, and utilize additional resources to learn best practices.
Perhaps in no other professional field is the dichotomy between theory and practice more starkly different than in the realm of software testing. Researchers and thought leaders claim that testing requires a high level of cognitive and interpersonal skills, in order to make judgments about the ability of software to fulfill its operational goals. In their minds, testing is about assessing and communicating the risks involved in deploying software in a specific state.
However, in many organizations, testing remains a necessary evil, and a cost to drive down as much as possible. Testing is merely a measure of conformance to requirements, without regard to the quality of requirements or how conformance is measured. This is certainly an important measure, but tells an incomplete story about the value of software in support of our business goals.
We as testers often help to perpetuate the status quo. Although in many cases we realize we can add far more value than we do, we continue to perform testing in a manner that reduces our value in the software development process.
This presentation looks at the state of the art as well of the state of common practice, and attempts to provide a rationale and roadmap whereby the practice of testing can be made more exciting and stimulating to the testing professional, as well as more valuable to the product and the organization.
This presentation goes into details about impediments, how to identify them, how to create a strategy for, escalate, and ultimately - if not removing them entirely - moving the needle to improve the situation. Apologies for the outdated styling - it's on my backlog to improve it!
Global Talent Acquisition: Metrics that Matter and Metrics that Mean NOTHINGRecruitingDaily.com LLC
Talent is an Unfair Game.
You need to know how to play.
Nick Mailey, VP of Talent Acquisition for Intuit (top-shelf industry-leading TA organization) has the playbook, and he's agreed to join ranks with RecruitingDaily for an hour of training and Q&A to guide you through the field.
Understanding which Recruiting Metrics Matter and which are a waste of your time is essential to your success - you already know that.
Nick is going to teach you what you don't know.
And you're going to want to take notes.
Here's what we're going to cover:
The Curse of Talent in an Unfair Game
Understanding Vanity Metrics
Learning and Utilizing Empathy
Community Metrics
Closing Passive Candidates
A whole lot more....
We're not going to feed you basic knowledge you can find on Google.
You're going to take home actionable plans, real-time tools, and informative, common-sense data that will increase your workflow.
So, what do you say?
Do you want to win at the talent game?
Jobvite, Recruitics, Beamery, RolePoint
Presentation for Agile Australia Conference 2013. Introducing Lean Startup concepts in a way accessible to people used to usual project management methods. With lean startup you don't assume you know the end state required, (as you do with a project), you assume you need to focus on learning to discover the end state to solve the problem you area you looking at.
“For every complex problem there is an answer that is short, simple, and wrong!”
To estimate the complexity and the size of the project we’re about to develop is definitely a complex problem. It doesn't matter if it is a simple app for buying cat food or a very elaborated banking system. Usually, we’re using different estimation approaches to deal with this problem, but it’s pretty easy to fall into various traps. The results of your fall-downs may be really painful, such as an unhappy client or a frustrated team.
In this presentation we’re speaking about different situations and mistakes we’ve made (or have observed in other teams) and we’ll try to give some tips how to avoid them.
Similar to Change the conversation keynote StarWest 2015 (20)
WWDC 2024 Keynote Review: For CocoaCoders AustinPatrick Weigel
Overview of WWDC 2024 Keynote Address.
Covers: Apple Intelligence, iOS18, macOS Sequoia, iPadOS, watchOS, visionOS, and Apple TV+.
Understandable dialogue on Apple TV+
On-device app controlling AI.
Access to ChatGPT with a guest appearance by Chief Data Thief Sam Altman!
App Locking! iPhone Mirroring! And a Calculator!!
Unveiling the Advantages of Agile Software Development.pdfbrainerhub1
Learn about Agile Software Development's advantages. Simplify your workflow to spur quicker innovation. Jump right in! We have also discussed the advantages.
Consistent toolbox talks are critical for maintaining workplace safety, as they provide regular opportunities to address specific hazards and reinforce safe practices.
These brief, focused sessions ensure that safety is a continual conversation rather than a one-time event, which helps keep safety protocols fresh in employees' minds. Studies have shown that shorter, more frequent training sessions are more effective for retention and behavior change compared to longer, infrequent sessions.
Engaging workers regularly, toolbox talks promote a culture of safety, empower employees to voice concerns, and ultimately reduce the likelihood of accidents and injuries on site.
The traditional method of conducting safety talks with paper documents and lengthy meetings is not only time-consuming but also less effective. Manual tracking of attendance and compliance is prone to errors and inconsistencies, leading to gaps in safety communication and potential non-compliance with OSHA regulations. Switching to a digital solution like Safelyio offers significant advantages.
Safelyio automates the delivery and documentation of safety talks, ensuring consistency and accessibility. The microlearning approach breaks down complex safety protocols into manageable, bite-sized pieces, making it easier for employees to absorb and retain information.
This method minimizes disruptions to work schedules, eliminates the hassle of paperwork, and ensures that all safety communications are tracked and recorded accurately. Ultimately, using a digital platform like Safelyio enhances engagement, compliance, and overall safety performance on site. https://safelyio.com/
UI5con 2024 - Boost Your Development Experience with UI5 Tooling ExtensionsPeter Muessig
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
Flutter is a popular open source, cross-platform framework developed by Google. In this webinar we'll explore Flutter and its architecture, delve into the Flutter Embedder and Flutter’s Dart language, discover how to leverage Flutter for embedded device development, learn about Automotive Grade Linux (AGL) and its consortium and understand the rationale behind AGL's choice of Flutter for next-gen IVI systems. Don’t miss this opportunity to discover whether Flutter is right for your project.
14 th Edition of International conference on computer visionShulagnaSarkar2
About the event
14th Edition of International conference on computer vision
Computer conferences organized by ScienceFather group. ScienceFather takes the privilege to invite speakers participants students delegates and exhibitors from across the globe to its International Conference on computer conferences to be held in the Various Beautiful cites of the world. computer conferences are a discussion of common Inventions-related issues and additionally trade information share proof thoughts and insight into advanced developments in the science inventions service system. New technology may create many materials and devices with a vast range of applications such as in Science medicine electronics biomaterials energy production and consumer products.
Nomination are Open!! Don't Miss it
Visit: computer.scifat.com
Award Nomination: https://x-i.me/ishnom
Conference Submission: https://x-i.me/anicon
For Enquiry: Computer@scifat.com
Artificia Intellicence and XPath Extension FunctionsOctavian Nadolu
The purpose of this presentation is to provide an overview of how you can use AI from XSLT, XQuery, Schematron, or XML Refactoring operations, the potential benefits of using AI, and some of the challenges we face.
How Can Hiring A Mobile App Development Company Help Your Business Grow?ToXSL Technologies
ToXSL Technologies is an award-winning Mobile App Development Company in Dubai that helps businesses reshape their digital possibilities with custom app services. As a top app development company in Dubai, we offer highly engaging iOS & Android app solutions. https://rb.gy/necdnt
8 Best Automated Android App Testing Tool and Framework in 2024.pdfkalichargn70th171
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
What to do when you have a perfect model for your software but you are constrained by an imperfect business model?
This talk explores the challenges of bringing modelling rigour to the business and strategy levels, and talking to your non-technical counterparts in the process.
Top Benefits of Using Salesforce Healthcare CRM for Patient Management.pdfVALiNTRY360
Salesforce Healthcare CRM, implemented by VALiNTRY360, revolutionizes patient management by enhancing patient engagement, streamlining administrative processes, and improving care coordination. Its advanced analytics, robust security, and seamless integration with telehealth services ensure that healthcare providers can deliver personalized, efficient, and secure patient care. By automating routine tasks and providing actionable insights, Salesforce Healthcare CRM enables healthcare providers to focus on delivering high-quality care, leading to better patient outcomes and higher satisfaction. VALiNTRY360's expertise ensures a tailored solution that meets the unique needs of any healthcare practice, from small clinics to large hospital systems.
For more info visit us https://valintry360.com/solutions/health-life-sciences
7. • Value
• Uncertainty
• Risk
• How might we really measure product quality?
Instead, let’s talk about:
• Whose job is it anyway?
• The mindset of the team
And perhaps a bit about:
7
23. • Project, product, organization, reputation,
contractual, regulatory, legal (ex. privacy),
ethical …..
• ASK – Why do your
customers want you
to test for them?
28. Is it your job?
What about the Who???
If every team member took a holistic view of
the product release and the risks it faces, then
every person on the team would be a critical
contributor to the delivery of that solution.
Matt Mansell - paraphrased
Is it the tester’s job
to think about quality?
29. So, do you follow behind looking for bugs?
or …. are you looking ahead for the risks?
29
30. Can we really
measure product
quality …..
if we don’t measure:
- bugs, or
- requirements or
- coverage?
36. From finding and
counting bugs
To preventing bugs
and measuring value
about measuring
product quality
37. Agile Testing: A Practical Guide for Testers and Agile Teams
More Agile Testing: Learning Journeys for the Whole Team
By Janet Gregory and Lisa Crispin
www.agiletester.ca
www.agiletester.com
Contact info
www.janetgregory.ca
Email: janet@agiletester.ca
Twitter: janetgregoryca
37
Copyright 2015 : Janet Gregory – DragonFire Inc.
38. References
• Dan North, StarEast 2015 keynote
• http://lizkeogh.com/embracing-uncertainty/
• Dave Snowden on Cynafin
http://www.youtube.com/watch?v=N7oz366X0-8
• Matt Mansell – Risk-based testing, ANZTB 2014
http://www.anztb.org/userfiles/files/MATT_MANSELL_EffectiveRiskB
asedTesting-Distribution.pdf
• Rob Lambert http://thesocialtester.co.uk/how-do-you-measure-the-
effectiveness-of-a-tester-the-only-calculation-you-need/
• http://cherylquirion.com/
• www.lisacrispin.com
Editor's Notes
I want you to think about your last release to production – to your customers. Was it successful? <show of hands>
The conversation I am talking about is the conversation on quality
How many bugs …. What kind of bugs… and so on.
Only matters when there are too many to be able to use the application
And that’s really not what is important to the customer – in today’s market, if you are paying for something, you expect a quality product.
What’s important to your customer?
We measure …
What type of bugs,
What severity, what priority
We have defect triage – estimating how long to fix
Waste
Sometimes we measure other things, like ‘did we get all our requirements in, and did we test them?”
How important is this?
In today’s age of agile, a disciplined delivery team works at a feature / story together with the customer, who accepts. We know we test all the requirements because we do it together. There’s not usually a need to add extra work to trace.
If necessary, we can extract the tests and test results from the automation for audits.
There are exceptions, but I don’t come across them very often.
Measuring anything gives them - management a feeling of control, but it’s an illusion.
We can’t control.
Probably not much … or as much as you think.
Much of the metrics we use, probably doesn’t‘ even tell us about the quality of the product, but more about the quality of the process.
Does the customer care about the process or the product.
Delivery teams often get stuck in the details.
Value – what is it?
Uncertainty – how can we reduce it?
Risk – how do we mitigate it?
How might we really measure product quality
Carcassonne, France – medieval city
Can we deliver what they want …. Or better yet, what they need?
value is not the same for everyone
When we understand what problem the customer really has, maybe we’ll stand a chance of actually delivering what they need.
So instead of specifying # of steps, the rise of each step, etc.
Maybe we start with “We need to be able to escape from the floor we are on, and get either up to the roof, or down to the street”.
When we build it, we have a common understanding of the problem we are trying to solve, when we test it, we can test to the problem & solution, not only to the specification.
When we think about business value, we need to think about priorities.
Priorities… the most valuable first
Let’s think about it.. Can we break a feature into smaller bits and deliver “just enough”
Story done
Feature done ...
Work with customers to understand the importance of acceptance. Try to get small acceptance of features – define feature acceptance, not only story acceptance
I realized that I had done the pieces I really wanted to .. The dress, the pajamas, those are really boring – lots of white, and not much value to me.
Think “outside the box” – it doesn’t have to be major, and sometimes one new idea makes a process a whole lot easier.
The most successful teams enjoy a culture of learning where everyone on the team is free to raise issues and experiment.
Experiment to change how you think about measuring value. Validate early – Customer acceptance – on each story, on each feature.
Reduce the risk of getting it wrong.
Project managers often want certainty, management wants control – or the illusion of control
But perhaps, we shouldn’t aim for control, but think about how to reduce uncertainty –
Introduce the Cynefin model so people can go explore and learn.
Cynefin Framework (pronounced Ki neh’ vin) is about different domains/contexts -------a sense making model (Dave Snowden
Simple (obvious/known)– we’ve done it before; example – communication protocols
Complicated – harder, but not new
Complex – unknown
Chaotic – reacting, responding to fires
Models can help us choose how to tackle a problem …
Is it simple – we’ve done it before : the same, no need for analysis
Complicated – harder, but not new - can apply good practices like break into smaller chunks, requires expertise, good practices like ATDD or BDD
Complex – unknown - needs probing, questioning, works through examples to understand, experiment, get a better understanding of what it means before we commit
Chaotic – reacting, responding to fires - couldn’t treat each problem exactly the same.
We don’t want to do the same thing for every single new feature that comes up. We need to think about how to reduce the uncertainty in those complex problem areas. But not waste time on known problem areas.
Do we have danger in our s/w development - Especially if we are working on a life critical application.
Comes back to context.
Example of project risk – scope, schedule, budget
Example of product risk – features, quality attributes such as performance
From a testing perspective, we usually mean the second – risks to the product.
In Dan North’s keynote at StarEast, he talked about several things including the idea of risk planes. One of his Software Faster patterns - These are his pictures – used with his permission.
Risk planes – 3 dimensions: likelihood, impact and probability.
D – high impact, high likelihood should probably have higher coverage …
F – unlikely to fail, and if it does fail, do we care? 80% too much testing
We call this risk based testing,
Components work together, not in isolation.
User journeys…. Weakest link
Each context belongs to a human being
Testers need to be inside each of the stakeholders heads, and ask…
We go back to the value to the customer, what is their risk threshold – what can they live with.
So, I said there 2 risks – but that is a myth …
There are many stakeholders, many risks.
Their perceived risk may not be what you are thinking at all.
By asking why they want you to test, perhaps you can figure out what the risks are they are trying to mitigate – what is the most important thing?
Ask not only what’s the best, but what’s the worst thing that can happen.
Unnecessary features add unnecessary risks.
Story about Australia – study showed that speed and alcohol were not the only major causes of accidents. It turns out that tiredness is right up there as well, so they addressed that issue by putting reminder signs like this along the way, and made sure there were rest stops on the major highways. The accidents were reduced. Started in 1986
How do we make sure our team and our stakeholders get the same understanding.
Risk is reduced when more people know the issues …
It’s about transparency – Make it easy for people to participate in helping …
Use brain storming techniques such as mind mapping
This is about testing early - Think about prevent defects instead of counting them after.
How do you know when you prevented a defect? By the ah ha someone says. But that’s harder to prove… harder to count.
When we make testing visible and reducing misinterpretations, and misunderstanding – it helps to building the right thing.
Think about the business rules and explore examples - at all levels
We often get engrossed in the details – that’s where our expertise comes in, but we need to think about the bigger picture.
We need to step back a bit and look at
where will it grow, how big will it get, do I need …..
I liked the way Matt Mansell really says Quality is everyone’s job.
A contributor the solution – much better than the person who breaks the software…
Holistic view – everyone’s responsibility ;
Do you look at your problems and really understand them.
I see so many teams that aren’t addressing real problems, or don’t understand some basic ideas.
Customer validation and experimentation needs to continue throughout product/solution development - from the initial seed of an idea through to feature enhancements of a mature product/solution.
I like to think of it in terms –
- Problem validation, - making sure we understand the problem we are trying to solve
- solution (definition) validation – making sure we have a shared understanding of what we are trying to build – testing assumptions early
- implementation validation…(testing the product)
Our attention should be on solution-market fit versus number of bugs we found.
Right now, if feels like we are often victims of our rituals – what we know, what we are comfortable with.
They are good things. Is it enough?
If you aim for zero tolerance during development - zero known bugs escaping an iteration (or story or feature), then we can look very closely at the issues found by the customer because there are few.
What about the business value the software adds?
What about revenue generated by the the software added?
What about the cycle time of work? --- again – that’s measuring process quality – not product quality.
Monitor how your customers use your product. How is the customer impacted in real time so we can act quickly.
If we address all the high risk items and only low risk items at the end of the project tells you what?
For example, if one of the biggest risks is usability, perhaps we can use some testing techniques borrowed from the user experience world – techniques like customer touch points
Use different approaches and tools
Ex. Story mapping, Impact mapping, Structured conversations
How can we become more flexible in our thinking – in getting better at what we give to our customers.
Just imagine, putting out a release with very few known defects … and being able to measure customer satisfaction not by bugs, but by real value.
We know that you get what you measure – think what is important to your organization.
Stop, and look at what you are measuring. Does it add value to the organization? Is there something else that we could measure, or change.
If you stop counting your defects, (which includes, logging them all and triaging), how much time would that give you to start thinking about the business problem, and being able to participate in validating the solution to that problem before the code is even written.
Knowing how many bugs are in your software tells you … how bad it is, and I’m pretty sure that is not what organization thinks is important.
We need to create a good / create impact on the minds of the customers. That's is what will give loyalty to your product.