Plan do-check-act
•Download as PPTX, PDF•
1 like•395 views
This 9 step process for continuous improvement begins with defining a problem, analyzing the current situation and root causes, assessing the impact, developing and implementing solutions, monitoring progress, evaluating effectiveness, and institutionalizing improvements by either making them permanent or identifying a new problem to address.
Report
Share
Report
Share
Recommended
2 anton muzhailo - formal test process improvement. how to invest to the te...
Anton muzhailo - formal test process improvement. how to invest to the test process improvement and win
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.
Dirk Van Dael - Test Accounting - EuroSTAR 2010
EuroSTAR Software Testing Conference 2010 presentation on Test Accounting by Dirk Van Dael. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
AiTi Education Software Testing Session 01 b
This document discusses key fundamentals of software testing. It explains why testing is necessary to build confidence and find faults. It covers the testing process, including re-testing fixes and regression testing to check for unintended effects of changes. The document stresses predicting expected results in advance and prioritizing tests to focus on the most important and riskiest areas given time constraints. Independence in testing and managing relationships with developers is also addressed.
Project Management Process overview
The project management process involves entering a phase or starting a project, initiating planning processes, executing processes while monitoring and controlling, and closing processes before exiting the phase or ending the project. Monitoring and controlling occurs throughout all phases of planning, executing, and closing processes.
ЄРМЕК КАДИРБАЄВ & АЛЕКС РИБКІН «How we train QAEs to join automation» Online ...
Online QADay 2021 #2
ЄРМЕК КАДИРБАЄВ & АЛЕКС РИБКІН
«How we train QAEs to join automation»
telegram: wwww.t.me/goqameetup
fb: www.fb.com/goqaevent
fb: www.fb.com/qaday.org
linkedin: https://www.linkedin.com/company/goqa/
Сайт: www.qaday.org
Overview of test process improvement frameworks
This document provides an overview of several test process improvement frameworks:
- The Test Maturity Model (TMM) uses five staged levels to measure test process maturity and suit regulatory environments.
- Test Process Improvement (TPI) allows for asynchronous improvements across four process cornerstones and twenty processes at four levels.
- Critical Testing Processes (CTP) focuses on continuously improving critical, high-impact testing processes.
- The Systematic Test and Evaluation Process (STEP) assesses planning, implementation, and measurement of testing through qualitative and quantitative metrics.
МАРІЯ ДУБИЦЬКА «Війна за тестову документацію на проекті» Online QADay 2021 #2
Online QADay 2021 #2
МАРІЯ ДУБИЦЬКА
«Війна за тестову документацію на проекті»
telegram: wwww.t.me/goqameetup
fb: www.fb.com/goqaevent
fb: www.fb.com/qaday.org
linkedin: https://www.linkedin.com/company/goqa/
Сайт: www.qaday.org
Recommended
2 anton muzhailo - formal test process improvement. how to invest to the te...
Anton muzhailo - formal test process improvement. how to invest to the test process improvement and win
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.
Dirk Van Dael - Test Accounting - EuroSTAR 2010
EuroSTAR Software Testing Conference 2010 presentation on Test Accounting by Dirk Van Dael. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
AiTi Education Software Testing Session 01 b
This document discusses key fundamentals of software testing. It explains why testing is necessary to build confidence and find faults. It covers the testing process, including re-testing fixes and regression testing to check for unintended effects of changes. The document stresses predicting expected results in advance and prioritizing tests to focus on the most important and riskiest areas given time constraints. Independence in testing and managing relationships with developers is also addressed.
Project Management Process overview
The project management process involves entering a phase or starting a project, initiating planning processes, executing processes while monitoring and controlling, and closing processes before exiting the phase or ending the project. Monitoring and controlling occurs throughout all phases of planning, executing, and closing processes.
ЄРМЕК КАДИРБАЄВ & АЛЕКС РИБКІН «How we train QAEs to join automation» Online ...
Online QADay 2021 #2
ЄРМЕК КАДИРБАЄВ & АЛЕКС РИБКІН
«How we train QAEs to join automation»
telegram: wwww.t.me/goqameetup
fb: www.fb.com/goqaevent
fb: www.fb.com/qaday.org
linkedin: https://www.linkedin.com/company/goqa/
Сайт: www.qaday.org
Overview of test process improvement frameworks
This document provides an overview of several test process improvement frameworks:
- The Test Maturity Model (TMM) uses five staged levels to measure test process maturity and suit regulatory environments.
- Test Process Improvement (TPI) allows for asynchronous improvements across four process cornerstones and twenty processes at four levels.
- Critical Testing Processes (CTP) focuses on continuously improving critical, high-impact testing processes.
- The Systematic Test and Evaluation Process (STEP) assesses planning, implementation, and measurement of testing through qualitative and quantitative metrics.
МАРІЯ ДУБИЦЬКА «Війна за тестову документацію на проекті» Online QADay 2021 #2
Online QADay 2021 #2
МАРІЯ ДУБИЦЬКА
«Війна за тестову документацію на проекті»
telegram: wwww.t.me/goqameetup
fb: www.fb.com/goqaevent
fb: www.fb.com/qaday.org
linkedin: https://www.linkedin.com/company/goqa/
Сайт: www.qaday.org
EuroSTAR webinar: creating Agile Test Strategies for larger Enterprises
Many organisations are reducing their test managers and Test Competence Centres. Quality is embedded in development. Testing is responsibility of the team. Still testing is on the rebound. In bigger projects and in enterprises an effective test strategy is vital to ensure that the team does the right testing, we focus on integration and we have insight in inter- team dependencies. In this webinar, Derk-Jan will share his experiences as an overall test manager in various projects and define some key ingredients of an Agile Test Strategy.
Testing fundamentals in a changing world (annotated slides)
Slides of my September SIGIST Keynote.
Description:
With the fast adoption of agile the definition of testing and our test approach changes. When deploying daily, there is no room for manual testing and a test report.
It’s time to get back to our fundamentals. Why do we work the way we do, and what needs do organisations have?
In this Keynote, Derk-Jan de Grood will explore the fundamental assets of the test profession, so we can reshape or test approach and make it work in an Agile context.
Although the daily focus shifts from working in silo’s to collaboration, from execution to coaching, from preparing to doing, the test fundamentals remain in place. In our search we will distinguish unchanged artefacts that we’ll create for a different reason and goals that remain unchanged but will only be achieved if we take a different route.
But bear in mind, not every project is done by using agile methods. Therefore we’ll also explore what concepts
of agile testing can we use to improve our traditional projects.
By understanding what is changed and what not we can adopt our approach, guide our stakeholders and
colleagues in order to align testing with the company goals.
Three key points:
Both agile and traditional projects are changing – testing needs to align
We still need some of the same test fundamentals – but perhaps for a different reason
We still have some of the same test goals – but we’ need to achieve them in different ways.
zero defect
This document discusses the concept of zero defects in manufacturing. It begins with an introduction to zero defects as a stretch goal to have no defects rather than just reducing defects over time. It then discusses some examples of companies that have achieved low defect rates. Several tools for achieving zero defects are mentioned, including mistake-proofing, statistical process control, design of experiments, and poka-yoke systems. The document argues that achieving very high quality levels like 99.99% defect-free can provide significant financial benefits in terms of reduced rework costs and increased profitability and competitiveness. It concludes that a zero defects approach adds value for customers and the business.
Managing agile testing
-Agile development and Agile testing.
-The aim of test management in Agile projects
- Tips and ideas for successfully managing your Agile testing process.
full webinar recording:
https://www.practitest.com/qa-learningcenter/webinars/agile-test-management/
Test Process Improvement in Agile
Jeroen Mengerink presented on test process improvement in Agile environments. He discussed how current TPI models focus on testing and structure but may not apply well to Agile. He proposed maturity levels for Agile testing - forming, norming, and performing. The presentation provided an assessment model to evaluate key areas like teamwork, test management, and regression testing. It offered examples and recommendations for improving processes in an Agile way, focusing on people, the development process, and testing flexibly.
Agile testing
I see many company which calls them agile but not. You can not apply agile without agile testing mindset.
Software quality kpi
This document discusses key performance indicators (KPIs) for software quality. It provides information on different types of KPIs including process, input, output, leading, and lagging KPIs. The document also outlines steps for creating KPIs such as defining objectives, identifying key result areas and tasks, and determining methods to measure results. Common mistakes in setting KPIs like having too many metrics or ones that do not change over time are also mentioned. Finally, the document recommends that KPIs should be clearly linked to strategy and provide answers to important questions.
Zero Defects Through Lean six Sigma
The document summarizes a Lean-Sigma program called "Zero Defects Through Lean-Sigma" that aims to help companies achieve zero defects through quality improvement. The program uses Lean and Six Sigma tools and methodologies delivered over 4 waves totaling 15 days. It involves classroom training, practical quality improvement projects at participants' companies, and mentoring sessions to equip participants with the skills to eliminate defects using Lean-Sigma approaches. The program is presented as a fast track alternative to help companies achieve quality targets more quickly compared to traditional Lean and Six Sigma implementations.
StarWest 2012 - Agile Defect Management: Focus On Prevention
Efficient agile organizations focus on defect prevention rather than downstream defect discovery, because discovering defects during or after testing adds to development costs. Delaying discovery and repair of defects can make an agile team feel like they are operating in a mini-waterfall. Sharing his experience with Scrum/ Kanban teams, Leveraging the lean concept of limiting work in progress, David Jellison describes how grouping defects into two major categories—work-in-progress defects and escaping defects—reduces development costs and improves reliability in the field. Dave illustrates how to manage problem discovery early and minimize the existence of escaping defects. Treating escaping defects as the exception rather than the norm results in a much smaller defect backlog and increased customer satisfaction. This approach encourages increased collaboration between quality engineers and developers, and shifts the focus of team measures from defect counts to product delivery velocity and cycle time, with increased confidence in quality as the work is completed.
Introduction to Agile Dr Richard Guerrero_Wessex AHSN Learning Lab
This document discusses different project management approaches including traditional, agile, and extreme project management. It provides descriptions of each approach and examples of the types of projects that may use each approach. It also summarizes key aspects of agile project management including common agile methods like Scrum and how teams are structured in agile projects.
BugDay Bangkok 2009 Defect Management
The document discusses defect management processes. It defines defects, describes different types of defects and their severity. It outlines the key steps in a defect management process: testing for defects, logging defects found, investigating defects, prioritizing defect resolutions, correcting defects, and reporting resolved defects. Traceability from requirements to testing is important. Defect metrics can help improve processes by identifying where and how defects are introduced and resolved. Collaboration between developers, testers, and other roles is essential for effective defect management.
extreme programming
Extreme Programming (XP) is an agile software development methodology formulated in 1999. It embraces change and values simplicity, communication, feedback, and courage. XP practices include whole team involvement, short planning iterations, customer acceptance tests, small regular releases, test-driven pair programming, continuous integration and refactoring. The goal is sustainable development of high quality, evolving code through frequent feedback and collective code ownership. Critics argue XP is too programmer-focused and unrealistic for large projects.
PI5_InspectAdapt
The document summarizes a session focused on improving processes in the customer transaction domain. Participants brainstormed ideas and voted on themes to identify issues, then conducted a root cause analysis to discover connections. Actions were agreed upon to take ownership of activities like creating domain-level roadmaps, identifying current products and capabilities, analyzing overlaps to decrease complexity, and reviewing scrum team products to align them with roadmaps. Over 50 people participated in the session to provide feedback and discuss topics.
Bug first Zero Defect
How could the concept of Zero Defect improve the quality of the software that is developed and deployed to customer.
Creating Agile Test Strategies for Larger Enterprises
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/
Agile pitfalls
This document discusses testing perspectives and pitfalls related to agile methodologies. It begins by noting that while entire programs adopt agile, testing often still uses traditional approaches. It proposes an agile testing manifesto modeled after the original agile manifesto. Common pitfalls are then outlined, including only partially implementing agile, unrealistic expectations of automation, and abuse of agile principles. The document concludes by stating that great flexibility in agile requires great discipline to fully realize its benefits.
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.
Using the test process improvement models. Case study based on TPI Next model...
The document discusses using the TPI Next test process improvement model. It provides an overview of the TPI Next model, which evaluates test processes across 16 key areas and 4 maturity levels. It then presents a case study example of implementing TPI Next on a project. The case study involves evaluating the current test process maturity, identifying improvement priorities, creating a test process improvement plan, implementing improvements, and planning the next improvement cycle. While most improvements were successfully implemented, one faced resistance from management.
Overview of test process improvement framework
This document provides an overview of several test process improvement frameworks: Test Maturity Model (TMM), Test Process Improvement (TPI), Critical Testing Processes (CTP), and Systematic Test and Evaluation Process (STEP). TMM defines 5 maturity levels for testing processes. TPI focuses on 4 process cornerstones and allows incremental improvement. CTP identifies attributes of critical testing processes. STEP assesses test planning, implementation, and measurement with qualitative and quantitative metrics.
Agile planning and monitoring
How are planning and monitoring In Agile project are quite different from traditional? Let's check it out!
Abc presentasi(rev)
Dokumen ini membahas penerapan metode activity based costing pada perusahaan elektronik Northern Hi Tech Ltd untuk menganalisis biaya overhead dua jenis printer mereka. Metode ini mengalokasikan biaya overhead berdasarkan aktivitas yang dikonsumsi masing-masing produk, sehingga menghasilkan perbedaan alokasi biaya dan margin laba antara dua produk dibandingkan dengan metode tradisional.
Farahnaz individual task chapter 4-final
This document discusses frameworks for understanding interorganizational relationships and organizational environments. It describes how businesses, governments, and nonprofits come together across sectors to address large, complex problems. Organizations must balance both technical and institutional dimensions, and they struggle for existence by competing for resources within their environment while also needing to conform to environmental expectations and norms. Frameworks examined include resource dependence theory, where organizations form partnerships to become more competitive and share scarce resources.
More Related Content
What's hot
EuroSTAR webinar: creating Agile Test Strategies for larger Enterprises
Many organisations are reducing their test managers and Test Competence Centres. Quality is embedded in development. Testing is responsibility of the team. Still testing is on the rebound. In bigger projects and in enterprises an effective test strategy is vital to ensure that the team does the right testing, we focus on integration and we have insight in inter- team dependencies. In this webinar, Derk-Jan will share his experiences as an overall test manager in various projects and define some key ingredients of an Agile Test Strategy.
Testing fundamentals in a changing world (annotated slides)
Slides of my September SIGIST Keynote.
Description:
With the fast adoption of agile the definition of testing and our test approach changes. When deploying daily, there is no room for manual testing and a test report.
It’s time to get back to our fundamentals. Why do we work the way we do, and what needs do organisations have?
In this Keynote, Derk-Jan de Grood will explore the fundamental assets of the test profession, so we can reshape or test approach and make it work in an Agile context.
Although the daily focus shifts from working in silo’s to collaboration, from execution to coaching, from preparing to doing, the test fundamentals remain in place. In our search we will distinguish unchanged artefacts that we’ll create for a different reason and goals that remain unchanged but will only be achieved if we take a different route.
But bear in mind, not every project is done by using agile methods. Therefore we’ll also explore what concepts
of agile testing can we use to improve our traditional projects.
By understanding what is changed and what not we can adopt our approach, guide our stakeholders and
colleagues in order to align testing with the company goals.
Three key points:
Both agile and traditional projects are changing – testing needs to align
We still need some of the same test fundamentals – but perhaps for a different reason
We still have some of the same test goals – but we’ need to achieve them in different ways.
zero defect
This document discusses the concept of zero defects in manufacturing. It begins with an introduction to zero defects as a stretch goal to have no defects rather than just reducing defects over time. It then discusses some examples of companies that have achieved low defect rates. Several tools for achieving zero defects are mentioned, including mistake-proofing, statistical process control, design of experiments, and poka-yoke systems. The document argues that achieving very high quality levels like 99.99% defect-free can provide significant financial benefits in terms of reduced rework costs and increased profitability and competitiveness. It concludes that a zero defects approach adds value for customers and the business.
Managing agile testing
-Agile development and Agile testing.
-The aim of test management in Agile projects
- Tips and ideas for successfully managing your Agile testing process.
full webinar recording:
https://www.practitest.com/qa-learningcenter/webinars/agile-test-management/
Test Process Improvement in Agile
Jeroen Mengerink presented on test process improvement in Agile environments. He discussed how current TPI models focus on testing and structure but may not apply well to Agile. He proposed maturity levels for Agile testing - forming, norming, and performing. The presentation provided an assessment model to evaluate key areas like teamwork, test management, and regression testing. It offered examples and recommendations for improving processes in an Agile way, focusing on people, the development process, and testing flexibly.
Agile testing
I see many company which calls them agile but not. You can not apply agile without agile testing mindset.
Software quality kpi
This document discusses key performance indicators (KPIs) for software quality. It provides information on different types of KPIs including process, input, output, leading, and lagging KPIs. The document also outlines steps for creating KPIs such as defining objectives, identifying key result areas and tasks, and determining methods to measure results. Common mistakes in setting KPIs like having too many metrics or ones that do not change over time are also mentioned. Finally, the document recommends that KPIs should be clearly linked to strategy and provide answers to important questions.
Zero Defects Through Lean six Sigma
The document summarizes a Lean-Sigma program called "Zero Defects Through Lean-Sigma" that aims to help companies achieve zero defects through quality improvement. The program uses Lean and Six Sigma tools and methodologies delivered over 4 waves totaling 15 days. It involves classroom training, practical quality improvement projects at participants' companies, and mentoring sessions to equip participants with the skills to eliminate defects using Lean-Sigma approaches. The program is presented as a fast track alternative to help companies achieve quality targets more quickly compared to traditional Lean and Six Sigma implementations.
StarWest 2012 - Agile Defect Management: Focus On Prevention
Efficient agile organizations focus on defect prevention rather than downstream defect discovery, because discovering defects during or after testing adds to development costs. Delaying discovery and repair of defects can make an agile team feel like they are operating in a mini-waterfall. Sharing his experience with Scrum/ Kanban teams, Leveraging the lean concept of limiting work in progress, David Jellison describes how grouping defects into two major categories—work-in-progress defects and escaping defects—reduces development costs and improves reliability in the field. Dave illustrates how to manage problem discovery early and minimize the existence of escaping defects. Treating escaping defects as the exception rather than the norm results in a much smaller defect backlog and increased customer satisfaction. This approach encourages increased collaboration between quality engineers and developers, and shifts the focus of team measures from defect counts to product delivery velocity and cycle time, with increased confidence in quality as the work is completed.
Introduction to Agile Dr Richard Guerrero_Wessex AHSN Learning Lab
This document discusses different project management approaches including traditional, agile, and extreme project management. It provides descriptions of each approach and examples of the types of projects that may use each approach. It also summarizes key aspects of agile project management including common agile methods like Scrum and how teams are structured in agile projects.
BugDay Bangkok 2009 Defect Management
The document discusses defect management processes. It defines defects, describes different types of defects and their severity. It outlines the key steps in a defect management process: testing for defects, logging defects found, investigating defects, prioritizing defect resolutions, correcting defects, and reporting resolved defects. Traceability from requirements to testing is important. Defect metrics can help improve processes by identifying where and how defects are introduced and resolved. Collaboration between developers, testers, and other roles is essential for effective defect management.
extreme programming
Extreme Programming (XP) is an agile software development methodology formulated in 1999. It embraces change and values simplicity, communication, feedback, and courage. XP practices include whole team involvement, short planning iterations, customer acceptance tests, small regular releases, test-driven pair programming, continuous integration and refactoring. The goal is sustainable development of high quality, evolving code through frequent feedback and collective code ownership. Critics argue XP is too programmer-focused and unrealistic for large projects.
PI5_InspectAdapt
The document summarizes a session focused on improving processes in the customer transaction domain. Participants brainstormed ideas and voted on themes to identify issues, then conducted a root cause analysis to discover connections. Actions were agreed upon to take ownership of activities like creating domain-level roadmaps, identifying current products and capabilities, analyzing overlaps to decrease complexity, and reviewing scrum team products to align them with roadmaps. Over 50 people participated in the session to provide feedback and discuss topics.
Bug first Zero Defect
How could the concept of Zero Defect improve the quality of the software that is developed and deployed to customer.
Creating Agile Test Strategies for Larger Enterprises
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/
Agile pitfalls
This document discusses testing perspectives and pitfalls related to agile methodologies. It begins by noting that while entire programs adopt agile, testing often still uses traditional approaches. It proposes an agile testing manifesto modeled after the original agile manifesto. Common pitfalls are then outlined, including only partially implementing agile, unrealistic expectations of automation, and abuse of agile principles. The document concludes by stating that great flexibility in agile requires great discipline to fully realize its benefits.
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.
Using the test process improvement models. Case study based on TPI Next model...
The document discusses using the TPI Next test process improvement model. It provides an overview of the TPI Next model, which evaluates test processes across 16 key areas and 4 maturity levels. It then presents a case study example of implementing TPI Next on a project. The case study involves evaluating the current test process maturity, identifying improvement priorities, creating a test process improvement plan, implementing improvements, and planning the next improvement cycle. While most improvements were successfully implemented, one faced resistance from management.
Overview of test process improvement framework
This document provides an overview of several test process improvement frameworks: Test Maturity Model (TMM), Test Process Improvement (TPI), Critical Testing Processes (CTP), and Systematic Test and Evaluation Process (STEP). TMM defines 5 maturity levels for testing processes. TPI focuses on 4 process cornerstones and allows incremental improvement. CTP identifies attributes of critical testing processes. STEP assesses test planning, implementation, and measurement with qualitative and quantitative metrics.
Agile planning and monitoring
How are planning and monitoring In Agile project are quite different from traditional? Let's check it out!
What's hot (20)
EuroSTAR webinar: creating Agile Test Strategies for larger Enterprises
EuroSTAR webinar: creating Agile Test Strategies for larger Enterprises
Testing fundamentals in a changing world (annotated slides)
Testing fundamentals in a changing world (annotated slides)
StarWest 2012 - Agile Defect Management: Focus On Prevention
StarWest 2012 - Agile Defect Management: Focus On Prevention
Introduction to Agile Dr Richard Guerrero_Wessex AHSN Learning Lab
Introduction to Agile Dr Richard Guerrero_Wessex AHSN Learning Lab
Creating Agile Test Strategies for Larger Enterprises
Creating Agile Test Strategies for Larger Enterprises
Using the test process improvement models. Case study based on TPI Next model...
Using the test process improvement models. Case study based on TPI Next model...
Viewers also liked
Abc presentasi(rev)
Dokumen ini membahas penerapan metode activity based costing pada perusahaan elektronik Northern Hi Tech Ltd untuk menganalisis biaya overhead dua jenis printer mereka. Metode ini mengalokasikan biaya overhead berdasarkan aktivitas yang dikonsumsi masing-masing produk, sehingga menghasilkan perbedaan alokasi biaya dan margin laba antara dua produk dibandingkan dengan metode tradisional.
Farahnaz individual task chapter 4-final
This document discusses frameworks for understanding interorganizational relationships and organizational environments. It describes how businesses, governments, and nonprofits come together across sectors to address large, complex problems. Organizations must balance both technical and institutional dimensions, and they struggle for existence by competing for resources within their environment while also needing to conform to environmental expectations and norms. Frameworks examined include resource dependence theory, where organizations form partnerships to become more competitive and share scarce resources.
Management Human Resource
Dokumen tersebut membahas sejarah perkembangan serikat pekerja di Indonesia, mulai dari munculnya serikat pekerja pertama pada akhir abad ke-19 hingga berdirinya Serikat Pekerja Seluruh Indonesia sebagai satu-satunya serikat buruh yang diakui pemerintah pada tahun 1973. Dokumen ini juga menyinggung beberapa peristiwa penting yang mempengaruhi perkembangan serikat pekerja seperti pemogokan buruh pada tahun 1920
Mengapa berserikat
Serikat pekerja atau buruh adalah organisasi pekerja yang bertujuan untuk mewakili dan membela hak-hak pekerja. Serikat pekerja memiliki peran dalam negosiasi perjanjian kerja bersama, penyelesaian pemutusan hubungan kerja, dan mewakili anggotanya di tingkat lembaga maupun pengadilan. Struktur organisasi serikat pekerja dapat berbasis geografis atau industri, sementara administrasinya berlandaskan pada prinsip
Study: The Future of VR, AR and Self-Driving Cars
We asked LinkedIn members worldwide about their levels of interest in the latest wave of technology: whether they’re using wearables, and whether they intend to buy self-driving cars and VR headsets as they become available. We asked them too about their attitudes to technology and to the growing role of Artificial Intelligence (AI) in the devices that they use. The answers were fascinating – and in many cases, surprising.
This SlideShare explores the full results of this study, including detailed market-by-market breakdowns of intention levels for each technology – and how attitudes change with age, location and seniority level. If you’re marketing a tech brand – or planning to use VR and wearables to reach a professional audience – then these are insights you won’t want to miss.
Hype vs. Reality: The AI Explainer
Artificial intelligence (AI) is everywhere, promising self-driving cars, medical breakthroughs, and new ways of working. But how do you separate hype from reality? How can your company apply AI to solve real business problems?
Here’s what AI learnings your business should keep in mind for 2017.
Viewers also liked (7)
Tugas kelompok tod implementing change at national industrial product
Tugas kelompok tod implementing change at national industrial product
Plan do-check-act
- 1. Plan-Do-Check-Act It’s a (9) Steps Plan Not a (4) Step Plan!!! 1. Problem Statement 2. Current Analysis 3. Cause & Effect Analysis 4. Impact Assessment 5. Solution Development 6. Implementation Solution 7. Monitoring & Check 8. Evaluate Effectiveness 9. Institutionalize Improvements and or Cycle Back to Step (1)