EuroSTAR Software Testing Conference 2009 presentation on Help We Have a QA Problem! by Niels Malotaux. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Christian Bk Hansen - Agile on Huge Banking Mainframe Legacy Systems - EuroST...TEST Huddle
EuroSTAR Software Testing Conference 2011 presentation on Agile on Huge Banking Mainframe Legacy Systems by Christian Bk Hansen. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Gitte Ottosen - Agility and Process Maturity, Of Course They Mix!TEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Agility and Process Maturity, Of Course They Mix! by Gitte Ottosen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Isabel Evans - Quality In Use - EuroSTAR 2011TEST Huddle
EuroSTAR Software Testing Conference 2011 presentation on Quality In Use by Isabel Evans. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Kristian Fischer - Put Test in the Driver's SeatTEST Huddle
The document discusses how test managers are often seen as "black sheep" who raise issues without solutions and cause delays. It argues that test managers need to shift from a reactive to proactive role by getting involved early in projects, changing attitudes, and applying a test management dashboard to provide transparency and value. The dashboard would use KPIs and metrics to track testing progress, quality, risks, and deliver early warnings so test managers are seen as project victors rather than victims.
'How To Apply Lean Test Management' by Bob van de BurgtTEST Huddle
Cost reductions and the quest for more efficiency are more evident in today’s business world. It also follows that our testing processes will ultimately be affected. When test techniques and methods for structured testing are introduced, this results in improvements in the production of more consistent and predictable results.
Introducing a risk based approach to testing makes it easier for the business to determine to what extent testing is necessary and most efficient. The resulting Go/No- Go decision process may not be sufficient for all companies so other creative methods need to be investigated. Many management theories speak about “Lean” as being one of the solutions. One of the key steps in using “Lean” is the identification of which steps add value to the customer and which do not. This track will give you information to start using “Lean” within testing and more specifically within test management.
The presenter will also look at Lean Six Sigma as being one of the more popular theories that introduces the concept of “Lean” in combination with obtaining higher quality products. This subject will also be explained in combination with testing and test management. This track will focus on applying Lean Six Sigma techniques to test management processes using practical examples from customer cases. The audience can take home a practical “Lean Test Management” overview which they can apply in their own companies.
This track is especially of interest to business managers, IT managers, QA managers and test managers that are involved in improving the quality of test management processes.
EuroSTAR Software Testing Conference 2010 presentation on Testing "slow flows" Fast, Automated End-2-End Testing using interrupts by Dominic Maes. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Jelle Calsbeek - Stay Agile with Model Based Testing revisedTEST Huddle
EuroSTAR Software Testing Conference 2009 presentation on Evolution of New Feature Verification in 3G Networks by Michael Monaghan. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
David Hayman - The Future of Testing is in New ZealandTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on The Future of Testing is in New Zealand by David Hayman. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Christian Bk Hansen - Agile on Huge Banking Mainframe Legacy Systems - EuroST...TEST Huddle
EuroSTAR Software Testing Conference 2011 presentation on Agile on Huge Banking Mainframe Legacy Systems by Christian Bk Hansen. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Gitte Ottosen - Agility and Process Maturity, Of Course They Mix!TEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Agility and Process Maturity, Of Course They Mix! by Gitte Ottosen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Isabel Evans - Quality In Use - EuroSTAR 2011TEST Huddle
EuroSTAR Software Testing Conference 2011 presentation on Quality In Use by Isabel Evans. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Kristian Fischer - Put Test in the Driver's SeatTEST Huddle
The document discusses how test managers are often seen as "black sheep" who raise issues without solutions and cause delays. It argues that test managers need to shift from a reactive to proactive role by getting involved early in projects, changing attitudes, and applying a test management dashboard to provide transparency and value. The dashboard would use KPIs and metrics to track testing progress, quality, risks, and deliver early warnings so test managers are seen as project victors rather than victims.
'How To Apply Lean Test Management' by Bob van de BurgtTEST Huddle
Cost reductions and the quest for more efficiency are more evident in today’s business world. It also follows that our testing processes will ultimately be affected. When test techniques and methods for structured testing are introduced, this results in improvements in the production of more consistent and predictable results.
Introducing a risk based approach to testing makes it easier for the business to determine to what extent testing is necessary and most efficient. The resulting Go/No- Go decision process may not be sufficient for all companies so other creative methods need to be investigated. Many management theories speak about “Lean” as being one of the solutions. One of the key steps in using “Lean” is the identification of which steps add value to the customer and which do not. This track will give you information to start using “Lean” within testing and more specifically within test management.
The presenter will also look at Lean Six Sigma as being one of the more popular theories that introduces the concept of “Lean” in combination with obtaining higher quality products. This subject will also be explained in combination with testing and test management. This track will focus on applying Lean Six Sigma techniques to test management processes using practical examples from customer cases. The audience can take home a practical “Lean Test Management” overview which they can apply in their own companies.
This track is especially of interest to business managers, IT managers, QA managers and test managers that are involved in improving the quality of test management processes.
EuroSTAR Software Testing Conference 2010 presentation on Testing "slow flows" Fast, Automated End-2-End Testing using interrupts by Dominic Maes. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Jelle Calsbeek - Stay Agile with Model Based Testing revisedTEST Huddle
EuroSTAR Software Testing Conference 2009 presentation on Evolution of New Feature Verification in 3G Networks by Michael Monaghan. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
David Hayman - The Future of Testing is in New ZealandTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on The Future of Testing is in New Zealand by David Hayman. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Michael Snyman - Software Test Automation Success TEST Huddle
EuroSTAR Software Testing Conference 2009 presentation on Software Test Automation Success by Michael Snyman. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
'Houston We Have A Problem' by Rien van Vugt & Maurice SiteurTEST Huddle
Prevent the surprise, become a pro-active test manager. Too often projects suddenly seem to spin out of control. Challenges and risks keep stacking up and the defect count grows exponentially. At the same time, management can put pressure on you, asking when testing will be completed.
A surprise? Not really, defects only paint half the picture. The test effort, after all, is primarily determined by the number of tests that need to be completed. For an on the spot status of testing and accurate view on the quality and risks of the entire project we need to organize the test process to provide flexible, up-to-date metrics and trends on a daily basis. E.g. we need a view on baseline vs. actuals and ETC’s on test cases. Advanced metrics will provide answers on what needs to be done tomorrow to stay on track, the location and root cause of issues and who is required to take action. Also the test effort remaining for an acceptable product (or a specific risk level) can be estimated fairly accurately.
In addition early involvement and preparation in the development life cycle, performing test intakes rather than reviews, will help you bridge the gap between different development teams and allows you to verify consistency between business requirements, the integration model, functional specifications and technical specifications. It facilitates knowledge transfer and provides you with the “story” behind the specifications. This will help prevent structural issues in an early stage and avoid blocking issues during test execution.
This presentation combines daily test metrics and trends with test process dynamics and shows you how to become a “pro-active” test manager. Even better you can apply it tomorrow and take your test process to a distinct higher maturity level.
James Whittaker - Pursuing Quality-You Won't Get There - EuroSTAR 2011TEST Huddle
EuroSTAR Software Testing Conference 2011 presentation on Pursuing Quality-You Won't Get There by James Whittaker. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Michael Bolton - Two Futures of Software TestingTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Two Futures of Software Testing by Michael Bolton. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Geoff Thompson - Why Do We Bother With Test StrategiesTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Why Do We Bother With Test Strategies by Geoff Thompson. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
End users, and more precisely end users involved in acceptance testing decide whether a new application or system will go live or not. Therefore it is very important they are in the same pursuit of quality as the rest of the project. End users are no dedicated testers, although sometimes we expect them to be. Just by looking at their available time for testing, we already know they are not. The fact that they are not trained to be testers, doesn’t make it easier.
But are we really looking for dedicated testers here?
During this presentation, Erik will explain how you can involve end users in such a way that we optimize their added value during their testing activities. An error often made in projects is that end users are only involved during test execution. It’s by having them participate in the test process on regular, well selected moments that we can get the best out of acceptance testing.
By means of a case study, Erik points out these moments. To start with, the acceptance testers need to know the goal of their testing activities. Knowing that, the acceptance testers are already involved at the end of the analysis phase in order to help the writing and prioritisation of high level test scenarios together with setting up the entry criteria for starting the acceptance test phase. Consequently, the acceptance testers will get demos on a regular basis of the software already delivered. These demos deliver valuable information, both for the project team as for the end users.
And finally, after having assessed the test readiness of the system through system testing, the end users will execute their test cases closely monitored by the test coordinator. While executing the tests, it is up to the test coordinator to make sure the end users are always updated on the defects.
The presentation will provide the audience with practical advice, examples and templates on how to set up their acceptance testing in a flexible way without drowning in administrative tasks.
Dorothy Graham - Can The Past Tell Us The FutureTEST Huddle
This document outlines the agenda and objectives for a workshop on how the past can inform the future of testing. The workshop will have participants discuss testing trends from previous decades, what has changed and remained the same, and lessons learned. Groups will generate manifesto statements summarizing advice from the past that can help guide the future of testing. The agenda includes introduction, breakout group discussions on past testing experiences and predictions, and concluding with generated manifesto statements.
EuroSTAR Software Testing Conference 2010 presentation on Testing and Lean Principles by Beata Karpinska . See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Derk jan de Grood - ET, Best of Both WorldsTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on ET, Best of Both Worlds by Derk jan de Grood. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
The document discusses moving from a defect reporting approach in software testing to a defect prevention approach using lean principles. It notes that preventing defects from the beginning is far more effective than finding faults later. It asks questions about the current state of testing and defect handling to determine opportunities to focus more on prevention activities like exploratory testing earlier and removing the root causes of defects.
Fredrik Rydberg - Can Exploratory Testing Save Lives - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on Can Exploratory Testing Save Lives by Fredrik Rydberg. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Thomas Axen - Lean Kaizen Applied To Software Testing - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on Lean Kaizen Applied To Software Testing by Thomas Axen . See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Martin Koojj - Testers in the Board of DirectorsTEST Huddle
Martin Kooij discusses the evolution and future of software testing. He traces his experience in testing telecom equipment from the 1960s to present day. Testing has matured from a technical focus on defects to a more strategic, risk-based approach. Metrics now consider risks rather than just defects. Kooij believes that by 2018, testers will report directly to boards of directors on product risks translated into business risks. Testers will broaden their skills and take responsibility for cost-effective testing to estimate and mitigate risks. For testing to continue evolving, testers must be brave, independent, and politically skilled while focusing on business risks over personal agendas.
Peter Zimmerer - Establishing Testing Knowledge and Experience Sharing at Sie...TEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Establishing Testing Knowledge and Experience Sharing at Siemens by Peter Zimmerer. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Hans-Henrik Olesen - What to Automate and What not to AutomateTEST Huddle
EuroSTAR Software Testing Conference 2009 presentation on What to Automate and What not to Automate by Hans-Henrik Olesen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Eric Jimmink - The Specialized Testers of the FutureTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on The Specialized Testers of the Future by Eric Jimmink. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Mickiel Vroon - Test Environment, The Future Achilles’ HeelTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Test Environment, The Future Achilles’ Heel by Mickiel Vroon. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
'Customer Testing & Quality In Outsourced Development - A Story From An Insur...TEST Huddle
RSA Scandinavia implemented a new test model to standardize testing across outsourced development projects. The model uses a risk-based approach and V-model framework. It defines requirements for test planning, design, execution, reporting, and responsibilities between RSA and suppliers. The implementation involved communicating the new model, providing training, and integrating it into project and contracting processes. Today, the model is used for all projects and is helping to streamline quality monitoring, reporting, and knowledge sharing across the organization and its suppliers.
Darius Silingas - From Model Driven Testing to Test Driven ModellingTEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on From Model Driven Testing to Test Driven Modelling by Darius Silingas. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Henrik Andersson - Exploratory Testing Champions - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on Henrik Andersson by Exploratory Testing Champions. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
These slides quickly illustrate how you can successfully adopt Agile to improve your development efforts. In addition to discussing how and why teams are interested in Agile, it covers some of the challenges of adopting it and suggestions for ensuring success.
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.
Michael Snyman - Software Test Automation Success TEST Huddle
EuroSTAR Software Testing Conference 2009 presentation on Software Test Automation Success by Michael Snyman. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
'Houston We Have A Problem' by Rien van Vugt & Maurice SiteurTEST Huddle
Prevent the surprise, become a pro-active test manager. Too often projects suddenly seem to spin out of control. Challenges and risks keep stacking up and the defect count grows exponentially. At the same time, management can put pressure on you, asking when testing will be completed.
A surprise? Not really, defects only paint half the picture. The test effort, after all, is primarily determined by the number of tests that need to be completed. For an on the spot status of testing and accurate view on the quality and risks of the entire project we need to organize the test process to provide flexible, up-to-date metrics and trends on a daily basis. E.g. we need a view on baseline vs. actuals and ETC’s on test cases. Advanced metrics will provide answers on what needs to be done tomorrow to stay on track, the location and root cause of issues and who is required to take action. Also the test effort remaining for an acceptable product (or a specific risk level) can be estimated fairly accurately.
In addition early involvement and preparation in the development life cycle, performing test intakes rather than reviews, will help you bridge the gap between different development teams and allows you to verify consistency between business requirements, the integration model, functional specifications and technical specifications. It facilitates knowledge transfer and provides you with the “story” behind the specifications. This will help prevent structural issues in an early stage and avoid blocking issues during test execution.
This presentation combines daily test metrics and trends with test process dynamics and shows you how to become a “pro-active” test manager. Even better you can apply it tomorrow and take your test process to a distinct higher maturity level.
James Whittaker - Pursuing Quality-You Won't Get There - EuroSTAR 2011TEST Huddle
EuroSTAR Software Testing Conference 2011 presentation on Pursuing Quality-You Won't Get There by James Whittaker. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Michael Bolton - Two Futures of Software TestingTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Two Futures of Software Testing by Michael Bolton. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Geoff Thompson - Why Do We Bother With Test StrategiesTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Why Do We Bother With Test Strategies by Geoff Thompson. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
End users, and more precisely end users involved in acceptance testing decide whether a new application or system will go live or not. Therefore it is very important they are in the same pursuit of quality as the rest of the project. End users are no dedicated testers, although sometimes we expect them to be. Just by looking at their available time for testing, we already know they are not. The fact that they are not trained to be testers, doesn’t make it easier.
But are we really looking for dedicated testers here?
During this presentation, Erik will explain how you can involve end users in such a way that we optimize their added value during their testing activities. An error often made in projects is that end users are only involved during test execution. It’s by having them participate in the test process on regular, well selected moments that we can get the best out of acceptance testing.
By means of a case study, Erik points out these moments. To start with, the acceptance testers need to know the goal of their testing activities. Knowing that, the acceptance testers are already involved at the end of the analysis phase in order to help the writing and prioritisation of high level test scenarios together with setting up the entry criteria for starting the acceptance test phase. Consequently, the acceptance testers will get demos on a regular basis of the software already delivered. These demos deliver valuable information, both for the project team as for the end users.
And finally, after having assessed the test readiness of the system through system testing, the end users will execute their test cases closely monitored by the test coordinator. While executing the tests, it is up to the test coordinator to make sure the end users are always updated on the defects.
The presentation will provide the audience with practical advice, examples and templates on how to set up their acceptance testing in a flexible way without drowning in administrative tasks.
Dorothy Graham - Can The Past Tell Us The FutureTEST Huddle
This document outlines the agenda and objectives for a workshop on how the past can inform the future of testing. The workshop will have participants discuss testing trends from previous decades, what has changed and remained the same, and lessons learned. Groups will generate manifesto statements summarizing advice from the past that can help guide the future of testing. The agenda includes introduction, breakout group discussions on past testing experiences and predictions, and concluding with generated manifesto statements.
EuroSTAR Software Testing Conference 2010 presentation on Testing and Lean Principles by Beata Karpinska . See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Derk jan de Grood - ET, Best of Both WorldsTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on ET, Best of Both Worlds by Derk jan de Grood. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
The document discusses moving from a defect reporting approach in software testing to a defect prevention approach using lean principles. It notes that preventing defects from the beginning is far more effective than finding faults later. It asks questions about the current state of testing and defect handling to determine opportunities to focus more on prevention activities like exploratory testing earlier and removing the root causes of defects.
Fredrik Rydberg - Can Exploratory Testing Save Lives - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on Can Exploratory Testing Save Lives by Fredrik Rydberg. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Thomas Axen - Lean Kaizen Applied To Software Testing - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on Lean Kaizen Applied To Software Testing by Thomas Axen . See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Martin Koojj - Testers in the Board of DirectorsTEST Huddle
Martin Kooij discusses the evolution and future of software testing. He traces his experience in testing telecom equipment from the 1960s to present day. Testing has matured from a technical focus on defects to a more strategic, risk-based approach. Metrics now consider risks rather than just defects. Kooij believes that by 2018, testers will report directly to boards of directors on product risks translated into business risks. Testers will broaden their skills and take responsibility for cost-effective testing to estimate and mitigate risks. For testing to continue evolving, testers must be brave, independent, and politically skilled while focusing on business risks over personal agendas.
Peter Zimmerer - Establishing Testing Knowledge and Experience Sharing at Sie...TEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Establishing Testing Knowledge and Experience Sharing at Siemens by Peter Zimmerer. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Hans-Henrik Olesen - What to Automate and What not to AutomateTEST Huddle
EuroSTAR Software Testing Conference 2009 presentation on What to Automate and What not to Automate by Hans-Henrik Olesen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Eric Jimmink - The Specialized Testers of the FutureTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on The Specialized Testers of the Future by Eric Jimmink. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Mickiel Vroon - Test Environment, The Future Achilles’ HeelTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Test Environment, The Future Achilles’ Heel by Mickiel Vroon. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
'Customer Testing & Quality In Outsourced Development - A Story From An Insur...TEST Huddle
RSA Scandinavia implemented a new test model to standardize testing across outsourced development projects. The model uses a risk-based approach and V-model framework. It defines requirements for test planning, design, execution, reporting, and responsibilities between RSA and suppliers. The implementation involved communicating the new model, providing training, and integrating it into project and contracting processes. Today, the model is used for all projects and is helping to streamline quality monitoring, reporting, and knowledge sharing across the organization and its suppliers.
Darius Silingas - From Model Driven Testing to Test Driven ModellingTEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on From Model Driven Testing to Test Driven Modelling by Darius Silingas. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Henrik Andersson - Exploratory Testing Champions - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on Henrik Andersson by Exploratory Testing Champions. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
These slides quickly illustrate how you can successfully adopt Agile to improve your development efforts. In addition to discussing how and why teams are interested in Agile, it covers some of the challenges of adopting it and suggestions for ensuring success.
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.
This document summarizes the transition of a large software development team from a hybrid "Mini Waterfall-Scrum" approach to fully embracing Scrum practices. It outlines issues they encountered initially like accumulating technical debt and many bugs. They then prepared for changes, defined a "Definition of Done", formed cross-functional teams, increased testing, and reduced work-in-progress. This led to positive results like reduced bugs, the first bug-free user stories, stable bug fix times, decreased technical debt, and improved release cycles. The presentation concludes that taking risks to make incremental changes aligned with Agile principles can successfully improve outcomes.
- The document compares Agile and waterfall methodologies, noting that Agile prioritizes individuals, collaboration, and responding to change over comprehensive documentation and following a strict plan.
- It provides best practices for Agile development like avoiding over-planning, utilizing acceptance criteria, and conducting retrospective meetings to improve.
- Tips are given for Spring-based product development like using Maven and best Java features while avoiding vendor lock-in, as well as for recovering investment costs through prioritizing features by business value and ROI.
In Agile Development, Testing is meant to be a part of the development process, right along with coding, but many “Agile Teams” are missing this vital component and experiencing degregated quality. In this presentation, we will discuss how to integrate Agile Testing in Kanban processes by discussing the following:
• Introduction to Agile and Lean
• How testers add value to cross-functional Agile Development Teams
• How testers participate in Agile ceremonies
• How to test in an Agile Environment
• The Four Environments (Dev, Test, Stage, Production)
• The types of testing that occurs in each environmen
Anton Muzhailo - Practical Test Process Improvement using ISTQBIevgenii Katsan
Here are a few potential questions from the document:
- What is the true value of ISTQB certifications beyond just checking a box for management? How can the knowledge be applied practically?
- How can metrics be designed and used effectively to assess quality and test coverage in an agile environment? What are some examples of valid and invalid metrics?
- What artifacts or information are useful to include in a test plan even for agile teams using tools like JIRA? How can a test plan provide value beyond just additional paperwork?
- What techniques can be used to effectively estimate defect severity when multiple testers with different perspectives are involved? How can consistency be achieved?
- How can root cause analysis be applied
Євген Лабунський: Agile in Enterprise. How do we do itLviv Startup Club
The document discusses how to implement agile practices in an enterprise setting. It describes using a combination of Scrum, XP techniques, lean practices, and traditional project management adapted to the enterprise context called "Adaptive". Key aspects include architectural planning, risk management, integration testing, continuous delivery, and working with complex requirements and stakeholder needs across multiple releases. The goal is to deliver working software in short iterations while managing the increased complexity of enterprise projects.
The document discusses the transformation of TomTom's engineering organization from a traditional waterfall process to scaled agile. It describes the initial context as having functional silos, resource managers owning engineers, long project timelines, lack of accountability, and decreasing quality. The key changes made were adopting SAFe, reorganizing into agile release trains, implementing requirements modeling, using Rally for planning and reporting, and adding continuous integration testing. The results included more reliable and predictable releases, faster feedback, improved transparency, and teams establishing better ways of working.
Tilt does not currently employ any quality engineers. How can we deliver quality software? Over the last year the organization has gone from terrifying deploys (followed by
When Management Asks You: “Do You Accept Agile as Your Lord and Savior?” - Ci...admford
Updated version of my original Cyphercon talk. With more useful information regarding how to enact change and better visual representation of certain concepts. This talk was given at CircleCityCon 10 in 2023
XBOSoft runs through the Top 10 Agile Metrics revealing the most fundamental data points Agile methodology requires to work effectively, and will put you on the highly targeted path to successful implementation of your Agile processes.
XBOSoft and Go2Group run through the top data points you should be measuring in your Agile Workflow. We’ll show you what to track, when and how often, and most importantly – why. Many believe that metrics are useless, but unless you measure, how can you systematically improve or know how you are doing? And with velocity as an overarching objective in agile, you should be tracking other things so that you know what else you could be impacting by going faster. But, with all the metrics so readily available to us today, how do we filter through to the most meaningful?
This document discusses implementing team wide testing to improve quality and reduce bugs. It describes current problems like developers feeling pressure to deliver code quickly without proper testing. This leads to bugs found later by testers, wasting time on rework. The team analyzed root causes like lack of test automation and testers. They decided to break down silos between developers and testers. The new process involves test-driven development, continuous testing, and demos at quality gates. While not all user stories were completed, the delivered stories had no bugs found by clients, showing the new process improved quality.
From Waterfall to Weekly Releases: A Case Study in using Evo and Kanban (2004...Tathagat Varma
The document describes how a company transitioned from a waterfall development process to a more agile process using evolutionary project management (Evo) and Kanban principles. They created a dedicated customer sustaining team using a cumulative hot fix process and weekly builds. This improved collaboration, reduced bugs and issues, increased customer satisfaction, and motivated the development team. The new process aligned well with Kanban principles of visualizing and limiting work in progress to improve flow.
The document summarizes key aspects of Scrum in 10 slides. It outlines the 5 Scrum values of commitment, focus, openness, respect and courage. It then describes the roles of the Product Owner who manages the product backlog and maximizes ROI, the Scrum Master who facilitates Scrum events and removes impediments, and the self-organizing Scrum Team. It also summarizes the product backlog, sprint goal, daily scrum meeting, sprint review, sprint retrospective and the process of continuous improvement in Scrum.
Shift left, shift right the testing swing.
This deck shows the testing framework we use today in our agile & Devops team. We do Behavior Driven Development (Shift left) and test in production as well (shift right).
The quest of one-piece-flow in IT by Pierre Masai, Toyota Motor EuropeInstitut Lean France
The document discusses Toyota's approach to one piece flow and problem solving. It describes how Toyota implements one piece flow throughout the entire business process improvement cycle and values delivering benefits in small, testable pieces. Toyota also takes a three-level approach to problem solving to thoroughly investigate issues, set challenging targets, and implement countermeasures to continuously improve.
The document discusses how a PMO can support agile development teams. It outlines that while agile teams focus on rapid delivery and value over documentation, the PMO can still play an important role by handling administrative tasks, coordinating resources across teams, and reporting at a high level to remove burdens from individual teams. The PMO monitors progress through daily standups and sprint reviews rather than static reports, and tracks issues and dependencies across teams rather than detailed logs. This allows agile teams to operate with flexibility while the PMO provides oversight at a program level.
This document provides an overview of Scrum fundamentals including its values, principles, pillars, ceremonies, artifacts, and processes. It also introduces Large Scale Scrum (LeSS), which applies Scrum principles across larger organizations. The key Scrum ceremonies are Sprint Planning, Daily Standup, Sprint Review, and Sprint Retrospective. The main Scrum artifacts are the Product Backlog, Sprint Backlog, and shippable product increment. LeSS utilizes similar ceremonies but includes representatives from multiple teams to coordinate work across the entire system.
Agile development methods can help improve the success rate of IT projects. Studies show that only 40% of traditional projects meet goals, while 65-80% of projects fail or run over budget and schedule. Requirements gaps, lack of collaboration, and poor communication are common causes of failure. Agile development addresses these issues through iterative development, frequent delivery of working software, and collaboration between developers and customers. Benefits of Agile include increased engagement, transparency, flexibility to adapt to changes, and a focus on delivering business value. Frameworks like Scrum, Kanban, and Scrumban structure the Agile process.
Similar to Niels Malotaux - Help We Have a QA Problem! (20)
Why We Need Diversity in Testing- AccentureTEST Huddle
In this webinar Rasa (Testing capability lead for Denmark) and Matthias (EALA Testing capability lead) will share some of their own experiences why diversity matters, give insights into how Accenture as a global firm is promoting diversity and how we are in the process of changing our attitudes and processes to make all of this sustainable
Keys to continuous testing for faster delivery euro star webinar TEST Huddle
Your business needs to deliver faster. To accommodate, Development needs to introduce fewer changes but in a much more frequent cadence. This creates a challenge for test teams to keep up with the rapid pace of change without compromising on quality. Automation is paramount to the success or failure of Continuous Delivery, and Continuous Testing enables early and frequent quality feedback throughout the CI/CD pipeline.
In this webinar, Eran & Ayal will explore how to implement Continuous Testing to ensure high quality releases in a Continuous Delivery environment; including what to test and when to automate new functionality in order to optimize your efforts.
Why you Shouldnt Automated But You Will Anyway TEST Huddle
The document discusses automation in software testing. It begins by outlining common claims made about the benefits of automation, such as saving time and improving quality, but argues that these claims often don't hold true. Automation does not inherently save time, guarantee quality, or reduce resources needed. It also does not always save money when development, maintenance, and infrastructure costs are considered. The document provides a formula for determining when automation is worthwhile based on how many times a test case would need to be rerun manually. It concludes by acknowledging that, despite these drawbacks, organizations will still automate testing because it is exciting, managers demand it, and it benefits careers.
In this webinar Carsten will explore the role of the tester in a Scrum team. He will examine where the tester play an important role in Scrum and how you can contribute to a teams performance.
Leveraging Visual Testing with Your Functional TestsTEST Huddle
Designing and implementing (or selecting) the right automation strategy, for functional testing, with visual testing, can help your project with greater test coverage while improving test scalability
Big Data: The Magic to Attain New HeightsTEST Huddle
This document discusses how big data and data science can be used to attain new heights, likening it to magic. It provides an overview of Ken Johnston's background and experiences in data science. It then discusses six keys to a "big" magic show with big data: trying multiple times, addressing issues with over-counting, experimentation techniques like A/B testing, infrastructure for big data, tools and skills, and security, privacy and fraud protection. The document emphasizes the importance of an assistant to help the data scientist or data engineer with various tasks.
This talk suggests how we might make sense of the tools landscape of the near future, where the pressure to modernise processes and automate is greatest, and what a new test process supported by tools might look like.
Takeaways:
- We need to take machine learning in testing seriously, but it won’t be taking our jobs just yet
- We don’t need more test automation tools; today we need tools that capture tester knowledge
- Tools that that learn and think can’t work for testers until we solve the knowledge capture challenge.
View On-Demand Webinar: https://youtu.be/EzyUdJFuzlE
The document discusses Test Driven Development (TDD) and Test Driven Design. It uses the analogy of building a lightsaber and later a Death Star to illustrate the TDD process and benefits. Some benefits mentioned are better test coverage, less debugging, and better design. The document provides tips for practicing TDD including planning ahead, defining boundaries, taking small steps to pass each test, and maintaining discipline. It emphasizes trying TDD in a team and considering Behavior Driven Development (BDD) as well.
Scaling Agile with LeSS (Large Scale Scrum)TEST Huddle
In this webinar, Elad will cover the principles that the #LeSS framework has to offer in order to enable bug organisations to become agile.
View webinar recording - https://huddle.eurostarsoftwaretesting.com/resource/agile-testing/scaling-agile-less-large-scale-scrum/
Creating Agile Test Strategies for Larger EnterprisesTEST Huddle
Having difficulty creating an agile test strategy for your company? Let Testing Excellence Award winner, Derk-Jan de Grood, show you how it’s done
View webinar recording here - http://huddle.eurostarsoftwaretesting.com/resource/agile-testing/creating-agile-test-strategies-larger-enterprises/
3 key takeaways
- Do you know the meaning of your organisation, system, product?
- Can you deliver the important risks right away?
- How can you communicate about the (process and product) risks your dealing with?
View Webinar recording: https://huddle.eurostarsoftwaretesting.com/resource/test-management/is-there-a-risk/
Are Your Tests Well-Travelled? Thoughts About Test CoverageTEST Huddle
This document summarizes a presentation on test coverage given by Dorothy Graham. It uses an analogy of travel to different locations to explain what test coverage means and some caveats. Coverage refers to the relationship between tests and the parts of a system being tested, but achieving 100% coverage does not mean everything is tested. There are four caveats discussed: coverage only measures one aspect of testing, a single test can achieve coverage, coverage does not indicate quality, and it only applies to the existing system not missing pieces. The key recommendation is to ask "coverage of what?" when the term is used rather than assuming more coverage is always better.
Growing a Company Test Community: Roles and Paths for TestersTEST Huddle
Over the past three years, our company’s test team has grown from three lonesome testers to a community of nine – with more planned. Since we don’t see testers as “click monkeys”, but as valuable and integrated project members who bring a specific skill set to the table, it’s important for us to choose testers well and to train them in various areas so that they can contribute, grow and see their own career path within testing.
To structure to our internal tester training program, we have been developing role descriptions, education paths and career options for our testers, which I’d like to share with you in this webinar.
View webinar - https://huddle.eurostarsoftwaretesting.com/resource/webinar/growing-company-test-community-roles-paths-testers/
It’s the same argument again and again. One side says “team members should all be able to do everything, and the programmers should do their testing and all testers should be writing code”. The other side says “No, that can’t possibly work – programmers don’t know how to test, they don’t have the right mindset”. And on and on it goes.
http://huddle.eurostarsoftwaretesting.com/resource/webinar/need-testers-agile-teams/
In this webinar, Dave Haeffner (Elemental Selenium, USA) discusses how to:
- Build an integrated feedback loop to automate test runs and find issues fast
- Setup your own infrastructure or connect to a cloud provider
-Dramatically improve test times with parallelization
https://huddle.eurostarsoftwaretesting.com/resource/webinar/use-selenium-successfully/
Testers & Teams on the Agile Fluency™ Journey TEST Huddle
The document discusses the Agile Fluency model, which aims to help teams and testers improve their agile skills and practices over time. It describes a pathway with increasing levels of fluency that provide more benefits, including delivering value, optimizing value, and innovating. Reaching higher levels requires investments in training, coaching, and changing team structures and roles. The model can help organizations determine what level of fluency they need and what investments are required for testing teams to operate at that level.
Practical Test Strategy Using HeuristicsTEST Huddle
Key Takeaways
- See what makes a good test strategy
- Learn how to make a thorough test strategy
- Identify what is the ‘Heuristic Test Strategy Model’ is
- Develop a solid test strategy that fits fast
- Discover how diversification can help you to create a test strategy
Key Takeaways:
- A diagramming method that helps discuss roles
- A one page analysis heuristic for roles
- Why roles matter on projects
https://huddle.eurostarsoftwaretesting.com/resource/people-skills/thinking-through-your-role/
Key Takeaways:
- What will this release contain
- What impact will it have on your test runs
- How can you preserve your existing investment in tests using the Selenium WebDriver APIs, and your even older RC tests
- Looking forward, when will the W3C spec be complete
- What can we expect from Selenium 4
https://huddle.eurostarsoftwaretesting.com/
Takashi Kobayashi and Hironori Washizaki, "SWEBOK Guide and Future of SE Education," First International Symposium on the Future of Software Engineering (FUSE), June 3-6, 2024, Okinawa, Japan
Flutter is a popular open source, cross-platform framework developed by Google. In this webinar we'll explore Flutter and its architecture, delve into the Flutter Embedder and Flutter’s Dart language, discover how to leverage Flutter for embedded device development, learn about Automotive Grade Linux (AGL) and its consortium and understand the rationale behind AGL's choice of Flutter for next-gen IVI systems. Don’t miss this opportunity to discover whether Flutter is right for your project.
What is Master Data Management by PiLog Groupaymanquadri279
PiLog Group's Master Data Record Manager (MDRM) is a sophisticated enterprise solution designed to ensure data accuracy, consistency, and governance across various business functions. MDRM integrates advanced data management technologies to cleanse, classify, and standardize master data, thereby enhancing data quality and operational efficiency.
GraphSummit Paris - The art of the possible with Graph TechnologyNeo4j
Sudhir Hasbe, Chief Product Officer, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Atelier - Innover avec l’IA Générative et les graphes de connaissancesNeo4j
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Allez au-delà du battage médiatique autour de l’IA et découvrez des techniques pratiques pour utiliser l’IA de manière responsable à travers les données de votre organisation. Explorez comment utiliser les graphes de connaissances pour augmenter la précision, la transparence et la capacité d’explication dans les systèmes d’IA générative. Vous partirez avec une expérience pratique combinant les relations entre les données et les LLM pour apporter du contexte spécifique à votre domaine et améliorer votre raisonnement.
Amenez votre ordinateur portable et nous vous guiderons sur la mise en place de votre propre pile d’IA générative, en vous fournissant des exemples pratiques et codés pour démarrer en quelques minutes.
UI5con 2024 - Keynote: Latest News about UI5 and it’s EcosystemPeter Muessig
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
Graspan: A Big Data System for Big Code AnalysisAftab Hussain
We built a disk-based parallel graph system, Graspan, that uses a novel edge-pair centric computation model to compute dynamic transitive closures on very large program graphs.
We implement context-sensitive pointer/alias and dataflow analyses on Graspan. An evaluation of these analyses on large codebases such as Linux shows that their Graspan implementations scale to millions of lines of code and are much simpler than their original implementations.
These analyses were used to augment the existing checkers; these augmented checkers found 132 new NULL pointer bugs and 1308 unnecessary NULL tests in Linux 4.4.0-rc5, PostgreSQL 8.3.9, and Apache httpd 2.2.18.
- Accepted in ASPLOS ‘17, Xi’an, China.
- Featured in the tutorial, Systemized Program Analyses: A Big Data Perspective on Static Analysis Scalability, ASPLOS ‘17.
- Invited for presentation at SoCal PLS ‘16.
- Invited for poster presentation at PLDI SRC ‘16.
What is Augmented Reality Image Trackingpavan998932
Augmented Reality (AR) Image Tracking is a technology that enables AR applications to recognize and track images in the real world, overlaying digital content onto them. This enhances the user's interaction with their environment by providing additional information and interactive elements directly tied to physical images.
Unveiling the Advantages of Agile Software Development.pdfbrainerhub1
Learn about Agile Software Development's advantages. Simplify your workflow to spur quicker innovation. Jump right in! We have also discussed the advantages.
Do you want Software for your Business? Visit Deuglo
Deuglo has top Software Developers in India. They are experts in software development and help design and create custom Software solutions.
Deuglo follows seven steps methods for delivering their services to their customers. They called it the Software development life cycle process (SDLC).
Requirement — Collecting the Requirements is the first Phase in the SSLC process.
Feasibility Study — after completing the requirement process they move to the design phase.
Design — in this phase, they start designing the software.
Coding — when designing is completed, the developers start coding for the software.
Testing — in this phase when the coding of the software is done the testing team will start testing.
Installation — after completion of testing, the application opens to the live server and launches!
Maintenance — after completing the software development, customers start using the software.
Neo4j - Product Vision and Knowledge Graphs - GraphSummit ParisNeo4j
Dr. Jesús Barrasa, Head of Solutions Architecture for EMEA, Neo4j
Découvrez les dernières innovations de Neo4j, et notamment les dernières intégrations cloud et les améliorations produits qui font de Neo4j un choix essentiel pour les développeurs qui créent des applications avec des données interconnectées et de l’IA générative.
SOCRadar's Aviation Industry Q1 Incident Report is out now!
The aviation industry has always been a prime target for cybercriminals due to its critical infrastructure and high stakes. In the first quarter of 2024, the sector faced an alarming surge in cybersecurity threats, revealing its vulnerabilities and the relentless sophistication of cyber attackers.
SOCRadar’s Aviation Industry, Quarterly Incident Report, provides an in-depth analysis of these threats, detected and examined through our extensive monitoring of hacker forums, Telegram channels, and dark web platforms.
Neo4j - Product Vision and Knowledge Graphs - GraphSummit ParisNeo4j
Dr. Jesús Barrasa, Head of Solutions Architecture for EMEA, Neo4j
Découvrez les dernières innovations de Neo4j, et notamment les dernières intégrations cloud et les améliorations produits qui font de Neo4j un choix essentiel pour les développeurs qui créent des applications avec des données interconnectées et de l’IA générative.
Zoom is a comprehensive platform designed to connect individuals and teams efficiently. With its user-friendly interface and powerful features, Zoom has become a go-to solution for virtual communication and collaboration. It offers a range of tools, including virtual meetings, team chat, VoIP phone systems, online whiteboards, and AI companions, to streamline workflows and enhance productivity.
OpenMetadata Community Meeting - 5th June 2024OpenMetadata
The OpenMetadata Community Meeting was held on June 5th, 2024. In this meeting, we discussed about the data quality capabilities that are integrated with the Incident Manager, providing a complete solution to handle your data observability needs. Watch the end-to-end demo of the data quality features.
* How to run your own data quality framework
* What is the performance impact of running data quality frameworks
* How to run the test cases in your own ETL pipelines
* How the Incident Manager is integrated
* Get notified with alerts when test cases fail
Watch the meeting recording here - https://www.youtube.com/watch?v=UbNOje0kf6E
1. 1QA Problem 2009
Niels Malotaux
+31-30-228 88 68 niels@malotaux.nl www.malotaux.nl
Help ! We have aHelp ! We have a
QA Problem !QA Problem !
2. 2QA Problem 2009
We have a QA problem !
• Large stockpile of modules to test
(hardware, firmware, software)
• You shall do Full Regression Tests
• Full Regression Tests take about 15 days each
• Too few testers (“Should we hire more testers ?”)
• Senior Tester paralyzed
• Can we do something about this?
3. 3QA Problem 2009
The essential ingredient: the PDCA Cycle
(Shewhart Cycle - Deming Cycle - Plan-Do-Study-Act Cycle - Kaizen)
!
4. 4QA Problem 2009
Instead of complaining about a problem …
(Stuck in the Check-phase)
Let’s do something about it !
(Moving to the Act-phase)
5. 5QA Problem 2009
Objectifying and quantifying the problem
is a first step to the solution
Estim
17
8
14
11
9
17
4
1
1
1
3
1.1
3
0.1
18
106
Line Activity
1 Package 1
2 Package 2
3 Package 3
4 Package 4 (wait for feedback)
5 Package 5
6 Package 6
7 Package 7
8 Package 8.1
9 Package 8.2
10 Package 8.3
11 Package 8.4
12 Package 8.5
13 Package 8.6
14 Package 8.7
15 Package 8.8
totals
Customer Will be done
(now=22Feb)
HT
Chrt
BMC
McC?
Ast
?
Cli
Sev
?
Chrt 24 Feb
Chrt
Yet 28 Feb
Yet 24 Mar
Cli After 8.5 OK
Ast
Alter
native
Junior
tester
Devel
opers
2 17 4
5 10
7 5 4
3 5
3 10 10
1 3
1
1
1
1
1.1
3
0.1
18
47 32 36
6. 6QA Problem 2009
TimeLine
Selecting the priority order of customers to be served
• “We’ll have a solution at that date … Will you be ready for it ?”
Another customer could be more eagerly waiting
• Most promising customers
wk
9 10 11 12 13 14 15 16 17 13
delivery
cust a
delivery
cust b,c
delivery
cust a,d
start (all done)
7. 7QA Problem 2009
Result
• Tester empowered
• Done in 9 weeks
• So called “Full Regression Testing” was redesigned
• Customers systematically happy and amazed
• Kept up with development ever since
• Increased revenue
Recently:
• Tester promoted to product manager
• Still coaching successors how to plan
8. 8QA Problem 2009
• Evo (short for Evolutionary...) uses PDCA consistently
• Applying the PDCA-cycle
actively, deliberately, rapidly and frequently,
for Product, Project and Process, based on ROI and highest value
• Combining Planning, Requirements- and Risk-Management into
Result Management
• We know we are not perfect, but the customer shouldn’t be affected
• Evo is about delivering Real Stuff to Real Stakeholders
doing Real Things “Nothing beats the Real Thing”
• Projects seriously applying Evo, routinely conclude
successfully on time, or earlier
Evo
9. 9QA Problem 2009
Who is the customer of Testing and QA ?
• Deming:
• Quality comes not from testing, but from improvement of
the development process. Testing does not improve
quality, nor guarantee quality. It’s too late. The quality,
good or bad, is already in the product. You cannot test
quality into a product.
• Developers are the customer
• Testers help developers to become perfect
• Testing is a project to run alongside and synchronized
to the development project
• Therefore, it must be organised like any other project
10. 10QA Problem 2009
Universal Project Goal
• Providing the customer with
• what he needs
• at the time he needs it
• to be satisfied
• to be more successful than he was without it
• Constrained by (win - win)
• what the customer can afford
• what we mutually beneficially and satisfactorily can deliver
• in a reasonable period of time
11. 11QA Problem 2009
Evo Project Planning
Evolutionary Project
Management (Evo)
• Plan-Do-Check-Act
• The powerful ingredient for success
• Business Case
• Why we are going to improve what
• Requirements Engineering
• What we are going to improve and what not
• How much we will improve: quantification
• Architecture and Design
• Selecting the optimum compromise for the conflicting requirements
• Early Review & Inspection
• Measuring quality while doing, learning to prevent doing the wrong things
• Weekly TaskCycle
• Short term planning
• Optimizing estimation
• Promising what we can achieve
• Living up to our promises
• Bi-weekly DeliveryCycle
• Optimizing the requirements and checking the assumptions
• Soliciting feedback by delivering Real Results to eagerly waiting Stakeholders
• TimeLine
• Getting and keeping control of Time: Predicting the future
• Feeding program/portfolio/resource management
Zero
Defects
Attitude
12. 12QA Problem 2009
The aim of Testing
• Being done as soon as the development is done
• Well, almost
• Excuses, excuses, excuses
• The developers are always late
(Evo developers live up to their promises)
• The developers don’t take us seriously
(Evo developers ask testers for help)
• The developers don’t inject enough defects
(now testing becomes a challenge)
• Helping development to be successful
13. 13QA Problem 2009
TimeLine
• Cutting the work into chunks
• Estimating
• Adding up (averages the uncertainties !)
• Usually doesn’t fit in the available time
• Find strategies to solve the dilemma
• Select ‘optimum’ strategy
• Predict what will happen when
• Learn and repeat every week, keeping predictions up-to-date
• Allow Portfolio Management to manage rather than to game
14. 14QA Problem 2009
Predicting what will be done when
Calibr
factor
1.0
1.0
1.0
1.4
1.4
1.4
1.4
1.4
1.4
Calibr
still to
1
2
1
4.2
1.4
4.2
5.6
7.0
9.8
Ratio
real/es
1.0
1.2
3.0
3.5
1.0
Spent Still to
spend
2 0
5 1
3 0
3 2
4 1
Estim
2
5
1
2
5
3
1
3
4
5
7
Line Activity
1 Activity 1
2 Activity 2
3 Activity 3
4 Activity 4
5 Activity 5
6 Activity 6
7 Activity 7
8 Activity 8
↓ ↓
16 Activity 16
17 Activity 17
18 Activity 18
Date
done
30 Mar 2009
1 Apr 2009
2 Apr 2009
9 Apr 2009
10 Apr 2009
16 Apr 2009
2 Jun 2009
11 Jun 2009
25 Jun 2009
15. 15QA Problem 2009
What do we do if we see we won’t make it on time ?
If it doesn’t fit ... count backwards
Value Still to EarnEarned Value
16. 16QA Problem 2009
Deceptive options
• Hoping for the best (fatalistic)
• Going for it (macho)
• Working Overtime (fooling ourselves)
• Moving the deadline
• Parkinson’s Law
• Work expands to fill the time for its completion
• Student Syndrome
• Starting as late as possible, only when the pressure
of the FatalDate is really felt
17. 17QA Problem 2009
The Myth of the
Man-Month
1 2 3 4 5 6 87 9 10 11 12 13 14 15 16
1
2
3
4
5
6
8
7
9
10
11
12
13
14
intuition
people x time = constant
Man-Month Myth
reality
(Putnam)
project
duration
number of people
lower cost
shorter time
nine
mothers
area
Economic
optimum?
Brooks’ Law (1975)
Adding people
to a late project
makes it later
18. 18QA Problem 2009
Saving time
We don’t have enough time, but we can save time
without negatively affecting the Result !
• Efficiency in what (why, for whom) we do - doing the right things
• Not doing what later proves to be superfluous
• Efficiency in how we do it - doing things differently
• The product
• Using proper and most efficient solution,
instead of the solution we always used
• The project
• Doing the same in less time,
instead of immediately doing it the way we always did
• Continuous improvement and prevention processes
• Constantly learning doing things better
and overcoming bad tendencies
• Efficiency in when we do it - right time, in the right order
• TimeBoxing - much more efficient than FeatureBoxing
19. 19QA Problem 2009
More• www.malotaux.nl/Booklets
1 Evolutionary Project Management Methods (2001)
Issues to solve, and first experience with the Evo Planning approach
2 How Quality is Assured by Evolutionary Methods (2004)
After a lot more experience: rather mature Evo Planning process
3 Optimizing the Contribution of Testing to Project Success (2005)
How Testing fits in
3a Optimizing Quality Assurance for Better Results (2005)
Same as Booklet 3, but for non-software projects
4 Controlling Project Risk by Design (2006)
How the Evo approach solves Risk by Design (by process)
5 TimeLine: How to Get and Keep Control over Longer Periods of Time (2007)
Replaced by Booklet 7
6 Human Behavior in Projects (2008)
Human Bahavioural aspects of Projects
7 How to Achieve the Most Important Requirement (2008)
Planning of longer periods of time, what to do if you don’t have enough time
8 Help ! We have a QA Problem ! (2009)
The story of this presentation
• www.malotaux.nl/nrm/Insp
Inspection pages
What is Evo
Short for Evolutionary Development/Delivery/Project ManagementEvo is a label we use for successful methods to deliver Quality On Time. Until now all the successful methods have an Evolutionary aspect in them. So we use the Evolutionary label. In short: Evo.
Deliberately going through the PDCA cycle rapidly and frequently, for product, project and processPlan - Do - Check - Act cycle, also called the Shewhart cycle or Deming cycle. Do is what we normally do. Most of us Plan, more, or less. Usually we “have no time” for the Check and Act parts. We use this cycle on everything: the Product (what is really needed and possible within the budget), the Project (how to learn to do things better) and even the Process: what doesn’t work is discarded: no burocracy.
Continuously thinking what to do, in which order, to which level of detail for nowWhat we have done until this very moment cannot be changed any more. What we have, we have. What we haven’t, we haven’t. What we thought last week what we should do does not matter. Based on what we know NOW: What is the best to do NOW, in which order (priority!) to which level of detail for now, because if we do more detail than is necessary NOW, we will have wasted time if we later find out that we should have done something different.
Methods for efficiently and effectively running development projects, delivering Quality On TimeEvo projects deliver routinely Quality On Time.
Delivering what the user needs at the time he needs itThat is what pays our salary