Managing The Delivery Of Zero Defect Software
•Download as PPTX, PDF•
1 like•1,445 views
Experience in delivery project with Zero Defects. - An intelligent Plan - Monitoring with a Quest for Quality - Building a Learning Team
Report
Share
Report
Share
Recommended
Lean/Agile/DevOps 2016 part 2
This document discusses concepts related to agile development practices including:
- User stories and job stories for planning development work
- Themes, epics, and user stories for organizing work
- Minimum viable product and fail fast approaches
- Change patterns for adopting agile practices
- Testing, refactoring, code reviews and other technical practices
- System thinking tools like the 5 whys technique
- Retrospective practices and formats
- Metrics for monitoring process and software quality
- Agile roles like the product owner role
- Shifting from a projects to a product organization model
Building a culture of quality real world examples #CAST2015
I gave this talk at CAST 2015 in Grand Rapids, MI. It focused on laying out what I think culture and quality are and then going through some real work examples of building a culture of quality from the bottom up.
Just Enough for Innovation
The document discusses how to conduct user experience research in an agile development environment. It proposes a method called Just Enough Testing (JET) where user research is conducted in short, monthly testing cycles. Each cycle involves testing low-fidelity prototypes with 8-10 users over 1-3 days and providing a rapid debrief and action plan. This allows for iterative user testing to inform product design while balancing the need for agility.
Agile UX
There are challenges in bringing UX and Agile processes together. This presentation contains 6 tips for incorporating these practices together.
Succeeding with Agile in the Federal Government: A Coach's Perspective
The document summarizes key principles from the Agile Manifesto and provides advice for implementing Agile practices in government organizations. It discusses embracing individuals and interactions over processes; delivering working software over documentation; prioritizing customer collaboration over contract negotiation; and responding to change rather than rigidly following a plan. The document offers dos and don'ts for applying these Agile concepts when working with government agencies and contractors.
How (fr)agile we are
This document discusses metrics in an agile environment. It notes that traditional metrics were designed for a linear world but product development is complex and unpredictable. Instead of trying to control outcomes, we can observe and learn from results to continually improve. The document outlines several types of metrics that can provide insights into business outcomes, product quality, processes, and team health/maturity without attempting to over-control the system. These include metrics like lead time, throughput, work in progress, technical debt, and happiness indexes. Cumulative flow diagrams and control charts are also discussed as ways to visualize workflow and identify improvement opportunities.
Analyse the analyst hire QAs for the right reasons
Lately, it seems as though the industry confuses the role of QA with ‘test automation engineer’. The presenters will explain why, for a number of reasons, being a skilled analyst is more beneficial to a team. They will propose that some of these qualities are being sidelined in the industry’s drive for QAs who code and will discuss the consequences of these hiring decisions.
Please don't test your product - Agile Testing
The document discusses the importance of being agile over creating perfect documentation upfront. It emphasizes that planning, development, and testing should be iterative processes. Automation, quality, and having fun with testing are important parts of an agile approach. The document promotes delivering working software in short cycles over attempting to make perfect documentation before starting work.
Recommended
Lean/Agile/DevOps 2016 part 2
This document discusses concepts related to agile development practices including:
- User stories and job stories for planning development work
- Themes, epics, and user stories for organizing work
- Minimum viable product and fail fast approaches
- Change patterns for adopting agile practices
- Testing, refactoring, code reviews and other technical practices
- System thinking tools like the 5 whys technique
- Retrospective practices and formats
- Metrics for monitoring process and software quality
- Agile roles like the product owner role
- Shifting from a projects to a product organization model
Building a culture of quality real world examples #CAST2015
I gave this talk at CAST 2015 in Grand Rapids, MI. It focused on laying out what I think culture and quality are and then going through some real work examples of building a culture of quality from the bottom up.
Just Enough for Innovation
The document discusses how to conduct user experience research in an agile development environment. It proposes a method called Just Enough Testing (JET) where user research is conducted in short, monthly testing cycles. Each cycle involves testing low-fidelity prototypes with 8-10 users over 1-3 days and providing a rapid debrief and action plan. This allows for iterative user testing to inform product design while balancing the need for agility.
Agile UX
There are challenges in bringing UX and Agile processes together. This presentation contains 6 tips for incorporating these practices together.
Succeeding with Agile in the Federal Government: A Coach's Perspective
The document summarizes key principles from the Agile Manifesto and provides advice for implementing Agile practices in government organizations. It discusses embracing individuals and interactions over processes; delivering working software over documentation; prioritizing customer collaboration over contract negotiation; and responding to change rather than rigidly following a plan. The document offers dos and don'ts for applying these Agile concepts when working with government agencies and contractors.
How (fr)agile we are
This document discusses metrics in an agile environment. It notes that traditional metrics were designed for a linear world but product development is complex and unpredictable. Instead of trying to control outcomes, we can observe and learn from results to continually improve. The document outlines several types of metrics that can provide insights into business outcomes, product quality, processes, and team health/maturity without attempting to over-control the system. These include metrics like lead time, throughput, work in progress, technical debt, and happiness indexes. Cumulative flow diagrams and control charts are also discussed as ways to visualize workflow and identify improvement opportunities.
Analyse the analyst hire QAs for the right reasons
Lately, it seems as though the industry confuses the role of QA with ‘test automation engineer’. The presenters will explain why, for a number of reasons, being a skilled analyst is more beneficial to a team. They will propose that some of these qualities are being sidelined in the industry’s drive for QAs who code and will discuss the consequences of these hiring decisions.
Please don't test your product - Agile Testing
The document discusses the importance of being agile over creating perfect documentation upfront. It emphasizes that planning, development, and testing should be iterative processes. Automation, quality, and having fun with testing are important parts of an agile approach. The document promotes delivering working software in short cycles over attempting to make perfect documentation before starting work.
It works on my machine!
Can we assure quality? Quality Assurance, what is it today? How we can improve QA and the symbiosis between Software Engineers and QA Engineers
Lean/Agile/DevOps 2016 part 1
This document is an agenda for a DevOps/Lean/Agile 2016 talk by Diego Pacheco. The agenda covers topics such as Waterfall vs Agile, the Agile Manifesto, eXtreme Programming (XP), Scrum, Lean principles and wastes, Kanban, management 3.0, Agile coaching, scaling frameworks like Spotify, and DevOps. Pacheco intends to discuss concepts, practices, and methods for each topic area, as well as user stories, change patterns, testing, technical practices, metrics, system thinking tools, retrospective practices, the Agile product owner role, A/B testing, data science, and creating an Agile organization.
Delight Your Customers: The #noestimates Way
This document discusses moving away from estimation practices in software development and instead focusing on delivering value to customers frequently through iterative development. It notes challenges with estimation such as durations often exceeding estimates and the "estimation game" where developers are pressured to provide unrealistic estimates. Instead of estimates, it recommends tracking lead time and throughput to manage workload and using probabilistic forecasts to set expectations on completion times. The document advocates for prioritizing work, analyzing tasks at a high level, and delivering in small batches to get feedback and adapt quickly.
Eastern Melbourne Agile Meetup - Challenge Constraints
Lightning talk at the Agile Meetup. Discusses the idea that if you are introducing change you need to understand how the organisation got the way it is now, and address the underlying concerns and drivers, so as to make the chanegs stick.
Agile basics
Agile Basics for Government with ThoughtWorks
Most people interested in the field of innovation have heard of agile innovation teams. These small, entrepreneurial groups are designed to stay close to customers and adapt quickly to changing conditions. When implemented correctly, they have a reputation for almost always result in higher team productivity and moral, faster time to market, better quality and lower risk than traditional approaches can achieve.
But while agile methods caught on first in IT departments and are now widely used in software development, the agile approach has potential to transform the public sector in ways far beyond better bits and bytes. Conditions are ripe for agile teams in any situation where problems are complex, solutions are at first unclear, project requirements are likely to change, and close collaboration with end users is feasible: a description that matches many facing a wide variety of public sector activities.
This session will provide participants with an opportunity to explore what the world of agile can teach them – about themselves, their work and their potential to serve their clients better, whatever their role. It will confront some of the common myths and misconceptions about agile, and demonstrate how an agile approach can enable teams to deliver sooner and scale faster through a proven learning culture that builds and strengthens the team and its capabilities.
How we Roll: engineering organisation at HouseTrip
The document summarizes the evolution of the engineering team at HouseTrip from 2011 to 2013. It grew from 5 developers and 3 product managers to 25 developers and 6 product managers. It describes the flat team structure, use of small focused teams led by a product manager and developer, and elders board to oversee major changes. It also discusses their agile processes, emphasis on quality and removing bottlenecks, use of tech Fridays for improvement projects, and focus on documentation and sharing knowledge.
Got work to do? Zest thoughts on making a process
The document outlines a seven-step process for building a process for work projects. It discusses reviewing existing processes, identifying good, bad, and ugly aspects, planning the new process on a board for discussion, integrating it into internal systems, getting client and team feedback, and regularly reviewing the process for improvements. The company applied this seven-step process to develop a new process for their web projects which has resulted in benefits like whole team buy-in, meeting client expectations, easier transitions back to work, quicker sign-offs, coverage for absences, positive client feedback, and space for creativity.
The argument for agile development
Agile development is a methodology that allows work to be done closer to estimates, gives customers more control over projects, and simplifies workloads. It increases accountability, allows for more innovation and marketing potential, and can increase profits. While not perfect, adopting agile development requires customer buy-in and will provide tough lessons initially. Next steps to consider agile development include reading more about it, appointing champions, acquiring necessary tools, and getting started with implementation.
Agile Gurgaon 2016 Conference | The game has changed! | Sudipta Lahiri
The document discusses how the game has changed for software development practices. It outlines how planning, requirements, testing and other practices are now different compared to past decades. Estimation, scheduling and forecasting have shifted from lengthy upfront processes to relative and iterative approaches. Requirements are now defined through collaboration rather than written specifications. Testing is a shared responsibility across teams rather than isolated to a separate testing team. The role of testing has changed from finding defects to delivering quality. Adopting agile practices means recognizing how the entire ecosystem for development has evolved.
A Software Development Approach to Help You End Up with the Product You Reall...
A presentation from New Orleans Entrepreneur Week 2014 by Peter Bodenheimer of FlatStack & Barrett Conrad of CotingaSoft. The goal of this presentation was help bridge the gap often found between business founders and the technical partners helping them execute their product development vision.
How to Best Develop Requirements for SharePoint Projects
The document discusses best practices for developing requirements for SharePoint projects. It explains that requirements involve eliciting information from stakeholders, analyzing this information without becoming paralyzed, and documenting requirements in a formal requirements document. The document provides tips for mapping requirements, validating requirements, and writing concise requirement statements to guide project development.
Real world dev ops
The document discusses real world DevOps practices based on the author's experience. It defines DevOps as not being a job or department but rather a value system of collaboration across teams to provide faster feedback and achieve business goals. The author provides "Don'ts" and "Do's" for DevOps, advising against silos between teams and different goals for Dev and Ops, and recommending providing self-service tools, constant cross-training, keeping systems simple, and automating processes. The overall message is that collaboration, feedback, and customer focus should be the highest priorities.
Measurement magic in world of DevOps
This document discusses the importance of measurement in software development and operations. It notes that measurement is needed as a basis for decisions, to gain situational awareness, and for improvement. However, what is measured needs to be useful, as measuring the wrong things can lead to pitfalls. The document outlines different aspects that can be measured in development, operations, and finance. It advocates relating measures to key performance indicators and using tools and machine learning to help deal with large volumes of data from measures. Automation is also emphasized.
B leach
This document discusses improving the quality of Microsoft Project schedules. It identifies ten common problems with schedule quality such as missing predecessors, successors, improper use of constraints and lags. Poor schedule quality can result in not knowing the true project finish date, rework, schedule slippage, budget overruns and lack of trust. The document promotes improving schedule quality by addressing issues such as ensuring tasks, resources, assignments and costs are accurate.
Introducing EDD: Error Driven Development
This document discusses Error Driven Development (EDD) as an alternative to traditional Test Driven Development (TDD). EDD emphasizes reproducing bugs through tests before fixing them. It addresses common reasons teams avoid TDD, such as not making mistakes or tests taking too long, by arguing bugs will still occur and fixing them without tests is not faster. EDD aims to have teams focus on bugs by learning to reproduce them in tests in order to fix issues and avoid regressions.
File 1 four extra slides 1
The document discusses various challenges that can occur in project management and provides solutions. It notes that project failure can result from cost and time overruns, quality issues, and low satisfaction. Other issues include scope creep where additional work is added, poor communication leading to lack of information sharing, and inadequate resources and commitment. The document recommends following formal processes for change management, communication planning, resource allocation, risk management, and defining clear deliverables to help address these challenges. It emphasizes the importance of thorough planning to project success.
File 1 four extra slides 2
This document provides an overview of project management and common project failures. It discusses that project management utilizes organizational resources in a controlled manner to achieve defined objectives. When projects do not meet stakeholder expectations, they are considered failures. Common causes of failure include cost and time overruns, quality issues, and low job satisfaction. The document then examines specific issues like scope creep, poor communication, inadequate resources, unclear requirements, unrealistic timelines, unmanaged risks, undefined deliverables, lack of planning, and insufficient project management skills. It emphasizes the importance of planning, change management, communication plans, resource planning, documentation, risk management, and formal project management training.
Intro to Lean Software Development
Presentation I gave to the Chicago ACM about Lean Software Development. Full audio can be found here:
https://soundcloud.com/griffinc/intro-to-lean-software
OPTIMIZING PERFORMANCE USING CONTINUOUS PRODUCTION PROFILING ,YONATAN GOLDSCH...
Everyone wants observability into their system, but find themselves with too many vendors and tools, each with its own API, SDK, agent and collectors.
With the increasing complexity of modern applications, continuous profiling methods and tools are gaining popularity among the Developer and Engineering communities. In this session, we cover what continuous profiling entails and why you should implement a profiler into your tech stack (if you haven’t done so already). We’ll then bring theory to practice and demonstrate a real-life scenario using gProfiler, a free open-source continuous profiling tool, covering Linux servers on multiple architectures (such as Graviton).
Intro to Agile Practices and Values
General introduction to agile practices like Scrum and Kanban. Also covers what situations Agile is best at, what situations Agile doesn't help with, and what an Agile team should look like. This deck is a general intro to Agile for OpenSource Connections clients.
Top Ten Obstacles To Project Success
The document presents the top 10 obstacles to project success as identified by over 1,000 project managers. They are described in descending order from #10 to #1, with explanations of how each obstacle can negatively impact a project if not mitigated properly. Effective communication, motivating teams, and holding team members accountable are identified as key skills that can help address many of these common challenges faced on projects.
Open Source Software Development Practices that Works
The document discusses open source software development practices that focus on being agile and iterative. Some key practices include using user stories instead of heavy documentation, delivering working software in short iterations, estimating tasks by breaking work down, respecting teammates, having daily standups, keeping to-do lists short, writing tests, holding retrospectives, and continuously improving through learning and adjustments. The overall message is that these agile practices work because they are simple, allow flexibility to adapt to changes, and focus on delivering working software.
More Related Content
What's hot
It works on my machine!
Can we assure quality? Quality Assurance, what is it today? How we can improve QA and the symbiosis between Software Engineers and QA Engineers
Lean/Agile/DevOps 2016 part 1
This document is an agenda for a DevOps/Lean/Agile 2016 talk by Diego Pacheco. The agenda covers topics such as Waterfall vs Agile, the Agile Manifesto, eXtreme Programming (XP), Scrum, Lean principles and wastes, Kanban, management 3.0, Agile coaching, scaling frameworks like Spotify, and DevOps. Pacheco intends to discuss concepts, practices, and methods for each topic area, as well as user stories, change patterns, testing, technical practices, metrics, system thinking tools, retrospective practices, the Agile product owner role, A/B testing, data science, and creating an Agile organization.
Delight Your Customers: The #noestimates Way
This document discusses moving away from estimation practices in software development and instead focusing on delivering value to customers frequently through iterative development. It notes challenges with estimation such as durations often exceeding estimates and the "estimation game" where developers are pressured to provide unrealistic estimates. Instead of estimates, it recommends tracking lead time and throughput to manage workload and using probabilistic forecasts to set expectations on completion times. The document advocates for prioritizing work, analyzing tasks at a high level, and delivering in small batches to get feedback and adapt quickly.
Eastern Melbourne Agile Meetup - Challenge Constraints
Lightning talk at the Agile Meetup. Discusses the idea that if you are introducing change you need to understand how the organisation got the way it is now, and address the underlying concerns and drivers, so as to make the chanegs stick.
Agile basics
Agile Basics for Government with ThoughtWorks
Most people interested in the field of innovation have heard of agile innovation teams. These small, entrepreneurial groups are designed to stay close to customers and adapt quickly to changing conditions. When implemented correctly, they have a reputation for almost always result in higher team productivity and moral, faster time to market, better quality and lower risk than traditional approaches can achieve.
But while agile methods caught on first in IT departments and are now widely used in software development, the agile approach has potential to transform the public sector in ways far beyond better bits and bytes. Conditions are ripe for agile teams in any situation where problems are complex, solutions are at first unclear, project requirements are likely to change, and close collaboration with end users is feasible: a description that matches many facing a wide variety of public sector activities.
This session will provide participants with an opportunity to explore what the world of agile can teach them – about themselves, their work and their potential to serve their clients better, whatever their role. It will confront some of the common myths and misconceptions about agile, and demonstrate how an agile approach can enable teams to deliver sooner and scale faster through a proven learning culture that builds and strengthens the team and its capabilities.
How we Roll: engineering organisation at HouseTrip
The document summarizes the evolution of the engineering team at HouseTrip from 2011 to 2013. It grew from 5 developers and 3 product managers to 25 developers and 6 product managers. It describes the flat team structure, use of small focused teams led by a product manager and developer, and elders board to oversee major changes. It also discusses their agile processes, emphasis on quality and removing bottlenecks, use of tech Fridays for improvement projects, and focus on documentation and sharing knowledge.
Got work to do? Zest thoughts on making a process
The document outlines a seven-step process for building a process for work projects. It discusses reviewing existing processes, identifying good, bad, and ugly aspects, planning the new process on a board for discussion, integrating it into internal systems, getting client and team feedback, and regularly reviewing the process for improvements. The company applied this seven-step process to develop a new process for their web projects which has resulted in benefits like whole team buy-in, meeting client expectations, easier transitions back to work, quicker sign-offs, coverage for absences, positive client feedback, and space for creativity.
The argument for agile development
Agile development is a methodology that allows work to be done closer to estimates, gives customers more control over projects, and simplifies workloads. It increases accountability, allows for more innovation and marketing potential, and can increase profits. While not perfect, adopting agile development requires customer buy-in and will provide tough lessons initially. Next steps to consider agile development include reading more about it, appointing champions, acquiring necessary tools, and getting started with implementation.
Agile Gurgaon 2016 Conference | The game has changed! | Sudipta Lahiri
The document discusses how the game has changed for software development practices. It outlines how planning, requirements, testing and other practices are now different compared to past decades. Estimation, scheduling and forecasting have shifted from lengthy upfront processes to relative and iterative approaches. Requirements are now defined through collaboration rather than written specifications. Testing is a shared responsibility across teams rather than isolated to a separate testing team. The role of testing has changed from finding defects to delivering quality. Adopting agile practices means recognizing how the entire ecosystem for development has evolved.
A Software Development Approach to Help You End Up with the Product You Reall...
A presentation from New Orleans Entrepreneur Week 2014 by Peter Bodenheimer of FlatStack & Barrett Conrad of CotingaSoft. The goal of this presentation was help bridge the gap often found between business founders and the technical partners helping them execute their product development vision.
How to Best Develop Requirements for SharePoint Projects
The document discusses best practices for developing requirements for SharePoint projects. It explains that requirements involve eliciting information from stakeholders, analyzing this information without becoming paralyzed, and documenting requirements in a formal requirements document. The document provides tips for mapping requirements, validating requirements, and writing concise requirement statements to guide project development.
Real world dev ops
The document discusses real world DevOps practices based on the author's experience. It defines DevOps as not being a job or department but rather a value system of collaboration across teams to provide faster feedback and achieve business goals. The author provides "Don'ts" and "Do's" for DevOps, advising against silos between teams and different goals for Dev and Ops, and recommending providing self-service tools, constant cross-training, keeping systems simple, and automating processes. The overall message is that collaboration, feedback, and customer focus should be the highest priorities.
Measurement magic in world of DevOps
This document discusses the importance of measurement in software development and operations. It notes that measurement is needed as a basis for decisions, to gain situational awareness, and for improvement. However, what is measured needs to be useful, as measuring the wrong things can lead to pitfalls. The document outlines different aspects that can be measured in development, operations, and finance. It advocates relating measures to key performance indicators and using tools and machine learning to help deal with large volumes of data from measures. Automation is also emphasized.
B leach
This document discusses improving the quality of Microsoft Project schedules. It identifies ten common problems with schedule quality such as missing predecessors, successors, improper use of constraints and lags. Poor schedule quality can result in not knowing the true project finish date, rework, schedule slippage, budget overruns and lack of trust. The document promotes improving schedule quality by addressing issues such as ensuring tasks, resources, assignments and costs are accurate.
Introducing EDD: Error Driven Development
This document discusses Error Driven Development (EDD) as an alternative to traditional Test Driven Development (TDD). EDD emphasizes reproducing bugs through tests before fixing them. It addresses common reasons teams avoid TDD, such as not making mistakes or tests taking too long, by arguing bugs will still occur and fixing them without tests is not faster. EDD aims to have teams focus on bugs by learning to reproduce them in tests in order to fix issues and avoid regressions.
File 1 four extra slides 1
The document discusses various challenges that can occur in project management and provides solutions. It notes that project failure can result from cost and time overruns, quality issues, and low satisfaction. Other issues include scope creep where additional work is added, poor communication leading to lack of information sharing, and inadequate resources and commitment. The document recommends following formal processes for change management, communication planning, resource allocation, risk management, and defining clear deliverables to help address these challenges. It emphasizes the importance of thorough planning to project success.
File 1 four extra slides 2
This document provides an overview of project management and common project failures. It discusses that project management utilizes organizational resources in a controlled manner to achieve defined objectives. When projects do not meet stakeholder expectations, they are considered failures. Common causes of failure include cost and time overruns, quality issues, and low job satisfaction. The document then examines specific issues like scope creep, poor communication, inadequate resources, unclear requirements, unrealistic timelines, unmanaged risks, undefined deliverables, lack of planning, and insufficient project management skills. It emphasizes the importance of planning, change management, communication plans, resource planning, documentation, risk management, and formal project management training.
Intro to Lean Software Development
Presentation I gave to the Chicago ACM about Lean Software Development. Full audio can be found here:
https://soundcloud.com/griffinc/intro-to-lean-software
OPTIMIZING PERFORMANCE USING CONTINUOUS PRODUCTION PROFILING ,YONATAN GOLDSCH...
Everyone wants observability into their system, but find themselves with too many vendors and tools, each with its own API, SDK, agent and collectors.
With the increasing complexity of modern applications, continuous profiling methods and tools are gaining popularity among the Developer and Engineering communities. In this session, we cover what continuous profiling entails and why you should implement a profiler into your tech stack (if you haven’t done so already). We’ll then bring theory to practice and demonstrate a real-life scenario using gProfiler, a free open-source continuous profiling tool, covering Linux servers on multiple architectures (such as Graviton).
What's hot (19)
Eastern Melbourne Agile Meetup - Challenge Constraints
Eastern Melbourne Agile Meetup - Challenge Constraints
How we Roll: engineering organisation at HouseTrip
How we Roll: engineering organisation at HouseTrip
Agile Gurgaon 2016 Conference | The game has changed! | Sudipta Lahiri
Agile Gurgaon 2016 Conference | The game has changed! | Sudipta Lahiri
A Software Development Approach to Help You End Up with the Product You Reall...
A Software Development Approach to Help You End Up with the Product You Reall...
How to Best Develop Requirements for SharePoint Projects
How to Best Develop Requirements for SharePoint Projects
OPTIMIZING PERFORMANCE USING CONTINUOUS PRODUCTION PROFILING ,YONATAN GOLDSCH...
OPTIMIZING PERFORMANCE USING CONTINUOUS PRODUCTION PROFILING ,YONATAN GOLDSCH...
Similar to Managing The Delivery Of Zero Defect Software
Intro to Agile Practices and Values
General introduction to agile practices like Scrum and Kanban. Also covers what situations Agile is best at, what situations Agile doesn't help with, and what an Agile team should look like. This deck is a general intro to Agile for OpenSource Connections clients.
Top Ten Obstacles To Project Success
The document presents the top 10 obstacles to project success as identified by over 1,000 project managers. They are described in descending order from #10 to #1, with explanations of how each obstacle can negatively impact a project if not mitigated properly. Effective communication, motivating teams, and holding team members accountable are identified as key skills that can help address many of these common challenges faced on projects.
Open Source Software Development Practices that Works
The document discusses open source software development practices that focus on being agile and iterative. Some key practices include using user stories instead of heavy documentation, delivering working software in short iterations, estimating tasks by breaking work down, respecting teammates, having daily standups, keeping to-do lists short, writing tests, holding retrospectives, and continuously improving through learning and adjustments. The overall message is that these agile practices work because they are simple, allow flexibility to adapt to changes, and focus on delivering working software.
Predictability at Axial
Given at Axial HQ for the New York chapter of Venwise, this talk details how Axial approaches building products predictably through a combination of focus, objectives, prioritization and forecasting. We call it stack.
Check out more of what we're building over at: axialcorps.com
2009 Top Ten Obstacles To Project Success
This presentation is intended for use by Project Management, Program Management, or Senior I.T. Leadership to understand the nature of the most common obstacles found by project managers on typical projects.
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.
Organization strategies to increase development productivity
Organization Strategies to Increase Development Productivity discusses how to increase productivity through a student worker program. It outlines how the speaker's team at Oakland University hired and trained student workers to take on development work. Key aspects included identifying mentors, varying work tasks, setting expectations, and involving students in open source contributions. When implemented well, the student program provides hands-on learning opportunities for students and additional development capacity for the organization. One student speaker discussed his positive experience in the program, where he gained real-world skills while having a flexible work schedule around his classes.
Top 10 Qualities of a QA Tester
Join Stacey Brown, President of MindLink Resources, for a webinar that will examine the top 10 qualities of a quality assurance (QA) tester. Learn how to bring out these traits in your current QA staff and how to watch for these soft skills when screening new candidates.
When localizing products, the QA step is essential in confirming the translation and making sure the product was successfully prepared for the target market. Managers trust the QA staff to catch translation and engineering errors and ensure product readiness to avoid quality issues caught by the end customer. Many managers make the mistake of assigning this critical role to a linguist who may not have the right characteristics of a good tester. When selecting QA staff, it is important to consider skills beyond just linguistic and technical. There are many “soft skills” to watch for in a candidate that will give localization managers the confidence that even small errors will be reported by their tester.
In this webinar, Stacey will discuss the top 10 qualities of a quality assurance (QA) tester, how to bring out these traits in current QA staff, and how to watch for these soft skills when screening new candidates.
About the presenter
Stacey Brown is the Talent Management Specialist and President of Mindlink Resources, LLC.. She has a passion for surrounding herself with talented people. For the past 15 years she has successfully built teams of contractors providing a variety of services at large fortune 500 companies in the Pacific Northwest. She specifically has over 12 years of experience recruiting, training and managing QA specialists. Stacey has a degree in Communications and an MBA in Technology Management.
WhoIsKenDeLong
This document contains Ken DeLong's work history, activities, favorite books, strengths, and views on software engineering best practices. It emphasizes hiring the best engineers, optimizing for learning, reducing waste, attention to quality, and avoiding technical and cultural debt.
Agile - Product is Progress.
The document compares traditional waterfall and agile product development approaches. It summarizes research finding that agile projects succeed three times more often than waterfall projects. Key aspects of agile methodologies like Scrum are outlined, including roles, ceremonies, and values. Challenges of adopting agile approaches are also discussed.
Agile for Me- CodeStock 2009
This document provides an overview of Agile software development. It begins by defining Agile as a project management process that encourages frequent inspection and adaptation. It then discusses some common Agile practices like Scrum and eXtreme Programming. The Agile Manifesto values individuals and interactions, working software, customer collaboration, and responding to change. Finally, it provides advice for different roles on how Agile can benefit them and their work.
How Agile Can We Go? Lessons Learned Moving from Waterfall
How agile are you? Once you jump off the waterfall and drink from the agile pool, there will probably be varying opinions as to the state of the organization’s agility. Some will be concerned that they are not agile enough; others will think they are agile while still adhering to old waterfall principles. Adapting to agile requires process changes that can cause friction within and between teams. Max McGregor’s organization Venafi has several teams working on multiple projects, spread worldwide. Even after a number of software releases using agile methods, teams still have challenges. Max provides insight into one mid-sized organization’s evolution through this process—where it’s working well, what the biggest challenges are, and what’s being done to increase its success with agile. Join Max to determine how agile you can or should become, and take back new ideas and methods to your teams to help them succeed.
What it Really Means to Be Agile
Some teams think they can be agile by using a defined process or set of practices as defined by one of the agile approaches. This is just “doing Agile.” Other teams are agile in name only – the team says it’s “doing Agile” but ends up using the same old practices and achieving the same results. Teams adopt agile for a variety of reasons, but it’s not the process or set of practices they select that produces the results they seek. Teams are most successful when they adopt a particular mindset in order to “be agile”. Join Kent McDonald as he describes this mindset through 7 key ideas based on how people and organizations work best. We’ll discuss some specific techniques you can use to adopt the mindset on your project, how the project manager role changes along with the mindset, and how to help your team move from “doing Agile” to actually “being agile”.
Introducing Agile Methodologies
Дмитро Бузоверя
Директор Cloud Computing департаменту в компанії AMC Bridge
Agile підхід до управління проектами існує вже більше 15 років, він досі є об’єктом багатьох дискусій та вважається інноваційним у деяких областях.
Дмитро Бузоверя, зробить огляд методології Agile у розробці програмного забезпечення. Він розкаже про історію Agile, його принципи та більш детально зупиниться на різних методиках: Extreme Programming (XP), Scrum, Lean та Kanban.
Ця лекція допоможе зібрати пазл з Agile термінології в єдину картинку.
Agile Team Performance Appraisal
The document provides information on performance management in an agile environment. It discusses that performance management should focus on setting goals at the beginning of the year and reviewing progress, providing feedback throughout the year. It also notes that performance is a shared responsibility between management and individuals, and that the system and environment set by management impacts performance more than individual responsibility alone. Regular feedback and discussions help individuals improve and align their goals with team and organizational goals.
scrum-talk
Nopparat and Samatchaya gave a presentation on Scrum and Agile. They discussed key concepts like the Agile Manifesto, Scrum roles, the Scrum process, and their experiences implementing Scrum. As an Agile coach, Nopparat helps teams build an environment for self-organization and continuous improvement through training, coaching, and ensuring stakeholder support for Agile goals. The presentation included games to illustrate Scrum concepts and a case study on challenges of creating an Agile culture.
Sprint. Don't Waterfall
The document discusses how to avoid "waterfalling" work during a sprint in Scrum. It recommends splitting stories into smaller tasks, identifying independent tasks early, and "swarming" to complete higher priority tasks first before moving to the next. This allows delivering items earlier and prevents bottlenecks at the end of sprints where everything needs to be tested and completed at once. Key principles are smaller batches, less work in progress, and more parallel work through collaboration within cross-functional teams.
Risk management at warp speed
The document discusses unconventional approaches to risk management in fast-growing companies. It advocates for limiting risk by testing ideas quickly with small groups of users rather than lengthy planning and debate. It also emphasizes the importance of working software over detailed project plans and status reports. Additionally, it suggests that companies should intentionally expose themselves to more problems and failures in order to learn faster through real-world experiences, rather than solely focusing on prevention. Quality is discussed as emerging from collaborative learning across teams rather than strict standardization or individual heroics like being paged at unusual hours.
Stldodn 2014 agile on a shoestring
Furthering your agile adoption efforts without huge training or tools investments by working with your most important asset, your people.
Agile Development at W3i
Agile development methodology focuses on iterative development where requirements and solutions evolve through collaboration between cross-functional teams. Some key aspects of agile include short development cycles, working software over documentation, customer collaboration, and responding to change. Scrum is a popular agile framework used at W3i that utilizes user stories, estimating, planning meetings, daily stand-ups, burndown charts, sprints, reviews and retrospectives to deliver working software frequently.
Similar to Managing The Delivery Of Zero Defect Software (20)
Open Source Software Development Practices that Works
Open Source Software Development Practices that Works
Organization strategies to increase development productivity
Organization strategies to increase development productivity
How Agile Can We Go? Lessons Learned Moving from Waterfall
How Agile Can We Go? Lessons Learned Moving from Waterfall
Recently uploaded
Trusted Execution Environment for Decentralized Process Mining
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Main news related to the CCS TSI 2023 (2023/1695)
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
A Comprehensive Guide to DeFi Development Services in 2024
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
Fueling AI with Great Data with Airbyte Webinar
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
Building Production Ready Search Pipelines with Spark and Milvus
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
AWS Cloud Cost Optimization Presentation.pptx
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
dbms calicut university B. sc Cs 4th sem.pdf
Its a seminar ppt on database management system using sql
Operating System Used by Users in day-to-day life.pptx
Dive into the realm of operating systems (OS) with Pravash Chandra Das, a seasoned Digital Forensic Analyst, as your guide. 🚀 This comprehensive presentation illuminates the core concepts, types, and evolution of OS, essential for understanding modern computing landscapes.
Beginning with the foundational definition, Das clarifies the pivotal role of OS as system software orchestrating hardware resources, software applications, and user interactions. Through succinct descriptions, he delineates the diverse types of OS, from single-user, single-task environments like early MS-DOS iterations, to multi-user, multi-tasking systems exemplified by modern Linux distributions.
Crucial components like the kernel and shell are dissected, highlighting their indispensable functions in resource management and user interface interaction. Das elucidates how the kernel acts as the central nervous system, orchestrating process scheduling, memory allocation, and device management. Meanwhile, the shell serves as the gateway for user commands, bridging the gap between human input and machine execution. 💻
The narrative then shifts to a captivating exploration of prominent desktop OSs, Windows, macOS, and Linux. Windows, with its globally ubiquitous presence and user-friendly interface, emerges as a cornerstone in personal computing history. macOS, lauded for its sleek design and seamless integration with Apple's ecosystem, stands as a beacon of stability and creativity. Linux, an open-source marvel, offers unparalleled flexibility and security, revolutionizing the computing landscape. 🖥️
Moving to the realm of mobile devices, Das unravels the dominance of Android and iOS. Android's open-source ethos fosters a vibrant ecosystem of customization and innovation, while iOS boasts a seamless user experience and robust security infrastructure. Meanwhile, discontinued platforms like Symbian and Palm OS evoke nostalgia for their pioneering roles in the smartphone revolution.
The journey concludes with a reflection on the ever-evolving landscape of OS, underscored by the emergence of real-time operating systems (RTOS) and the persistent quest for innovation and efficiency. As technology continues to shape our world, understanding the foundations and evolution of operating systems remains paramount. Join Pravash Chandra Das on this illuminating journey through the heart of computing. 🌟
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Recently uploaded (20)
Trusted Execution Environment for Decentralized Process Mining
Trusted Execution Environment for Decentralized Process Mining
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
A Comprehensive Guide to DeFi Development Services in 2024
A Comprehensive Guide to DeFi Development Services in 2024
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
Operating System Used by Users in day-to-day life.pptx
Operating System Used by Users in day-to-day life.pptx
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Managing The Delivery Of Zero Defect Software
- 1. Experiences in Delivering Project with Zero Defects SrikanthRao July 2010
- 2. Usual Reactions on Zero Defects in Software Projects July 10 “Are you kidding me?. It is a miracle. How can we expect zero defects in software development? It is harder to define, harder to test, harder to predict results. Bugs is a perfectly normal thing, we can’t bring them to zero. But we should minimize them using all possible ways. ”The Last Bug is a mirage” Like any other PM, I started with a “Zero Defects Mentality” which is not about having zero bugs as a target (as you're never sure of achieving it), but about doing all that's necessary to prevent bugs. Then the “Zero Defect software Delivery” happened!. I guess I got lucky(?). The purpose of the ppt is to share some best practices that were used to pursue the “Zero Defect Mentality”. Luck is probably a dividend of sweat! The author was also instrumental in architecting the Quality Management System for a Global software company and had co-authored the V-Process model
- 3. My Experience in Managing a Zero Defect Project July 10
- 6. Built contingency for course correction; e.g. Internal Schedule was tighter than schedule committed to customer“The more intelligently you plan, the luckier you get.” July 10
- 10. Every week was a deadline; The “True Status” should be determined by the PM based on his/her assessment of the quality of the deliverables rather than relying on the status reported by the team member. July 10
- 12. Challenged the Team to deliver a zero-defect Unit tested Code (where the PM cannot find errors).
- 14. Support to meet deadlines/Debugging“A work output of a Developer working under two different Project Managers (PMs) is different. The PM who demands quality would not only get a better output but would also be valued by the Team Members for adding value to them and enabling their professional development .” July 10
- 16. Development Environment different from Production environment
- 17. Two hardware Dongles (for a team of 10); Team worked in shifts
- 18. Frequent Power Outage
- 20. Zero Defect during UAT