Invite the tester to the party
•
0 likes•43 views
This slide deck was used at the Global Scrum Gathering in Prague in 2015. The deck provides inspiration on: * How to make the tester part of the Development Team * How to eliminate the need for "Quality Control" * Foster collaboration within the team.
Report
Share
Report
Share
Download to read offline
Recommended
From Gatekeeper to Partner by Kelsey Shannahan
The document discusses moving from a "gatekeeper" model of testing, where testing is done separately after development, to a "partner" model where testing is integrated into development and shared responsibility of the team. It provides tips for making this transition, such as fixing problems developers experience with testing, integrating testing into development workflows, and helping testers contribute to other parts of development to become true partners. The overall message is that testing is most effective when it is easy to do and an inherent part of the development process done collaboratively by the entire team.
Gearing Startups for Success through Product Engineering
In the August edition of the #99XTWebinar Series, catch two of 99X Technology’s tech experts as they share some intuitive insights into product engineering for startups, and how they harnessed digital transformation to successfully launch a product.
Testing & Scrum
The document discusses organizing testing within the Scrum framework. It provides key messages: 1) everyone is a tester, 2) testing is infused into everything, not isolated, 3) some testing can be placed outside the Scrum team if multiple teams exist, and 4) complexity determines who performs different types of testing. It also discusses test ownership, automation, regression testing, and defines types of testing like isolated, contract, and integration testing. The overall message is that testing is integral to Scrum and should involve the whole team, while allowing for specialized testing roles.
ProductSavvy - Scrum and QA
Scrum is an agile process that focuses on delivering high business value in short iterations. It incorporates QA into the scrum process through:
1) Including testers in sprint planning and estimation. Testing tasks are estimated alongside development tasks.
2) Having testers participate in daily stand-ups to report on testing progress and blockers.
3) Having testers identify lessons learned and best practices from each sprint and drive needs for new test cases.
4) Clearly defining test responsibilities between developers and testers, with developers owning unit testing and testers owning other testing types.
Become a Quality Enabler
Instead of being just another cost center for a customer where you develop what you're told, how can you become proactive by understanding the business requirement and truly being a Quality Enabler? Xian Tharindra shares some great insights on this
Creating change from within - Agile Practitioners 2012
Faced with management that do not care about "being agile" what can a single developer do? Quite a lot!
Every developer has the power to improve the organization he works in in small iterative steps – and I can show you how.
If you want to make the change and don't know where to start – look no further, in this session I'll share my experience and show a few tips and tricks I learnt. As well as discuss the do and don'ts that can make all the.
- How to be agile developer in a waterfall company.
- Influencing people without formal authority.
- Using the right practices that makes the difference
- How to avoid alienating people
- Discovering your allies
- Know when to fight and when to "retreat" and cut your losses
- Making a change without disrupting the daily routine
- What being an agile evangelist is all about
QA tester in the Scrum
A QA tester plays an important role in each part of the Scrum process. In sprint planning, they help estimate development and QA tasks and share test specifications. During the sprint, they write automation and manual tests, review each other's work, and share testing knowledge. In daily standups, they update on previous and current tasks. At the end of the sprint, they participate in the review and retrospective.
QA in an Agile World for Agile and Beyond 2015
This document outlines an agenda for a presentation on adopting agile QA practices. It discusses establishing quality standards and definitions of done, gathering and prominently displaying metrics, and automating testing, builds, and releases. Key differences from traditional QA are highlighted, such as embracing emergent design over big upfront planning, shorter iterations and feedback loops, baking quality in rather than testing it in, and whole team ownership of quality rather than separate QA teams. Exercises are used to demonstrate these concepts in practice.
Recommended
From Gatekeeper to Partner by Kelsey Shannahan
The document discusses moving from a "gatekeeper" model of testing, where testing is done separately after development, to a "partner" model where testing is integrated into development and shared responsibility of the team. It provides tips for making this transition, such as fixing problems developers experience with testing, integrating testing into development workflows, and helping testers contribute to other parts of development to become true partners. The overall message is that testing is most effective when it is easy to do and an inherent part of the development process done collaboratively by the entire team.
Gearing Startups for Success through Product Engineering
In the August edition of the #99XTWebinar Series, catch two of 99X Technology’s tech experts as they share some intuitive insights into product engineering for startups, and how they harnessed digital transformation to successfully launch a product.
Testing & Scrum
The document discusses organizing testing within the Scrum framework. It provides key messages: 1) everyone is a tester, 2) testing is infused into everything, not isolated, 3) some testing can be placed outside the Scrum team if multiple teams exist, and 4) complexity determines who performs different types of testing. It also discusses test ownership, automation, regression testing, and defines types of testing like isolated, contract, and integration testing. The overall message is that testing is integral to Scrum and should involve the whole team, while allowing for specialized testing roles.
ProductSavvy - Scrum and QA
Scrum is an agile process that focuses on delivering high business value in short iterations. It incorporates QA into the scrum process through:
1) Including testers in sprint planning and estimation. Testing tasks are estimated alongside development tasks.
2) Having testers participate in daily stand-ups to report on testing progress and blockers.
3) Having testers identify lessons learned and best practices from each sprint and drive needs for new test cases.
4) Clearly defining test responsibilities between developers and testers, with developers owning unit testing and testers owning other testing types.
Become a Quality Enabler
Instead of being just another cost center for a customer where you develop what you're told, how can you become proactive by understanding the business requirement and truly being a Quality Enabler? Xian Tharindra shares some great insights on this
Creating change from within - Agile Practitioners 2012
Faced with management that do not care about "being agile" what can a single developer do? Quite a lot!
Every developer has the power to improve the organization he works in in small iterative steps – and I can show you how.
If you want to make the change and don't know where to start – look no further, in this session I'll share my experience and show a few tips and tricks I learnt. As well as discuss the do and don'ts that can make all the.
- How to be agile developer in a waterfall company.
- Influencing people without formal authority.
- Using the right practices that makes the difference
- How to avoid alienating people
- Discovering your allies
- Know when to fight and when to "retreat" and cut your losses
- Making a change without disrupting the daily routine
- What being an agile evangelist is all about
QA tester in the Scrum
A QA tester plays an important role in each part of the Scrum process. In sprint planning, they help estimate development and QA tasks and share test specifications. During the sprint, they write automation and manual tests, review each other's work, and share testing knowledge. In daily standups, they update on previous and current tasks. At the end of the sprint, they participate in the review and retrospective.
QA in an Agile World for Agile and Beyond 2015
This document outlines an agenda for a presentation on adopting agile QA practices. It discusses establishing quality standards and definitions of done, gathering and prominently displaying metrics, and automating testing, builds, and releases. Key differences from traditional QA are highlighted, such as embracing emergent design over big upfront planning, shorter iterations and feedback loops, baking quality in rather than testing it in, and whole team ownership of quality rather than separate QA teams. Exercises are used to demonstrate these concepts in practice.
Dedicated QA person in scrum team
A dedicated QA person in a Scrum team can help achieve quality by focusing solely on quality assurance tasks. The document describes a scenario where one Scrum team with a dedicated QA person delivered a higher quality product than other teams without dedicated QA. Having a QA specialist allows the person to fully concentrate on test case development, automation, and testing without also having development responsibilities. This dedicated role is needed because quality assurance requires significant mental effort that may not get fully addressed if distributed among generalist team members with other priorities.
Test Strategy-The real silver bullet in testing by Matthew Eakin
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
How to Build in Quality from Day 1 using Lean QA and Agile Testing
The document discusses how to build quality into software development from the start using Lean QA and Agile Testing. It emphasizes that quality is a team effort and should be considered from the beginning of development. Key aspects discussed include minimizing waste, risk-based testing, automating tests, traceability between requirements and tests, and integrating testing into continuous development processes.
Introducing QA Into an Agile Environment
This document discusses introducing quality assurance (QA) processes into an agile development environment. It describes some common challenges that can arise when development and testing are not well integrated, such as business stakeholders finding bugs late in the process. The author advocates for making QA practices and results visible and incorporating QA personnel into agile ceremonies like planning and demos. With collaboration, commitment to quality, and clear communication, the QA team was able to gain trust and find bugs earlier. Their approach evolved to take on more types of testing, and they worked with business to define different testing levels and work testing around releases.
Stc chandan patary_ua_testing _ stc
This document discusses ways to improve product development cycles through effective user acceptance testing and engagement. It describes how one organization achieved targets like reducing production to release cycles from 15 to 10 months by having product owners actively participate in validation testing. Stories from the trenches are shared about having product engineers directly involved in validation testing to better represent customer needs. Exploratory "monkey" testing of system boundaries is also discussed. The key takeaway is how design thinking principles were applied, like creating focus groups, prototyping solutions, and getting faster customer feedback through various iterative testing approaches.
Trends in Agile Testing by Lisa Crispin
- The document discusses trends in agile testing and how testing approaches have changed from traditional to agile methods. It focuses on practices like continuous integration, test-driven development, automating regression tests, and exploratory testing.
- Key aspects of agile testing covered include the whole team approach, collaboration between testers and developers, automating tests at different levels, and using feedback to continuously improve.
- The presentation highlights current trends like behavior-driven development, open source testing tools, and more emphasis on examples and collaboration with customers.
War for Agile
This document provides advice for teams considering adopting Agile practices. It lists reasons both for and against starting an Agile process. It then provides recommendations for implementing Agile in different project types and common best practices. Finally, it addresses potential adoption issues and asks if the reader has any other questions.
QA and scrum
Recently I was asked to to a presentation presentation at University of Cape Town entitled QA and SCRUM. This made very little sense to me but it did substantiate my belief that the understanding of agile development is generally very superficial ...
'The Real Agile Testing Quadrants' with Michael Bolton
EuroSTAR Conferences, with the support of ISA Software Skillnet, Irish Software Innovation Network and SoftTest, were delighted to bring you a half-day software testing masterclass with Michael Bolton
In this session, Michael Bolton (who has extensive experience as a tester, as a programmer, and as a project manager) explained the role of skilled software testers, and why you might not want to think of testing as "quality assurance".
He present ideas about the relationship between management and testers, and about the service that testers really provide: making quality assurance possible by lighting the way of the project. For those of you who who attended this event, we really hope it was of use to you in your testing careers.
www.eurostarconferences.com
Cost of defects
The raw number of defects found in a product version is not an adequate measure of the cost of the defects. This presentation explains how to qualify and monetize the cost of these defects throughout the SDLC
TDD in Agile
The document discusses test driven development (TDD) in an agile environment. It covers topics like the agile manifesto, evolutionary design, TDD steps and philosophy, myths about TDD, test qualities, benefits and costs of TDD, plugins and language support. The author shares their experience with TDD, noting that it improved code quality and refactoring while requiring support from leads to be effective long-term. Acceptance TDD is recommended to ensure shared understanding of what is being built.
Agile QA 2.0
This is the talk that I gave at the 2013 Agile Central Europe Conference in Krakow, Poland, Apr. 15-16.
How to be proud when you are done
This document discusses the importance of having a shared Definition of Done (DoD) between all parties involved in a project. It explains that without a DoD, different stakeholders can have conflicting understandings of what constitutes "done" work, leading to broken expectations. The document recommends introducing a DoD as early as possible in a project. It should be created collaboratively with input from customers, teams, and management. Automating checks against the DoD helps ensure work is truly done before moving forward. Continuous inspection and adaptation of the DoD also helps address problems over time. Having a DoD establishes a common vocabulary and allows the team to work together effectively to meet goals.
Understanding Kanban
Nikos Batsios presents an overview of Kanban principles and practices for managing workflow, including visualizing work, limiting work-in-process, and managing flow. Key aspects covered are using a Kanban board to visualize workflow stages and work items, establishing work-in-process limits to improve throughput, addressing bottlenecks, and helping work flow through the system by reducing waste and handoffs between stages. Metrics like throughput are also discussed. The presentation provides examples and recommendations for applying Kanban principles to optimize an organization's workflow.
Understanding Scrum
This document provides an overview and introduction to Agile and Scrum concepts. It discusses what Agile is and its values and principles like test-driven development. It also describes Scrum roles like Product Owner and Scrum Master, events like the daily scrum and sprint planning, and artifacts like the product backlog. The document summarizes Scrum practices for requirements gathering, estimation, the definition of done, backlog refinement, and retrospectives. It also briefly touches on topics like cross-functional teams, team formation models, and conditions for high performing teams.
Scrum Process For Offshore Team
The document outlines the scrum process for an offshore development team, including an overview of scrum methodology, roles like the product owner and scrum master, artifacts like the product backlog and sprint burndown chart, and activities in the sprint planning, daily standups, and retrospectives. It provides details on tailoring scrum for offshore teams and defining roles for the project manager, development team, and business analyst to work with the onshore client.
Agile tester 3.0
The document discusses Daniel Ricardo de Amorim and his role as an Agile QA Consultant. It explores how agile testers work as part of development teams rather than as separate roles. It sorts QA profiles into three dimensions: business, technical, and DevOps. The business dimension involves acceptance testing and BDD. The technical dimension covers programming skills, TDD, test automation, and security and performance testing. The DevOps dimension focuses on continuous delivery and automating repeatable tasks. All QAs keep the team focused on delivery, product quality, test ownership, and wear many hats to infect the team with quality practices.
Quality Awareness When Practicing Agile Testing
At the recently held “CodeCamp” event, Ana Milutinovic spoke about the challenges of Quality Assurance in Agile Development and presented lots of best practice experience.
Quality Assurance Challenges in Agile Development
While many books have been written about Agile Development methodologies and their success stories - little has been said about how to handle quality assurance and testing in Agile projects.
After getting involved with her first Agile Development project some years ago, Ana Milutinovic – QA Engineer at youngculture – found herself confronted with the challenge of having to rethink traditionally established testing processes that worked well for Waterfall Projects but which were not suitable for Agile Development. Problems arose like how to do proper test planning, if no scope planning was available? How to fit in writing test cases and test execution in 2-week sprints that looked like mini-Waterfall Projects? There was never enough time for quality assurance and bugs were accumulating.
Best Practise Tips
That’s when Ana and her colleagues began to develop their own model for Agile testing, which has since been refined in many e-commerce and other projects. Some best practice tips:
1. Quality in Planning: Actively involve QA Engineers in sprint planning
In order to avoid running into time constraints a realistic planning of both – development and quality assurance – is crucial. It is therefore important that QA engineers get a profound understanding of the features in order to estimate realistic test efforts. An “easy-to-develop” feature might mean a huge testing effort and vice versa.
2. Quality in Test-Design: Engage developers in writing test cases
Instead of handing over quality assurance to the test department, developers should be included in writing test cases. This not only raises the focus on quality, but also helps developers in making the specification, because the QA engineer might point out use cases they would not have otherwise thought of.
3. Quality in Test-Execution: Closer collaboration brings better results
As a consequence of closer collaboration between software and QA engineers in the test-planning and design phases, QA engineers will have a better insight into the project goals and will be therefore more effective in test-execution.
4. Quality in Reporting and Metrics: tool based & fast feedback
In order to cope with agile processes, efficient and focused test feedback is key. Forget about detailed strategy papers, test documentation and extensive test reports. Rather work with checklists and modern test management tools.
[HCMC STC Jan 2015] Workshop Of Context-Driven Testing In Agile
[HCMC STC Jan 2015] Workshop Of Context-Driven Testing In AgileHo Chi Minh City Software Testing Club
Ho Chi Minh City Software Testing Conference January 2015
Software Testing in the Agile World
Website: www.hcmc-stc.org
Author: Nhat Do, Vu Duong
Context-Driven Testing (CDT) rejects the notion of generalized “best practices” that apply to all projects, and instead accepts that different practices work best under different circumstances. The third principle of the seven defined in CDT states that people are the most important part of any project’s context. Less of a focus on processes and tools, with more emphasis on people and their collaboration empowers testers with the freedom to make choices about how best to do their job without following a restrictive plan.
In joining the game of workshop and some theory sharing in slides, you will a better understanding of Context-Driven Testing practices, principles and its benefits as well as know how is a nice Marriage of Agile and Context-Driven Testing.Integrate testing activities in Agile (EuroSTAR webinar)
At 23 July 2014 I presented a EuroSTAR webinar on the topic of integrating testing activities in Agile. The webinar was based on the EuroSTAR ebook "Integrage Test Activities in Agile Projects" by Leo van der Aalst and myself. Also it was inspired by the books "TMap NEXT in Scrum" and "PointZERO" that were both published in 2012.
Crash Course Scrum - handout
A 1 Day training that shows you all you need to know about Scrum, the afternoon contains a practical part where we perform several sprints using Lego as our means of production
Agile testing
- Agile development is not an excuse for sloppy coding practices - it requires discipline and testing throughout the development process.
- In an Agile sprint, testers are involved from the beginning in planning, designing tests as features are developed, and testing iteratively throughout the sprint. Every iteration should result in a potentially shippable product that is tested.
- While some documentation is not needed, testing is still required. Automated testing is important for regression testing to avoid manually retesting everything as more is added, and it needs to be prioritized and maintained.
More Related Content
What's hot
Dedicated QA person in scrum team
A dedicated QA person in a Scrum team can help achieve quality by focusing solely on quality assurance tasks. The document describes a scenario where one Scrum team with a dedicated QA person delivered a higher quality product than other teams without dedicated QA. Having a QA specialist allows the person to fully concentrate on test case development, automation, and testing without also having development responsibilities. This dedicated role is needed because quality assurance requires significant mental effort that may not get fully addressed if distributed among generalist team members with other priorities.
Test Strategy-The real silver bullet in testing by Matthew Eakin
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
How to Build in Quality from Day 1 using Lean QA and Agile Testing
The document discusses how to build quality into software development from the start using Lean QA and Agile Testing. It emphasizes that quality is a team effort and should be considered from the beginning of development. Key aspects discussed include minimizing waste, risk-based testing, automating tests, traceability between requirements and tests, and integrating testing into continuous development processes.
Introducing QA Into an Agile Environment
This document discusses introducing quality assurance (QA) processes into an agile development environment. It describes some common challenges that can arise when development and testing are not well integrated, such as business stakeholders finding bugs late in the process. The author advocates for making QA practices and results visible and incorporating QA personnel into agile ceremonies like planning and demos. With collaboration, commitment to quality, and clear communication, the QA team was able to gain trust and find bugs earlier. Their approach evolved to take on more types of testing, and they worked with business to define different testing levels and work testing around releases.
Stc chandan patary_ua_testing _ stc
This document discusses ways to improve product development cycles through effective user acceptance testing and engagement. It describes how one organization achieved targets like reducing production to release cycles from 15 to 10 months by having product owners actively participate in validation testing. Stories from the trenches are shared about having product engineers directly involved in validation testing to better represent customer needs. Exploratory "monkey" testing of system boundaries is also discussed. The key takeaway is how design thinking principles were applied, like creating focus groups, prototyping solutions, and getting faster customer feedback through various iterative testing approaches.
Trends in Agile Testing by Lisa Crispin
- The document discusses trends in agile testing and how testing approaches have changed from traditional to agile methods. It focuses on practices like continuous integration, test-driven development, automating regression tests, and exploratory testing.
- Key aspects of agile testing covered include the whole team approach, collaboration between testers and developers, automating tests at different levels, and using feedback to continuously improve.
- The presentation highlights current trends like behavior-driven development, open source testing tools, and more emphasis on examples and collaboration with customers.
War for Agile
This document provides advice for teams considering adopting Agile practices. It lists reasons both for and against starting an Agile process. It then provides recommendations for implementing Agile in different project types and common best practices. Finally, it addresses potential adoption issues and asks if the reader has any other questions.
QA and scrum
Recently I was asked to to a presentation presentation at University of Cape Town entitled QA and SCRUM. This made very little sense to me but it did substantiate my belief that the understanding of agile development is generally very superficial ...
'The Real Agile Testing Quadrants' with Michael Bolton
EuroSTAR Conferences, with the support of ISA Software Skillnet, Irish Software Innovation Network and SoftTest, were delighted to bring you a half-day software testing masterclass with Michael Bolton
In this session, Michael Bolton (who has extensive experience as a tester, as a programmer, and as a project manager) explained the role of skilled software testers, and why you might not want to think of testing as "quality assurance".
He present ideas about the relationship between management and testers, and about the service that testers really provide: making quality assurance possible by lighting the way of the project. For those of you who who attended this event, we really hope it was of use to you in your testing careers.
www.eurostarconferences.com
Cost of defects
The raw number of defects found in a product version is not an adequate measure of the cost of the defects. This presentation explains how to qualify and monetize the cost of these defects throughout the SDLC
TDD in Agile
The document discusses test driven development (TDD) in an agile environment. It covers topics like the agile manifesto, evolutionary design, TDD steps and philosophy, myths about TDD, test qualities, benefits and costs of TDD, plugins and language support. The author shares their experience with TDD, noting that it improved code quality and refactoring while requiring support from leads to be effective long-term. Acceptance TDD is recommended to ensure shared understanding of what is being built.
Agile QA 2.0
This is the talk that I gave at the 2013 Agile Central Europe Conference in Krakow, Poland, Apr. 15-16.
How to be proud when you are done
This document discusses the importance of having a shared Definition of Done (DoD) between all parties involved in a project. It explains that without a DoD, different stakeholders can have conflicting understandings of what constitutes "done" work, leading to broken expectations. The document recommends introducing a DoD as early as possible in a project. It should be created collaboratively with input from customers, teams, and management. Automating checks against the DoD helps ensure work is truly done before moving forward. Continuous inspection and adaptation of the DoD also helps address problems over time. Having a DoD establishes a common vocabulary and allows the team to work together effectively to meet goals.
Understanding Kanban
Nikos Batsios presents an overview of Kanban principles and practices for managing workflow, including visualizing work, limiting work-in-process, and managing flow. Key aspects covered are using a Kanban board to visualize workflow stages and work items, establishing work-in-process limits to improve throughput, addressing bottlenecks, and helping work flow through the system by reducing waste and handoffs between stages. Metrics like throughput are also discussed. The presentation provides examples and recommendations for applying Kanban principles to optimize an organization's workflow.
Understanding Scrum
This document provides an overview and introduction to Agile and Scrum concepts. It discusses what Agile is and its values and principles like test-driven development. It also describes Scrum roles like Product Owner and Scrum Master, events like the daily scrum and sprint planning, and artifacts like the product backlog. The document summarizes Scrum practices for requirements gathering, estimation, the definition of done, backlog refinement, and retrospectives. It also briefly touches on topics like cross-functional teams, team formation models, and conditions for high performing teams.
Scrum Process For Offshore Team
The document outlines the scrum process for an offshore development team, including an overview of scrum methodology, roles like the product owner and scrum master, artifacts like the product backlog and sprint burndown chart, and activities in the sprint planning, daily standups, and retrospectives. It provides details on tailoring scrum for offshore teams and defining roles for the project manager, development team, and business analyst to work with the onshore client.
Agile tester 3.0
The document discusses Daniel Ricardo de Amorim and his role as an Agile QA Consultant. It explores how agile testers work as part of development teams rather than as separate roles. It sorts QA profiles into three dimensions: business, technical, and DevOps. The business dimension involves acceptance testing and BDD. The technical dimension covers programming skills, TDD, test automation, and security and performance testing. The DevOps dimension focuses on continuous delivery and automating repeatable tasks. All QAs keep the team focused on delivery, product quality, test ownership, and wear many hats to infect the team with quality practices.
Quality Awareness When Practicing Agile Testing
At the recently held “CodeCamp” event, Ana Milutinovic spoke about the challenges of Quality Assurance in Agile Development and presented lots of best practice experience.
Quality Assurance Challenges in Agile Development
While many books have been written about Agile Development methodologies and their success stories - little has been said about how to handle quality assurance and testing in Agile projects.
After getting involved with her first Agile Development project some years ago, Ana Milutinovic – QA Engineer at youngculture – found herself confronted with the challenge of having to rethink traditionally established testing processes that worked well for Waterfall Projects but which were not suitable for Agile Development. Problems arose like how to do proper test planning, if no scope planning was available? How to fit in writing test cases and test execution in 2-week sprints that looked like mini-Waterfall Projects? There was never enough time for quality assurance and bugs were accumulating.
Best Practise Tips
That’s when Ana and her colleagues began to develop their own model for Agile testing, which has since been refined in many e-commerce and other projects. Some best practice tips:
1. Quality in Planning: Actively involve QA Engineers in sprint planning
In order to avoid running into time constraints a realistic planning of both – development and quality assurance – is crucial. It is therefore important that QA engineers get a profound understanding of the features in order to estimate realistic test efforts. An “easy-to-develop” feature might mean a huge testing effort and vice versa.
2. Quality in Test-Design: Engage developers in writing test cases
Instead of handing over quality assurance to the test department, developers should be included in writing test cases. This not only raises the focus on quality, but also helps developers in making the specification, because the QA engineer might point out use cases they would not have otherwise thought of.
3. Quality in Test-Execution: Closer collaboration brings better results
As a consequence of closer collaboration between software and QA engineers in the test-planning and design phases, QA engineers will have a better insight into the project goals and will be therefore more effective in test-execution.
4. Quality in Reporting and Metrics: tool based & fast feedback
In order to cope with agile processes, efficient and focused test feedback is key. Forget about detailed strategy papers, test documentation and extensive test reports. Rather work with checklists and modern test management tools.
[HCMC STC Jan 2015] Workshop Of Context-Driven Testing In Agile
[HCMC STC Jan 2015] Workshop Of Context-Driven Testing In AgileHo Chi Minh City Software Testing Club
Ho Chi Minh City Software Testing Conference January 2015
Software Testing in the Agile World
Website: www.hcmc-stc.org
Author: Nhat Do, Vu Duong
Context-Driven Testing (CDT) rejects the notion of generalized “best practices” that apply to all projects, and instead accepts that different practices work best under different circumstances. The third principle of the seven defined in CDT states that people are the most important part of any project’s context. Less of a focus on processes and tools, with more emphasis on people and their collaboration empowers testers with the freedom to make choices about how best to do their job without following a restrictive plan.
In joining the game of workshop and some theory sharing in slides, you will a better understanding of Context-Driven Testing practices, principles and its benefits as well as know how is a nice Marriage of Agile and Context-Driven Testing.Integrate testing activities in Agile (EuroSTAR webinar)
At 23 July 2014 I presented a EuroSTAR webinar on the topic of integrating testing activities in Agile. The webinar was based on the EuroSTAR ebook "Integrage Test Activities in Agile Projects" by Leo van der Aalst and myself. Also it was inspired by the books "TMap NEXT in Scrum" and "PointZERO" that were both published in 2012.
What's hot (20)
Test Strategy-The real silver bullet in testing by Matthew Eakin
Test Strategy-The real silver bullet in testing by Matthew Eakin
How to Build in Quality from Day 1 using Lean QA and Agile Testing
How to Build in Quality from Day 1 using Lean QA and Agile Testing
'The Real Agile Testing Quadrants' with Michael Bolton
'The Real Agile Testing Quadrants' with Michael Bolton
[HCMC STC Jan 2015] Workshop Of Context-Driven Testing In Agile
[HCMC STC Jan 2015] Workshop Of Context-Driven Testing In Agile
Integrate testing activities in Agile (EuroSTAR webinar)
Integrate testing activities in Agile (EuroSTAR webinar)
Similar to Invite the tester to the party
Crash Course Scrum - handout
A 1 Day training that shows you all you need to know about Scrum, the afternoon contains a practical part where we perform several sprints using Lego as our means of production
Agile testing
- Agile development is not an excuse for sloppy coding practices - it requires discipline and testing throughout the development process.
- In an Agile sprint, testers are involved from the beginning in planning, designing tests as features are developed, and testing iteratively throughout the sprint. Every iteration should result in a potentially shippable product that is tested.
- While some documentation is not needed, testing is still required. Automated testing is important for regression testing to avoid manually retesting everything as more is added, and it needs to be prioritized and maintained.
Project management for qa manager
The document provides guidance for a QA manager's role in project management. It outlines responsibilities like managing the QA team, interacting with other teams, and ensuring work is on time and high quality. It also describes tasks for project planning such as understanding requirements, defining deliverables, scheduling testing activities, and communicating with stakeholders. Standard templates, reviews, reports, and post-mortem analyses are recommended to help manage the quality of the work.
Methodology: IT test
like Google, Improve your Test perception & practices and learn how Test might be a key lever to improve your business.
- Understand the different types of Test
- Best & Worst practices of Test
Scrum 101
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
Practicing Agile through Scrum
Scrum is an agile framework that focuses on rapid delivery of working software in short cycles called sprints. It involves self-organizing cross-functional teams, prioritized backlogs and artifacts like product backlogs, sprint backlogs and increments. Key roles include the product owner who prioritizes features, the development team who work on delivering features and the scrum master who facilitates the process. Ceremonies like sprint planning, daily standups, sprint reviews and retrospectives help ensure transparency and process improvement.
Agile testing
I see many company which calls them agile but not. You can not apply agile without agile testing mindset.
Vladimir Lozanov How to deliver high quality apps to the app store
Mobile QA teams are responsible for thoroughly testing apps before release to ensure high quality. They use a variety of manual and automated testing methods at different stages of development. QA works closely with development and customer support to catch bugs, validate fixes, and improve the product based on user feedback. The goal is to deliver stable, bug-free apps through collaboration across teams.
QA Best Practices in Agile World_new
The document discusses QA best practices in an Agile development environment. It describes key aspects of Agile like iterative delivery, self-organizing teams, and rapid feedback. It addresses challenges of fitting QA into short iterations and questions around testing approaches. The document advocates for testing to be collaborative, automated, and continuous throughout development. It provides recommendations for QA roles in activities like planning, stand-ups, retrospectives and acceptance testing. Overall it promotes testing practices in Agile that focus on early feedback, automation, and involvement of QA throughout the development process.
Sustainable agile testing
The agile community has done a very good job over the last few years in re-thinking the software development process and practices. What about testing though ? Are we really agile about it ? For most companies testing and QAs are still a bottleneck. In this session we will explore practices and techniques which will enable us to bring testing to the next level. We will focus particurarly on the concept of acceptance tests driven development and the role played by the "software developer in test"
Scrum toufiq
Scrum is an agile framework for managing software development projects, characterized by short development cycles called sprints, daily stand-up meetings, and emphasis on self-organizing cross-functional teams. Key roles include the product owner, who prioritizes features; the scrum master, who facilitates the process; and the development team. Scrum uses artifacts like the product backlog, sprint backlog, and burndown charts to track progress. Ceremonies like sprint planning, daily scrums, sprint reviews, and retrospectives promote inspection and adaptation.
Scrum à la Pablo (English)
Experiments that have worked for me in the last 7 years playing with Scrum in Agile teams.
The presentation covers 4 key pilars of Scrum:
- Roles: Product Owner, Scrum Master and Development Team.
- Scrum Events: Planning Meeting, Daily Stand-up, Grooming/Refinement, Demo and Retrospective.
- Scrum Artifacts: Product Backlog, User Stories, Definition of Done, Sprint Backlog, Sprint Dashboad.
- Reports: End of Sprint Report, New Sprint Report, Burn-up/Burn-down, Product Report.
Tester career path
This document discusses career paths for testing engineers. It begins by describing a typical interview where the candidate's lack of technical skills is apparent. It then discusses a tester's concerns about their career progression and perceptions of testers. The document outlines stories of individuals who grew their careers in testing over long periods of time, taking on roles such as test automation engineer and testing director. It provides advice on making good career choices by gaining experience in one's current role and waiting for opportunities, rather than changing roles frequently or due to money alone. Specific career paths are suggested such as build master, release engineer, and testing management. The document emphasizes that experience over time strengthens one's position and makes them competitive for career growth.
Scrum and-xp-from-the-trenches 06 testing
This document discusses testing in Scrum projects. It cannot be avoided, but can be minimized. Putting testers in the Scrum team increases quality by having developers tested by experts. Doing less per sprint also increases quality. Acceptance testing may require its own phase after sprints. Prioritize fixing old bugs found before starting new work. Alleviate bottlenecks by increasing test automation, adding testers, or adjusting sprint length. True cross-functional teams share testing duties.
Agile_basics
Basics of Agile for beginners. It will help you to understand what is agile and what are all terminologies we use in Agile.
Getting Agile Right - Rebooting an Agile organization in 100 days - Agile Tou...
Presentation at Agile Tour Montreal 2018 by Maurizio Mancini of Exempio and Paul T. Ryan CTO of OpenX.
Many organizations think they are Agile when they are not. Here is how to recognize when you need an Agile reboot and how to reboot your organization to become a true Agile organization.
Summer Scrum Public
This document provides an overview of Scrum, an agile project management framework. It describes Scrum as a lightweight framework using iterative and incremental development approaches. The key Scrum components include roles like the Product Owner and Scrum Master, prioritized backlogs, sprints, and events like sprint planning and retrospectives. Benefits of Scrum include increased productivity, quality, and customer satisfaction compared to traditional waterfall models. Scrum enables flexibility and incorporating feedback throughout development rather than having a fixed plan.
Fundamentals of agile tntu (2015-04-27)
The document provides an overview of fundamentals of agile, including:
- Describing the waterfall process and limitations with knowledge work
- Introducing the Agile Manifesto which values individuals, working software, customer collaboration, and responding to change over processes and tools
- Outlining common agile approaches like XP, Scrum, and Kanban including roles, ceremonies, and artifacts
- Defining roles like Scrum Master, Product Owner, and cross-functional delivery teams
- Explaining the overall agile process flow including visioning, backlog organization, sprint planning, daily stand-ups, sprint reviews and retrospectives
scrum-talk
Nopparat and Samatchaya gave a presentation on Scrum and Agile. They discussed key concepts like the Agile Manifesto, Scrum roles, the Scrum process, and their experiences implementing Scrum. As an Agile coach, Nopparat helps teams build an environment for self-organization and continuous improvement through training, coaching, and ensuring stakeholder support for Agile goals. The presentation included games to illustrate Scrum concepts and a case study on challenges of creating an Agile culture.
Scrum and agile principles
- Scrum is an agile framework for managing product development, with roles of Product Owner, Scrum Master, and Development Team.
- Key rituals include Sprint Planning, Daily Stand-ups, Sprint Review and Retrospective.
- The Product Owner prioritizes features in the Product Backlog to maximize business value, while the Development Team works in sprints to deliver increments of functionality. The Scrum Master facilitates the process and removes impediments.
Similar to Invite the tester to the party (20)
Vladimir Lozanov How to deliver high quality apps to the app store
Vladimir Lozanov How to deliver high quality apps to the app store
Getting Agile Right - Rebooting an Agile organization in 100 days - Agile Tou...
Getting Agile Right - Rebooting an Agile organization in 100 days - Agile Tou...
Recently uploaded
National Security Agency - NSA mobile device best practices
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Pushing the limits of ePRTC: 100ns holdover for 100 days
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
Infrastructure Challenges in Scaling RAG with Custom AI models
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
Video Streaming: Then, Now, and in the Future
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
TrustArc Webinar - 2024 Global Privacy Survey
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
Communications Mining Series - Zero to Hero - Session 1
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Removing Uninteresting Bytes in Software Fuzzing
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Mind map of terminologies used in context of Generative AI
Mind map of common terms used in context of Generative AI.
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
Recently uploaded (20)
National Security Agency - NSA mobile device best practices
National Security Agency - NSA mobile device best practices
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 days
Infrastructure Challenges in Scaling RAG with Custom AI models
Infrastructure Challenges in Scaling RAG with Custom AI models
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Communications Mining Series - Zero to Hero - Session 1
Communications Mining Series - Zero to Hero - Session 1
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Mind map of terminologies used in context of Generative AI
Mind map of terminologies used in context of Generative AI
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Invite the tester to the party
- 1. Contact information Email: allan@coreagile.eu Twitter: @rennebo Phone: +45 60 84 85 00 Invite the tester to the party Global Scrum Gathering – Prague 2015
- 2. About me Allan Rennebo Jepen • Agile Transformation Coach • People enthusiast • Former IT-everything (almost) • Founder of Agile Copenhagen • Senior Partner and Founder of Coregile • Have a bunch of badges ☺
- 3. Who are you? • How Scrum mature is your organization? • How extensive is your personal Scrum experience? • What is your current role?
- 4. What are your biggest frustrations?
- 5. My promises to you • You will get practical inspiration on how you can include the tester - starting Monday morning. • You will be able to help eliminate the need for "Quality Control". • You will be able to turn the battle between developers and testers into a collaborative process.
- 6. Let’s get started With a tour in the real world
- 7. Production line mentality • Testing is always down prioritized (it comes last) • Most solutions are inferior (if not completely useless) Result • Talk to the sponsors • Analyze what you need to build (User Requirement Specification) • Create solution design • Build the solution • Test it • Go Live Theflow
- 8. • There is very little room for the team to navigate • Developers don’t take responsibility for quality • The solution is never in a stable state • Tests only verify the requirements – not that the needs are met • Software is created as an iterative process • Define accept criteria for all requirements in great detail • Design test cases as part of the User Story definition • Developers build the solution according to specification • Testers verify the solution after the Sprint is completed ResultTheflow Iterative production line
- 9. Scrum (with waterfall elements) • Testers are always bored in the beginning of a Sprint • Towards the end of a Sprint the testers are overloaded • The Sprint ends before all bugs are corrected • You get a tale of corrections that has an impact on future sprints • Create software iteratively • User accept criteria is defined for each User Story • Developers evolve the solution as a creative agile team • Testers verify the solution when developers have built it ResultTheflow
- 10. A different world How do we get there?
- 11. Pop Quiz • Who do you consider your primary stakeholders? • What does it take to be done in your team? • Why do you perform testing?
- 12. A Imagine you are buying a new car
- 13. Are you happy?and this is what you get delivered
- 14. Use of the Scrum board • Get stuff done (and not just coded) • Limit the work in progress
- 15. Stage 1: Adjust the flow Developers picks a task Developers explains the solution to tester Tester validates and provide feedback Developers and tester agrees Developers implements while tester prepares Tester verifies the implementation Tester and developer updates the board together
- 16. Stage 2: The tester doesn’t test How does that satisfy the need of the customer? Have you considered [Problem statement] ? What would happen if someone was to [Unexpected behaviour] ?
- 17. Wrap it up
- 18. Sprint Review • Starting Monday morning (or maybe even Thursday): • Make the tester as a central part of the team collaboration by making the test process part of the development flow (If you don’t have limits on Work in Progress, it will help you to introduce them • Eliminate the need for "Quality Control“: • By reducing risk! When the tester is a natural part of the development flow, you have addressed the issues in real time. (You are not able to “repair the car while driving”) • Enable collaboration between developers and testers: • I hope that part is obvious ☺
- 20. Contact information Email: allan@coreagile.eu Twitter: @rennebo Phone: +45 60 84 85 00 Invite the tester to the party Global Scrum Gathering – Prague 2015