The document discusses agile requirements and measuring quality in software projects. It introduces two models for estimating quality: a defect estimation model and a quality factor model. It also discusses measuring quality by looking at where defects are inserted into the design and code and where they are detected, with the goal of reducing fault slip through and improving customer satisfaction. Quality is influenced by management factors as well as the performance of design, testing and other project phases.
Controlling Project Performance using PDM - PSQT2005 - Ben LindersBen Linders
• A hands-on model for control of product and process quality.
• Support of release risk decisions based on defect data.
• ODC and Test Matrices applied in different test phases.
• Usage of feedback to analyze data and come to actions.
• Using project data for a business case for improvement.
Controlling Project Performance by Using a Defect Model - SEPG NA 2008 - Ben ...Ben Linders
Wouldn’t it be nice if you had more insight in product quality, during development? To estimate defects inserted in the product, and check how effective test is in capturing defects? We developed a model to measure defects from requirements to customer feedback after release. It is used to control projects (putting quality next to planning/budget), evaluate risks, and decide on release and support. Baseline data is used to measure and improve process performance.
Reaching Business Goals with Value Adding CMMI Assessments, Ben Linders, Euro...Ben Linders
This presentation will show how to apply the CMMI in a business focussed way, by doing frequent assessments. Goals are input to the planning of assessments, a matrix is used to assure both organisation and process area coverage, and the results of assessments integrate smoothly within operational targets of existing groups within the organisation.
Practical tools support the frequent assessments, and experience with the CMMI is used to optimize the assessment and improvement cycle, resulting in continuously improving the performance of the organisation towards its goals.
Controlling Project during Development with a Defect Model, Ben Linders, ICST...Ben Linders
Wouldn’t it be nice if you could have more insight into the quality of a product, while it is developed, and not afterwards? Would you like to be able to estimate how many defects are inserted in the product in a certain phase, and how effective a (test) phase is in capturing these defects? To optimize your test phases regarding focus and effort in relation to how many defects they will find? This presentation will show a simple but very effective model that makes it possible: The Project Defect Model.
The aim of the Project Defect Model is to track product quality, take corrective actions and reduce quality risks. To get more insight into the quality of the product during development, it is needed to measure the software development processes with two views: Introduction and detection of defects. Introduction is done during the specification, design and coding phases; defects are either introduced into documents or into the actual product. Detection of defects is done via inspections and test during all the phases of the project.
A tool was developed using a spreadsheet. The purpose of the tool was to estimate the number of defects per phase, and to track all defects discovered in inspections and tests against these estimates. The tool supported analysis of the data with both calculated values and graphs comparing actuals to estimates in terms of current status and trends over time.
The Project Defect Model has been beneficial to projects. It has helped estimating, planning, and tracking quality during the project, including an estimate of the the number of defects left in the released product. The quality data has been used in the project together with time and cost data, to take better decisions on test, review and inspections, and design. Also it has identified quality risks at an early stage, helping the project take corrective actions and decisions on product release and maintenance capacity planning. Finally the model provided insight into the effectiveness of the verification activities, supporting effective process improvement.
Paper:
The presentation is on a defect planning/tracking tool and approach. Focus will be upon:
• Goals: What was the purpose of the model, why developed, what did we want to reach?
• How: Show the definition of the model and its implementation and application.
• Tools: The tool that was developed to implement the model, how it works, strengths.
• Results: How did the model and tool help the project? Did it live up to its purpose?
• Success factors: What were key issues that we have dealt successfully with?
• Future: How is this model used in future projects, what could further increase its benefits?
Controlling Project during Development with a Defect Model, Ben Linders, Euro...Ben Linders
To get more insight into the quality of the product during development, it is needed to measure processes with two views: Introduction of defects, and detection. Introduction is done during the requirements, architecture, design and coding phases; defects are either introduced into documents or into the actual product code. Detection is done in test phases, and in the previously mentioned phases by means of inspections and reviews. By using these two measurements, a project can determine if and what the quality risk is: Too many defects in the product, or insufficient testing done.
The presentation will focus upon:
- Goals: What was the purpose of the model, why was it developed, what did we want to reach?
- How: Both the definition of the model and its implementation and application will be highlighted?
- Tools: The tool that was developed to implement the model, how it works, strengths.
- Results: How did the model and tool help the project? Did it live up to its purpose?
- Success factors: What were the key issues that we have dealt successfully with? Why did we focus on them, and how?
- Future: How is this model used in future projects, what could further increase its benefits?
The presentation will show the benefits that the model/tool has brought to the project and organisation. Mainly it was the ability to manage process & product quality, and support decisions, based on data collected in the project and industrial date, i.e. without having to build up historical data in previous projects.
The defect model uses techniques like Orthogonal Defect Classification and Test Matrices for analysis of the defect data. Feedback of the data towards designers, testers, and project management was key in validating the data, and getting good analysis results for corrective and preventive actions.
Experiences using Root Cause Analysis for Improvement, Ben Linders, European ...Ben Linders
http://www.benlinders.com
The presentation will show how Root Cause Analysis (RCA) can be applied in way that it supports reaching the business goals of an organisation. It is based on the results of an investigation done after applying RCA for several years. This has lead to effective RCA methods, applied at specific points in the processes, with significant results.
Also the role of RCA in Total Quality Management and Statistical Process Control is explained, and RCA as a pragmatic implementation of the CMMI Causal Analysis & Resolution process area is elaborated.
Controlling Project Performance using PDM - PSQT2005 - Ben LindersBen Linders
• A hands-on model for control of product and process quality.
• Support of release risk decisions based on defect data.
• ODC and Test Matrices applied in different test phases.
• Usage of feedback to analyze data and come to actions.
• Using project data for a business case for improvement.
Controlling Project Performance by Using a Defect Model - SEPG NA 2008 - Ben ...Ben Linders
Wouldn’t it be nice if you had more insight in product quality, during development? To estimate defects inserted in the product, and check how effective test is in capturing defects? We developed a model to measure defects from requirements to customer feedback after release. It is used to control projects (putting quality next to planning/budget), evaluate risks, and decide on release and support. Baseline data is used to measure and improve process performance.
Reaching Business Goals with Value Adding CMMI Assessments, Ben Linders, Euro...Ben Linders
This presentation will show how to apply the CMMI in a business focussed way, by doing frequent assessments. Goals are input to the planning of assessments, a matrix is used to assure both organisation and process area coverage, and the results of assessments integrate smoothly within operational targets of existing groups within the organisation.
Practical tools support the frequent assessments, and experience with the CMMI is used to optimize the assessment and improvement cycle, resulting in continuously improving the performance of the organisation towards its goals.
Controlling Project during Development with a Defect Model, Ben Linders, ICST...Ben Linders
Wouldn’t it be nice if you could have more insight into the quality of a product, while it is developed, and not afterwards? Would you like to be able to estimate how many defects are inserted in the product in a certain phase, and how effective a (test) phase is in capturing these defects? To optimize your test phases regarding focus and effort in relation to how many defects they will find? This presentation will show a simple but very effective model that makes it possible: The Project Defect Model.
The aim of the Project Defect Model is to track product quality, take corrective actions and reduce quality risks. To get more insight into the quality of the product during development, it is needed to measure the software development processes with two views: Introduction and detection of defects. Introduction is done during the specification, design and coding phases; defects are either introduced into documents or into the actual product. Detection of defects is done via inspections and test during all the phases of the project.
A tool was developed using a spreadsheet. The purpose of the tool was to estimate the number of defects per phase, and to track all defects discovered in inspections and tests against these estimates. The tool supported analysis of the data with both calculated values and graphs comparing actuals to estimates in terms of current status and trends over time.
The Project Defect Model has been beneficial to projects. It has helped estimating, planning, and tracking quality during the project, including an estimate of the the number of defects left in the released product. The quality data has been used in the project together with time and cost data, to take better decisions on test, review and inspections, and design. Also it has identified quality risks at an early stage, helping the project take corrective actions and decisions on product release and maintenance capacity planning. Finally the model provided insight into the effectiveness of the verification activities, supporting effective process improvement.
Paper:
The presentation is on a defect planning/tracking tool and approach. Focus will be upon:
• Goals: What was the purpose of the model, why developed, what did we want to reach?
• How: Show the definition of the model and its implementation and application.
• Tools: The tool that was developed to implement the model, how it works, strengths.
• Results: How did the model and tool help the project? Did it live up to its purpose?
• Success factors: What were key issues that we have dealt successfully with?
• Future: How is this model used in future projects, what could further increase its benefits?
Controlling Project during Development with a Defect Model, Ben Linders, Euro...Ben Linders
To get more insight into the quality of the product during development, it is needed to measure processes with two views: Introduction of defects, and detection. Introduction is done during the requirements, architecture, design and coding phases; defects are either introduced into documents or into the actual product code. Detection is done in test phases, and in the previously mentioned phases by means of inspections and reviews. By using these two measurements, a project can determine if and what the quality risk is: Too many defects in the product, or insufficient testing done.
The presentation will focus upon:
- Goals: What was the purpose of the model, why was it developed, what did we want to reach?
- How: Both the definition of the model and its implementation and application will be highlighted?
- Tools: The tool that was developed to implement the model, how it works, strengths.
- Results: How did the model and tool help the project? Did it live up to its purpose?
- Success factors: What were the key issues that we have dealt successfully with? Why did we focus on them, and how?
- Future: How is this model used in future projects, what could further increase its benefits?
The presentation will show the benefits that the model/tool has brought to the project and organisation. Mainly it was the ability to manage process & product quality, and support decisions, based on data collected in the project and industrial date, i.e. without having to build up historical data in previous projects.
The defect model uses techniques like Orthogonal Defect Classification and Test Matrices for analysis of the defect data. Feedback of the data towards designers, testers, and project management was key in validating the data, and getting good analysis results for corrective and preventive actions.
Experiences using Root Cause Analysis for Improvement, Ben Linders, European ...Ben Linders
http://www.benlinders.com
The presentation will show how Root Cause Analysis (RCA) can be applied in way that it supports reaching the business goals of an organisation. It is based on the results of an investigation done after applying RCA for several years. This has lead to effective RCA methods, applied at specific points in the processes, with significant results.
Also the role of RCA in Total Quality Management and Statistical Process Control is explained, and RCA as a pragmatic implementation of the CMMI Causal Analysis & Resolution process area is elaborated.
The National Institute of Standards and Technology estimates that software bugs cost the U.S. economy $59.5 billion annually. If more comprehensive software testing was performed, a third of these costs could be avoided. The value of software testing is derived from the quality, price and time that are saved by releasing superior products to satisfied customers. Through techniques such as the utilization of knowledgeable and inventive software testers and early identification of defects, a company can decrease the time to market and the cost of quality, while amplifying the end-user satisfaction level. - See more at: http://www.qualitestgroup.com/The-Value-of-Software-Testing#sthash.BJI9tf3b.dpuf
Patricia Carlin, General Manager ThoughtWorks talks about Metrics versus Diagnostics, Reporting Progress and Providing Visibility. And also the necessity of producing metrics that add value and eliminating metrics that are now deemed irrelevant. The discussion also comprises guidelines on effectively using metrics on an Agile Project as well as different types of metrics used on ThoughtWorks projects.
Agile Metrics for Senior Managers and ExecutivesVersionOne
In this webinar, find out about agile appropriate metrics at the customer, portfolio and project levels. Presented by LitheSpeed, LLC.
Want to check out the full webinar? Visit http://pm.versionone.com/Webinar_MetricsExecs.html
In business it is all about measurement. If something can’t be measured it is deemed unimportant or relegated to “cost” status. Anything put in the “cost” bucket has no chance to grow or prosper, especially in the current economic climate. For the Business Analyst position to grow in respect and requirement within a business, measurement tools must be established.
Currently, there are no generally accepted standards for measuring the success for failure of a BA. In this web seminar we will discuss what measurement tools could be established and what tools organizations are currently using “out in the wild” to measure their BA performance. The goal is to give you a concert idea on how to start developing a BA measurement solution to validate you or your team’s success and worth. The ultimate goal is to push the IIBA to drive the development of generally accepted measuring tools for the BA position.
You will learn:
·Reasons why measurement in business is important
·Why it is critical the BA role doesn’t get lumped into the “cost” bucket
·Potential tools for measuring BA performance
·Options that other organizations are currently using in the wild
·Ideas on how to start implementing a measurement solution
·Importance of IIBA support in driving measurement standards
Software Metrics: Taking the Guesswork Out of Software ProjectsTechWell
Why bother with measurement and metrics? If you never use the data you collect, this is a valid question—and the answer is “Don’t bother, it’s a waste of time.” In that case, you’ll manage with opinions, personalities, and guesses—or even worse, misconceptions and misunderstandings. Based on his more than forty years of software and systems development experience, Ed Weller describes reasons for measurement, key measures in both traditional and agile environments, decisions enabled by measurement, and lessons learned from successful—and not so successful—measurement programs. Find out how to develop and maintain consistent data and valid measures so you can estimate reliably, deliver products with known quality, and have happy users and customers—the ultimate trailing indicator. Learn to manage projects dynamically with the support of current metrics and data from past projects to guide your management planning and control. Join Ed to explore how to invest in measurements that provide leading indicators to help you meet your company and customer goals.
Customer Collaboration & Product Innovation Using Social NetworksJohn Carter
This presentation to the Silicon Valley PMI Annual Symposium discusses the migration of social networks into products and product development processes. It presents the best practices and pitfalls of innovating with customers using social media and suggests some next steps for companies that are new to the use of social networks in product development.
Software Quality Dashboard Benchmarking StudyJohn Carter
Software metrics best practices from a benchmarking assignment that indicates how software metrics are reported to management and used to drive behavior. We learned how leading companies used dashboards to report on quality progress and improvement results. We found the best organizations focused on the vital few metrics but also had automated systems with the ability to drill down on metrics at the divisional and team levels. In addition, the best normalized the metrics by number of customers or complexity. They systematically used root cause analysis to analyze bugs in the field. The SW Quality metrics often went beyond the strict definition of quality in that they also measured release predictability and feature expectations. Finally, the best companies used external benchmarks to set their quality targets.
2008-02-14 - IASTED Innsbruck 2008 - Customer Retention and Delivery Quality ...Jaap van Ekris
Customer retention is vital for the survival of software development organizations, especially under current economic trend of global outsourcing. We show that the traditional definition of project success has a blind spot to aspects are extremely relevant for customer retention.
Agile Project Management in a Waterfall World: Managing Sprints with Predicti...John Carter
Applying Agile methods in a waterfall world seemed impossible until we discovered the 10 essential skills and tools. Five of these skills are organizational, while others translate the short intervals characteristic of Agile to the world outside of Software. User Stories becomes Boundary Conditions; Burn-down charts becomes Deliverable Hit Rate charts; Sprints become HW intervals; Sprint Retrospectives become Event Timeline Retrospectives, while the project as a whole is managed using Boundary Conditions. This presentation shows examples of these tools and shows examples of how they are applied.
Continuous Improvement, make it visible - ICSPI 2006 - Ben LindersBen Linders
Communication is an important factor in improvement programs. Communication pictures the goals and approach of an improvement program. It can motivate people to commit to change, by showing expected benefits and early results. But wrong or too much communication can also frustrate people, getting them to resist changing.
Many improvement programs are run by technical persons, in a technical environment. Often communication is undervalued and underestimated, and perceived as difficult. It is something that people are inexperienced in, which makes them feel uncomfortable. But if they get started, and take some hurdles, they can get better in it. This presentation provides hands-on information, and hint & tips.
This presentation will show how vital communication is for improvement programs. It supplies a set of tools and techniques to improve the visibility of targets and results, and will explain how this has been used to monitor and steer continuous improvement in an R&D organization. Views on continuous improvement from different stakeholders are included, to show their needs on communication.
Keynote Need for Continuous Improvement - Agile Tour Kaunas 2016 - Ben LindersBen Linders
Agile isn’t a silver bullet, and it’s not a one size fits all approach. Continuous improvement is what makes it work, it’s at the heart of agile. Ben will show why continuous improvement matters in agile and what you can do to help your teams and organization to be more agile.
The National Institute of Standards and Technology estimates that software bugs cost the U.S. economy $59.5 billion annually. If more comprehensive software testing was performed, a third of these costs could be avoided. The value of software testing is derived from the quality, price and time that are saved by releasing superior products to satisfied customers. Through techniques such as the utilization of knowledgeable and inventive software testers and early identification of defects, a company can decrease the time to market and the cost of quality, while amplifying the end-user satisfaction level. - See more at: http://www.qualitestgroup.com/The-Value-of-Software-Testing#sthash.BJI9tf3b.dpuf
Patricia Carlin, General Manager ThoughtWorks talks about Metrics versus Diagnostics, Reporting Progress and Providing Visibility. And also the necessity of producing metrics that add value and eliminating metrics that are now deemed irrelevant. The discussion also comprises guidelines on effectively using metrics on an Agile Project as well as different types of metrics used on ThoughtWorks projects.
Agile Metrics for Senior Managers and ExecutivesVersionOne
In this webinar, find out about agile appropriate metrics at the customer, portfolio and project levels. Presented by LitheSpeed, LLC.
Want to check out the full webinar? Visit http://pm.versionone.com/Webinar_MetricsExecs.html
In business it is all about measurement. If something can’t be measured it is deemed unimportant or relegated to “cost” status. Anything put in the “cost” bucket has no chance to grow or prosper, especially in the current economic climate. For the Business Analyst position to grow in respect and requirement within a business, measurement tools must be established.
Currently, there are no generally accepted standards for measuring the success for failure of a BA. In this web seminar we will discuss what measurement tools could be established and what tools organizations are currently using “out in the wild” to measure their BA performance. The goal is to give you a concert idea on how to start developing a BA measurement solution to validate you or your team’s success and worth. The ultimate goal is to push the IIBA to drive the development of generally accepted measuring tools for the BA position.
You will learn:
·Reasons why measurement in business is important
·Why it is critical the BA role doesn’t get lumped into the “cost” bucket
·Potential tools for measuring BA performance
·Options that other organizations are currently using in the wild
·Ideas on how to start implementing a measurement solution
·Importance of IIBA support in driving measurement standards
Software Metrics: Taking the Guesswork Out of Software ProjectsTechWell
Why bother with measurement and metrics? If you never use the data you collect, this is a valid question—and the answer is “Don’t bother, it’s a waste of time.” In that case, you’ll manage with opinions, personalities, and guesses—or even worse, misconceptions and misunderstandings. Based on his more than forty years of software and systems development experience, Ed Weller describes reasons for measurement, key measures in both traditional and agile environments, decisions enabled by measurement, and lessons learned from successful—and not so successful—measurement programs. Find out how to develop and maintain consistent data and valid measures so you can estimate reliably, deliver products with known quality, and have happy users and customers—the ultimate trailing indicator. Learn to manage projects dynamically with the support of current metrics and data from past projects to guide your management planning and control. Join Ed to explore how to invest in measurements that provide leading indicators to help you meet your company and customer goals.
Customer Collaboration & Product Innovation Using Social NetworksJohn Carter
This presentation to the Silicon Valley PMI Annual Symposium discusses the migration of social networks into products and product development processes. It presents the best practices and pitfalls of innovating with customers using social media and suggests some next steps for companies that are new to the use of social networks in product development.
Software Quality Dashboard Benchmarking StudyJohn Carter
Software metrics best practices from a benchmarking assignment that indicates how software metrics are reported to management and used to drive behavior. We learned how leading companies used dashboards to report on quality progress and improvement results. We found the best organizations focused on the vital few metrics but also had automated systems with the ability to drill down on metrics at the divisional and team levels. In addition, the best normalized the metrics by number of customers or complexity. They systematically used root cause analysis to analyze bugs in the field. The SW Quality metrics often went beyond the strict definition of quality in that they also measured release predictability and feature expectations. Finally, the best companies used external benchmarks to set their quality targets.
2008-02-14 - IASTED Innsbruck 2008 - Customer Retention and Delivery Quality ...Jaap van Ekris
Customer retention is vital for the survival of software development organizations, especially under current economic trend of global outsourcing. We show that the traditional definition of project success has a blind spot to aspects are extremely relevant for customer retention.
Agile Project Management in a Waterfall World: Managing Sprints with Predicti...John Carter
Applying Agile methods in a waterfall world seemed impossible until we discovered the 10 essential skills and tools. Five of these skills are organizational, while others translate the short intervals characteristic of Agile to the world outside of Software. User Stories becomes Boundary Conditions; Burn-down charts becomes Deliverable Hit Rate charts; Sprints become HW intervals; Sprint Retrospectives become Event Timeline Retrospectives, while the project as a whole is managed using Boundary Conditions. This presentation shows examples of these tools and shows examples of how they are applied.
Continuous Improvement, make it visible - ICSPI 2006 - Ben LindersBen Linders
Communication is an important factor in improvement programs. Communication pictures the goals and approach of an improvement program. It can motivate people to commit to change, by showing expected benefits and early results. But wrong or too much communication can also frustrate people, getting them to resist changing.
Many improvement programs are run by technical persons, in a technical environment. Often communication is undervalued and underestimated, and perceived as difficult. It is something that people are inexperienced in, which makes them feel uncomfortable. But if they get started, and take some hurdles, they can get better in it. This presentation provides hands-on information, and hint & tips.
This presentation will show how vital communication is for improvement programs. It supplies a set of tools and techniques to improve the visibility of targets and results, and will explain how this has been used to monitor and steer continuous improvement in an R&D organization. Views on continuous improvement from different stakeholders are included, to show their needs on communication.
Keynote Need for Continuous Improvement - Agile Tour Kaunas 2016 - Ben LindersBen Linders
Agile isn’t a silver bullet, and it’s not a one size fits all approach. Continuous improvement is what makes it work, it’s at the heart of agile. Ben will show why continuous improvement matters in agile and what you can do to help your teams and organization to be more agile.
Spicing up Agile Retrospectives - Agile Practitioners 2016 - Ben LindersBen Linders
The agile manifesto proposes that a “team reflects on how to become more effective”. Agile retrospectives can be used to inspect and adapt the way of working. Retrospectives help teams to deploy agile practices in an effective way and to continuously learn and improve themselves. Ben Linders, co-author of Getting Value out of Agile Retrospectives, will talk about the why and how of agile retrospectives, with much practical tips, stories, and examples. Ben also gives full-day workshops on Valuable Agile Retrospectives.
Real Agile Value with Agile Retrospectives - The making of...Ben Linders
Ben Linders takes you on a journey about writing and self-publicing books. He talk about how the book Getting Value out of Agile Retrospectives started, explain how he works remotely with his co-author Luis Gonçalves and how the book has been translated to Dutch by a self-organized agile team of volunteers.
Spicing up Agile Retrospectives - Agile Tour London 2015 - Ben LindersBen Linders
The agile manifesto proposes that a “team reflects on how to become more effective”. Agile retrospectives can be used to inspect and adapt the way of working. Retrospectives help teams to deploy agile practices in an effective way and to continuously learn and improve themselves. Ben Linders, co-author of Getting Value out of Agile Retrospectives, will talk about the why and how of agile retrospectives, with much practical tips, stories, and examples. Ben will also give a workshop on Valuable Agile Retrospectives on October 22.
Becoming agile in an agile way - ITMPI webinar by Ben LindersBen Linders
Software development organizations need to become more agile and lean, to deliver products and services that satisfy the needs of their customers. There are multiple ways to do this, which asks for an agile approach to you change your way of working in small directed steps. Retrospectives help you to inspect and adapt your agile journey, assuring that you will get results from your agile and lean transition.
For a writeup on this webinar topic see http://www.benlinders.com/2013/becoming-agile-in-an-agile-way/
Spice up your agile retrospectives - LKFR14 - Ben LindersBen Linders
The agile manifesto proposes that a “team reflects on how to become more effective”. Agile retrospectives can be used to inspect and adapt the way of working. But sometimes teams struggle to figure out what an agile retrospective is? And they wonder how they should do them?
Retrospectives help teams to deploy agile practices in an effective way and to continuously learn and improve themselves.
The retrospective facilitator (often the scrum master) should have a toolbox of retrospective exercises, and be able to pick the most effective one.
This presentation explains the “what” and “why” of retrospectives and the business value and benefits that they can bring. You will experience several exercises that you can use to facilitate retrospectives, supported with advice for introducing and improving retrospectives.
Retrospectives are a great way for teams to improve their way of working, to become more agile and lean. Getting actions out of a retrospective that are doable, and getting them done helps teams to learn and improve continuously.
Need for Continuous Improvement in Agile - 1stconf Melbourne 2016 - Ben LindersBen Linders
Agile isn't a silver bullet, and it’s not a one size fits all approach. Continuous improvement is what makes it work, it’s at the heart of agile. Ben will show why continuous improvement matters in agile and what you can do to help your teams and organization to be more agile.
Sustainable Improvement Through Retrospectives - SEPG Europe 2013 - Ben LindersBen Linders
Buy-in from professional is crucial to make changes succeed in organizations. Many improvement programs fail when professionals are insufficiently involved during the changes. Agile retrospectives can be used to do continuous and lasting improvements in organizations. They are owned and done by the teams, who decide when, where, and how they will change their way of working. This is why agile retrospectives are a sustainable approach for improvement.
For a summary of this presentation, see http://www.benlinders.com/2013/sustainable-improvement-through-agile-retrospectives/.
Agile Quality: maximize results with a small quality team, Ben Linders, Europ...Ben Linders
The Ericsson Operational Development & Quality team has managed to introduce a new Management System with a process baseline, rolled out measurements throughout the organization using a Balanced ScoreCard approach, and kept up a focused continuous improvement program. This presentation shows how (obstacles, KSF, results).
At all times, management has made clear that they need control of all aspects of the operation. With a collaborated approach of management and Operational Development (OD), the balanced scorecard was introduced. OD has streamlined target setting, monthly reporting, and quarterly management reviews. The monthly report has been enhanced from a figures only report to full analysis, action definition and forecasting per reported target, involving the line by means of feedback interviews.
A Management System was introduced, moulding and optimizing the existing organisation structure, authorities, and policies. With this management system, the set of processes was reduced, and process support was re-enforced.
A continuous improvement program was continued, with more focus on organizational targets. Existing tools like audits, root cause analysis, and improvement sessions were used to extract vital few actions together with line and project management; the resulting actions were tracked to completing by the OD team.
Key success factors have been the management commitment & active support, the drive of the OD & Quality team, and the build up of skills and knowledge that was needed to implement the changes. Cross-organizational co-operation was stimulated, and management was involved through the monthly reporting & feedback cycle. This presentation will give examples of this, and hints & tips on how to exploit these key success factors in your own organization.
The result is an efficient organization, capable of running projects and supporting activities in a largely quantitative managed way, meeting the required business results.
The Business Benefit of Root Cause Analysis, Ben Linders, SM/ASM Conference 2003Ben Linders
The presentation will show how Root Cause Analysis (RCA) can be applied in way that it supports reaching the business goals of an organisation. It is based on collected data of RCA sessions (done for several years) and the impact on business results, and analysing this data together with non-quantitative information. This has lead to effective RCA methods, applied at specific points in the processes, with significant business results.
Also the role of RCA in Total Quality Management and Statistical Process Control is explained, including how RCA used results from Orthogonal Defect Classification for maximum result. Finally, RCA as a pragmatic implementation of the CMMI Causal Analysis & Resolution process area, is elaborated.
The road to agility - AgileEE conference 2016 - Ben LindersBen Linders
Adopting agile often doesn’t go as smoothly as expected in an organization. The road to agility can be hard to travel: You can’t plan your journey up front and there will be surprises along the way. Becoming agile is a learning process which requires that you reflect regularly and adopt your way of working, finding better ways to travel.
Ben Linders will explore what teams, agile coaches, Scrum masters, and managers can do to be prepared for a journey to agility, what to pack and how to decide which road to follow along the way. This talk will help you to successfully deploy ideas and practices that you’ve learned at the conference.
Doing Valuable Agile Retrospectives -ATBru 2014 - Ben LindersBen Linders
The agile manifesto proposes that a “team reflects on how to become more effective”. Agile retrospectives can be used to inspect and adapt the way of working. They help teams to deploy agile practices in an effective way and to continuously learn and improve themselves.But sometimes teams struggle to figure out what an agile retrospective is? And they wonder how they should do them? This presentation explains the “what” and “why” of retrospectives and the business value and benefits that they can bring. It shows several exercises from the book "Getting Value out of Agile Retrospectives" to help you to facilitate retrospectives, supported with advice for introducing and improving retrospectives. Retrospectives are a great way for teams to improve their way of working, to become more agile and lean. Getting actions out of a retrospective that are doable, and getting them done helps teams to learn and improve continuously.
Valuable Agile Retrospectives - Book Launch for SPIder - Ben LindersBen Linders
Presentation given at the SPIder Book Event to announce the Dutch edition Waardevolle Agile Retrospectives (translation from Getting Value out of Agile Retrospectives).
With plenty of exercises for your personal retrospective toolbox, Getting Value out of Agile Retrospectives will help you to become more proficient in doing retrospectives and to get more out of them.
Learning to Become Agile, with Retrospectives - QCon London 2015 - Ben LindersBen Linders
The agile manifesto proposes that a “team reflects on how to become more effective”. Agile retrospectives can be used to inspect and adapt the way of working. They help teams to become agile by deploying agile practices in an effective way and continuously learning and improve themselves.
This talk explains the “what” and “why” of retrospectives and the business value and benefits that they can bring. Examples will be given of exercises that you can use to facilitate retrospectives, supported with advice for introducing and improving retrospectives. It is based on the successful book Getting Value out of Agile Retrospectives which is published on InfoQ, Amazon, Leanpub.
Retrospectives are a great way for teams to improve their way of working, to become more agile and lean. Getting actions out of a retrospective that are doable, and getting them done helps teams to improve continuously and deliver more value to their customers.
Gathering And Documenting Your Bi Business RequirementsWynyard Group
Business requirements are critical to any project. Recent studies show that 70% of organisations fail to gather business requirements well. What is worse is that poor requirements can lead a project to over spend its original budget by 95%.
Business Intelligence and Performance Management projects are no different. This session will provide a series of tips, techniques and ideas on how you can discover, analyse, understand and document your business requirements for your BI and PM projects. This session will also touch on specific issues, hurdles and obstacle that occur for a typical BI or PM project
• The importance of business requirements and a well defined business requirements process
• Understanding the difference between a “wish-list” or vision and business requirements
• The need and benefits of having a business traceability matrix
Start your BI projects on the right foot – understand your requirements
Product QA - A test engineering perspectiveImaginea
Imaginea's time test product qa methodology. Our hawkeye methodology helps products get released to maker more efficiently and in lesser time. Products have to be tested with a gotomarket testing approach and thats what we specialize at.
Agile Testing: The Role Of The Agile TesterDeclan Whelan
This presentation provides an overview of the role of testers on agile teams.
In essence, the differences between testers and developers should blur so that focus is the whole team completing stories and delivering value.
Testers can add more value on agile teams by contributing earlier and moving from defect detection to defect prevention.
Psychological Safety in Teams - FlowCon France 2024 - Ben LindersBen Linders
Psychological safety in teams is important; team members must feel safe and able to communicate and collaborate effectively to deliver value. It’s also necessary to build long-lasting teams since things will happen and relationships will be strained.
But, how safe is a team? How can we determine if there are any factors that make the team unsafe or have an impact on the team’s culture?
In this mini-workshop, we’ll play games for psychological safety and team culture utilizing a deck of coaching cards, The Psychological Safety Cards. We will learn how to use gamification to gain a better understanding of what’s going on in teams. Individuals share what they have learned from working in teams, what has impacted the team’s safety and culture, and what has led to positive change.
Different game formats will be played in groups in parallel. Examples are an ice-breaker to get people talking about psychological safety, a constellation where people take positions about aspects of psychological safety in their team or organization, and collaborative card games where people work together to create an environment that fosters psychological safety.
Why people hate working in Agile teams - QA Challenge Accepted 2023 - Ben Lin...Ben Linders
By now, many of us have been through one or more "agile transformations". We've been surrounded by agile coaches and Scrum masters who tried to help us adapt to agile, with managers who became servant leaders. Hopefully they weren't telling you what to do or how to do your work! A lot of people simply hate working in agile teams - Ben hears that all the time. And that is why he's here! In this talk, Ben will explore the difficulties of collaborating in teams and what we can do to make it beneficial and worthwhile for people to work in teams. Ben will delve into what teams really need, and what leaders should do and should not do to support them, including providing an environment and culture where teams can flourish and supporting teams in removing barriers. Through this talk, attendees will gain a better understanding of the reasons why people struggle to work in agile teams, and what leaders can do to create a positive and supportive environment for teams. The talk is intended for anyone working in a team or working with teams, from agile coaches and Scrum masters to managers and team members who are looking to improve their collaboration skills and create a more positive and productive work environment.
Improving Your Testing Skills and Practices with Gamification - Testing Unite...Ben Linders
So many challenges, so little time. As testers or quality engineers, we need to sharpen the saw, but how? Gamification can be a way to look at how you’re doing and find out where to improve. It’s a great way to have everyone engaged and get the best out of people.
In this presentation, Ben Linders will show how playing games (onsite or online) with the Agile Testing Coaching Cards and Agile Quality Coaching Cards help to explore your current quality and testing practice and decide as a team on what to improve or experiment with.
Start up distributed teams online - Mini XP days 2022 - Ben LindersBen Linders
How to start up a distributed team online with gamification
Remote first is becoming the norm, and this is also true for new teams. Where you would previously organize one or more onsite kick-off sessions to start a new team, a new distributed team would have to be working online together from day 1.
Techniques used for team chartering might still be useful, but they would need a different approach for online working. Gamification, incentifying people’s engagement by using game-style principles and practices, can help you to build strong teams.
In this session, we’ll look at several tools and playing formats that can be used to start up distributed teams and foster further development.
We’ll do the exercises in teams, and as we will be experimenting with both in-person and online exercises it’s good to bring your laptop or tablet too.
Mini XP Days
Instead of scaling up further, XP Days decided to “scale-out”: they rerun some of the favourite sessions of the previous year’s XP Days at the “Mini XP Day”, a one day conference with three tracks. Mini XP Day is ideal if you’ve missed XP Days or if you want to get a “taste” of what XP Days is.
Mini XP Days 2022 will be held on May 17 at the Van der Valk Hotel Beveren.
Increasing psychological safety in agile teams - Agile humans lean coffee 202...Ben Linders
Psychological safety in teams is important; it is necessary for the team to be able to communicate and collaborate effectively in order to deliver value. It's also necessary to build long-lasting teams since things will happen and relationships will be strained; team members must be informed of what's going on in the team and feel comfortable dealing with it. But, how safe is a team? How can we determine if there are any factors that make the team unsafe or have an impact on the team's culture?
In this mini-workshop, we'll play a game for psychological safety and team culture utilizing a deck of coaching cards. We will learn how to use gamification to gain a better understanding of what's going on in teams. Individuals can share what they have learned from working in teams, how it impacted the team's safety and culture, and what led to positive change.
We'll use a Jamboard for the game, so you will need a Google account to join the Jamboard. All participants will receive a code along with a discount for buying the cards.
Improving your quality and testing skills with gamification - Spring 2021 Onl...Ben Linders
For the first time, I’m doing a session at the Online Testing Conference. I’ll be playing games with the Agile Testing Coaching Cards and Agile Quality Coaching Cards to help people explore how things are going and to improve their way of working.
Improving Your Quality and Testing Skills with Gamification
So many challenges, so little time. As testers we need to sharpen the saw, but how? Gamification can be a way to look at how you’re doing and find out where to improve. It’s a great way to have everyone involved and get the best out of people.
In this presentation, Ben Linders will play games with the Agile Testing Coaching Cards and Agile Quality Coaching Cards to show how you can explore your current quality and testing practice and decide in your team on what to improve or experiment with.
Players can use the coaching cards to discuss quality and testing values, principles, and practices. In teams, people can use the cards to share their experiences and learnings.
Different game formats can be used to share experiences on testing and quality principles and practices and explore how they can be applied effectively.
Takeaways
Show how to use gamification to self-assess your current way of working.
Play games with the Agile Testing Coaching Cards and Agile Quality Coaching Cards.
Explore how to facilitate games to enhance quality and testing in agile teams.
\
Online Testing Conference
OnlineTestConf was the first 100% online conference to provide all the advantages of attending professional QA related conferences: personal learning, networking etc. without the shortcomings of scheduling, expenses and travel. The conference has been running for the past 5 years on a semi-annual basis, long before COVID-19 forced all live events online.
Our next event will be our 10th OnlineTestConf! Conference attendees are from all parts of the world, we host well known speakers as well as young presenters, and discuss everything that relates to Testing and QA. Attendance is and will remain free of charge and we invite anyone who sees themselves involved in testing and the testing community to join.
How agile are you? - Agile New England 2021 - Ben LindersBen Linders
On April 1, 2021, (no joke) I did an Agile 101 for Agile New England where we played the Agile Self-assessment Game online.
The Agile Self-assessment Game: How Agile Are You? by Ben Linders
The Agile Self-assessment Game is an Agile ” compass & map” to find out where you are and inspire you with ideas and suggestions on where to go next on your agile journey. It’s a cooperative card game to discover how agile you are and what you can do to increase your agility to deliver more value to their customers and stakeholders.
In this session, Ben Linders explored how a game can enable people to pull in ideas for change and apply those in a way that best suits their collective needs. And we have played with the Agile self-assessment cards online.
Ben Linders is an Independent Consultant in Agile, Lean, Quality, and Continuous Improvement. As an adviser, trainer, and coach, he helps organizations with effectively deploying software development and management practices. He focuses on continuous improvement, collaboration and communication, and professional development, to deliver business value to customers. Ben is an active member of networks on Agile, Lean, and Quality, and a well-known speaker and author. Creator of many Agile Coaching Tools, for example, the Agile Self-assessment Game.
Mini workshop collaborative problem solving - OOP 2021 - Ben LindersBen Linders
Problem? What Problem? Practice Collaborative Problem-solving
Working in teams we face problems in our daily work. As a team, we should be able to solve problems collaboratively. Agile calls these problems impediments.
Impediments can be something in the way of working, processes, tools, or organizational rules or structures. They can also be something cultural or structural.
In this mini-workshop, we’ll practice solving an impediment as a team. Next, we’ll explore how we solved it, how we worked together. What hindered and helped us. We’ll learn what we can do to collaborate better.
Futurespective on Software Development in 2040 - Agile Tour Brussels 2020 - B...Ben Linders
Back to the Future – A Futurespective on Software Development in 2040
We start the futurespective by sketching the future. How is software developed in 2040? Is it people, AI, or a combination? Teams, large groups, or individual work? Programming and testing, or other approaches? Continuous delivery, chunks, iterations, push or pull? Distributed, dispersed, localized teams? There are no limits, let your imagination flow to visualize ideas about developing software products in 2040.
Next, we’ll discuss what got us there. How did these new ways of developing software come into existence? How did we discover them? What experiments led to this? What drove us or influenced us along the way?
Finally, we think about the steps that we can take in 2020 to reach the castle in the sky of software development. What can we do now to become better? What should we stop as it won’t exist in the future anymore?
Let’s find out how the future of software development looks, by doing a futurespective exercise in groups!
How agile are you - Agile Tour London 2020 - Ben LindersBen Linders
Let’s Play a Game to Self-assess Your Agility
Every team, every organization is less or more agile. But how agile are you, and how can you increase your agility? Methods or frameworks don’t tell you how to become agile or increase your agility.
The Agile Self-Assessment Game is an “agile map” with coaching cards for Scrum, DevOps, Kanban, and Business Agility.
Playing the game inspires you with ideas and suggestions on where to go next on your agile journey. Join this session to experience different playing formats in teams, learn how you can discover how agile you are, and get fresh ideas to increase your agility.
Mini workshop retrospecting your retrospectives - Experience Agile 2020 - Be...Ben Linders
The mini-workshop Retrospecting your Retrospectives at eXperience Agile 2020 provides you with ideas to debug your agile retrospectives, find out why they aren’t working and learn how to spice them up and bring the energy back in the team.
Are your retrospective meetings not helping teams to improve? Same actions coming up every retro? People skip the retro, or find them boring? A lack of energy in the room? Chit-chatting instead of discussing real issues? No need for that, let’s retrospect your retrospectives!
In this mini-workshop, you will experience how to use retrospective exercises to debug your retrospective meetings. People will work in teams to reflect on how their retrospectives are going and will learn what they can do to make them valuable again.
It’s a highly interactive session, learning by doing. I’ll bring in my experience from 20 years of doing agile retrospectives, and will set a culture where people will share their ideas and learn.
Agile retrospectives should help teams to reflect at the end of each iteration to learn and decide what to improve and take action in the next iteration. Valuable Agile Retrospectives provide the solution for a successful agile adoption at all levels in the organization. They help teams to reflect and learn how to apply agile practices effectively, and support managers with ideas to set conditions for their teams to grow and deliver more value.
But sometimes retrospectives don’t live up their expectation. Problems that can happen are:
The same questions (what went well, what to improve) are being asked
Similar actions keep coming up in every retrospective
Nothing happens after the meeting, actions are not done
People are postponing or skipping the retrospective meeting
Team members complain that retrospectives are boring and a waste of time
There’s a lack of energy in the room during the meeting, people are not engaged
People don’t feel safe to speak up and share their view
Discussions in the retrospective are not about the real problems (elephant in the room)
The retrospective facilitator is leading people towards a pre-defined answer/solution
In this session, teams will be doing 5 different exercises. In a time slot of two hours, teams rotate to do 2-3 of them.
Intended audience: Scrum masters, agile coaches, tech leads, developers, testers, operations, and anyone who facilitates retrospectives.
This session includes ideas published in my book Getting Value out of Agile Retrospectives, practices from the Retrospective Exercises Toolbox, and agile coaching tools available in my webshop. It’s partly based on things that I teach in one of my workshops: Increasing Organizational Agility with Retrospectives.
Learning Objectives:
Learn to use exercises to reflect on your current practice of retrospectives
See how to create a safe and productive environment to run retrospectives
Practice effective skills for facilitating retrospectives and getting people engaged
Webinar enhancing quality and testing in agile teams - PractiTest - Ben LindersBen Linders
It can be hard for agile teams to deal with quality and testing challenges and decide what to do to deliver high-quality products. There are many different approaches and solutions, which, depending on the context, the problem at hand, and how they are applied, can be more or less effective.
In this webinar, Ben Linders will show you how can use gamification to self-assess your current way of working and enhance quality and testing in agile teams. Playing games with the Agile Testing Coaching Cards and Agile Quality Coaching Cards make it possible to explore your current quality and testing practice and reach a consensus on what could be improved.
Players can use the coaching cards to discuss quality and testing values, principles, and practices. In teams, people can use the cards to share their experiences and learnings.
During the webinar, we’ll pick out cards from the coaching decks to go into detail on specific principles and practices and explore how they can be applied effectively.
Futurespective on software development in 2040 - Aginext - Ben LindersBen Linders
I just came back from 2040 to find out that we are still making software. But it’s not as we know it, Jim! Software development is done completely differently compared to the agile wave that we had at the start of the century. How different? Well, let’s futuresplore it together.
Leading for Self-organization - Stretch 2020 - Ben LindersBen Linders
Agile is something for teams, right? True, but teams don’t function in a vacuum. As a manager, you can set the stage and support teams who want to increase their agility. This presentation explores three topics that managers can work on to make teams succeed and increase the company’s agility: Leadership, Collaboration, and Culture.
Pecha Kucha How to screw up your agile retrospective big time - Ben Linders -...Ben Linders
Retrospectives are great, except when they are not. This tongue-in-cheek presentation explores how you can make agile retrospectives unsuccessful by screwing them, up. I gave this Pecha Kucha at OOP 2020.
Agile Retrospectives to the Next Level - Organizational Agility - OOP 2020 - ...Ben Linders
Agile Retrospectives can be used to deal with problems in teams, at a project or product level, or those related to the collaboration between the team and stakeholders. But you need a different approach compared to team level retrospectives to do organizational-wide improvement.
This session shows how to use agile retrospectives to reveal and solve systemic organizational problems and to increase the company’s agility It explores different approaches, formats, and techniques for agile retrospectives that are done beyond the development team.
Extended Abstract
Nowadays many agile teams are doing retrospectives regularly. They are investing their time to reflect, learn, and take action to improve their way of working and deal with problems that they are facing in a structural way.
Organizations are seeing the benefits from this: teams that are becoming empowered, being able to deliver more value to customers and stakeholders, happy employees, and fewer people leaving the organization. It’s time to take retrospectives to a higher level, and use them to reveal and solve systemic organizational problems. Agile Retrospectives can be used to do that, but you need a different approach.
In this session, I will show how we can use retrospectives to improve the agility of organizations.
Note: Some might call the above approach scaling retrospectives. If that goes towards imposing how teams do retrospectives with some kind of framework, then I believe it doesn’t work. Increasing agility with retrospectives is about creating an environment where teams not only focus on their own improvement needs but also on the company as a whole, and get support from management when improvements go over their team borders or outside their autonomy.
Learning at Scale - FlowCon France 2019 - Ben LindersBen Linders
Where we are seeing more and more individual and team level learning and continuous improvement in organizations, improvements at the higher levels still tend to pose significant challenges. We learn as a team and learn how to be a team, but when we reach the borders of our team and have to deal with more complex systems involving people from our ecosystem and even sometimes from people outside our ecosystem, many improvement practices break down and don’t lead to sustainable results. At the same time, the bigger and more complex our solutions become, the more we need to be able to secure improvement at all levels in the organization.
In this talk, Ben Linders will explore what we can do to increase our understanding of systematic problems at higher levels in organizations, and how to use that to improve the performance and agility of organizations. He will show how we can apply techniques like system/multi-team retrospectives and systems thinking to get improvement going at a level of two higher than the team, and present the benefits that this can bring to teams and organizations as a whole.
Organizational agility: Taking retrospectives to the next level - DevOpsCon M...Ben Linders
Nowadays, many agile teams are doing retrospectives regularly. They are investing time to reflect, learn, and take action to improve their way of working and deal with problems that they are facing in a structural way. Organizations are seeing the benefits from this: teams that are becoming empowered, being able to deliver more value, happy employees, and fewer people leaving the organization. It’s time to take retrospectives to a higher level, and use them to reveal and solve systematic organizational problems. Problems that exist at a project or product level are related to the collaboration between teams and their stakeholders. Agile retrospectives can be used to do that, but you need a different approach. In this session, Ben Linders will show how we can use retrospectives to improve the agility of organizations.
Dealing effectively with impediments - Agile Management Congress 2019 - Ben L...Ben Linders
If your organization wants to become agile and lean, teams need to be able to handle impediments quickly and effectively.
Playing the Impediment Board Game, you will practice how to recognize and analyze impediments, understand how they hinder teams, and decide what to do by deploying agile and lean principles and good practices. You’ll learn to become more effective by recognizing impediments early and get rid of them before they become a major issue.
The impediment game teaches you the five steps for handling impediments effectively:
– recognize and analyze impediments
– find out how they hinder the team
– find effective solutions to deal with them
– decide what to do and who can do it
– learn how to become more effective in dealing with impediments
Agile coaches use the Impediment Board Game in agile transformations to coach teams and help them to become self-organized and empowered to solve any impediments that they might face on their agile journey.
Come play the impediment board game!
Teams what is in it for me - Agile Portugal 2019 - Ben LindersBen Linders
Agile talks a lot about self-organized teams, where developers and testers work together to deliver software. But what can you do to make teams succeed? This talk explores why people would like to work in teams, what managers can do to enable a team structure and culture, and how to (not) manage agile teams.
Recruiting in the Digital Age: A Social Media MasterclassLuanWise
In this masterclass, presented at the Global HR Summit on 5th June 2024, Luan Wise explored the essential features of social media platforms that support talent acquisition, including LinkedIn, Facebook, Instagram, X (formerly Twitter) and TikTok.
LA HUG - Video Testimonials with Chynna Morgan - June 2024Lital Barkan
Have you ever heard that user-generated content or video testimonials can take your brand to the next level? We will explore how you can effectively use video testimonials to leverage and boost your sales, content strategy, and increase your CRM data.🤯
We will dig deeper into:
1. How to capture video testimonials that convert from your audience 🎥
2. How to leverage your testimonials to boost your sales 💲
3. How you can capture more CRM data to understand your audience better through video testimonials. 📊
Premium MEAN Stack Development Solutions for Modern BusinessesSynapseIndia
Stay ahead of the curve with our premium MEAN Stack Development Solutions. Our expert developers utilize MongoDB, Express.js, AngularJS, and Node.js to create modern and responsive web applications. Trust us for cutting-edge solutions that drive your business growth and success.
Know more: https://www.synapseindia.com/technology/mean-stack-development-company.html
Kseniya Leshchenko: Shared development support service model as the way to ma...Lviv Startup Club
Kseniya Leshchenko: Shared development support service model as the way to make small projects with small budgets profitable for the company (UA)
Kyiv PMDay 2024 Summer
Website – www.pmday.org
Youtube – https://www.youtube.com/startuplviv
FB – https://www.facebook.com/pmdayconference
Digital Transformation and IT Strategy Toolkit and TemplatesAurelien Domont, MBA
This Digital Transformation and IT Strategy Toolkit was created by ex-McKinsey, Deloitte and BCG Management Consultants, after more than 5,000 hours of work. It is considered the world's best & most comprehensive Digital Transformation and IT Strategy Toolkit. It includes all the Frameworks, Best Practices & Templates required to successfully undertake the Digital Transformation of your organization and define a robust IT Strategy.
Editable Toolkit to help you reuse our content: 700 Powerpoint slides | 35 Excel sheets | 84 minutes of Video training
This PowerPoint presentation is only a small preview of our Toolkits. For more details, visit www.domontconsulting.com
Implicitly or explicitly all competing businesses employ a strategy to select a mix
of marketing resources. Formulating such competitive strategies fundamentally
involves recognizing relationships between elements of the marketing mix (e.g.,
price and product quality), as well as assessing competitive and market conditions
(i.e., industry structure in the language of economics).
An introduction to the cryptocurrency investment platform Binance Savings.Any kyc Account
Learn how to use Binance Savings to expand your bitcoin holdings. Discover how to maximize your earnings on one of the most reliable cryptocurrency exchange platforms, as well as how to earn interest on your cryptocurrency holdings and the various savings choices available.
Buy Verified PayPal Account | Buy Google 5 Star Reviewsusawebmarket
Buy Verified PayPal Account
Looking to buy verified PayPal accounts? Discover 7 expert tips for safely purchasing a verified PayPal account in 2024. Ensure security and reliability for your transactions.
PayPal Services Features-
🟢 Email Access
🟢 Bank Added
🟢 Card Verified
🟢 Full SSN Provided
🟢 Phone Number Access
🟢 Driving License Copy
🟢 Fasted Delivery
Client Satisfaction is Our First priority. Our services is very appropriate to buy. We assume that the first-rate way to purchase our offerings is to order on the website. If you have any worry in our cooperation usually You can order us on Skype or Telegram.
24/7 Hours Reply/Please Contact
usawebmarketEmail: support@usawebmarket.com
Skype: usawebmarket
Telegram: @usawebmarket
WhatsApp: +1(218) 203-5951
USA WEB MARKET is the Best Verified PayPal, Payoneer, Cash App, Skrill, Neteller, Stripe Account and SEO, SMM Service provider.100%Satisfection granted.100% replacement Granted.
Improving profitability for small businessBen Wann
In this comprehensive presentation, we will explore strategies and practical tips for enhancing profitability in small businesses. Tailored to meet the unique challenges faced by small enterprises, this session covers various aspects that directly impact the bottom line. Attendees will learn how to optimize operational efficiency, manage expenses, and increase revenue through innovative marketing and customer engagement techniques.
B2B payments are rapidly changing. Find out the 5 key questions you need to be asking yourself to be sure you are mastering B2B payments today. Learn more at www.BlueSnap.com.
3. Problem Statement Introduction
Quality improvement needed in many organizations
Business case
• Identification of problem areas
• Selected improvement
• Decision
Quantified
• Costs & benefits
• Lead time to result
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 3
3
4. Quantification problems Introduction
Much time needed to gather data
Difficult to measure things
Hard to keep management commitment
Expensive
Required: Business case, with limited but sufficient
measurement effort, to gain management
commitment and funding
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 4
4
5. Affiliate Collaboration Introduction
SEI Pittsburgh, PA:
Software Engineering Measurement & Analysis Group
Ericsson Netherlands:
Market Unit Northern Europe & Main R&D Center
The Software Engineering Institute Affiliate Program provides
sponsoring organizations with an opportunity to contribute their best
ideas and people to a uniquely collaborative peer group who combine
their technical knowledge and experience to help define superior
software engineering practices.
Affiliates: http://www.sei.cmu.edu/collaborating/affiliates/affiliates.html
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 5
5
6. Two models Introduction
Defect Estimation Model Resident Defects in
Design Base
• Data, tuned with expert opinion Design Process
Competence, skills
Defects Inserted
(documentation,
Defect Density
Tools, environment code)
Estimate Fault Slip Through
Detection Rate
• Test Process
Competence, skills
Test Capacity
Defects Detected
(Inspection, test)
Fault Slip Through
Tools, environment Defect Classification
• Project/Product Quality Resident Defects in
Delivered Product
(Un)happy customers Process
Inputs and outputs
Influencing factors
Defect Level Measurement
Quality Factor Model
• Expert opinion, extend with data
• Quick Quality Scan
• Prediction Fault Slip Through
• Improvement Areas
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 6
6
7. Measuring quality Business
Cases
Insertion: Where are defects made? How to prevent?
Detection: Where are defects found? Early/economic removal?
Quality: How many defect are left in the product at release?
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 7
7
8. Process View Business
Cases
Resident Defects in
Design Base
Design Process Defects Inserted Defect Density
Competence, skills (documentation,
Tools, environment code)
Detection Rate
Test Process
Competence, skills Defects Detected Fault Slip Through
Test Capacity (Inspection, test)
Tools, environment Defect Classification
Resident Defects in (Un)happy customers Process
Delivered Product Inputs and outputs
Influencing factors
Defect Level Measurement
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 8
8
9. Fault Slip Through Business
Cases
Lead
??? Time
Cost
??? FST
Quality
???
Fault Slip Through = Number of defects detected in integration
& customer test that should have been detected earlier
“Should” implies that the defect is more cost effective to find earlier.
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 9
9
15. Quality performance assessment Agile Req.
Survey based upon Quality Factors
• 34 respondents from management & technical roles
• 4 management areas & 7 technical areas
2 sub questions for each quality factor:
• How relevant is the factor when we want to improve quality?
“little if any,” “moderate,” “substantial,” or “extensive,”
• How well are we doing currently?
“poor,” “fair,” “good,” and “excellent.”
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 15
15
17. Pilot “Business Case for Quality” Agile Req.
Context:
• Process management
• Quality steering
• Starting with Agile
Pilot: Agile for Requirements
• Calculate value of process change
• Run the pilot
• Evaluate the result
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 17
17
18. Improve: Requirements Stability Agile Req.
Requirements Stability – Inverse of the amount of requirement
changes over time. (The less changes, the higher stability.)
Agile deployment
• Backlog with Prioritized User Stories
• Product manager as Product Owner
• (Pre-) Planning game
• Architecture team
• Stand up meetings
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 18
18
19. Improve: Scope Stability Agile Req.
Scope Stability – Impact of major changes in projects that are
related to changes in the product roadmap, including stability of
the products to be developed, development teams involved in
projects, and major changes in project funding or delivery
dates.
Agile deployment
• Backlog
• Responsibility of Agile teams and Product Owner
• (Pre-) Planning game
• Retrospectives
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 19
19
20. Improve: Requirement Definition Agile Req.
Capability
Requirements Definition Capability – The skill and experience level
of the people doing requirements definition (e.g., product
managers).
Agile deployment
• (Pre-) Planning game
• Stand up meetings
• Collaborative Culture
• Retrospectives
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 20
20
21. Steering Agile Quality Agile Req.
• Estimate latent defects after demo (planning game)
• Collect defects during test (after demo).
• Classify defects:
• “introduction phase“
• “should have been detected phase”
• Root cause analysis: Prevention
• Decide improvement actions and communicate
• Re-estimate and predict release quality.
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 21
21
22. Results Agile for Requirements Agile Req.
• Very low number of requirement defects
• Previous projects also had a low number
• Based upon the data no conclusion could be drawn
Root Cause Analysis:
• understanding requirements increased:
planning game & stand-up meetings.
• Improvements from retrospectives increased cooperation
between development team and product owner.
Requirements quality performance increased!
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 22
22
23. Conclusions Conclusions
Quicker Business Case:
• Quality Factors/Performance
• Fault Slip Through
• Combining data and expert opinion
Improved Requirements Performance
• Agile increased requirements quality
• Less defects after release
• Increased flexibility and collaboration
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 23
23
24. More information Conclusions
Publications:
• Building Process Improvement Business Cases
SEI Technical Note: http://www.sei.cmu.edu/library/abstracts/reports/09tn017.cfm
• Controlling Project Performance by Using the Project Defect Model
in proceedings PSQT West Conference 2005
• The Business Benefit of Root Cause Analysis
in proceedings SM/ASM conference 2003
• SPI, the agile way!
To be presented at the SPIder conference, october 2009
www.spiderconferentie.nl
Contact:
• Email: benlinders@gmail.com
• http://www.linkedin.com/in/benlinders
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 24
24
26. Solution Introduction
Technologies
• Bayesian Belief Networks (BBN)
• Monte Carlo Simulation
• Root Cause Analysis
• Cost of Quality, Defect Slippage
Six Sigma DMAIC Approach
• Modeling Business Cases
• Research Quality Factors & quantify Quality Improvement
• Validate “Business Case for Quality”
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 26
26
27. Building a business case Business
Cases
Quality Quality Fault
Quality
Factor Slip
BBN Quality
Factor
Phase
Through
Performance
Factor
Quality
Factor
Historical
Industry
Project
Data
Data
Monte Current Improved
Quality Phase Quality Phase
Carlo Performance Performance
Subjective
Expert
Opinion
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 27
27
28. Bayes Belief Network (BBN) Business
Cases
• Probabilistic graphical model, to model uncertainty
• Diagnose and explain why an outcome happened
• Predict outcomes based on insight to one or more factors
Used:
• Modeling Quality Factors
• Predicting Quality Phase Performance
• What if Scenario
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 28
28
29. Monte Carlo Simulation Business
Cases
• Compute a result based on random sampling
• Modeling distributions of data
• Can make uncertainty visible
Used:
• Calculate value of process changes
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 29
29
30. Quality Prediction Business
Cases
Current Model: Estimation
• Extrapolate past performance
• Based on inserted/detected defects
• Plan & track
Wanted: Prediction
• Causes of defects
• What if Scenarios All models are wrong
• Decision taking
Some models are useful
Deming
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 30
30
31. Step 2: Defect Prediction Business
Cases
Fault Slip Through
Defect found in a (later) test phase that should have been found earlier
“Should”: More Cost effective (economical)
Predict Defect Reduction
• Determine process impact
• Simulate quality change
• Predict savings
Pilots
• Agile
• Model Driven Development
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 31
31
32. Quantify Quality Improvement Quality
Factors
Connect defect data with Quality performance
• Maximum quality factor => Industry best in class
Published industry data from various sources
• Distribution: Linear (keep it simple)
Extend BBN to calculate remaining defects after each phase
Result: Model for “what if scenario’s”
• Calculate defects in release products, when quality performance improves
• Cost of Quality data to calculate savings
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 32
32
33. Monte Carlo: Quality performance Quality
Factors
Monte Carlo simulation
• Input from 5 experts
• Estimated chance of occurrence and impact on FST (1-5 scale)
• Simulation done to calculate impact on quality factors
• Result used in BBN model to calculate effect on defect slippage
Expected result:
• Reduced number of requirement defects introduced
• Increased effectiveness of late testing phases
• Less defects in products shipped to customers
• Cost saving:
— Limited saving in the project
— Major saving during maintenance
Agile Requirements Agile Consortium Benelux, sep 30, 2009 (C) Ben Linders 33
33
Editor's Notes
After an agile pilot, ETM decided to fully roll out the agile way of working. All projects have setup cross functional teams, some including I&V. Stakeholders like product managers, system managers and projects managers enable that teams can produce the right software. Support functions, like CM, QA, CPI, and managers, and process responsibles are also using agile techniques, to prioritize work and deliver value to the projects. So how does this impact process management? This presentation shows that processes are still important at ETM, but in a different way: agile integrated into enhanced streamline development. The main goal here is to get an "every employee improving our value stream and efficiency continuously" environment/culture.
Color coded agenda, so that the audience can see where we are. Intro: Problem statement, approach as SE affiliate, overview of technologies used Business Cases: Defect slippage as target, overview of the BBN/Monte Carlo model Quality Factors: Details of the model, what influences quality Pilot: Survey to determine improvement area (BBN), agile improvement (Monte Carlo) Conclusions: Is this approach useful, what did we learn?
Link between improvement and a business case: Investment/benefit
Why the current approach doesn’t work. What do we need to solve it?
Show quickly to let the audience know that this was a collaboration (maybe too much text?)
Position Fault Slip Through as main indicator of Quality, since: Accepted within Ericsson Indicates significant savings Can also be used to get cost/time savings
First sheet of the Quality Factors part: Zoom into factors that determine quality. This is the BBN model. Overview of the Quality phases: Management factors Defect Insertion Defect detection Background. This model has been made to investigate quality improvement at Ericsson R&D The Netherlands. It includes quality factors that most probably will have an impact on quality at that development site. It is by no means intended to be a complete model, and different factors may be applicable for other companies.
Zoom into the 4 areas of management factors Explain shortly why the influence of strategic and operational line management is indirect (via project/process)
Shortly show the main phases in software development where potentially defects are included.
Show the main phases where defects are detected. Explain that defects left is input for the defects slippage (main indicator of quality).
Show some detail on how the quality phase performance is build up, example on code inspection.
How the assessment was done: Survey based SEI survey tool Questions reviewed with the SEI Representation of compete R&D flow 2 axes: Relevant & performance
Show some detail on how the quality phase performance is build up, example on code inspection.
First sheet of the pilot part of the presentation. Explain the 2 steps: Assessment to determine potential areas of improvement (BBN) Actual improvement (agile requirements), calculate & validate results
Very low number of requirement defects, from which Some on not yet release functionality (implemented later) Some due to changes in platform software, could not be prevented Only 1 defect which could have been prevented in planning game
Mention the technologies used, and that the project was run in a Six Sigma way.
Animated sheet! BBN technology is used to model the quality phase performance, based up Quality factors. This is used to models the target that we focus upon: defect slippage. Historical and industry data have been used to quantify the relationship between quality phase performance and fault slippage. The BBN models current performance. Based upon expert opinion, using Monte Carlo, a calculation is done of the quality phase performance after the improvement. This is fed into the BBN to calculate the impact on defect slippage, and the potential savings.
Explain how the Quality Phase performance is linked to defect slippage, though the use of industry and historical data. This will probably trigger questions, propose to discuss them after the presentation (BoF or …)?