Find out if you're making these common testing metric mistakes and what to do if you are. In this hour-long XBOSoft webinar, ARGO Data's Quality Assurance Manager will teach you how to improve your metrics and build better software testing and QA teams.
Challenges & Successes of Agile Implementation Webinar with BlackLine - XBOSoftXBOSoft
In this hour-long webinar, BlackLine's Director of Software Development Greg Burns and Scrum Master and Agile Coach Ron Ben Yosef discuss the company's agile conversion experience -- the challenges, successes, and benefits gained from implementation.
Whether you’re new to Agile or part of an experienced Agile team you will inevitably be faced with various challenges in becoming a successful team. In this session we will look at some common challenges teams are faced with and discuss various ways of overcoming those challenges.
Today many teams and companies are turning to Agile product development. Scrum is among the most popular choices. The promises from Agile are several. Still it is good advice to do a couple of things before you go Agile. In the following I will list and discuss five things to do before you go Agile.
This is a presentation made to Surge Accelerator in Houston in March 2013. This serves as a Guide to Early Stage Technology Companies, building enterprise class software.
This covers the typical lifecycle of a software start-up, fundamentals of Agile software development, and some do's and don't for how to build successful software companies.
Real world experience from Microsoft - Deniz ErcoskunAgileSparks
Microsoft developer division has implemented SCRUM while developing Visual Studio 2012, and TFS 2012. In this talk we will cover information on this implementation. You will learn about why Microsoft has decided to implement SCRUM, best practices that was helpful for us. How implementing SCRUM has changed our cadence and product delivery cycle. The content will be our developer division SCRUM journey. We are not pure SCRUM put at future leavel we are. I will also discuss which part of our process is SCRUm which part still is not.
Ken Whitaker shares pragmatic techniques to help project managers and software development leaders put into practice innovative scheduling techniques, make consistent customer-centric decisions, reduce project risk, quickly negotiate with product owners the most important project scope, and transition teams to become more agile. Ken shares revealing statistical data on how waterfall is simply not suited for modern-day adaptive software development projects. With fellow participants, you’ll spend time performing a “Scrum walkabout” to get the idea of just how an agile project really works. These best practices are presented to motivate your team to deliver projects on time, every time. Although this tutorial doesn’t incorporate intensive role-play, we’ll have lively interaction that will incorporate lessons learned from actual case studies and attendees’ project experiences. Take away powerful, yet simple, ways to bridge the gap between PMI’s PMBOK® Guide and agile.
Agile has become mainstream in the IT industry, since that the multiplication of Agile practices which makes Agile implementation complex and uncertain, we have started to see failure in Agile implementations.
During this presentation we will start a simplification process by going back to the source of Agile, understand what Agile is and what it is not. We will discover what is the Heart of Agile, its essence, and how it embraces management
Challenges & Successes of Agile Implementation Webinar with BlackLine - XBOSoftXBOSoft
In this hour-long webinar, BlackLine's Director of Software Development Greg Burns and Scrum Master and Agile Coach Ron Ben Yosef discuss the company's agile conversion experience -- the challenges, successes, and benefits gained from implementation.
Whether you’re new to Agile or part of an experienced Agile team you will inevitably be faced with various challenges in becoming a successful team. In this session we will look at some common challenges teams are faced with and discuss various ways of overcoming those challenges.
Today many teams and companies are turning to Agile product development. Scrum is among the most popular choices. The promises from Agile are several. Still it is good advice to do a couple of things before you go Agile. In the following I will list and discuss five things to do before you go Agile.
This is a presentation made to Surge Accelerator in Houston in March 2013. This serves as a Guide to Early Stage Technology Companies, building enterprise class software.
This covers the typical lifecycle of a software start-up, fundamentals of Agile software development, and some do's and don't for how to build successful software companies.
Real world experience from Microsoft - Deniz ErcoskunAgileSparks
Microsoft developer division has implemented SCRUM while developing Visual Studio 2012, and TFS 2012. In this talk we will cover information on this implementation. You will learn about why Microsoft has decided to implement SCRUM, best practices that was helpful for us. How implementing SCRUM has changed our cadence and product delivery cycle. The content will be our developer division SCRUM journey. We are not pure SCRUM put at future leavel we are. I will also discuss which part of our process is SCRUm which part still is not.
Ken Whitaker shares pragmatic techniques to help project managers and software development leaders put into practice innovative scheduling techniques, make consistent customer-centric decisions, reduce project risk, quickly negotiate with product owners the most important project scope, and transition teams to become more agile. Ken shares revealing statistical data on how waterfall is simply not suited for modern-day adaptive software development projects. With fellow participants, you’ll spend time performing a “Scrum walkabout” to get the idea of just how an agile project really works. These best practices are presented to motivate your team to deliver projects on time, every time. Although this tutorial doesn’t incorporate intensive role-play, we’ll have lively interaction that will incorporate lessons learned from actual case studies and attendees’ project experiences. Take away powerful, yet simple, ways to bridge the gap between PMI’s PMBOK® Guide and agile.
Agile has become mainstream in the IT industry, since that the multiplication of Agile practices which makes Agile implementation complex and uncertain, we have started to see failure in Agile implementations.
During this presentation we will start a simplification process by going back to the source of Agile, understand what Agile is and what it is not. We will discover what is the Heart of Agile, its essence, and how it embraces management
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
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.
Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone AgileSparks
The document summarizes Pelephone IT's transition to agile methodologies. It describes how Pelephone IT struggled with long development cycles, inability to adapt to changes, and internal blaming cultures. This prompted them to learn agile/Kanban approaches. They started by training managers and developers, then formed cross-functional teams and began regular production releases. This improved time to market, collaboration, and business satisfaction. Moving forward, Pelephone IT aims to refine their agile practices and skills through experience, with an understanding that change takes time and mistakes are expected.
Managing IT Projects - Onsite Offshore CoordinationMahesh Dedhia
In the Software industry, quite often development and testing jobs are outsourced and a small percentage of the team is placed at the client location to coordinate between client teams and offshore teams. This presentation talks about specific challenges faced when teams are geographically distributed and some of the best practices that have helped in my experiences as onsite coordinator as well as offshore project manager.
Backlog blunders can undermine an agile team's productivity. Common issues include stories that are unclear or lack acceptance criteria, dependencies between stories that are not defined, and estimates set too high due to unknowns. Formatting stories well with clear acceptance criteria and estimating honestly helps. Regularly refining the backlog through ceremonies ensures it remains valuable and prioritized based on feedback. Defining "done" criteria and keeping the backlog transparent helps teams deliver working functionality each sprint.
The document provides 10 secrets for managing successful projects from an experienced project manager. It discusses the importance of having a detailed plan and schedule, daily stand-up meetings, managing issues and risks, clear communication, mediating team discussions, managing scope, addressing resource issues, and caring about the project's success. Project management fundamentals like scope, schedule, budget, risk, and issues are also covered.
Webvirtue is a leading offshore software development company based in India specialized in ecommerce software development, custom software development, web software development and more. For more details visit here http://www.webvirtue.com/software-development.php
Agile and DevOps Transformations in Large OrganizationsTechWell
Many large scale organizations experience significant challenges as they pursue agile and DevOps transformations. They embark on adopting agile practices yet fail to reap the benefits of continuous release and delivery. Siraj Berhan explores common challenges—people, processes, technology, and operations—in the agile journey of large-scale organizations. Siraj explores a project suitability assessment tool for evaluating as well as mitigating risks specific to agile delivery, incorporating a time-and-material funding model, and maintaining a cross-functional self-managing team with a generalist-specialist attitude. Siraj discusses moving from a test-last mentality to a test-driven culture with a heavy emphasis on automation that supports continuous integration, release, and delivery. He offers suggestions for promoting collocated development model to maximize the team’s agility and velocity while leveraging the usage of collaboration tools to its fullest. Explore ways to revamp engineering skillsets across the enterprise with practices and approaches that enable agility. Learn twelve helpful tips for getting started and additional advice for scaling your agile and DevOps journey.
The document discusses the business case for adopting agile methods. It outlines how business environments have become more dynamic and uncertain, requiring more flexible approaches. Agile prioritizes individuals, interactions, working software and responding to change over rigid processes and documentation. Common myths about agile are addressed, and how agile approaches help manage risk and deliver value incrementally through iterative development and feedback loops. The document advocates that both teams and enterprises need to change to become more collaborative, customer-centric and quality-focused to succeed with agile.
Titas Lapinskas - Technical Team Leader in AgileAgile Lietuva
This document discusses the role of a technical team leader in agile projects. It describes when Scrum works well for projects, such as those with stable teams developing codebases over many years. It also discusses when Scrum may not be suitable, like for short-term projects with fixed costs, schedules, and scopes. The technical team leader acts as a group player, specialist, and manager, providing technical leadership. Their responsibilities include infrastructure setup, prototyping, documentation, and code reviews when needed. The goal is to help the team grow their skills over time and avoid failures by preventing issues before they occur.
Lean Software Development: Values and PrinciplesBalaji Sathram
This document discusses Lean Software Development. It begins with a brief history of Lean, noting its origins in manufacturing and its application to software development starting in the 1990s. It then defines Lean according to the five pillars of Lean thinking: value, value stream, flow, pull, and perfection. The document outlines six Lean values related to accepting human factors and complexity while striving for better economic and social outcomes. It also lists seven Lean principles for software development, such as eliminating waste, building quality in, and respecting people. The document provides examples of Lean practices and concludes that Lean is a methodology for trimming non-value-added activities from the software development process while following any development methodology.
Introduction to Agility from Saint Louis Day of Dot Net session:
History, Definition, Comparison to Waterfall, Agile methodologies, Myths & Misconceptions, Common failure, & Advanced discussion points.
This document provides an overview of designing a minimum viable product (MVP). It defines an MVP and explains why they are useful for reducing risk and getting faster feedback. An example is given of how Dropbox designed their MVP by identifying their riskiest assumption that people would try an easy to use file syncing product. Attendees will learn how to use a tool called the Javelin Board to develop their own MVP by turning assumptions into experiments. The agenda includes explaining problem statements, demonstrating the Javelin Board technique, having participants practice on the boards, and discussing next steps after ideating an MVP.
You’re already selling ahead of your roadmap and your dev team is getting pretty big. Trish Khoo outlines two approaches to keeping pace and quality high without hiring an army, drawing on a decade of software testing at Campaign Monitor, Google and Microsoft.
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.
Business Case for Agile - Time for ROI CheckTathagat Varma
When we talk of agility, we often refer to number of user stories or story points delivered, or burn down charts or velocity, etc. I call them 'lower-order agility' and howsomuch interesting they are, they make no sense to the 'higher-order agility' at business level. Why is that outrageous claims of performance, productivity and quality improvements at lower-order agility don't translate to commensurate higher-order agility? In this talk, I explore some of these issues. I also propose some ideas on how the whole notion of portfolio planning should be seen in the context of higher-order agility.
I delivered this talk on 19 July 2012 at the launch of Agile Leadership Network, Bangalore chapter, hosed by Valtech at their office.
I have an app idea, now what (ascendle) (ProductCamp Boston 2016)ProductCamp Boston
You have a great idea for an app...but you aren't technical. How do you get your app built? Where do you start? What are your options?
In this session, software expert Dave Todaro will outline your options. He'll explain the benefits and drawbacks of each approach and give you tips to get what you want and avoid getting burned.
You'll learn:
Various approaches including a technical co-founder, contractors, and outsourcing.
The difference between on-shoring, near-shoring, offshoring and hybrid models.
Credibility indicators to look for when choosing a software development partner.
When it's the right move to hire your own in-house team.
What to keep in mind for after your product ships.
About Dave Todaro
President/COO of @Ascendle, a firm specializing in agile coaching, software product strategy and commercial-grade mobile and web app development. bio from Twitter
Dave has spent the last 30+ years designing and building mission-critical software applications in a variety of leadership roles.
He is Founder, President and COO of Ascendle, a contract software development firm in Southern New Hampshire that specializes in custom cloud and mobile solutions for small to midsize businesses.
Dave started programming at age 11 and shipped his first commercial software product at age 15. He is the former chairman of the Software Association of New Hampshire.
The document discusses five things to do before implementing Agile practices: 1) Identify the reasons for adopting Agile, 2) Inform and educate teams and the organization about Agile ways of working, 3) Define engineering practices to use, 4) Define a product backlog, and 5) Set a definition of done. It emphasizes understanding why an organization wants to adopt Agile and how Agile will benefit the organization. It also discusses communicating changes to working styles and focusing on developing working software iteratively.
The document discusses developing a career development plan, including getting certified in software testing, attending conferences and workshops, and participating in a local professional association to expand knowledge and skills in the automation testing field. It also provides examples of SMART goals for these career development activities and outlines training phases for learning automation testing skills using Ruby and other tools. The plan aims to benchmark current skills and develop new skills to progress in an automation QA analyst role.
Agile Metrics to Boost Software Quality improvementXBOSoft
Why don't metrics apply to Agile development methodologies? Wrong! They Do, but you have to know how and when.
Find out in this webinar (recording) in special collaboration with the Chicago Quality Assurance Association (CQAA).
Agile, a development methodology, designed to allow team members to work iteratively during the development process instead of delivering a final product all at once, is now 20 years old. And when it comes to testing within an Agile process, there are those that use pyramids, and rectangles as mental models for where you should put your effort, or not.
Sometimes, software quality in Agile is mistranslated as the idea that everyone is responsible for software testing. But within Agile software development, ensuring quality is much more than testing and must include activities at different levels, including estimates for the workload for each iteration. Otherwise, testing happens last minute—or sometimes not at all, depending on time constraints. To have a successful Agile team, most software developers know that velocity is an essential component.
But it’s not just about measuring velocity, as velocity is only one factor or measurement for success. There are many other factors to measure when you want to assess the success of your Agile team in delivering a quality product. In this webinar, we specifically look at some key metrics for us the measure the success and progress of our quality in Agile.
Tune in with Philip Lew as he goes through ways you can gather insights in slicing, dicing, and analyzing (and interpreting) data. We’ll use Jira as an example, but you can do this with practically any issue tracking collaboration tool to help your team improve software quality.
Our top 10 Metrics reveal the most fundamental data points Agile methodology requires to work effectively, and will put you on the highly targeted path to successful implementation of your Agile processes.
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
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.
Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone AgileSparks
The document summarizes Pelephone IT's transition to agile methodologies. It describes how Pelephone IT struggled with long development cycles, inability to adapt to changes, and internal blaming cultures. This prompted them to learn agile/Kanban approaches. They started by training managers and developers, then formed cross-functional teams and began regular production releases. This improved time to market, collaboration, and business satisfaction. Moving forward, Pelephone IT aims to refine their agile practices and skills through experience, with an understanding that change takes time and mistakes are expected.
Managing IT Projects - Onsite Offshore CoordinationMahesh Dedhia
In the Software industry, quite often development and testing jobs are outsourced and a small percentage of the team is placed at the client location to coordinate between client teams and offshore teams. This presentation talks about specific challenges faced when teams are geographically distributed and some of the best practices that have helped in my experiences as onsite coordinator as well as offshore project manager.
Backlog blunders can undermine an agile team's productivity. Common issues include stories that are unclear or lack acceptance criteria, dependencies between stories that are not defined, and estimates set too high due to unknowns. Formatting stories well with clear acceptance criteria and estimating honestly helps. Regularly refining the backlog through ceremonies ensures it remains valuable and prioritized based on feedback. Defining "done" criteria and keeping the backlog transparent helps teams deliver working functionality each sprint.
The document provides 10 secrets for managing successful projects from an experienced project manager. It discusses the importance of having a detailed plan and schedule, daily stand-up meetings, managing issues and risks, clear communication, mediating team discussions, managing scope, addressing resource issues, and caring about the project's success. Project management fundamentals like scope, schedule, budget, risk, and issues are also covered.
Webvirtue is a leading offshore software development company based in India specialized in ecommerce software development, custom software development, web software development and more. For more details visit here http://www.webvirtue.com/software-development.php
Agile and DevOps Transformations in Large OrganizationsTechWell
Many large scale organizations experience significant challenges as they pursue agile and DevOps transformations. They embark on adopting agile practices yet fail to reap the benefits of continuous release and delivery. Siraj Berhan explores common challenges—people, processes, technology, and operations—in the agile journey of large-scale organizations. Siraj explores a project suitability assessment tool for evaluating as well as mitigating risks specific to agile delivery, incorporating a time-and-material funding model, and maintaining a cross-functional self-managing team with a generalist-specialist attitude. Siraj discusses moving from a test-last mentality to a test-driven culture with a heavy emphasis on automation that supports continuous integration, release, and delivery. He offers suggestions for promoting collocated development model to maximize the team’s agility and velocity while leveraging the usage of collaboration tools to its fullest. Explore ways to revamp engineering skillsets across the enterprise with practices and approaches that enable agility. Learn twelve helpful tips for getting started and additional advice for scaling your agile and DevOps journey.
The document discusses the business case for adopting agile methods. It outlines how business environments have become more dynamic and uncertain, requiring more flexible approaches. Agile prioritizes individuals, interactions, working software and responding to change over rigid processes and documentation. Common myths about agile are addressed, and how agile approaches help manage risk and deliver value incrementally through iterative development and feedback loops. The document advocates that both teams and enterprises need to change to become more collaborative, customer-centric and quality-focused to succeed with agile.
Titas Lapinskas - Technical Team Leader in AgileAgile Lietuva
This document discusses the role of a technical team leader in agile projects. It describes when Scrum works well for projects, such as those with stable teams developing codebases over many years. It also discusses when Scrum may not be suitable, like for short-term projects with fixed costs, schedules, and scopes. The technical team leader acts as a group player, specialist, and manager, providing technical leadership. Their responsibilities include infrastructure setup, prototyping, documentation, and code reviews when needed. The goal is to help the team grow their skills over time and avoid failures by preventing issues before they occur.
Lean Software Development: Values and PrinciplesBalaji Sathram
This document discusses Lean Software Development. It begins with a brief history of Lean, noting its origins in manufacturing and its application to software development starting in the 1990s. It then defines Lean according to the five pillars of Lean thinking: value, value stream, flow, pull, and perfection. The document outlines six Lean values related to accepting human factors and complexity while striving for better economic and social outcomes. It also lists seven Lean principles for software development, such as eliminating waste, building quality in, and respecting people. The document provides examples of Lean practices and concludes that Lean is a methodology for trimming non-value-added activities from the software development process while following any development methodology.
Introduction to Agility from Saint Louis Day of Dot Net session:
History, Definition, Comparison to Waterfall, Agile methodologies, Myths & Misconceptions, Common failure, & Advanced discussion points.
This document provides an overview of designing a minimum viable product (MVP). It defines an MVP and explains why they are useful for reducing risk and getting faster feedback. An example is given of how Dropbox designed their MVP by identifying their riskiest assumption that people would try an easy to use file syncing product. Attendees will learn how to use a tool called the Javelin Board to develop their own MVP by turning assumptions into experiments. The agenda includes explaining problem statements, demonstrating the Javelin Board technique, having participants practice on the boards, and discussing next steps after ideating an MVP.
You’re already selling ahead of your roadmap and your dev team is getting pretty big. Trish Khoo outlines two approaches to keeping pace and quality high without hiring an army, drawing on a decade of software testing at Campaign Monitor, Google and Microsoft.
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.
Business Case for Agile - Time for ROI CheckTathagat Varma
When we talk of agility, we often refer to number of user stories or story points delivered, or burn down charts or velocity, etc. I call them 'lower-order agility' and howsomuch interesting they are, they make no sense to the 'higher-order agility' at business level. Why is that outrageous claims of performance, productivity and quality improvements at lower-order agility don't translate to commensurate higher-order agility? In this talk, I explore some of these issues. I also propose some ideas on how the whole notion of portfolio planning should be seen in the context of higher-order agility.
I delivered this talk on 19 July 2012 at the launch of Agile Leadership Network, Bangalore chapter, hosed by Valtech at their office.
I have an app idea, now what (ascendle) (ProductCamp Boston 2016)ProductCamp Boston
You have a great idea for an app...but you aren't technical. How do you get your app built? Where do you start? What are your options?
In this session, software expert Dave Todaro will outline your options. He'll explain the benefits and drawbacks of each approach and give you tips to get what you want and avoid getting burned.
You'll learn:
Various approaches including a technical co-founder, contractors, and outsourcing.
The difference between on-shoring, near-shoring, offshoring and hybrid models.
Credibility indicators to look for when choosing a software development partner.
When it's the right move to hire your own in-house team.
What to keep in mind for after your product ships.
About Dave Todaro
President/COO of @Ascendle, a firm specializing in agile coaching, software product strategy and commercial-grade mobile and web app development. bio from Twitter
Dave has spent the last 30+ years designing and building mission-critical software applications in a variety of leadership roles.
He is Founder, President and COO of Ascendle, a contract software development firm in Southern New Hampshire that specializes in custom cloud and mobile solutions for small to midsize businesses.
Dave started programming at age 11 and shipped his first commercial software product at age 15. He is the former chairman of the Software Association of New Hampshire.
The document discusses five things to do before implementing Agile practices: 1) Identify the reasons for adopting Agile, 2) Inform and educate teams and the organization about Agile ways of working, 3) Define engineering practices to use, 4) Define a product backlog, and 5) Set a definition of done. It emphasizes understanding why an organization wants to adopt Agile and how Agile will benefit the organization. It also discusses communicating changes to working styles and focusing on developing working software iteratively.
The document discusses developing a career development plan, including getting certified in software testing, attending conferences and workshops, and participating in a local professional association to expand knowledge and skills in the automation testing field. It also provides examples of SMART goals for these career development activities and outlines training phases for learning automation testing skills using Ruby and other tools. The plan aims to benchmark current skills and develop new skills to progress in an automation QA analyst role.
Agile Metrics to Boost Software Quality improvementXBOSoft
Why don't metrics apply to Agile development methodologies? Wrong! They Do, but you have to know how and when.
Find out in this webinar (recording) in special collaboration with the Chicago Quality Assurance Association (CQAA).
Agile, a development methodology, designed to allow team members to work iteratively during the development process instead of delivering a final product all at once, is now 20 years old. And when it comes to testing within an Agile process, there are those that use pyramids, and rectangles as mental models for where you should put your effort, or not.
Sometimes, software quality in Agile is mistranslated as the idea that everyone is responsible for software testing. But within Agile software development, ensuring quality is much more than testing and must include activities at different levels, including estimates for the workload for each iteration. Otherwise, testing happens last minute—or sometimes not at all, depending on time constraints. To have a successful Agile team, most software developers know that velocity is an essential component.
But it’s not just about measuring velocity, as velocity is only one factor or measurement for success. There are many other factors to measure when you want to assess the success of your Agile team in delivering a quality product. In this webinar, we specifically look at some key metrics for us the measure the success and progress of our quality in Agile.
Tune in with Philip Lew as he goes through ways you can gather insights in slicing, dicing, and analyzing (and interpreting) data. We’ll use Jira as an example, but you can do this with practically any issue tracking collaboration tool to help your team improve software quality.
Our top 10 Metrics reveal the most fundamental data points Agile methodology requires to work effectively, and will put you on the highly targeted path to successful implementation of your Agile processes.
XBOSoft runs through the Top 10 Agile Metrics revealing the most fundamental data points Agile methodology requires to work effectively, and will put you on the highly targeted path to successful implementation of your Agile processes.
XBOSoft and Go2Group run through the top data points you should be measuring in your Agile Workflow. We’ll show you what to track, when and how often, and most importantly – why. Many believe that metrics are useless, but unless you measure, how can you systematically improve or know how you are doing? And with velocity as an overarching objective in agile, you should be tracking other things so that you know what else you could be impacting by going faster. But, with all the metrics so readily available to us today, how do we filter through to the most meaningful?
Software quality improvement expert Jan Princen and XBOSoft CEO Philip Lew discuss the use of Predictive Analytics to prevent software defects in this XBOSoft webinar on Defect Prevention.
Barely any modern software development project will be initiated without the discussion on test automation. With the demand to deliver software products in higher quality faster, test automation is oftentimes perceived by project leads as the silver bullet, allowing to ‘test everything’ without high overhead in employing skilled workforce. The tools are being discussed more often, than development and maintenance costs of automation frameworks that can support projects from inception into delivery and post-production.
Incorrect approaches that result in choosing invalid test automation strategies are often the cause of much frustration later in the project, when the reality of test automation activities become visible and need to be accounted for.
In this webinar, Anna will discuss her experiences in selecting short term and long term test automation strategies applied within various contexts, various skill sets that are required for running a successful test automation project, and suggest alternatives to full-blown test automation with the insufficient project resources.
Learn:
* when the test automation is an enabler, and when it’s an impediment to project success
* when to start planning for automation, and how to select the tools and methods most suitable for specific project needs
* how to anticipate investment costs and support long term automation effort across multiple projects
* skills and roles in test automation
150 this is not my beautiful product how did i get here-communicating your ...ProductCamp Boston
This document outlines five strategies for communicating a product message more accurately and successfully within and outside an organization. It discusses common problems that arise during handoffs between product managers and marketers, such as inaccurate or missing information in marketing collateral. To address this, it presents a repeatable "Product SBAR" process involving five steps: understanding the product's scope, value proposition, assets, relaying domain knowledge, and establishing communication norms. Using a standardized template can help ensure the right message is conveyed concisely and consistently throughout the product launch process.
This PPT is from the Mobile Testing Report 2015 by XBOSoft. The PPT summarizes some of the major findings and was discussed in a webinar with panelists, Melissa Tondi, Lloyd Bell and Raj
The document summarizes the key principles of the Lean Startup methodology for building startups. It discusses two tales of startups, one that failed spending $40M over 5 years by making assumptions without customer validation, and one called IMVU that shipped frequently and earned $10M in revenue in 2007. The Lean Startup methodology advocates continuous deployment, rapid A/B testing to validate hypotheses, and using the "Five Whys" technique to understand root causes of problems. Adopting these principles can help startups iterate quickly and reduce the risk of expensive failures.
This chapter introduces fundamentals of software testing. It discusses the skills required to become a software tester, including analytical, communication, time management, and technical skills. It explains the importance of software testing and principles of testing such as defect clustering, pesticide paradox, and early testing. It also discusses the difference between the software development lifecycle and software testing lifecycle, with testing phases corresponding to development phases.
Agile Product and User-Centered Design Methodologies Webinar - XBOSoftXBOSoft
This document summarizes an Agile product and user-centered design webinar hosted by XBOSoft. The webinar discusses integrating user research methods like usability testing, personas and prototypes into Agile software development processes. It emphasizes establishing a culture where employees are empowered to explore user needs and provide early, continuous feedback to improve products. The webinar aims to help organizations make better products faster by putting users first.
The bank achieved 95% automation of testing with IBM Rational Quality Management Solutions. They established a central testing unit with standardized testing methodology and tools. This was done in response to issues found during a second core banking system release. Challenges included determining what to automate, managing test environments, and dealing with legacy applications. Future goals are to test all new releases within 5 days and provide testing support for new projects.
Technology has come a long way and with it, the daunting task of delivering even quicker software releases. How can you keep up with the demand of ever increasing development cycles, agile methodologies and a desire to move as fast as possible while maintaining quality?
Crowdsourced testing delivers a unique, scalable and affordable option to deliver exactly the kind of quality your mobile apps and websites deserve. Find out the fundamentals of crowdsourced testing and determine exactly how to implement it within your own organisation.
Want to know more? Visit https://www.globalapptesting.com to learn more.
XBOSoft webinar - How Did I Miss That Bug - Cognitive Biases in Software TestingXBOSoft
The document discusses cognitive biases that can cause testers to miss bugs. It explains that software testing involves both objective comparisons to specifications as well as subjective judgments, and that missed bugs result from errors in judgment influenced by cognitive biases. Some biases discussed include representative bias, confirmation bias, and anchoring effect. The document advocates managing cognitive biases through techniques like exploratory testing, which focuses more on intuition and learning than requirements coverage. It suggests testers, managers, and the QA profession shift focus from finding bugs to providing information.
Agile Metrics - how to use metrics to manage agile teamsXBOSoft
In managing agile teams, how to use tools and agile metrics to improve velocity, lower costs or increase end user experience.
- How to use metric to manage agile teams
- What tools to use to analyze those metrics
- How to create and improve development through a dashboard
The document summarizes an exploratory testing workshop. It discusses exploratory testing approaches, common traps testers fall into, and provides tips for effective exploratory testing. As an exercise, participants are asked to use exploratory testing to find issues with a Tilted Twister device within 20 minutes. Key problems identified include inability to detect color differences, motor arm overshooting, difficulty turning it on, calibration cube being too big, and taking too long to solve with memory issues. The debrief discusses the testing process and importance of the tester mindset in exploratory and automated testing.
Presentation for ICCA Boston on October 29, 2008.
Abstract:
The facts are all stacked against us as consultants: 30+% requirements churn for projects, with 50+% of projects completing late or failing entirely and a market mindset of instant gratification. How do small consulting companies compete in today’s environment without having to take incredible risks along the way? This is the key question facing leaders of small firms. Clients are getting harder to find in an economic climate that is eroding so we have to make every client count! To do this effectively is going to require changing the way we do business. One potential solution is use of agile practices and principles to drive an agile process.
This presentation will explore the principles and practices that drive the agile process. In particular it will look at how using an agile approach can help mitigate risk for small consulting businesses. It will also explain the potential client benefits from using an agile approach. When the vendor is providing exceptional value to the client a long-term relationship can be established which benefits both parties. From the perspective of a small consulting company these relationships are the most valuable not just from a revenue perspective, but also as references and for word-of-mouth lead generation. This presentation will describe how having an agile approach in your toolbox may be enable you to unlock additional opportunities.
How to assess your it needs and implement technology at your nonprofitTechSoup Canada
This document outlines 8 steps for nonprofits to assess their IT needs and implement new technology:
1. Assess the entire organization including size, geography, goals, pain points and new technology needs.
2. Evaluate network assets such as firewalls, routers, switches and wireless access points to identify vulnerabilities.
3. Review servers to ensure reliability, warranty coverage, security updates and disaster recovery.
4. Assess workstations and laptops for operating systems, security, software and administrator access.
5. Evaluate line-of-business software for support, hosting, future needs and reliability.
6. Review policies on acceptable use, email/computer monitoring, and bring-your
Talk for Business of Software 2015 (Boston) laying out some laws of gravity for the software business. Also serialized as 4 long posts on www.mironov.com
Similar to Are You Making These 7 'Testing Metric' Mistakes? Webinar - Mark Bentsen, Philip Lew (20)
Agile Test Management Using Jira and ZephyrXBOSoft
Do you have traceability where you can efficiently determine the cause of defects if there was an unclear requirement? Are you sure your test cases cover your requirements? Can you easily execute targeted regression when you’ve updated your software’s functionality? Now with software development teams mostly working from home or in dispersed geographies, supporting effective collaboration between remote workers is critical. In this XBOSoft quarterly webinar, our CEO, Philip Lew, teams up with BDQ’s CEO Chris Bland, to discuss the problems with working remotely, integrating the phases of testing in development in an Agile, and how this can be done using Zephyr, one of the predominant plugins in the Atlassian marketplace for test management. In this webinar, you will learn how to:
--Link tests with user stories and group tests within test cycles.
--Tie your results (defects) all the way back to user stories for effective defect root cause analysis.
--Classify defects to analyze and prioritize your test efforts.
--Use the traceability matrix with Zephr for deep visibility into your Agile process.
Is this possible? Artificial Intelligence Based Test Automation but with no AI? Well, according to Jeremias Roessler, it is! Find out how in this quarterly webinar slidedeck with XBOSoft's special guest speaker, Jeremy Rößler. What good are 400 additional AI-generated UI tests, if we don’t want to maintain our existing human-created ones? This question lies at the heart of AI-based test generation. Recheck-web addresses this issue elegantly and without any “AI-magic” … using a whole different approach to test automation. This refreshingly unusual approach to test automation (difference testing) has many advantages over conventional test automation and he shows how to overcome the oracle problem. This approach makes tests easy to create and maintain, robust and more complete. You can use this approach today in your existing UI testing setup for websites (currently available for Selenium/Java, more to come).
What Aircrews Can Teach Software Testing Teams - XBOSoft Webinar w/Peter VarholXBOSoft
Aircrew resource management principles enable any team member to question decisions and directions that seem to be wrong. Testing teams, whose members have diverse experience and expertise that give them different perspectives, need to embrace these principles to make the right decisions.
United Flight 232 should have crashed with 296 lives lost. In contrast, Asiana Flight 214 should not have crashed at all. The critical difference between the two was the interactions of their respective aircrews. Aircrew resource management refers to how cockpit crew members work together to make flights as safe and efficient as possible. These principles have been applied to other professional fields, and should be a central practice of every testing team.
Testing teams require expertise in all aspects of software design, development, test, delivery, and operations. There can be no “command pilot” whose expertise over all aspects of testing is greater than the combined expertise and experience of others. And while the leader of the team is the final authority, he or she must listen to and consider team members whose knowledge and experience can make the difference between success and failure.
This presentation discusses how aircrew resource management has evolved to focus on expertise, collaboration, and decision-making in the cockpit. It applies these lessons to testing teams, where complementary expertise is necessary to deliver high quality and working applications, updated continuously. It highlights the characteristics of successful aircrew teams and how those characteristics apply to building and delivering great software.
Attendees will learn:
1. What testing teams can learn from successful teams in other fields.
2. How testing teams must work collaboratively, especially in crises and under pressure.
3. How blind deference to authority and automation can be detrimental to a testing team.
Agile User Acceptance Testing - Incorporating UAT into AgileXBOSoft
This document discusses incorporating user acceptance testing (UAT) into Agile development processes. It provides an overview of XBOSoft, a company dedicated to software quality improvement. It then discusses some common problems with traditional UAT approaches and how UAT can be better integrated into Agile. Key aspects covered include developing epics and user stories, writing acceptance criteria, and defining acceptance tests. The presentation provides examples and best practices for representing requirements in a way that facilitates effective UAT within an Agile framework.
Challenges in Using Big Data for Software QAXBOSoft
In this webinar, our guest speakers, Jennifer Bonine and Rick Faulise from TapQA shared their thoughts on using #BigData for #softwaretesting and #SoftwareQA. What #metrics to use and what not to use, and how to combine them together to get some real meaning and insights versus just data.
Defect Patterns Analysis for Agile and Waterfall - XBOSoft Webinar with Micha...XBOSoft
Whether you’re waterfall or agile, this presentation will uncover 3 keys to accelerating schedule by managing defect prevention, detection, and remediation by software teams. Actual Industry Case Studies will reveal how to implement an end-to-end defect strategy that maximizes the likelihood of team’s success. Topics covered will include waterfall, Agile, pair programming, test-driven development, and outsourced projects. We’ll also look at techniques that use defect curves to “predict the trajectory” of a project and its Development and QA phases.
Proactive SQA™ Shifting Left w/Proactive Software Quality PracticesXBOSoft
This webinar hosted by XBOSoft featured our guest speaker, Robin Goldsmith. Robin, an expert in software requirements and business analysis, presented how to develop a definition of software quality as a first step any software development process. Although most of what is called SQA today actually is just testing, true SQA is much different from quality control (QC) testing. SQA can and should do far more, contributing proactively to assure the software process in fact does the right things well so it truly produces high quality cheaper, preventing errors or catching them earlier when they can be fixed more easily. This interactive webinar positions SQA and explains the six proactive functions it should perform to provide far greater value.
Mobile Testing Challenges and Solutions XBOSoft WebinarXBOSoft
In this webinar, XBOSoft's VP of Engineering discusses some of the challenges that he and his team have faced in the areas of mobile test automation and mobile usability testing. He'll discuss how to gain the best platform coverage, when to use automation, when not to, and when to use shared cloud services versus emulators and real devices.
Heidi Araya - XBOSoft Webinar Guest Speaker - Working with Remote Agile TeamsXBOSoft
In this XBOSoft webinar, we were glad to have Heidi Araya, a seasoned agile coach, discuss the reality or non-reality of agile teams being colocated. She covered many tips and techniques for working remotely in an agile environment.
PSQT Keynote: Quality Challenges in the Internet of Things EraXBOSoft
The Internet of Things is made up of three core elements: things, communications and computing. Things are devices connected to the Internet such as a watch, car or appliances in your home. For IoT to work, these things need to be connected, communicating statuses and other information with each other in real time. And with this information, the last element of IoT is computing and storage. What will all this information be used for? What actions can or should be taken? How and where will the information be stored, on a server, on a mobile phone? And who will it be accessible by?
IoT offers both efficiency and automation to daily life, and with an estimated 26 billion connected devices by 2020, there’s bound to be issues with security, reliability and connectivity within that enormous, intricate network. This makes the role of QA critical.
For example: security. Will someone be able to hack into my home network and then into my wearable device and steal my medical information? Then there’s data storage, the actual efficiency of the device and user interactions to account for. IoT is still growing so quickly that QA testers must be able to keep up with the increasing complexity of it as it continues to expand.
Simply making sure that the device and its software works correctly in a controlled environment in isolation is not acceptable. Yet, how can you test all the scenarios? Scenarios include not only the multitude of devices that can connect together in a combination of ecosystems, but also, the data they produce. How we develop test data sets that accurately represent the real world must also be considered, as well as how we can make sure it is secure with such a multitude of sensors collecting data. Lastly, IoT is not about devices. We still have to make sure the user has an integrated experience across devices and software. Hence, usability in IoT could be the most overlooked game breaker for IoT. In this session, find out the latest technologies, thought patterns, techniques and methods to move beyond old school QA (desktops, web and mobile) where devices work mostly in isolation.
7 Habits of Highly Effective Agile Testing - Test IstanbulXBOSoft
This document summarizes a presentation on applying Stephen Covey's 7 Habits of Highly Effective People to agile testing. It discusses the original 7 habits and how they can help teams succeed with agile. Maintaining an improvement mindset, treating users as the top priority, and building trust are some key ways the habits were applied. Regular retrospectives and a focus on efficiency and effectiveness were emphasized as important agile practices.
Managing Agile Software Projects With Risk and UncertaintyXBOSoft
In chasing velocity, we often ignore or don’t understand the uncertainties and associated risks in our processes and their results. Agile is designed to handle uncertainty in requirements as new features are requested and priorities shift. But shouldn’t we also be thinking about and mitigating the uncertainties that are unique or even introduced by using agile? Phil Lew suggests that our problem is that we sometimes carry assumptions which either cause us to spend too much effort on things we can’t control or give us unfounded comfort and reassurance. If we can’t understand the uncertainties and risks, how can we have confidence in our software as systems become more complex? Phil overlays classic risk management techniques with an agile process to identify and address the uncertainties that matter—and those that don’t. Then Phil outlines methods that you can use to address these risks while maintaining rhythm in your agile software processes. Come and learn about risks you never thought of and see how you can manage or avoid them.
Top IOT Testing Challenges Webinar with Jon HagarXBOSoft
Our special guest embedded and IOT testing expert Jon Hagar shares his thoughts on mobile testing, embedded testing, and IOT testing and how they intersect to form the perfect storm in the coming 4th Industrial Revolution where all businesses become software businesses and security/privacy reach new heights of concern.
Testing in Agile with Coaching Agile Journeys and XBOSoftXBOSoft
Philip Lew joins Coaching Agile Journeys to discuss Testing in Agile. In this webinar, Phil covers the agile process and how agile testing not only fits in, but how software testers can move up and downstream to improve quality throughout.
Using JMeter and Google Analytics for Software Performance TestingXBOSoft
Ed Curran, VP of Engineering at XBOSoft, shares some of his hands on experience in working with JMeter for load and performance testing. In the webinar, he provided explanations of different types of performance testing and how you can use Google Analytics to understand what users are really doing on your web apps and then how to leverage JMeter and analyze the results to improve your app's performance.
Storytelling: Discover the Big Picture for Agile Efforts Webinar - Tom Cagley...XBOSoft
This document summarizes a webinar about using storytelling for agile efforts. It introduces the speakers and provides an overview of how storytelling has been used historically. Additionally, it discusses different types of story patterns that can be used, elements of business stories, facilitating storytelling sessions, and using a process of generating a "big picture" story. Examples of techniques like the Lean Change Canvas and a six-word story exercise are also presented.
ASTQB w/ XBOSoft CEO Phil Lew: Agile and Waterfall - What Do Testers Do Diffe...XBOSoft
ASTQB invited XBOSoft CEO Phil Lew to present a webinar on the differences between Agile testing and other testing methods.
Visit xbosoft.com for more Agile testing resources.
When Agile is a Quality Game Changer Webinar - Michael Mah, Philip LewXBOSoft
Accelerate your Agile success with in-depth research and smarter decisions. Michael Mah of QSM Associates shows you what it takes to find and utilize patterns of successful Agile development in this quarterly XBOSoft webinar.
QAI QUEST 2016 Webinar Series: Pairwise Testing w/ Philip LewXBOSoft
In anticipation of the QAI QUEST 2016 Conference & Expo in Chicago, Illinois, XBOSoft’s CEO Philip Lew presented a live webinar on Pairwise Testing. Find out what pairwise testing is, the advantages and disadvantages of implementing this method, and when to use it and how.
For Philip Lew's demonstration of pairwise testing, view the recorded webinar at https://vimeo.com/155889518
FluentConf 2016: Avoiding Critical UX Mistakes with Philip LewXBOSoft
Here are the slides from XBOSoft CEO Philip Lew's presentation at the 2016 Fluent Conference in San Francisco (March 7-10, 2016). Lew covered how to avoid critical UX mistakes and how to keep your users coming back with more than just "pretty colors and buttons."
DevOps Consulting Company | Hire DevOps Servicesseospiralmantra
Spiral Mantra excels in providing comprehensive DevOps services, including Azure and AWS DevOps solutions. As a top DevOps consulting company, we offer controlled services, cloud DevOps, and expert consulting nationwide, including Houston and New York. Our skilled DevOps engineers ensure seamless integration and optimized operations for your business. Choose Spiral Mantra for superior DevOps services.
https://www.spiralmantra.com/devops/
Alluxio Webinar | 10x Faster Trino Queries on Your Data PlatformAlluxio, Inc.
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
The Comprehensive Guide to Validating Audio-Visual Performances.pdfkalichargn70th171
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.
Odoo releases a new update every year. The latest version, Odoo 17, came out in October 2023. It brought many improvements to the user interface and user experience, along with new features in modules like accounting, marketing, manufacturing, websites, and more.
The Odoo 17 update has been a hot topic among startups, mid-sized businesses, large enterprises, and Odoo developers aiming to grow their businesses. Since it is now already the first quarter of 2024, you must have a clear idea of what Odoo 17 entails and what it can offer your business if you are still not aware of it.
This blog covers the features and functionalities. Explore the entire blog and get in touch with expert Odoo ERP consultants to leverage Odoo 17 and its features for your business too.
An Overview of Odoo ERP
Odoo ERP was first released as OpenERP software in February 2005. It is a suite of business applications used for ERP, CRM, eCommerce, websites, and project management. Ten years ago, the Odoo Enterprise edition was launched to help fund the Odoo Community version.
When you compare Odoo Community and Enterprise, the Enterprise edition offers exclusive features like mobile app access, Odoo Studio customisation, Odoo hosting, and unlimited functional support.
Today, Odoo is a well-known name used by companies of all sizes across various industries, including manufacturing, retail, accounting, marketing, healthcare, IT consulting, and R&D.
The latest version, Odoo 17, has been available since October 2023. Key highlights of this update include:
Enhanced user experience with improvements to the command bar, faster backend page loading, and multiple dashboard views.
Instant report generation, credit limit alerts for sales and invoices, separate OCR settings for invoice creation, and an auto-complete feature for forms in the accounting module.
Improved image handling and global attribute changes for mailing lists in email marketing.
A default auto-signature option and a refuse-to-sign option in HR modules.
Options to divide and merge manufacturing orders, track the status of manufacturing orders, and more in the MRP module.
Dark mode in Odoo 17.
Now that the Odoo 17 announcement is official, let’s look at what’s new in Odoo 17!
What is Odoo ERP 17?
Odoo 17 is the latest version of one of the world’s leading open-source enterprise ERPs. This version has come up with significant improvements explained here in this blog. Also, this new version aims to introduce features that enhance time-saving, efficiency, and productivity for users across various organisations.
Odoo 17, released at the Odoo Experience 2023, brought notable improvements to the user interface and added new functionalities with enhancements in performance, accessibility, data analysis, and management, further expanding its reach in the market.
Nashik's top web development company, Upturn India Technologies, crafts innovative digital solutions for your success. Partner with us and achieve your goals
A Comprehensive Guide on Implementing Real-World Mobile Testing Strategies fo...kalichargn70th171
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.
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdfBaha Majid
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.
Why Apache Kafka Clusters Are Like Galaxies (And Other Cosmic Kafka Quandarie...Paul Brebner
Closing talk for the Performance Engineering track at Community Over Code EU (Bratislava, Slovakia, June 5 2024) https://eu.communityovercode.org/sessions/2024/why-apache-kafka-clusters-are-like-galaxies-and-other-cosmic-kafka-quandaries-explored/ Instaclustr (now part of NetApp) manages 100s of Apache Kafka clusters of many different sizes, for a variety of use cases and customers. For the last 7 years I’ve been focused outwardly on exploring Kafka application development challenges, but recently I decided to look inward and see what I could discover about the performance, scalability and resource characteristics of the Kafka clusters themselves. Using a suite of Performance Engineering techniques, I will reveal some surprising discoveries about cosmic Kafka mysteries in our data centres, related to: cluster sizes and distribution (using Zipf’s Law), horizontal vs. vertical scalability, and predicting Kafka performance using metrics, modelling and regression techniques. These insights are relevant to Kafka developers and operators.
Unveiling the Advantages of Agile Software Development.pdfbrainerhub1
Learn about Agile Software Development's advantages. Simplify your workflow to spur quicker innovation. Jump right in! We have also discussed the advantages.
What to do when you have a perfect model for your software but you are constrained by an imperfect business model?
This talk explores the challenges of bringing modelling rigour to the business and strategy levels, and talking to your non-technical counterparts in the process.
Malibou Pitch Deck For Its €3M Seed Roundsjcobrien
French start-up Malibou raised a €3 million Seed Round to develop its payroll and human resources
management platform for VSEs and SMEs. The financing round was led by investors Breega, Y Combinator, and FCVC.
Liberarsi dai framework con i Web Component.pptxMassimo Artizzu
In Italian
Presentazione sulle feature e l'utilizzo dei Web Component nell sviluppo di pagine e applicazioni web. Racconto delle ragioni storiche dell'avvento dei Web Component. Evidenziazione dei vantaggi e delle sfide poste, indicazione delle best practices, con particolare accento sulla possibilità di usare web component per facilitare la migrazione delle proprie applicazioni verso nuovi stack tecnologici.
Orca: Nocode Graphical Editor for Container OrchestrationPedro J. Molina
Tool demo on CEDI/SISTEDES/JISBD2024 at A Coruña, Spain. 2024.06.18
"Orca: Nocode Graphical Editor for Container Orchestration"
by Pedro J. Molina PhD. from Metadev
Consistent toolbox talks are critical for maintaining workplace safety, as they provide regular opportunities to address specific hazards and reinforce safe practices.
These brief, focused sessions ensure that safety is a continual conversation rather than a one-time event, which helps keep safety protocols fresh in employees' minds. Studies have shown that shorter, more frequent training sessions are more effective for retention and behavior change compared to longer, infrequent sessions.
Engaging workers regularly, toolbox talks promote a culture of safety, empower employees to voice concerns, and ultimately reduce the likelihood of accidents and injuries on site.
The traditional method of conducting safety talks with paper documents and lengthy meetings is not only time-consuming but also less effective. Manual tracking of attendance and compliance is prone to errors and inconsistencies, leading to gaps in safety communication and potential non-compliance with OSHA regulations. Switching to a digital solution like Safelyio offers significant advantages.
Safelyio automates the delivery and documentation of safety talks, ensuring consistency and accessibility. The microlearning approach breaks down complex safety protocols into manageable, bite-sized pieces, making it easier for employees to absorb and retain information.
This method minimizes disruptions to work schedules, eliminates the hassle of paperwork, and ensures that all safety communications are tracked and recorded accurately. Ultimately, using a digital platform like Safelyio enhances engagement, compliance, and overall safety performance on site. https://safelyio.com/
All you need to know about Spring Boot and GraalVM
Are You Making These 7 'Testing Metric' Mistakes? Webinar - Mark Bentsen, Philip Lew
1. XBOSoft, Inc. All Rights Reserved. 1
Are You Making These 7 Metric Mistakes?
And What to Do If You Are
with Mark Bentsen, ARGO Data
#XBOSoftWebinar
#TestingMetricMistakes
2. XBOSoft
Dedicated to software quality improvement
Founded in 2006
We speed products to market with our expert:
• Software QA consulting
• Software testing
Global team with offices in San Francisco, Beijing
and Amsterdam
“Thorough, accurate and fast”
XBOSoft, Inc. All Rights Reserved. 2
3. House Rules
Participants other than the speakers are muted
Ask questions in the GoToWebinar control on the
R-side of your screen or through Twitter @XBOSoft
Questions may be asked throughout the webinar -
we’ll try to answer them at the end
You’ll receive info on recording after the webinar
XBOSoft, Inc. All Rights Reserved. 3
Event hashtags: #XBOSoftWebinar
#TestingMetricMistakes
4. Meet Our Speakers
Philip Lew
CEO and Founder, XBOSoft
• Relevant specialties and
passions
o Software quality process,
evaluation, measurement
and improvement
o Software quality in use /
UX design
o Mobile User Experience
and usability
o Cycling and travel
XBOSoft, Inc. All Rights Reserved. 4
Rachel Geibig
Marketing Manager, XBOSoft
• Emails you about our
industry hot topic
webinars
• Invites you to download
our latest trends in
software testing white
papers
XBOSoft Team
5. Guest Presenter
Mark Bentsen
XBOSoft, Inc. All Rights Reserved. 5
• Quality Assurance Manager, ARGO Data
CTAL-Full, CSTE, PMP, ASQ CMQ/OE
• Leading cross-enterprise collaboration in the DFW
area among Software Quality practitioners for the
past seven years. Gathering corporately on a
quarterly basis and on field trips to one another’s
work places, the QA Trailblazers are pushing each
other to expand the capabilities of the modern
software testing organization.
• He is the QA Manager of ARGO Data, a software development company providing
mission-critical and analytical solutions for financial services and healthcare.
• Mark & his wife Melissa are the President Couple of Better Marriages Texas and have
been active in Marriage Enrichment since they said “I do” in 2001. Prior to working in
technology, he worked in YWAM & Mercy Ships in Switzerland and Namibia.
• Contact: Mark.Bentsen@argodata.com
6. Agenda
XBOSoft, Inc. All Rights Reserved. 6
1. Why We’re Here
2. 7 Metrics Mistakes
3. What you can do about it!
7. Is There Ever TMI In Testing?
XBOSoft, Inc. All Rights Reserved. 7
• No
• But There Is TMD… Too Much Data
• Reporting too much data and not enough
information
8. What do we do?
XBOSoft, Inc. All Rights Reserved. 8
• Reduce Risk & Eliminate Waste
• Effective software testing teams:
– Build confidence
– Reduce “Risk & Surprises”
– Detect defects early
– Provide valuable information
9. What do we do?
XBOSoft, Inc. All Rights Reserved. 9
• Reduce Risk & Eliminate Waste
• Effective Quality Assurance teams:
– Identify risks
– Prevent defects
– Focus on continuous improvement of SDLC quality
– Guard the company brand
11. Communication Heuristics
XBOSoft, Inc. All Rights Reserved. 11
• Misconception is that status and metrics only
go out in email.
• If you depend on email, you have one
“where” and one “how” in your
communication tool belt. There are a lot of
other tools available to the wise test manager.
13. 1-Flash In The Pan
XBOSoft, Inc. All Rights Reserved. 13
Too ambitious in the beginning
• Symptom: Having trouble keeping metrics
current and reported when they are needed.
• Principle: Slow is fast.
• Solution: Make a sustainable decision up
front.
• Then: Steadily report meaningful information.
14. 2-Heavy Lifting
XBOSoft, Inc. All Rights Reserved. 14
Choosing to work hard instead of smart
• Symptom: Overly manual processes required
to produce.
• Principle: Maintainability is a key quality
attribute and a success criteria for process
success.
• Solution: Build in telemetry.
• Then: Automate, or automation assist.
15. 3-Message In A Bottle
XBOSoft, Inc. All Rights Reserved. 15
Communicating in a vacuum, throwing the
bottle into the ether and expecting the best
• Symptom: No one responds to status reports
from testing.
• Principle: Communication is what the listener
(recipient) does.
16. 3-Message In A Bottle
XBOSoft, Inc. All Rights Reserved. 16
Communicating in a vacuum, throwing the
bottle into the ether and expecting the best
• Solution: Know your audience. Who they are
and what they care about.
• Then: Answer the questions they have, and
address their concerns.
17. 4-House on Fire
XBOSoft, Inc. All Rights Reserved. 17
Ongoing state of emergency
• Symptom: Poor reporting and insight into QA
processes through reporting.
• Principle: Reporting should be part of every
testing process.
18. 4-House on Fire
XBOSoft, Inc. All Rights Reserved. 18
Ongoing state of emergency
• Solution: Validate you have meaningful metrics
for each stage of your testing processes leading
into a milestone.
• Then: Remove the mystery from what is taking
place.
19. 5-Mine Goes To Eleven
XBOSoft, Inc. All Rights Reserved. 19
Reporting is too complicated & cumbersome
• Symptom: No one understands the metrics or
the implications, including the Test Analyst
sending it out.
• Principle: Keep it simple.
20. 5-Mine Goes To Eleven
XBOSoft, Inc. All Rights Reserved. 20
Reporting is too complicated & cumbersome
• Solution: Choose to be pragmatic over trying
to be impressive.
• Then: Be consistent & crystal clear in your
narratives.
21. 6-Fish Out Of Water
XBOSoft, Inc. All Rights Reserved. 21
Answering the wrong questions
• Symptom: Suffering from “This is the way we
always do it” mentality.
• Principle: Know your audience.
22. 6-Fish Out Of Water
XBOSoft, Inc. All Rights Reserved. 22
Answering the wrong questions
• Solution: Answer questions that should be
asked and avoid the status quo.
• Then: Follow-up in person with key
stakeholders and adjust.
23. 7-Rearview Mirror Driver
XBOSoft, Inc. All Rights Reserved. 23
Haphazardly moving forward without knowing
what to expect in the days/weeks ahead.
• Symptom: You are spending all your time trying
to find defects instead of preventing them.
• Principle: An ounce of prevention is worth a
pound of cure.
24. 7-Rearview Mirror Driver
XBOSoft, Inc. All Rights Reserved. 24
Haphazardly moving forward without knowing
what to expect in the days/weeks ahead.
• Solution: Predict what your metrics will be in
the next two weeks. Document it.
• Then: Compare reality with predictions. Adjust
until forecasting accurately.
25. AND NOW
What to do about it…
XBOSoft, Inc. All Rights Reserved. 25
27. Tactical versus Strategic
XBOSoft, Inc. All Rights Reserved. 27
• Tactical
– Standardize metrics across teams
• Strategic
– Align to KPIs
– YoY performance
– Enterprise Quality Roadmap
28. BLUF
XBOSoft, Inc. All Rights Reserved. 28
• Bottom Line Up Front
• Follow with a “Headline”
• Impact to the triple constraint?
29. Less is More
XBOSoft, Inc. All Rights Reserved. 29
"I would have written you a shorter
letter if I had more time."
- Blaise Pascal
30. Post your webinar questions on Twitter @XBOSoft
Registrants will receive an email with information on where to view the recording
and slides from today’s webinar.
Join us to keep updated on all our webinars, reports and white papers:
facebook.com/xbosoft
+xbosoft
linkedin.com/company/xbosoft
Check out our blog: http://xbosoft.com/software-quality-blog/
Download our free white papers: http://xbosoft.com/knowledge-center/
Contact us with ideas for future webinars or questions regarding our services!
services@xbosoft.com
Thank you!
Q+A
www.xbosoft.com
Editor's Notes
Reporting upward
Goal is to build confidence that their involvement is not needed unless requested
Content / details varies for audience (Team, Managers, Directors, Officers)
Concise, accurate, confidence-building
Start with less, but make sure you have asked the right questions and have answers
Flows always help- high level, block flows with associated test cases
Communication Heuristics –
Does not always happen in email
Always needs a headline. Would you read a newspaper or magazine article without one? What else do they use in their format?
After meetings – big game hunting
In an elevator
Take the elevator challenge
Ground to top floor/to lowest floor
Kung Fu Reporting
Take an opportunity (they call you) and you turn it
When you “do” send email, make sure it is relevant.
When are the meetings where people need your info.
When do PM’s begin preparing their reports? Your report needs to be in their outlook before they start that process
Flash In The Pan.
Symptom: Too ambitious in the beginning.
Principle: Slow is fast.
Solution: Make a good decision up front:
Then: Steadily report meaningful information
Double is trouble
Metrics on the same thing in multiple ways
Be sure to be consistent
Heavy Lifting – Choosing to work hard instead of smart.
Symptom: Overly manual processes required to produce.
Principle: Maintainability is a key quality attribute and a success criteria for process success.
Solution – Build in telemetry
Then: Automate, or automation assist.
Message In A Bottle – communicating in a vacuum, throwing the bottle into the ether and expecting the best
Symptom: No one responds to status reports from testing.
Principle: Communication is what the listener (recipient) does.
Solution – Know your audience. Who they are and what they care about. Sample informal review of internal customers to your testing organization
What do you need & want from QA?
How well are we meeting your needs?
What is your perception of the QA team? (tell me the truth…)
Then: Answer the questions they have and address their concerns.
Message In A Bottle – communicating in a vacuum, throwing the bottle into the ether and expecting the best
Symptom: No one responds to status reports from testing.
Principle: Communication is what the listener (recipient) does.
Solution – Know your audience. Who they are and what they care about. Sample informal review of internal customers to your testing organization
What do you need & want from QA?
How well are we meeting your needs?
What is your perception of the QA team? (tell me the truth…)
Then: Answer the questions they have and address their concerns.
House on Fire. – The house is always on fire
Symptom: Ongoing state of emergency is a symptom of poor reporting and insight into QA processes through reporting
Principle: Reporting should be part of every testing process
Solution: Validate you have meaningful metrics for each stage of your testing processes leading into a milestone.
Are you on Track?
What to adjust?
Then: Remove the mystery from what is taking place
House on Fire. – The house is always on fire
Symptom: Ongoing state of emergency is a symptom of poor reporting and insight into QA processes through reporting
Principle: Reporting should be part of every testing process
Solution: Validate you have meaningful metrics for each stage of your testing processes leading into a milestone.
Are you on Track?
What to adjust?
Then: Remove the mystery from what is taking place
Mine Goes To Eleven – The opposite of simple
Symptom: Exaggerated, Hollow, Pretentious. No one understands the metrics or the implications; this includes the person sending it out.
Principle – Keep it simple.
Gate guard example
Solution: Choose to be pragmatic over trying to be impressive.
Then: Be consistent. Be crystal clear in your narratives.
Bonus – Measure surprises
Good
Bad
Don’t let your reports surprise any of the recipients – prewire
Forgetting who they are for – The “Order” of understanding
You
Then others, “who” can only understand the metrics if you do first
Can you interpret what this means to your plan?
Assumption: You have a plan.
Mine Goes To Eleven – The opposite of simple
Symptom: Exaggerated, Hollow, Pretentious. No one understands the metrics or the implications; this includes the person sending it out.
Principle – Keep it simple.
Gate guard example
Solution: Choose to be pragmatic over trying to be impressive.
Then: Be consistent. Be crystal clear in your narratives.
Bonus – Measure surprises
Good
Bad
Don’t let your reports surprise any of the recipients – prewire
Forgetting who they are for – The “Order” of understanding
You
Then others, “who” can only understand the metrics if you do first
Can you interpret what this means to your plan?
Assumption: You have a plan.
Are you providing numbers, but not answering relevant key questions for your senior stakeholders?
The traditional questions Executives ask, “Are they outdated?”
How many test cases did you run?
How many are automated?
How many bugs did you find?
Defect metrics / Trends?
You learned that QA probably can’t cover everything…
What is important for you?
Performance? Core functions?
What didn’t QA test?
What are the limitations?
What are you afraid of? (don’t need data give me a gut feel)
Would more time help or not?
Appropriate Trends/Metrics
Simple Data points followed up by complex appendix…
When reporting:
Start with a simple Yes or NO (on a release vote)
Gut check, what am I worried about…
Go a bit deeper with feature level data (Check, Check + etc...)
Schedule compression number
QA typically never gets the X days requested to test
Publish a compression number to indicate risk
We only had 10/15 days so 0.67 compression (risk is high)
If you had calculated you need a full tank of gas to make it to Houston, would you go with 2/3?
Go a bit deeper with regression coverage maps
NO Test cases run, or defect metrics etc…
Example:
Yes , Go Release
Areas for concern XYZ
Because we got it late and configuration nightmare to test
Schedule Compression = 0.67 (we got crunched badly)
Test Case point total = 892/1000 (we got close but not all the way)
New feature Coverage Map 2 areas yellow rest 6 Green
Appendix:
Test Cases run, defects trends, LOKI, Intermittent defect list etc., etc.…
Mitigations for all of the above when possible
Looks like a 1 page go/no go/ with a large appendix
Think ESPN Box score, but with full stats later down in the article
Also: – Wrong context of report for the testing
Example – Functional API testing vs. Functional testing executed via Quality Center
Are you providing numbers, but not answering relevant key questions for your senior stakeholders?
“Are they outdated?” The traditional questions Executives ask:
How many test cases did you run?
How many are automated?
How many bugs did you find?
Defect metrics / Trends?
You learned that QA can’t cover everything…
What is important for you?
Performance? Features and Functionality (F&F), especially critical functions?
What didn’t QA test?
What are the limitations?
What are you afraid of? (don’t need data give me your thoughts based on intuition and expertise)
Would more time help or not?
Appropriate Trends/Metrics
Simple Data points followed up by comprehensive appendix…
When reporting:
Start with a simple Yes or NO (on a release vote)
Reality check, what am I worried about…
Go a bit deeper with feature level data (Check, Check + etc...)
Schedule compression number
QA typically never gets the X days requested to test
Publish a compression number to indicate risk
We only had 10/15 days so 0.67 compression (risk is high)
If you had calculated you need a full tank of gas to make it to Houston, would you go with 2/3?
Go a bit deeper with regression coverage maps
NO Test cases run, or defect metrics etc…
Example:
Yes , Go Release
Areas for concern XYZ
Because we got it late and configuration nightmare to test
Schedule Compression = 0.67 (we got crunched badly)
Test Case point total = 892/1000 (we got close but not all the way)
New feature Coverage Map (2) areas yellow rest (6) Green
Appendix:
Test Cases run, defects trends, Intermittent defect list etc., etc.…
Mitigations for all of the above when possible
Looks like a 1 page go/no go/ with a large appendix
Think Horse race grid, but with full stats provided below or in this case, later in the status
Also: – Wrong context of report for the testing
Example – Functional API testing vs. Functional testing executed via Quality Center
Rearview Mirror Driver – Constant focus on the past without forecasting the future.
Symptom: You are spending all your time trying to find defects instead of time allocated to activities that would prevent them.
Principle: An ounce of prevention is worth a pound of cure.
Solution: Predict what your metrics will be in the next two weeks. Document it.
Then: Compare reality with your predictions. Adjust as appropriate until you can accurately forecast.
SDLC Quality & Root Causes
Are you capturing root causes or excuses?
ARGO thirteen
Definitions
Accountability
Process
Make it actionable
Predict outcomes and measure results
Wash, rinse, and repeat
Rearview Mirror Driver – Constant focus on the past without forecasting the future.
Symptom: You are spending all your time trying to find defects instead of time allocated to activities that would prevent them.
Principle: An ounce of prevention is worth a pound of cure.
Solution: Predict what your metrics will be in the next two weeks. Document it.
Then: Compare reality with your predictions. Adjust as appropriate until you can accurately forecast.
SDLC Quality & Root Causes
Are you capturing root causes or excuses?
ARGO thirteen
Definitions
Accountability
Process
Make it actionable
Predict outcomes and measure results
Wash, rinse, and repeat
Guidance Regarding What To Do About It
The Test Management Trifecta
What have you completed?
What did you learn?
Defects
Risks
What testing remains?
Tactical vs. Strategic
Tactical – Standardize across teams
Strategic – Align to KPIs, YoY performance, Enterprise Quality Roadmap
97/97/250
Find 97% of the defects
Fix 97% of those prior to release
Drive the cost of a function point of development to $250
System health assessment. Need to know the definition of “healthy” in your context.
GA Readiness
Version Release (VR)
Exit Criteria
And Then (and then, and then)
BLUF – know your bottom line and lead with that. Think in terms of triple constraint.
Schedule – We need an additional three days to complete planned testing. We lost five days to configuration management issues, but are working more efficiently as a team, so I’m confident this amount of time will be sufficient.
Scope – We will now need to define additional test scenarios based on the change request getting approved
Resources – We need two people from the product team to assist us in testing the new logic for the business rules
Quality – We would like an additional three days to test functionality that had higher than anticipated defects found in regression.
Doug’s advice – Don’t have the cost of the project on the final slide of the deck. Start with it. This is going to cost a million dollars, and here’s why…
Less is more.
"I would have written you a shorter letter if I had more time." - Blaise Pascal
There are three habits that keep most people from being succinct:
The habit of over explaining
The habit of underpreparing
The habit to completely miss the point