Agile Bug Fixing (Zero Bug Policy)
•
1 like•1,714 views
The document discusses methods for preventing and triaging bugs in agile development, including placing bugs in the product backlog, fixing them in hardening sprints, using bug courts, and dedicating sprints to bugs. It also discusses metrics for tracking open bugs and implementing a zero bug policy by either fixing bugs immediately or closing them as "won't fix". The conclusions emphasize that bug fixing should be part of the engineering culture and that teams need balance between fixing bugs and sprint development.
Report
Share
Report
Share
Download to read offline
Recommended
Scaling Agile without frameworks
This document discusses scaling agile without frameworks and focuses on the limits of teams, products, and dependencies. It makes the following key points:
Focus and independence are limits to scaling. Too many products per team or teams per product lead to loss of focus and coordination challenges. Dependencies between teams introduce risks to integration.
Dividing products into independent sub-products and using techniques like Scrum of Scrums can help improve communication at scale. Release trains can synchronize teams but may slow overall delivery. Automating integrations is also suggested.
While frameworks like SAFe and Nexus are mentioned, the document emphasizes checking with the Agile Manifesto and discovering what the product is through techniques like Lean Startup before
How to Develop a DevOps Culture
This presentation provides perspectives on how to build a culture suitable for DevOps. What are principals to create an open, transparent culture.
How to make your design process agile
You know you need a great user experience, but you're on a deadline. Can you have good design at speed? Running a design sprint allows teams to utilise the best parts of agile, design thinking and 'gamestorming'. This talk will go over how to run a sprint successfully, with advice on pitfalls, breaking down departmental silos and how to adapt the process to fit your team.
Visual Studio 2012 Tips & Tricks
This document appears to be a presentation about Visual Studio tips and tricks. It discusses navigation, demos, debugging, extensions, Windows 8, and thanks the audience. It was given by Matteo Pagani, a Microsoft MVP and software engineer, and includes links to his website and Twitter account for further resources. The presentation notes it contains information as of a certain date and that Microsoft cannot guarantee the accuracy of any information after that date.
The road to potential shippable increments
This document outlines a 6 step program for a Scrum team to start delivering shippable software increments. The steps include: 1) learning the improvement kata to better focus retrospectives, 2) focusing on quality by implementing a zero-bug policy, 3) identifying and addressing bottlenecks to improve workflow, 4) making bottlenecks visible using work-in-progress limits, 5) anticipating bottlenecks early using service level agreements, and 6) composing the sprint backlog strategically using service level agreements. Implementing these steps has helped the team deliver higher quality, bug-free software more accurately and consistently compared to a year earlier.
10+ Testing Pitfalls and How to Avoid them
Join Joel Montvelisky, PractiTest's chief solution architect in this webinar as he takes you through the common pitfalls of testing you need to be aware of and how to avoid them.
Google’s 5-Day Design Sprint: Event 2 – DIVERGE (Conceptual Solutions/Sketches)
This presentation features the activity of "Diverge," which is the second stage of Google Ventures' Design Sprint (DS) Methodology. The presentation contains visual checklists as well as three case studies to facilitate application of the Design Sprint (DS) Methodology when solving big problems as well as testing new ideas.
Agile Bug Fixing: Priority! Backlog! Estimate!
Bugs should be prioritized and fixed immediately by the developer originally working on the topic. Bugs should be estimated along with the product backlog item and fixed within the same sprint. If not all bugs for a PBI are fixed, the PBI is not complete and does not count toward velocity. Late bugs found after implementation are new product backlog items. Teams should inspect and adapt their bug fixing process based on experience.
Recommended
Scaling Agile without frameworks
This document discusses scaling agile without frameworks and focuses on the limits of teams, products, and dependencies. It makes the following key points:
Focus and independence are limits to scaling. Too many products per team or teams per product lead to loss of focus and coordination challenges. Dependencies between teams introduce risks to integration.
Dividing products into independent sub-products and using techniques like Scrum of Scrums can help improve communication at scale. Release trains can synchronize teams but may slow overall delivery. Automating integrations is also suggested.
While frameworks like SAFe and Nexus are mentioned, the document emphasizes checking with the Agile Manifesto and discovering what the product is through techniques like Lean Startup before
How to Develop a DevOps Culture
This presentation provides perspectives on how to build a culture suitable for DevOps. What are principals to create an open, transparent culture.
How to make your design process agile
You know you need a great user experience, but you're on a deadline. Can you have good design at speed? Running a design sprint allows teams to utilise the best parts of agile, design thinking and 'gamestorming'. This talk will go over how to run a sprint successfully, with advice on pitfalls, breaking down departmental silos and how to adapt the process to fit your team.
Visual Studio 2012 Tips & Tricks
This document appears to be a presentation about Visual Studio tips and tricks. It discusses navigation, demos, debugging, extensions, Windows 8, and thanks the audience. It was given by Matteo Pagani, a Microsoft MVP and software engineer, and includes links to his website and Twitter account for further resources. The presentation notes it contains information as of a certain date and that Microsoft cannot guarantee the accuracy of any information after that date.
The road to potential shippable increments
This document outlines a 6 step program for a Scrum team to start delivering shippable software increments. The steps include: 1) learning the improvement kata to better focus retrospectives, 2) focusing on quality by implementing a zero-bug policy, 3) identifying and addressing bottlenecks to improve workflow, 4) making bottlenecks visible using work-in-progress limits, 5) anticipating bottlenecks early using service level agreements, and 6) composing the sprint backlog strategically using service level agreements. Implementing these steps has helped the team deliver higher quality, bug-free software more accurately and consistently compared to a year earlier.
10+ Testing Pitfalls and How to Avoid them
Join Joel Montvelisky, PractiTest's chief solution architect in this webinar as he takes you through the common pitfalls of testing you need to be aware of and how to avoid them.
Google’s 5-Day Design Sprint: Event 2 – DIVERGE (Conceptual Solutions/Sketches)
This presentation features the activity of "Diverge," which is the second stage of Google Ventures' Design Sprint (DS) Methodology. The presentation contains visual checklists as well as three case studies to facilitate application of the Design Sprint (DS) Methodology when solving big problems as well as testing new ideas.
Agile Bug Fixing: Priority! Backlog! Estimate!
Bugs should be prioritized and fixed immediately by the developer originally working on the topic. Bugs should be estimated along with the product backlog item and fixed within the same sprint. If not all bugs for a PBI are fixed, the PBI is not complete and does not count toward velocity. Late bugs found after implementation are new product backlog items. Teams should inspect and adapt their bug fixing process based on experience.
VISUAL_BASIC_LECTURE_NOTE_A_Z_MADE_EASY.pdf
This document contains lecture notes on error handling in Visual Basic .NET. It discusses the different types of errors that can occur, including syntax errors, logical errors, and run-time errors. It introduces exception handling in VB.NET using Try/Catch blocks to trap errors. Specific exception classes are described that can be used to trap different error types. Finally, it discusses using the Throw statement to raise custom exceptions. The notes provide an overview of using exceptions to prevent programs from crashing and make them more robust.
Lean Software Development & Kanban
Rishi Chaddha introduces lean software development principles. He discusses the origins of lean from the Toyota Production System and its focus on eliminating waste. The presentation then covers the seven principles of lean software development which include eliminating waste, building quality in, deferring commitment, delivering fast, respecting people, and optimizing the whole. Kanban and various agile practices are presented as tools that can be mixed and matched to implement lean ideas.
Shape Up Your Agility
The way a development team operates has a huge impact on what it achieves. The methodologies used, practices, cross-functionality within the team, and communication styles, all have a definite impact on building the foundations of the team and the successful execution of a project. From estimations, resource management, managing project costs, keeping track of tickets on different boards, encouraging faster and smoother communication, adapting to change requests and everything else that it entails, every development team struggles to keep everything on track. And to be honest, no methodology seems to fit right and at times, we are left to wonder, do these methods actually make an impact? You find yourself busy with making estimations that don't match, reports that are far different from the forecast, you see your team moving tickets without a proper understanding of the end goal of the product, and trying to keep a clear line of communication within the team and with the client. Have you been frantically searching for a method that collects the pros from different methodologies and empowers the team to execute a project faster and better without losing sight of the business aspect of the product? Join and discover.
Originate - Think In Hours Not Sprints
Why software will never be the same... Discuss why agile and lean development methodologies alone are not enough to compete in today's software startup market. Explore real-time prototyping and minimal viable experiments that can accelerate learning down to hours, not sprints.
Starting Agile in a Company
The document provides tips for organizing teams, projects, and support when adopting Agile in a company. It recommends splitting the organization into cross-functional feature teams and creating a backlog of prioritized product features for each team to work on. Teams should be kept together permanently to become high-performing. Support work should also be planned and prioritized in the backlog instead of handled reactively to reduce fires and bugs. The document stresses starting the transition now with courage and external help if needed.
Product owners-manual
This document provides advice for new product owners on their role and responsibilities in Scrum. It discusses establishing a clear product vision through collaboration. An effective vision should describe the target customer and value proposition in a concise, memorable way. It also covers principles for effective story writing like defining requirements of ready and focusing on user experience. Release planning techniques like story mapping and calculating team velocity are presented. The document emphasizes that an empowered, dedicated product owner with a strong vision is key to achieving great results with Scrum.
Debugging
The document discusses debugging processes and techniques. It defines debugging as the process of finding, correcting and removing bugs from programs. There are three main types of errors: syntactic, semantic, and logic errors. The debugging process involves reproducing the problem reliably, finding the source of the error, fixing just that one error, testing the fix, and optionally looking for more errors. Key debugging techniques include inserting print statements, using a debugger, explaining the code to someone else, and fixing only one error at a time. The overall goal of debugging is to methodically match symptoms to causes to locate and correct errors in code.
Kaizen in Action for Regional Scrum Gathering Tokyo 2017
Presentation slides for "Kaizen in Action" session in Regional Scrum Gathering on Jan 12th and 13th, 2017.
#RGST2017
Believe it or not - keynote CAS 2015
The document discusses various topics related to software development practices including Scrum, pair programming, test-driven development, and studies on project success rates. It questions some commonly held beliefs and presents alternative perspectives. For example, it notes that while co-located work seems more productive, remote work can be effective if certain techniques are used. Studies on practices like pair programming and TDD have had mixed results. It cautions against making definitive conclusions from correlations without considering other factors and possibilities of bias.
Software engineering for CEOs ch1
The start of 'What you should know about building software if you work at a software company', Chapter 1 covers Problem #1, communication time.
Failing With Agile
Presentation for Mile High PMI Workshop on November 15, 2008
Abstract:
There are always people who want agile projects to fail. This will probably be the case until agile is the preferred process methodology used for projects. Are you one of them? In this workshop Bob Hartman will give participants a how-to guide for causing agile process failure. Attendees will learn various failure modes and how to cause them. There will be group discussions and exercises exploring how the failure modes can manifest themselves in real projects. At the end of this workshop each attendee should have the ability to cause agile project failure in a variety of ways and under a variety of conditions.
Obviously the first paragraph is a bit tongue-in-cheek. Hopefully project managers do not want agile projects to fail, but they need to know how they could fail. This knowledge will translate into an ability to recognize the failure modes and take corrective action. Interestingly, many of the agile project failure modes are also failure modes in other project process methodologies. All project managers on agile projects or in organizations that are considering using an agile process should attend this workshop. Project managers in organizations which typically struggle with projects may also gain insight into their project failure modes.
152-3 Lean six sigma gets you from coping to solving operational problems
152-3 Lean six sigma gets you from coping to solving operational problemsFrancisco Pulgar-Vidal, MBA, Lean Six Sigma MBB
The document discusses how Lean Six Sigma is better than just doing typical projects for solving operational problems. Lean Six Sigma is designed to discover the root cause of problems and find sustainable solutions, whereas most projects just implement known solutions. Lean Six Sigma uses a structured approach to explore and analyze problems, then discover and implement the best solution. It encourages organizations to stop just coping with problems and start solving them systematically using Lean Six Sigma. The four main types of operational problems Lean Six Sigma can address are things taking too long, too many errors, overly complex ways of working, and high costs.Agile and scrum masterclass
The document describes an Agile and Scrum Masterclass training program. The program provides a comprehensive overview of Agile and Scrum frameworks through 20 modules taught over 9 days of self-paced learning. Students will learn practical skills for roles like Product Owner and Scrum Master, and prepare for Scrum certifications. The training also uses case studies and examples to illustrate how Scrum is applied in real-life projects.
Design Sprint 3.0 vs Design Sprint 1.0 (SPRINT Book)
The document compares Design Sprint 1.0 and 3.0, which are processes for solving problems and launching new products. Design Sprint 1.0 is a 5-phase process useful for startups to reduce risks when launching new products, while Design Sprint 3.0 is a 6-phase process for enterprises to solve complex business and customer problems. The key differences are that 3.0 includes an additional problem framing phase, involves stakeholders earlier, and aims to gain alignment on core business opportunities.
Maheen oop
The document discusses exceptions and exception handling in programs. It defines an exception as a problem that arises during program execution, such as attempting to divide by zero. Exception handling allows programs to respond to errors in a more organized way using try and catch blocks. It describes four approaches programs can take to respond to errors: crashing, informing the user and exiting, informing the user to attempt recovery, or taking corrective action without disturbing the user. The key aspects of exception handling are try blocks to detect where exceptions may occur, catch blocks to determine the type of exception and how to handle it, and throw to raise an exception from anywhere in the code.
7 types of mistake proofing systems that improve product quality
Read this blog post by copying and pasting this link into your browser: http://www.cmc-consultants.com/blog/7-types-of-mistake-proofing-systems-that-improve-product-quality
Chinese factory managers often say things such as “these three people caused this issue”, “it is their fault”, and “these are human mistakes and they can’t be avoided”. However, one could argue that the factory’s systems are at fault. And who can develop and implement systems? The managers themselves, not their employees.
Which systems need to be put in place to avoid mistakes and improve product quality? Let’s look into 7 mistake proofing approaches that work...
Agile pitfalls
This document discusses testing perspectives and pitfalls related to agile methodologies. It begins by noting that while entire programs adopt agile, testing often still uses traditional approaches. It proposes an agile testing manifesto modeled after the original agile manifesto. Common pitfalls are then outlined, including only partially implementing agile, unrealistic expectations of automation, and abuse of agile principles. The document concludes by stating that great flexibility in agile requires great discipline to fully realize its benefits.
Agile Lean Conference 2016 - Buglione_Lean for (being) Agile
This document discusses measurement practices for Lean and Agile approaches. It presents an agenda covering introduction topics on Lean, Agile and measurement; best practices including requirements elicitation and management, sizing units, estimation, monitoring and control; and conclusions. The goal is to analyze common measurement practices, discuss potential issues, and propose countermeasures to strengthen measurement in Lean-Agile teams and projects.
bug-advocacy
The document discusses techniques for software testers to advocate for bugs they have found to get them prioritized and fixed. It recommends testers think of bug reports as tools to convince programmers to spend time fixing issues. Effective bug reports motivate programmers by highlighting impact and addressing objections. Testers should research failure conditions thoroughly by varying their own behavior, program options/settings, and software/hardware environments to prove bugs are more serious or widespread than initially found. The goal is to provide compelling arguments to prioritize and fix bugs.
6 easy bug tracking tips & tricks every developer should know!
When it comes to bug tracking there’s a lot of discipline required from everybody involved.
Tracking & solving bugs encourages everyone involved to stand to the rules. Especially in creative- & startup-driven industries it can be pretty hard to discourage any informal communication. Bug tracking isn't that much fun. But promise me: it can be super-fun.
I’d like to present you 6 simple bug tracking tips for your next bug tracking project, which will help you feel way more comfortable while tracking & fixing bugs.
According to Technopedia bug tracking is defined as:
"...a process used by quality assurance personnel and programmers to keep track of software problems and resolutions.”
Therefore a bug tracking tool stores all the information about reported bugs and keeps track of the status of each bug. You definitely see the need of extensive information while tracking bugs.
For further read, I recommend the following blog posts:
>> surprisingly easy bug tracking hacks: http://usersnap.com/blog/easy-bug-tracking-hacks-developers/
>> How to set up a bug-free environment: http://usersnap.com/blog/bug-free-development-environment/
Mejorando Scrum, un Sprint a la vez
Daniel Dominguez presentó cómo Bunny Inc. mejoró su proceso de desarrollo de software al implementar Scrum, dividiendo su equipo en grupos más pequeños y asignando roles como Product Owner y Scrum Master. Analizó cuatro equipos Scrum internos que realizaron múltiples sprints y aprendieron lecciones sobre estimaciones, calidad y estrictamente de Scrum. Concluyó que Scrum les permitió medir mejor el desempeño del equipo y encontrar nuevas métricas.
Doing UX in an Agile World
Agile UX involves incorporating UX design methods into agile software development methodologies. Traditional UX design operates separately from development in a more linear fashion, while agile UX integrates design and development in short iterative cycles. The document discusses how lean UX focuses on applying UX methods in dynamic startup environments, while agile UX updates existing agile software methods to include UX design processes and deliverables.
More Related Content
Similar to Agile Bug Fixing (Zero Bug Policy)
VISUAL_BASIC_LECTURE_NOTE_A_Z_MADE_EASY.pdf
This document contains lecture notes on error handling in Visual Basic .NET. It discusses the different types of errors that can occur, including syntax errors, logical errors, and run-time errors. It introduces exception handling in VB.NET using Try/Catch blocks to trap errors. Specific exception classes are described that can be used to trap different error types. Finally, it discusses using the Throw statement to raise custom exceptions. The notes provide an overview of using exceptions to prevent programs from crashing and make them more robust.
Lean Software Development & Kanban
Rishi Chaddha introduces lean software development principles. He discusses the origins of lean from the Toyota Production System and its focus on eliminating waste. The presentation then covers the seven principles of lean software development which include eliminating waste, building quality in, deferring commitment, delivering fast, respecting people, and optimizing the whole. Kanban and various agile practices are presented as tools that can be mixed and matched to implement lean ideas.
Shape Up Your Agility
The way a development team operates has a huge impact on what it achieves. The methodologies used, practices, cross-functionality within the team, and communication styles, all have a definite impact on building the foundations of the team and the successful execution of a project. From estimations, resource management, managing project costs, keeping track of tickets on different boards, encouraging faster and smoother communication, adapting to change requests and everything else that it entails, every development team struggles to keep everything on track. And to be honest, no methodology seems to fit right and at times, we are left to wonder, do these methods actually make an impact? You find yourself busy with making estimations that don't match, reports that are far different from the forecast, you see your team moving tickets without a proper understanding of the end goal of the product, and trying to keep a clear line of communication within the team and with the client. Have you been frantically searching for a method that collects the pros from different methodologies and empowers the team to execute a project faster and better without losing sight of the business aspect of the product? Join and discover.
Originate - Think In Hours Not Sprints
Why software will never be the same... Discuss why agile and lean development methodologies alone are not enough to compete in today's software startup market. Explore real-time prototyping and minimal viable experiments that can accelerate learning down to hours, not sprints.
Starting Agile in a Company
The document provides tips for organizing teams, projects, and support when adopting Agile in a company. It recommends splitting the organization into cross-functional feature teams and creating a backlog of prioritized product features for each team to work on. Teams should be kept together permanently to become high-performing. Support work should also be planned and prioritized in the backlog instead of handled reactively to reduce fires and bugs. The document stresses starting the transition now with courage and external help if needed.
Product owners-manual
This document provides advice for new product owners on their role and responsibilities in Scrum. It discusses establishing a clear product vision through collaboration. An effective vision should describe the target customer and value proposition in a concise, memorable way. It also covers principles for effective story writing like defining requirements of ready and focusing on user experience. Release planning techniques like story mapping and calculating team velocity are presented. The document emphasizes that an empowered, dedicated product owner with a strong vision is key to achieving great results with Scrum.
Debugging
The document discusses debugging processes and techniques. It defines debugging as the process of finding, correcting and removing bugs from programs. There are three main types of errors: syntactic, semantic, and logic errors. The debugging process involves reproducing the problem reliably, finding the source of the error, fixing just that one error, testing the fix, and optionally looking for more errors. Key debugging techniques include inserting print statements, using a debugger, explaining the code to someone else, and fixing only one error at a time. The overall goal of debugging is to methodically match symptoms to causes to locate and correct errors in code.
Kaizen in Action for Regional Scrum Gathering Tokyo 2017
Presentation slides for "Kaizen in Action" session in Regional Scrum Gathering on Jan 12th and 13th, 2017.
#RGST2017
Believe it or not - keynote CAS 2015
The document discusses various topics related to software development practices including Scrum, pair programming, test-driven development, and studies on project success rates. It questions some commonly held beliefs and presents alternative perspectives. For example, it notes that while co-located work seems more productive, remote work can be effective if certain techniques are used. Studies on practices like pair programming and TDD have had mixed results. It cautions against making definitive conclusions from correlations without considering other factors and possibilities of bias.
Software engineering for CEOs ch1
The start of 'What you should know about building software if you work at a software company', Chapter 1 covers Problem #1, communication time.
Failing With Agile
Presentation for Mile High PMI Workshop on November 15, 2008
Abstract:
There are always people who want agile projects to fail. This will probably be the case until agile is the preferred process methodology used for projects. Are you one of them? In this workshop Bob Hartman will give participants a how-to guide for causing agile process failure. Attendees will learn various failure modes and how to cause them. There will be group discussions and exercises exploring how the failure modes can manifest themselves in real projects. At the end of this workshop each attendee should have the ability to cause agile project failure in a variety of ways and under a variety of conditions.
Obviously the first paragraph is a bit tongue-in-cheek. Hopefully project managers do not want agile projects to fail, but they need to know how they could fail. This knowledge will translate into an ability to recognize the failure modes and take corrective action. Interestingly, many of the agile project failure modes are also failure modes in other project process methodologies. All project managers on agile projects or in organizations that are considering using an agile process should attend this workshop. Project managers in organizations which typically struggle with projects may also gain insight into their project failure modes.
152-3 Lean six sigma gets you from coping to solving operational problems
152-3 Lean six sigma gets you from coping to solving operational problemsFrancisco Pulgar-Vidal, MBA, Lean Six Sigma MBB
The document discusses how Lean Six Sigma is better than just doing typical projects for solving operational problems. Lean Six Sigma is designed to discover the root cause of problems and find sustainable solutions, whereas most projects just implement known solutions. Lean Six Sigma uses a structured approach to explore and analyze problems, then discover and implement the best solution. It encourages organizations to stop just coping with problems and start solving them systematically using Lean Six Sigma. The four main types of operational problems Lean Six Sigma can address are things taking too long, too many errors, overly complex ways of working, and high costs.Agile and scrum masterclass
The document describes an Agile and Scrum Masterclass training program. The program provides a comprehensive overview of Agile and Scrum frameworks through 20 modules taught over 9 days of self-paced learning. Students will learn practical skills for roles like Product Owner and Scrum Master, and prepare for Scrum certifications. The training also uses case studies and examples to illustrate how Scrum is applied in real-life projects.
Design Sprint 3.0 vs Design Sprint 1.0 (SPRINT Book)
The document compares Design Sprint 1.0 and 3.0, which are processes for solving problems and launching new products. Design Sprint 1.0 is a 5-phase process useful for startups to reduce risks when launching new products, while Design Sprint 3.0 is a 6-phase process for enterprises to solve complex business and customer problems. The key differences are that 3.0 includes an additional problem framing phase, involves stakeholders earlier, and aims to gain alignment on core business opportunities.
Maheen oop
The document discusses exceptions and exception handling in programs. It defines an exception as a problem that arises during program execution, such as attempting to divide by zero. Exception handling allows programs to respond to errors in a more organized way using try and catch blocks. It describes four approaches programs can take to respond to errors: crashing, informing the user and exiting, informing the user to attempt recovery, or taking corrective action without disturbing the user. The key aspects of exception handling are try blocks to detect where exceptions may occur, catch blocks to determine the type of exception and how to handle it, and throw to raise an exception from anywhere in the code.
7 types of mistake proofing systems that improve product quality
Read this blog post by copying and pasting this link into your browser: http://www.cmc-consultants.com/blog/7-types-of-mistake-proofing-systems-that-improve-product-quality
Chinese factory managers often say things such as “these three people caused this issue”, “it is their fault”, and “these are human mistakes and they can’t be avoided”. However, one could argue that the factory’s systems are at fault. And who can develop and implement systems? The managers themselves, not their employees.
Which systems need to be put in place to avoid mistakes and improve product quality? Let’s look into 7 mistake proofing approaches that work...
Agile pitfalls
This document discusses testing perspectives and pitfalls related to agile methodologies. It begins by noting that while entire programs adopt agile, testing often still uses traditional approaches. It proposes an agile testing manifesto modeled after the original agile manifesto. Common pitfalls are then outlined, including only partially implementing agile, unrealistic expectations of automation, and abuse of agile principles. The document concludes by stating that great flexibility in agile requires great discipline to fully realize its benefits.
Agile Lean Conference 2016 - Buglione_Lean for (being) Agile
This document discusses measurement practices for Lean and Agile approaches. It presents an agenda covering introduction topics on Lean, Agile and measurement; best practices including requirements elicitation and management, sizing units, estimation, monitoring and control; and conclusions. The goal is to analyze common measurement practices, discuss potential issues, and propose countermeasures to strengthen measurement in Lean-Agile teams and projects.
bug-advocacy
The document discusses techniques for software testers to advocate for bugs they have found to get them prioritized and fixed. It recommends testers think of bug reports as tools to convince programmers to spend time fixing issues. Effective bug reports motivate programmers by highlighting impact and addressing objections. Testers should research failure conditions thoroughly by varying their own behavior, program options/settings, and software/hardware environments to prove bugs are more serious or widespread than initially found. The goal is to provide compelling arguments to prioritize and fix bugs.
6 easy bug tracking tips & tricks every developer should know!
When it comes to bug tracking there’s a lot of discipline required from everybody involved.
Tracking & solving bugs encourages everyone involved to stand to the rules. Especially in creative- & startup-driven industries it can be pretty hard to discourage any informal communication. Bug tracking isn't that much fun. But promise me: it can be super-fun.
I’d like to present you 6 simple bug tracking tips for your next bug tracking project, which will help you feel way more comfortable while tracking & fixing bugs.
According to Technopedia bug tracking is defined as:
"...a process used by quality assurance personnel and programmers to keep track of software problems and resolutions.”
Therefore a bug tracking tool stores all the information about reported bugs and keeps track of the status of each bug. You definitely see the need of extensive information while tracking bugs.
For further read, I recommend the following blog posts:
>> surprisingly easy bug tracking hacks: http://usersnap.com/blog/easy-bug-tracking-hacks-developers/
>> How to set up a bug-free environment: http://usersnap.com/blog/bug-free-development-environment/
Similar to Agile Bug Fixing (Zero Bug Policy) (20)
Kaizen in Action for Regional Scrum Gathering Tokyo 2017
Kaizen in Action for Regional Scrum Gathering Tokyo 2017
152-3 Lean six sigma gets you from coping to solving operational problems
152-3 Lean six sigma gets you from coping to solving operational problems
Design Sprint 3.0 vs Design Sprint 1.0 (SPRINT Book)
Design Sprint 3.0 vs Design Sprint 1.0 (SPRINT Book)
7 types of mistake proofing systems that improve product quality
7 types of mistake proofing systems that improve product quality
Agile Lean Conference 2016 - Buglione_Lean for (being) Agile
Agile Lean Conference 2016 - Buglione_Lean for (being) Agile
6 easy bug tracking tips & tricks every developer should know!
6 easy bug tracking tips & tricks every developer should know!
More from Daniel Dominguez
Mejorando Scrum, un Sprint a la vez
Daniel Dominguez presentó cómo Bunny Inc. mejoró su proceso de desarrollo de software al implementar Scrum, dividiendo su equipo en grupos más pequeños y asignando roles como Product Owner y Scrum Master. Analizó cuatro equipos Scrum internos que realizaron múltiples sprints y aprendieron lecciones sobre estimaciones, calidad y estrictamente de Scrum. Concluyó que Scrum les permitió medir mejor el desempeño del equipo y encontrar nuevas métricas.
Doing UX in an Agile World
Agile UX involves incorporating UX design methods into agile software development methodologies. Traditional UX design operates separately from development in a more linear fashion, while agile UX integrates design and development in short iterative cycles. The document discusses how lean UX focuses on applying UX methods in dynamic startup environments, while agile UX updates existing agile software methods to include UX design processes and deliverables.
Planeación Estratégica
El documento describe los pasos para realizar una planeación estratégica, incluyendo un análisis FODA para evaluar las fortalezas, oportunidades, debilidades y amenazas de una organización. Explica que el análisis FODA permite conocer la situación actual y tomar decisiones acordes a los objetivos. Luego, guía cómo realizar el análisis FODA identificando variables internas y externas, y finalmente pregunta cómo aprovechar las fortalezas y oportunidades y cómo reducir las debilidades y amenazas.
Códigos QR
Este documento describe los códigos QR, que son sistemas bidimensionales para almacenar información que pueden ser leídos por dispositivos móviles. Fueron creados en 1994 y pueden almacenar hasta 7000 caracteres. Se usan comúnmente para compartir enlaces, contactos, boletos y más. Existen numerosas aplicaciones para generar y leer códigos QR tanto en la web como en dispositivos móviles.
Nuevas aplicaciones en tecnología móvil
El documento habla sobre las nuevas aplicaciones en tecnología móvil y la tendencia creciente hacia el uso de dispositivos móviles como medios de comunicación e información. Explica que las aplicaciones móviles facilitan el acceso a la información y que el marketing móvil permite segmentar mercados y conectar marcas con clientes a través de sus dispositivos personales.
i-azul "QR Codes" (2009) - Español
Un código QR es un sistema para almacenar información en una matriz de puntos bidimensional que permite leer los datos contenidos mediante un dispositivo móvil. Se puede generar códigos QR de forma gratuita en sitios web o descargando programas, e incluyen opciones para codificar texto, enlaces, números y más. Del mismo modo, existen aplicaciones móviles, de escritorio y web para leer los códigos QR usando la cámara del dispositivo. Los códigos QR son ampliamente usados para compartir información suplementaria,
Paper (2007) - English
The document describes the development of a 3D virtual simulator for the Khepera II mobile robot. The mathematical models for the robot's kinematics, dynamics, and geometry were programmed in Matlab Simulink. The VRML toolbox was used to visualize the models in 3D and create a virtual environment. The virtual robot behaves according to the real robot's programmed models. This allows controlling the real robot and observing its movements and position in virtual space. The integrated simulator provides an interface for studying the robot's performance in realistic simulated scenarios.
Proyecto De Grado (2005) - Español
El objetivo principal del proyecto fue diseñar y construir un robot móvil explorador controlado mediante una computadora portátil Palm. El proyecto involucró tres etapas: 1) el diseño mecánico y construcción del robot móvil, 2) la programación del robot en el software de la Palm para realizar recorridos definidos y aleatorios, y 3) la interacción entre la Palm y el robot utilizando protocolos de comunicación serial para transmitir instrucciones desde la Palm al microcontrolador del robot. El proyecto demostró la viabilidad de utilizar
Proyecto De Grado (2005) - Español
El documento describe el diseño y construcción de un robot móvil explorador controlado por una computadora de mano Palm. El robot tiene ruedas con tracción independiente y sensores, y la Palm programa su movimiento y exploración a través de protocolos de comunicación serial. El software de la Palm controla el robot mediante ventanas interactivas y permite al usuario seleccionar programas de exploración. El proyecto logró una interfaz efectiva entre el robot, la Palm y el usuario para control remoto y recolección de datos durante la exploración.
i-azul Slide (2009)
Este documento presenta a Daniel Domínguez, un ingeniero en mecatrónica y gerente general de i-azul Ltda, una empresa colombiana de desarrollo de aplicaciones para tecnología móvil. La empresa ofrece servicios como SDK, códigos QR, almacenamiento de información y marketing de proximidad a través de publicidad Bluetooth para hacer accesible la información desde y hacia dispositivos móviles. El marketing de proximidad permite distribuir contenido publicitario a dispositivos Bluetooth cercanos de forma segmentada y efectiva.
More from Daniel Dominguez (12)
Recently uploaded
The Power of Visual Regression Testing_ Why It Is Critical for Enterprise App...
Visual testing plays a vital role in ensuring that software products meet the aesthetic requirements specified by clients in functional and non-functional specifications. In today's highly competitive digital landscape, users expect a seamless and visually appealing online experience. Visual testing, also known as automated UI testing or visual regression testing, verifies the accuracy of the visual elements that users interact with.
Upturn India Technologies - Web development company in Nashik
Nashik's top web development company, Upturn India Technologies, crafts innovative digital solutions for your success. Partner with us and achieve your goals
Alluxio Webinar | 10x Faster Trino Queries on Your Data Platform
Alluxio Webinar
June. 18, 2024
For more Alluxio Events: https://www.alluxio.io/events/
Speaker:
- Jianjian Xie (Staff Software Engineer, Alluxio)
As Trino users increasingly rely on cloud object storage for retrieving data, speed and cloud cost have become major challenges. The separation of compute and storage creates latency challenges when querying datasets; scanning data between storage and compute tiers becomes I/O bound. On the other hand, cloud API costs related to GET/LIST operations and cross-region data transfer add up quickly.
The newly introduced Trino file system cache by Alluxio aims to overcome the above challenges. In this session, Jianjian will dive into Trino data caching strategies, the latest test results, and discuss the multi-level caching architecture. This architecture makes Trino 10x faster for data lakes of any scale, from GB to EB.
What you will learn:
- Challenges relating to the speed and costs of running Trino in the cloud
- The new Trino file system cache feature overview, including the latest development status and test results
- A multi-level cache framework for maximized speed, including Trino file system cache and Alluxio distributed cache
- Real-world cases, including a large online payment firm and a top ridesharing company
- The future roadmap of Trino file system cache and Trino-Alluxio integration
如何办理(hull学位证书)英国赫尔大学毕业证硕士文凭原版一模一样
原版定制【微信:bwp0011】《(hull学位证书)英国赫尔大学毕业证硕士文凭》【微信:bwp0011】成绩单 、雅思、外壳、留信学历认证永久存档查询，采用学校原版纸张、特殊工艺完全按照原版一比一制作（包括：隐形水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠，文字图案浮雕，激光镭射，紫外荧光，温感，复印防伪）行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备，十五年致力于帮助留学生解决难题，业务范围有加拿大、英国、澳洲、韩国、美国、新加坡，新西兰等学历材料，包您满意。
【业务选择办理准则】
一、工作未确定，回国需先给父母、亲戚朋友看下文凭的情况，办理一份就读学校的毕业证【微信bwp0011】文凭即可
二、回国进私企、外企、自己做生意的情况，这些单位是不查询毕业证真伪的，而且国内没有渠道去查询国外文凭的真假，也不需要提供真实教育部认证。鉴于此，办理一份毕业证【微信bwp0011】即可
三、进国企，银行，事业单位，考公务员等等，这些单位是必需要提供真实教育部认证的，办理教育部认证所需资料众多且烦琐，所有材料您都必须提供原件，我们凭借丰富的经验，快捷的绿色通道帮您快速整合材料，让您少走弯路。
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
【关于价格问题（保证一手价格）】
我们所定的价格是非常合理的，而且我们现在做得单子大多数都是代理和回头客户介绍的所以一般现在有新的单子 我给客户的都是第一手的代理价格，因为我想坦诚对待大家 不想跟大家在价格方面浪费时间
对于老客户或者被老客户介绍过来的朋友，我们都会适当给一些优惠。
Optimizing Your E-commerce with WooCommerce.pptx
Learn how WooCommerce can transform your WordPress site into a powerful and flexible e-commerce store.
Ensuring Efficiency and Speed with Practical Solutions for Clinical Operations
Clinical operations professionals encounter unique challenges. Balancing regulatory requirements, tight timelines, and the need for cross-functional collaboration can create significant internal pressures. Our upcoming webinar will introduce key strategies and tools to streamline and enhance clinical development processes, helping you overcome these challenges.
Strengthening Web Development with CommandBox 6: Seamless Transition and Scal...
Strengthening Web Development with CommandBox 6: Seamless Transition and Scal...Ortus Solutions, Corp
Join us for a session exploring CommandBox 6’s smooth website transition and efficient deployment. CommandBox revolutionizes web development, simplifying tasks across Linux, Windows, and Mac platforms. Gain insights and practical tips to enhance your development workflow.
Come join us for an enlightening session where we delve into the smooth transition of current websites and the efficient deployment of new ones using CommandBox 6. CommandBox has revolutionized web development, consistently introducing user-friendly enhancements that catalyze progress in the field. During this presentation, we’ll explore CommandBox’s rich history and showcase its unmatched capabilities within the realm of ColdFusion, covering both major variations.
The journey of CommandBox has been one of continuous innovation, constantly pushing boundaries to simplify and optimize development processes. Regardless of whether you’re working on Linux, Windows, or Mac platforms, CommandBox empowers developers to streamline tasks with unparalleled ease.
In our session, we’ll illustrate the simple process of transitioning existing websites to CommandBox 6, highlighting its intuitive features and seamless integration. Moreover, we’ll unveil the potential for effortlessly deploying multiple websites, demonstrating CommandBox’s versatility and adaptability.
Join us on this journey through the evolution of web development, guided by the transformative power of CommandBox 6. Gain invaluable insights, practical tips, and firsthand experiences that will enhance your development workflow and embolden your projects.🏎️Tech Transformation: DevOps Insights from the Experts 👩💻
Connect with fellow Trailblazers, learn from industry experts Glenda Thomson (Salesforce, Principal Technical Architect) and Will Dinn (Judo Bank, Salesforce Development Lead), and discover how to harness DevOps tools with Salesforce.
Operational ease MuleSoft and Salesforce Service Cloud Solution v1.0.pptx
Operational ease MuleSoft and Salesforce Service Cloud Solution v1.0
The Comprehensive Guide to Validating Audio-Visual Performances.pdf
Ensuring the optimal performance of your audio-visual (AV) equipment is crucial for delivering exceptional experiences. AV performance validation is a critical process that verifies the quality and functionality of your AV setup. Whether you're a content creator, a business conducting webinars, or a homeowner creating a home theater, validating your AV performance is essential.
What’s New in VictoriaLogs - Q2 2024 Update
These are the slides of the presentation given during the Q2 2024 Virtual VictoriaMetrics Meetup. View the recording here: https://www.youtube.com/watch?v=hzlMA_Ae9_4&t=206s
Topics covered:
1. What is VictoriaLogs
Open source database for logs
● Easy to setup and operate - just a single executable with sane default configs
● Works great with both structured and plaintext logs
● Uses up to 30x less RAM and up to 15x disk space than Elasticsearch
● Provides simple yet powerful query language for logs - LogsQL
2. Improved querying HTTP API
3. Data ingestion via Syslog protocol
* Automatic parsing of Syslog fields
* Supported transports:
○ UDP
○ TCP
○ TCP+TLS
* Gzip and deflate compression support
* Ability to configure distinct TCP and UDP ports with distinct settings
* Automatic log streams with (hostname, app_name, app_id) fields
4. LogsQL improvements
● Filtering shorthands
● week_range and day_range filters
● Limiters
● Log analytics
● Data extraction and transformation
● Additional filtering
● Sorting
5. VictoriaLogs Roadmap
● Accept logs via OpenTelemetry protocol
● VMUI improvements based on HTTP querying API
● Improve Grafana plugin for VictoriaLogs -
https://github.com/VictoriaMetrics/victorialogs-datasource
● Cluster version
○ Try single-node VictoriaLogs - it can replace 30-node Elasticsearch cluster in production
● Transparent historical data migration to object storage
○ Try single-node VictoriaLogs with persistent volumes - it compresses 1TB of production logs from
Kubernetes to 20GB
● See https://docs.victoriametrics.com/victorialogs/roadmap/
Try it out: https://victoriametrics.com/products/victorialogs/
Secure-by-Design Using Hardware and Software Protection for FDA Compliance
This webinar explores the “secure-by-design” approach to medical device software development. During this important session, we will outline which security measures should be considered for compliance, identify technical solutions available on various hardware platforms, summarize hardware protection methods you should consider when building in security and review security software such as Trusted Execution Environments for secure storage of keys and data, and Intrusion Detection Protection Systems to monitor for threats.
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdf
IBM watsonx Code Assistant for Z, our latest Generative AI-assisted mainframe application modernization solution. Mainframe (IBM Z) application modernization is a topic that every mainframe client is addressing to various degrees today, driven largely from digital transformation. With generative AI comes the opportunity to reimagine the mainframe application modernization experience. Infusing generative AI will enable speed and trust, help de-risk, and lower total costs associated with heavy-lifting application modernization initiatives. This document provides an overview of the IBM watsonx Code Assistant for Z which uses the power of generative AI to make it easier for developers to selectively modernize COBOL business services while maintaining mainframe qualities of service.
Call Girls Bangalore🔥7023059433🔥Best Profile Escorts in Bangalore Available 24/7
Call Girls Bangalore🔥7023059433🔥Best Profile Escorts in Bangalore Available 24/7
Building API data products on top of your real-time data infrastructure
This talk and live demonstration will examine how Confluent and Gravitee.io integrate to unlock value from streaming data through API products.
You will learn how data owners and API providers can document, secure data products on top of Confluent brokers, including schema validation, topic routing and message filtering.
You will also see how data and API consumers can discover and subscribe to products in a developer portal, as well as how they can integrate with Confluent topics through protocols like REST, Websockets, Server-sent Events and Webhooks.
Whether you want to monetize your real-time data, enable new integrations with partners, or provide self-service access to topics through various protocols, this webinar is for you!
A Comprehensive Guide on Implementing Real-World Mobile Testing Strategies fo...
In today's fiercely competitive mobile app market, the role of the QA team is pivotal for continuous improvement and sustained success. Effective testing strategies are essential to navigate the challenges confidently and precisely. Ensuring the perfection of mobile apps before they reach end-users requires thoughtful decisions in the testing plan.
Hands-on with Apache Druid: Installation & Data Ingestion Steps
Supercharge your analytics workflow with https://bityl.co/Qcuk Apache Druid's real-time capabilities and seamless Kafka integration. Learn about it in just 14 steps.
Boost Your Savings with These Money Management Apps
A money management app can transform your financial life by tracking expenses, creating budgets, and setting financial goals. These apps offer features like real-time expense tracking, bill reminders, and personalized insights to help you save and manage money effectively. With a user-friendly interface, they simplify financial planning, making it easier to stay on top of your finances and achieve long-term financial stability.
Recently uploaded (20)
The Power of Visual Regression Testing_ Why It Is Critical for Enterprise App...
The Power of Visual Regression Testing_ Why It Is Critical for Enterprise App...
Upturn India Technologies - Web development company in Nashik
Upturn India Technologies - Web development company in Nashik
Alluxio Webinar | 10x Faster Trino Queries on Your Data Platform
Alluxio Webinar | 10x Faster Trino Queries on Your Data Platform
Ensuring Efficiency and Speed with Practical Solutions for Clinical Operations
Ensuring Efficiency and Speed with Practical Solutions for Clinical Operations
Strengthening Web Development with CommandBox 6: Seamless Transition and Scal...
Strengthening Web Development with CommandBox 6: Seamless Transition and Scal...
🏎️Tech Transformation: DevOps Insights from the Experts 👩💻
🏎️Tech Transformation: DevOps Insights from the Experts 👩💻
Operational ease MuleSoft and Salesforce Service Cloud Solution v1.0.pptx
Operational ease MuleSoft and Salesforce Service Cloud Solution v1.0.pptx
The Comprehensive Guide to Validating Audio-Visual Performances.pdf
The Comprehensive Guide to Validating Audio-Visual Performances.pdf
Secure-by-Design Using Hardware and Software Protection for FDA Compliance
Secure-by-Design Using Hardware and Software Protection for FDA Compliance
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdf
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdf
Call Girls Bangalore🔥7023059433🔥Best Profile Escorts in Bangalore Available 24/7
Call Girls Bangalore🔥7023059433🔥Best Profile Escorts in Bangalore Available 24/7
Building API data products on top of your real-time data infrastructure
Building API data products on top of your real-time data infrastructure
A Comprehensive Guide on Implementing Real-World Mobile Testing Strategies fo...
A Comprehensive Guide on Implementing Real-World Mobile Testing Strategies fo...
Hands-on with Apache Druid: Installation & Data Ingestion Steps
Hands-on with Apache Druid: Installation & Data Ingestion Steps
Boost Your Savings with These Money Management Apps
Boost Your Savings with These Money Management Apps
Agile Bug Fixing (Zero Bug Policy)
- 1. The Art of Agile Development: No Bugs Daniel Dominguez 1
- 2. Rather than fixing bugs, agile methods strive to prevent them. 2
- 3. Methods for triaging bugs 1 2 3 4 3
- 4. 1. In the Product Backlog 4
- 5. 2. In a Hardending Sprint 5
- 9. Our Bug Metrics May 2016 9
- 10. May 2016 (18 Bugs Open) 10
- 11. May 2016 (18 Bugs Open) 11
- 12. zero bug policy What if? 12
- 13. 13
- 14. How does zero bug policy works? Bugs can be generalized into 2 categories: 1. Bugs that were opened during the sprint for user stories (features you are now implementing) - Fix them right away, otherwise the story/feature is not really DONE. 2. All the other bugs (regression, customer bugs, etc.). Non-sprint bugs. - Either fix them right away (or in the next sprint). Or close them as "won't fix". 14
- 15. Conclusions - Bug fixing should be part of our “Engineering Culture”. - Solving Bugs shouldn’t be considered a “Punishment”. - The team should have a balance between bug fixing and sprint development. 15