Agile Testing - Testboss presentation 02/Oct/14
•Download as PPTX, PDF•
1 like•293 views
The document discusses how the role of testers has changed with the shift from waterfall to agile development methods. Specifically, it notes that testers were previously responsible for test plans, scripts, results, and environments under waterfall, but are now part of delivery teams involved in user testing, test-driven development, and ensuring tests are assets under agile. It raises challenges around hiring the right people, costs, and evaluating team performance given these changes to the testing role and process.
Report
Share
Report
Share
Recommended
Creating test stability to create continuous delivery
Trisha Chetani discusses her experience transforming automated tests at Visenze from being slow and flaky to stable to enable continuous delivery. She analyzed the root causes of flakiness, which included changing locators, flows, and application slowness. Through coding best practices, team responsibility, stable environments, skills development, product testability improvements, and continuous learning, she was able to reduce test execution time from 30 to 5 minutes and maintain a stable pipeline.
Agile Testing
This document discusses how testers can contribute in an agile environment. It begins by defining agile testing as testing done incrementally and in parallel with development. Testers should have a mindset of collaboration, communication, ongoing planning, and viewing failures as opportunities to learn.
Testers can contribute in agile events like planning, refinement, and retrospectives. They can help write user stories and acceptance criteria. They also help determine if work is done by demonstrating increments and providing feedback. Defects are viewed as unfinished work rather than managed in a separate phase.
The document discusses metrics that matter like working software, velocity trends, and release burndowns. It emphasizes documentation should be "just enough" and
QA in Agile World
This document discusses quality assurance (QA) in agile software development. It explains that in agile, QA is a continuous process integrated throughout the project lifecycle. Each iteration aims to produce potentially shippable code through practices like test-driven development, refactoring, and continuous integration which help build quality in from the start. The agile lifecycle is broken into short iterative cycles in contrast to the traditional waterfall model where testing occurs in distinct phases after coding is complete.
Scrum, A Brief Introduction
Check out this brief introduction of Scrum, the Agile Software Development Framework. This is just a high level introduction that is why there are only 10 slides. Please like and share if you find it useful.
Scrum Team Workshop Training Agenda
This 2-day workshop teaches teams how to apply agile and Scrum principles through hands-on simulations and exercises. The workshop covers agile concepts like product vision, user stories, sprint planning, daily stand-ups and retrospectives. Attendees will learn how to establish agile processes, identify bottlenecks, and enhance practices through collaborative teamwork. The trainer has over 18 years experience in agile software development and helping companies successfully adopt agile methods.
Reference_Success_Story_GoSend
This document summarizes the agile transition of a 14-member development team for an international e-commerce startup. The transition involved 4 main steps: 1) Establishing scrum roles and ceremonies like daily standups; 2) Implementing product roadmapping and tracking; 3) Splitting the large team into 4 smaller feature teams; 4) Integrating testing into the sprint process. The results of the transition included better visibility, tracking of progress, and collaboration within the team.
An “amuse bouche” a la Agile
This document introduces Agile project management. It outlines the key principles of the Agile manifesto which focus on individuals, working software, customer collaboration, and responding to change over rigid plans. The document compares the traditional Waterfall process to the iterative Agile process. In Agile, requirements are captured in a product backlog and prioritized in sprints. Teams work in short sprints to deliver working software and get feedback through reviews and retrospectives to continuously improve.
Scrum_BLR 10th meet up 13 sept-2014 - Challenges of Transformation to Agile -...
This document discusses the challenges of transitioning to an agile methodology for a team and project manager. It outlines some key challenges including changes to team structure and processes, a shift from defined to empirical models, and ensuring collaboration both within and outside the team. The roles of the project manager also change from directing tasks to focusing on leadership, coaching, and removing obstacles for the self-organizing team. Measuring the success of the transformation is also discussed.
Recommended
Creating test stability to create continuous delivery
Trisha Chetani discusses her experience transforming automated tests at Visenze from being slow and flaky to stable to enable continuous delivery. She analyzed the root causes of flakiness, which included changing locators, flows, and application slowness. Through coding best practices, team responsibility, stable environments, skills development, product testability improvements, and continuous learning, she was able to reduce test execution time from 30 to 5 minutes and maintain a stable pipeline.
Agile Testing
This document discusses how testers can contribute in an agile environment. It begins by defining agile testing as testing done incrementally and in parallel with development. Testers should have a mindset of collaboration, communication, ongoing planning, and viewing failures as opportunities to learn.
Testers can contribute in agile events like planning, refinement, and retrospectives. They can help write user stories and acceptance criteria. They also help determine if work is done by demonstrating increments and providing feedback. Defects are viewed as unfinished work rather than managed in a separate phase.
The document discusses metrics that matter like working software, velocity trends, and release burndowns. It emphasizes documentation should be "just enough" and
QA in Agile World
This document discusses quality assurance (QA) in agile software development. It explains that in agile, QA is a continuous process integrated throughout the project lifecycle. Each iteration aims to produce potentially shippable code through practices like test-driven development, refactoring, and continuous integration which help build quality in from the start. The agile lifecycle is broken into short iterative cycles in contrast to the traditional waterfall model where testing occurs in distinct phases after coding is complete.
Scrum, A Brief Introduction
Check out this brief introduction of Scrum, the Agile Software Development Framework. This is just a high level introduction that is why there are only 10 slides. Please like and share if you find it useful.
Scrum Team Workshop Training Agenda
This 2-day workshop teaches teams how to apply agile and Scrum principles through hands-on simulations and exercises. The workshop covers agile concepts like product vision, user stories, sprint planning, daily stand-ups and retrospectives. Attendees will learn how to establish agile processes, identify bottlenecks, and enhance practices through collaborative teamwork. The trainer has over 18 years experience in agile software development and helping companies successfully adopt agile methods.
Reference_Success_Story_GoSend
This document summarizes the agile transition of a 14-member development team for an international e-commerce startup. The transition involved 4 main steps: 1) Establishing scrum roles and ceremonies like daily standups; 2) Implementing product roadmapping and tracking; 3) Splitting the large team into 4 smaller feature teams; 4) Integrating testing into the sprint process. The results of the transition included better visibility, tracking of progress, and collaboration within the team.
An “amuse bouche” a la Agile
This document introduces Agile project management. It outlines the key principles of the Agile manifesto which focus on individuals, working software, customer collaboration, and responding to change over rigid plans. The document compares the traditional Waterfall process to the iterative Agile process. In Agile, requirements are captured in a product backlog and prioritized in sprints. Teams work in short sprints to deliver working software and get feedback through reviews and retrospectives to continuously improve.
Scrum_BLR 10th meet up 13 sept-2014 - Challenges of Transformation to Agile -...
This document discusses the challenges of transitioning to an agile methodology for a team and project manager. It outlines some key challenges including changes to team structure and processes, a shift from defined to empirical models, and ensuring collaboration both within and outside the team. The roles of the project manager also change from directing tasks to focusing on leadership, coaching, and removing obstacles for the self-organizing team. Measuring the success of the transformation is also discussed.
Metrics to guide: agile fluency, continuous delivery and product teams
A short talk about how metrics are only good when they're gathered to help determine how to reach a goal. Different goals means different metrics.
The Agile Fluency Framework describes how teams and organisations can work towards different goals depending on what stage they're in, or aspire to. So for those different stages, this means different types of metrics are going to useful. We show some examples.
Agile Testing: It's about time
This document discusses the role of quality assurance (QA) engineers at Atlassian in an agile development environment. It outlines that QA's role is to assist, not assure, quality and focus on exploratory testing using lightweight and agile techniques. The document also notes challenges such as the need for faster issue creation and less context switching, and solutions such as using Bonfire, a tool that provides real-time information and supports exploratory automation.
Scrum Testing
Scrum is a framework for developing products using an iterative approach with sprints. The key roles are the product owner, who manages the product backlog and maximizes ROI; the scrum master, who facilitates the scrum process and removes impediments; and the self-organizing development team of 4-9 people. The product backlog is an ordered list of features that is prioritized and estimated. Sprints are time boxed iterations, usually 2 weeks, where the team selects backlog items for the sprint and defines how they will be completed. Daily stand-up meetings allow the team to synchronize. At the end of each sprint there is a sprint review and retrospective to demonstrate work and improve the process.
Useful stepping stones in growth towards Agile testing by Kees Blokland
Kees gave this talk at the Dutch Testing Day in 2015 in Eindhoven. It s about how to improve agile testing step by step.
19 creamer et workshop-agile2019-wash_pp_16-9_1
The document provides an agenda for a workshop on how to coach exploratory testing sessions. It covers basics of exploratory testing including obstacles, how to determine what to test, writing charters, and isolating and recording results. The agenda includes activities for writing charters, prioritizing them, and practicing exploratory testing in pairs with one participant testing and the other coaching. The roles of the coach and participant are defined. Ways to share results are also discussed.
Golden ratiotestertodev debashis banerjee - upload
Every cross functional Agile Team has a set of specialists who pitch in at various time to ensure a backlog is ready to be customer shippable sprint by sprint. These could be development specialists, test specialists, documentation specialists, operations specialists, business analysts and other specializations. As in mathematics the ratio of each of these is critical to the success of any sprint as their skills lend expertise and learning to others. In this session we explore if the number of devlopment specialist to test specialist within a cross functional agile team has a golden ratio? In this experience report what will be covered is learnings from scenarios where there is no test specialist in the team to a ratio where number of test specialists are more than development specialists. What will be covered are examples of sample ratios and the good and the bad of these ratios to an actual scenario. The implications of getting this ratio are discussed not just from product development but from a financial, people and type of company (startup, enterprise, service, product). In the end the session should help product owners, scrum masters and scrum team members get a insight into this crucial element of any agile project
Alexey Kovoliov. 100 legacy systems
Real life case study about the Agile adoption in telecommunications service provider company (TEO LT) and different organizational patterns, tried for the Agile software development unit.
Getting Agile Right - Rebooting an Agile organization in 100 days - Agile Tou...
Presentation at Agile Tour Montreal 2018 by Maurizio Mancini of Exempio and Paul T. Ryan CTO of OpenX.
Many organizations think they are Agile when they are not. Here is how to recognize when you need an Agile reboot and how to reboot your organization to become a true Agile organization.
Lean Kanban India 2016 | Connecting Agile, Scrum, Lean and Kanban Approaches ...
The document discusses connecting different agile and lean approaches such as Scrum, Kanban, Agile and Lean. It describes that while Agile and Lean are concepts based on principles, Scrum and Kanban are specific implementations. Both Scrum and Kanban draw from Agile and Lean values like limiting work in progress, visualizing workflow and continuously improving processes. The document recommends selecting aspects of Scrum and Kanban that best suit a team's goals and context rather than prescribing a single method.
Quality not-speed-for-distrobution
The document argues that agile practices prioritize quality over speed, which ultimately leads to faster delivery. It provides reasons for using practices like user stories, planning, continuous integration, testing, and code reviews: they catch bugs early and prevent wasted time on substandard or wrong software. While these practices take time up front, they save significantly more time than fixing issues late in a project, leading to higher quality and value delivered to customers. The document asserts that high quality projects complete more quickly due to fewer bugs and reworks.
Scrum_BLR 10th meet up 13 sept-2014 - The Slippery Slope from Agile to Scrum ...
This document discusses how organizations can fall into "Scrum-Fall" patterns when adopting Agile methods. It provides an example of a project that initially saw success with Agile but then faced challenges like increased rework, decreased productivity and velocity, and ballooning defects when management pressures increased iteration timelines and scope was set by business owners without consideration for costs and tradeoffs. The document advocates testing business processes not just individual use cases, and emphasizes that fixing issues later in a project costs significantly more than addressing needs up front with a "right-first-time" approach especially for non-functional requirements and architecture.
20180416 reactive is_a_product_rs
My keynote presentation from React Sphere, about how to treat Reactive and non-functional concerns as a product
Evolving to agile testing
This document discusses an enterprise's journey towards more agile testing practices. It outlines some of the challenges that led the organization to change, including delays in development cascading to testing, large amounts of manual testing slowing delivery, and late defect discovery impacting timelines and quality. The journey involved adopting practices like test-driven development, test automation, and integrating testing scopes from cross-functional teams earlier in iterations. It also discusses challenges of setting up an agile test organization, implementing test automation at scale, determining how and when to do integration and non-functional testing. The approach involved training, coaching, conferences, evolving practices using kanban principles, and starting with current capabilities while experimenting safely.
Methodologies, frameworks, and processes Part 2
Scrum is a popular lightweight agile framework that is easy to understand. It is documented in the Scrum Guide and based on principles of transparency, inspection, and adaptation. The Scrum team consists of a Product Owner, Scrum Master, and team of 5-9 members. The Product Owner is responsible for goals and priorities while the Scrum Master removes impediments. The team self-organizes during sprints which include planning, daily stand-ups, review and retrospective meetings. Key activities focus on backlog refinement, sprint planning, daily scrums and sprint reviews and retrospectives.
Scrum In 15 Minutes
Scrum is an agile framework for managing product development that focuses on continuous delivery of working software in short cycles called sprints, typically two weeks or less. Scrum emphasizes self-organizing cross-functional teams and accountability, iterative development and progress transparency through regular inspection of working increments. Key Scrum practices include sprint planning, daily stand-up meetings, sprint reviews, and retrospectives. Scrum can scale to large, complex projects through techniques like Scrum of Scrums.
The changing role of the team leader in a DevOps transformation
There is much discussion about the changing roles of Development and Operations staff when organisations undergo agile/digital/devops transformations. But what about the changing role of the Team Leader?
In pre-agile environments, as a Team Lead, your role is one of structure and co-ordination, it is through you that work routes. You know the skills and capacity of your team and are regularly making decisions about what can and can’t be done.
But as your team starts to work in agile teams, the need for you to keep them busy is reduced, as this is now a responsibility of the product owner and agile team itself.
Useful stepping stones in growth towards Agile testing door Kees Blokland.
Kees explains how to implement an agile testing proces step-by-step. This talk was held at the TestNet spring event in 2016.
QA in Agile
Presentation from Agile Ukraine conference (Kiev 2008) about QA process establishment in Agile environment.
Scrum_Blr 11th meet up 13 dec-2014 - Introduction to SAFe - Nagesh_Sharma
The document provides an introduction to the Scaled Agile Framework (SAFe) for applying agile practices at an enterprise scale. It discusses challenges organizations face with scaling agile and how SAFe addresses these challenges through its three layers (Portfolio, Program, Team). SAFe draws from Scrum, Extreme Programming, Kanban, lean principles and flows to provide transparency, alignment and program execution capabilities. It emphasizes continuous delivery through Agile Release Trains, empowered self-organizing teams, and roles like the Product Owner and Release Train Engineer. An example case study shows how a financial services company rapidly adopted SAFe to deliver more value faster by aligning their portfolio and programs.
An Introduction to Agile Testing Agile Tour Kaunas 2013
This document introduces agile testing and how it differs from traditional testing approaches. It discusses how at Callcredit, testing is now seen as part of the overall development process with quality as everyone's responsibility. Key aspects of agile testing covered include having testers and developers work as one team, taking a flexible generalist approach over siloed specialists, and advocating for quality rather than just providing assurance. The document also outlines agile testing strategies like lightweight visible strategies and continuous integration, as well as techniques like behavior driven development, test automation, and using the right tools for different test types and layers. It concludes that agile testing requires a new mindset compared to traditional testing and is a more integrated, technical, and challenging
WSO2Con USA 2017: Building a Successful Delivery Team for Customer Success
Ensuring customer success is the the highest priority when we engage with customers. We need to strive to get the customers into production within the shortest time possible to make sure they have sustainable use of WSO2 products. The key to success is to understand the right products for the solution, define an iterative architecture, come up with an agile engagement model and define clarity in terms of scope and acceptance.
The WSO2 Delivery team is well experienced in ensuring customer success with their experiences in the support and services space. Join this session to learn how to best position WSO2 products and learn some best practices in the engagement models.
Scaled agile implementation
Kumar Rajasekaran presented learnings from scaled agile implementations. Key topics included transitioning from a business process to an execution process, implementing a release train with focus on tools, metrics, user experience, agile coaching, trainings and workshops, and conducting agility assessments from team to program level. Challenges included priority/scope change management, sprint cycle duration, acceptance criteria, dependencies, capacity planning and standardization. Opportunities included delivering working software, aligning delivery to business value, and improving test practices.
More Related Content
What's hot
Metrics to guide: agile fluency, continuous delivery and product teams
A short talk about how metrics are only good when they're gathered to help determine how to reach a goal. Different goals means different metrics.
The Agile Fluency Framework describes how teams and organisations can work towards different goals depending on what stage they're in, or aspire to. So for those different stages, this means different types of metrics are going to useful. We show some examples.
Agile Testing: It's about time
This document discusses the role of quality assurance (QA) engineers at Atlassian in an agile development environment. It outlines that QA's role is to assist, not assure, quality and focus on exploratory testing using lightweight and agile techniques. The document also notes challenges such as the need for faster issue creation and less context switching, and solutions such as using Bonfire, a tool that provides real-time information and supports exploratory automation.
Scrum Testing
Scrum is a framework for developing products using an iterative approach with sprints. The key roles are the product owner, who manages the product backlog and maximizes ROI; the scrum master, who facilitates the scrum process and removes impediments; and the self-organizing development team of 4-9 people. The product backlog is an ordered list of features that is prioritized and estimated. Sprints are time boxed iterations, usually 2 weeks, where the team selects backlog items for the sprint and defines how they will be completed. Daily stand-up meetings allow the team to synchronize. At the end of each sprint there is a sprint review and retrospective to demonstrate work and improve the process.
Useful stepping stones in growth towards Agile testing by Kees Blokland
Kees gave this talk at the Dutch Testing Day in 2015 in Eindhoven. It s about how to improve agile testing step by step.
19 creamer et workshop-agile2019-wash_pp_16-9_1
The document provides an agenda for a workshop on how to coach exploratory testing sessions. It covers basics of exploratory testing including obstacles, how to determine what to test, writing charters, and isolating and recording results. The agenda includes activities for writing charters, prioritizing them, and practicing exploratory testing in pairs with one participant testing and the other coaching. The roles of the coach and participant are defined. Ways to share results are also discussed.
Golden ratiotestertodev debashis banerjee - upload
Every cross functional Agile Team has a set of specialists who pitch in at various time to ensure a backlog is ready to be customer shippable sprint by sprint. These could be development specialists, test specialists, documentation specialists, operations specialists, business analysts and other specializations. As in mathematics the ratio of each of these is critical to the success of any sprint as their skills lend expertise and learning to others. In this session we explore if the number of devlopment specialist to test specialist within a cross functional agile team has a golden ratio? In this experience report what will be covered is learnings from scenarios where there is no test specialist in the team to a ratio where number of test specialists are more than development specialists. What will be covered are examples of sample ratios and the good and the bad of these ratios to an actual scenario. The implications of getting this ratio are discussed not just from product development but from a financial, people and type of company (startup, enterprise, service, product). In the end the session should help product owners, scrum masters and scrum team members get a insight into this crucial element of any agile project
Alexey Kovoliov. 100 legacy systems
Real life case study about the Agile adoption in telecommunications service provider company (TEO LT) and different organizational patterns, tried for the Agile software development unit.
Getting Agile Right - Rebooting an Agile organization in 100 days - Agile Tou...
Presentation at Agile Tour Montreal 2018 by Maurizio Mancini of Exempio and Paul T. Ryan CTO of OpenX.
Many organizations think they are Agile when they are not. Here is how to recognize when you need an Agile reboot and how to reboot your organization to become a true Agile organization.
Lean Kanban India 2016 | Connecting Agile, Scrum, Lean and Kanban Approaches ...
The document discusses connecting different agile and lean approaches such as Scrum, Kanban, Agile and Lean. It describes that while Agile and Lean are concepts based on principles, Scrum and Kanban are specific implementations. Both Scrum and Kanban draw from Agile and Lean values like limiting work in progress, visualizing workflow and continuously improving processes. The document recommends selecting aspects of Scrum and Kanban that best suit a team's goals and context rather than prescribing a single method.
Quality not-speed-for-distrobution
The document argues that agile practices prioritize quality over speed, which ultimately leads to faster delivery. It provides reasons for using practices like user stories, planning, continuous integration, testing, and code reviews: they catch bugs early and prevent wasted time on substandard or wrong software. While these practices take time up front, they save significantly more time than fixing issues late in a project, leading to higher quality and value delivered to customers. The document asserts that high quality projects complete more quickly due to fewer bugs and reworks.
Scrum_BLR 10th meet up 13 sept-2014 - The Slippery Slope from Agile to Scrum ...
This document discusses how organizations can fall into "Scrum-Fall" patterns when adopting Agile methods. It provides an example of a project that initially saw success with Agile but then faced challenges like increased rework, decreased productivity and velocity, and ballooning defects when management pressures increased iteration timelines and scope was set by business owners without consideration for costs and tradeoffs. The document advocates testing business processes not just individual use cases, and emphasizes that fixing issues later in a project costs significantly more than addressing needs up front with a "right-first-time" approach especially for non-functional requirements and architecture.
20180416 reactive is_a_product_rs
My keynote presentation from React Sphere, about how to treat Reactive and non-functional concerns as a product
Evolving to agile testing
This document discusses an enterprise's journey towards more agile testing practices. It outlines some of the challenges that led the organization to change, including delays in development cascading to testing, large amounts of manual testing slowing delivery, and late defect discovery impacting timelines and quality. The journey involved adopting practices like test-driven development, test automation, and integrating testing scopes from cross-functional teams earlier in iterations. It also discusses challenges of setting up an agile test organization, implementing test automation at scale, determining how and when to do integration and non-functional testing. The approach involved training, coaching, conferences, evolving practices using kanban principles, and starting with current capabilities while experimenting safely.
Methodologies, frameworks, and processes Part 2
Scrum is a popular lightweight agile framework that is easy to understand. It is documented in the Scrum Guide and based on principles of transparency, inspection, and adaptation. The Scrum team consists of a Product Owner, Scrum Master, and team of 5-9 members. The Product Owner is responsible for goals and priorities while the Scrum Master removes impediments. The team self-organizes during sprints which include planning, daily stand-ups, review and retrospective meetings. Key activities focus on backlog refinement, sprint planning, daily scrums and sprint reviews and retrospectives.
Scrum In 15 Minutes
Scrum is an agile framework for managing product development that focuses on continuous delivery of working software in short cycles called sprints, typically two weeks or less. Scrum emphasizes self-organizing cross-functional teams and accountability, iterative development and progress transparency through regular inspection of working increments. Key Scrum practices include sprint planning, daily stand-up meetings, sprint reviews, and retrospectives. Scrum can scale to large, complex projects through techniques like Scrum of Scrums.
The changing role of the team leader in a DevOps transformation
There is much discussion about the changing roles of Development and Operations staff when organisations undergo agile/digital/devops transformations. But what about the changing role of the Team Leader?
In pre-agile environments, as a Team Lead, your role is one of structure and co-ordination, it is through you that work routes. You know the skills and capacity of your team and are regularly making decisions about what can and can’t be done.
But as your team starts to work in agile teams, the need for you to keep them busy is reduced, as this is now a responsibility of the product owner and agile team itself.
Useful stepping stones in growth towards Agile testing door Kees Blokland.
Kees explains how to implement an agile testing proces step-by-step. This talk was held at the TestNet spring event in 2016.
QA in Agile
Presentation from Agile Ukraine conference (Kiev 2008) about QA process establishment in Agile environment.
Scrum_Blr 11th meet up 13 dec-2014 - Introduction to SAFe - Nagesh_Sharma
The document provides an introduction to the Scaled Agile Framework (SAFe) for applying agile practices at an enterprise scale. It discusses challenges organizations face with scaling agile and how SAFe addresses these challenges through its three layers (Portfolio, Program, Team). SAFe draws from Scrum, Extreme Programming, Kanban, lean principles and flows to provide transparency, alignment and program execution capabilities. It emphasizes continuous delivery through Agile Release Trains, empowered self-organizing teams, and roles like the Product Owner and Release Train Engineer. An example case study shows how a financial services company rapidly adopted SAFe to deliver more value faster by aligning their portfolio and programs.
What's hot (19)
Metrics to guide: agile fluency, continuous delivery and product teams
Metrics to guide: agile fluency, continuous delivery and product teams
Useful stepping stones in growth towards Agile testing by Kees Blokland
Useful stepping stones in growth towards Agile testing by Kees Blokland
Golden ratiotestertodev debashis banerjee - upload
Golden ratiotestertodev debashis banerjee - upload
Getting Agile Right - Rebooting an Agile organization in 100 days - Agile Tou...
Getting Agile Right - Rebooting an Agile organization in 100 days - Agile Tou...
Lean Kanban India 2016 | Connecting Agile, Scrum, Lean and Kanban Approaches ...
Lean Kanban India 2016 | Connecting Agile, Scrum, Lean and Kanban Approaches ...
Scrum_BLR 10th meet up 13 sept-2014 - The Slippery Slope from Agile to Scrum ...
Scrum_BLR 10th meet up 13 sept-2014 - The Slippery Slope from Agile to Scrum ...
The changing role of the team leader in a DevOps transformation
The changing role of the team leader in a DevOps transformation
Useful stepping stones in growth towards Agile testing door Kees Blokland.
Useful stepping stones in growth towards Agile testing door Kees Blokland.
Scrum_Blr 11th meet up 13 dec-2014 - Introduction to SAFe - Nagesh_Sharma
Scrum_Blr 11th meet up 13 dec-2014 - Introduction to SAFe - Nagesh_Sharma
Similar to Agile Testing - Testboss presentation 02/Oct/14
An Introduction to Agile Testing Agile Tour Kaunas 2013
This document introduces agile testing and how it differs from traditional testing approaches. It discusses how at Callcredit, testing is now seen as part of the overall development process with quality as everyone's responsibility. Key aspects of agile testing covered include having testers and developers work as one team, taking a flexible generalist approach over siloed specialists, and advocating for quality rather than just providing assurance. The document also outlines agile testing strategies like lightweight visible strategies and continuous integration, as well as techniques like behavior driven development, test automation, and using the right tools for different test types and layers. It concludes that agile testing requires a new mindset compared to traditional testing and is a more integrated, technical, and challenging
WSO2Con USA 2017: Building a Successful Delivery Team for Customer Success
Ensuring customer success is the the highest priority when we engage with customers. We need to strive to get the customers into production within the shortest time possible to make sure they have sustainable use of WSO2 products. The key to success is to understand the right products for the solution, define an iterative architecture, come up with an agile engagement model and define clarity in terms of scope and acceptance.
The WSO2 Delivery team is well experienced in ensuring customer success with their experiences in the support and services space. Join this session to learn how to best position WSO2 products and learn some best practices in the engagement models.
Scaled agile implementation
Kumar Rajasekaran presented learnings from scaled agile implementations. Key topics included transitioning from a business process to an execution process, implementing a release train with focus on tools, metrics, user experience, agile coaching, trainings and workshops, and conducting agility assessments from team to program level. Challenges included priority/scope change management, sprint cycle duration, acceptance criteria, dependencies, capacity planning and standardization. Opportunities included delivering working software, aligning delivery to business value, and improving test practices.
Prince2 certification-india(foundation+practitioner)
PRINCE2 ® (PRojects IN Controlled Environments) is a process-based approach for project management providing an easily tailored and scalable method for the man-
agement of all types of projects. The method is the de-facto standard for project management in the UK and is practiced worldwide. KnowledgeHut has been assessed after rigorous evaluation and conferred the title of Accredited Training Organization (ATO) by APMG Group, UK.
Transitioning from Timeboxes to Continuous Product Delivery (by Steve Stolt a...
Agile continuous flow (Kanban) methods aren’t only for Operations and Support anymore -- Product Development teams now use them for strategic, date-sensitive initiatives to achieve faster time to market. Proceed with caution! Simply throwing away timeboxes can be dangerous.
We took the journey from a timeboxed to a continuous flow software delivery model. We brought along a large tribe of developers, testers, product owners, dev-ops people, UX designers, and stakeholders. We got lost a few times on the way, but we did find our destination.
Agile Gurugram 2019 Conference | Agile Culture for High Performance | Abhigya...
1) Abhigya Pokharel is an Agile Project Manager at Ncell telecom in Nepal who led the company's transformation to Agile. Under the new Agile approach, Ncell launched 10 products in a year compared to only 4 in 18 months previously. Employee and customer satisfaction scores increased.
2) The transformation required a holistic approach that changed the company's values, processes, functions, teams, and leadership. This included empowering self-organized teams, adopting Agile ceremonies, using visualization tools, embracing failure, and focusing on continuous learning.
3) Challenges included cultural shifts, performance management, and ensuring business value. These were addressed through experiments, team commitments, alignment
The seven deadly sins of Scrum
The document discusses the "Seven Deadly Sins of Scrum" which can undermine the benefits of an agile Scrum framework. The sins include having a culture and mindset that does not fully embrace the values of agile, not properly aligning all stakeholders to the change, and failing to involve testers fully in planning, estimation and definition of done activities. Other sins are an overemphasis on pushing work rather than teams pulling work, not refining product backlogs collaboratively, and Scrum Masters failing to facilitate organizational change and focus on agile values. The document emphasizes the importance of culture change and embracing agile values to truly realize the benefits of Scrum.
Agile ncr pramila hitachi consulting_future_coaching
This document discusses challenges in building a product organization within a services company and provides recommendations. It addresses issues like fixed-bid projects using agile methods, distributed teams, quantitative metrics, performance reviews, and tool selection. The key recommendations are to break projects into prioritized phases, focus on business value, improve collaboration, assess team behaviors, provide training and certifications, implement objective metrics tracking, tailor reviews to roles, and select tools that address technical debt. The overall message is that a mindset, process, and system transformation is needed to move from services to value engineering and deliver better outcomes through self-organizing teams.
Agile For All- Transformation Journey of a Telco
This document discusses the agile transformation journey of a telecommunications company in Nepal. It provides an overview of the company's business challenges that necessitated the transformation to agile. It then outlines the holistic approach taken to drive change across the organization's values, processes, teams, leadership and learning. This included establishing agile practices like daily stand-ups, sprint planning and retrospectives. Challenges in cultural transformation, performance, and return on action are also discussed. Examples of successful agile projects and lessons learned are provided. The presentation concludes with recommendations for building an agile organization through practices like flexible work hours, rewards, and career development.
A traditional team's agile transformation
This document summarizes a presentation about transforming a traditional team to agile. It discusses how the current environment requires more agility to address changing needs. It then contrasts the waterfall vs agile approaches. The presentation covers transforming the organization, processes, engineering practices and product management to be more agile. This includes shifting to a feature team structure, implementing scrum, continuous integration and emphasizing working software over documentation. Benefits of the agile transformation include delivering value earlier, receiving more feedback and adapting faster to change.
CHUNNEL PROJECT OUALITY MANAGEMENT
The Chunnel project between the UK and France required extensive quality management. Quality was a high priority given the complexity of tunneling under the English Channel. In the inception phase, the Inter-Governmental Commission mandated that the higher standard between the two countries would prevail to ensure safety. During implementation, stringent quality requirements and state-of-the-art technology helped deliver the tunnel on time despite challenges. Through an effective quality program during the closeout phase, workplace safety standards were surpassed and the tunnel performed as designed. The success of the massive Chunnel project demonstrated the importance of quality management.
BE mechanical engineer with 9.7 years experience in production
BE mechanical engineer with 9.7 years exp in production department ,good experience in planning,5s,kaizen,fmea,7 qc tools & story,lean manufacturing ,smed,spc techniques
Agile Mumbai 2019 Conference | Agile Culture for High Performance | Abhigya P...
The document discusses Agile transformation at a leading telecom company in Nepal called Ncell. It provides details on how Ncell implemented Agile practices to improve employee satisfaction, increase productivity, and deliver products faster. Key aspects of Ncell's Agile transformation included adopting a holistic approach to change by focusing on values, processes, teams, leadership and learning. Challenges in the transformation involved cultural shifts and ensuring return on actions. Ceremonies like daily stand-ups and retrospectives helped establish Agile ways of working. The results saw improved engagement scores and successful delivery of products within shorter timelines and budgets.
How to measure the outcome of agile transformation
This presentation covers details on how we can measure that Agile Transformation is providing the intended outcome or not. I presents a research & survey which tries to understand how different people measure value of Agile Transformation
Agile scrum brown bag
Agile Scrum is a collaborative project management methodology focused on short releases and delivering working software at the end of each release that provides immediate value. It is based on values like honesty, transparency, and collaboration. Key practices include short sprints, daily stand-ups, product backlogs to track work, and emphasizing working software over documentation.
Project Management Journey
The document provides an overview of various project management methodologies including PRINCE2, PMP, Agile, and Scrum. It discusses the credentials associated with each and growth trends. PRINCE2 focuses on processes while PMP is based on PMBOK guidelines. Agile and Scrum are used to deliver projects. The frameworks can be used together with PRINCE2 for corporate direction, PMP for management, and Agile/Scrum for delivery. A case study demonstrates recommending PRINCE2 for senior leadership, PMP for inexperienced PMs, Agile for experienced PMs, and Scrum for developers on a new risk management system project.
Михайло Кравець “Використання Agile методології в AAA розробці ігор” GameDev ...
The document discusses the use of Agile methodologies in AAA game development. It provides an overview of Agile principles and Scrum framework, including roles, ceremonies and artifacts. While some aspects of Scrum like cross-functional teams and customer collaboration do not directly apply to embedded game development teams, the speaker argues that an iterative approach, daily stand-ups, sprint planning and retrospectives can still benefit teams. The document cautions against adopting Agile practices without understanding how they apply specifically to one's environment or "cult-like" following.
Software Testing Process, Testing Automation and Software Testing Trends
This is the slide deck that KMS Technology's experts shared useful information about latest and greatest achievements of software testing field with lecturers of HCMC University of Industry.
7 NEW QC Tools | 7 NEW QC Tools Training
New 7 QC Tools Training Conducted by Industry Experts,customized for you & connect with relevance to your Industry & Processes
JB Resume
- K. Jothibasu is seeking roles in quality assurance and supplier development with over 11 years of experience in the automotive and electronics industries.
- He has extensive experience leading quality assurance activities with suppliers including supplier evaluation, PPAP approval, corrective action handling, and performance monitoring.
- Key achievements include reducing supplier PPM from over 12,000 to 348 through continuous supplier development activities.
Similar to Agile Testing - Testboss presentation 02/Oct/14 (20)
An Introduction to Agile Testing Agile Tour Kaunas 2013
An Introduction to Agile Testing Agile Tour Kaunas 2013
WSO2Con USA 2017: Building a Successful Delivery Team for Customer Success
WSO2Con USA 2017: Building a Successful Delivery Team for Customer Success
Prince2 certification-india(foundation+practitioner)
Prince2 certification-india(foundation+practitioner)
Transitioning from Timeboxes to Continuous Product Delivery (by Steve Stolt a...
Transitioning from Timeboxes to Continuous Product Delivery (by Steve Stolt a...
Agile Gurugram 2019 Conference | Agile Culture for High Performance | Abhigya...
Agile Gurugram 2019 Conference | Agile Culture for High Performance | Abhigya...
Agile ncr pramila hitachi consulting_future_coaching
Agile ncr pramila hitachi consulting_future_coaching
BE mechanical engineer with 9.7 years experience in production
BE mechanical engineer with 9.7 years experience in production
Agile Mumbai 2019 Conference | Agile Culture for High Performance | Abhigya P...
Agile Mumbai 2019 Conference | Agile Culture for High Performance | Abhigya P...
How to measure the outcome of agile transformation
How to measure the outcome of agile transformation
Михайло Кравець “Використання Agile методології в AAA розробці ігор” GameDev ...
Михайло Кравець “Використання Agile методології в AAA розробці ігор” GameDev ...
Software Testing Process, Testing Automation and Software Testing Trends
Software Testing Process, Testing Automation and Software Testing Trends
Recently uploaded
Unlock the Secrets to Effortless Video Creation with Invideo: Your Ultimate G...
Unlock the Secrets to Effortless Video Creation with Invideo: Your Ultimate G...The Third Creative Media
"Navigating Invideo: A Comprehensive Guide" is an essential resource for anyone looking to master Invideo, an AI-powered video creation tool. This guide provides step-by-step instructions, helpful tips, and comparisons with other AI video creators. Whether you're a beginner or an experienced video editor, you'll find valuable insights to enhance your video projects and bring your creative ideas to life.Why Apache Kafka Clusters Are Like Galaxies (And Other Cosmic Kafka Quandarie...
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.
🏎️Tech Transformation: DevOps Insights from the Experts 👩💻
Connect with fellow Trailblazers, learn from industry experts Glenda Thomson (Salesforce, Principal Technical Architect) and Will Dinn (Judo Bank, Salesforce Development Lead), and discover how to harness DevOps tools with Salesforce.
一比一原版(sdsu毕业证书)圣地亚哥州立大学毕业证如何办理
原版一模一样【微信：741003700 】【(sdsu毕业证书)圣地亚哥州立大学毕业证成绩单】【微信：741003700 】学位证，留信认证（真实可查，永久存档）原件一模一样纸张工艺/offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原。
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
【主营项目】
一.毕业证【q微741003700】成绩单、使馆认证、教育部认证、雅思托福成绩单、学生卡等！
二.真实使馆公证(即留学回国人员证明,不成功不收费)
三.真实教育部学历学位认证（教育部存档！教育部留服网站永久可查）
四.办理各国各大学文凭(一对一专业服务,可全程监控跟踪进度)
如果您处于以下几种情况：
◇在校期间，因各种原因未能顺利毕业……拿不到官方毕业证【q/微741003700】
◇面对父母的压力，希望尽快拿到；
◇不清楚认证流程以及材料该如何准备；
◇回国时间很长，忘记办理；
◇回国马上就要找工作，办给用人单位看；
◇企事业单位必须要求办理的
◇需要报考公务员、购买免税车、落转户口
◇申请留学生创业基金
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
办理(sdsu毕业证书)圣地亚哥州立大学毕业证【微信：741003700 】外观非常简单，由纸质材料制成，上面印有校徽、校名、毕业生姓名、专业等信息。
办理(sdsu毕业证书)圣地亚哥州立大学毕业证【微信：741003700 】格式相对统一，各专业都有相应的模板。通常包括以下部分：
校徽：象征着学校的荣誉和传承。
校名:学校英文全称
授予学位：本部分将注明获得的具体学位名称。
毕业生姓名：这是最重要的信息之一，标志着该证书是由特定人员获得的。
颁发日期：这是毕业正式生效的时间，也代表着毕业生学业的结束。
其他信息：根据不同的专业和学位，可能会有一些特定的信息或章节。
办理(sdsu毕业证书)圣地亚哥州立大学毕业证【微信：741003700 】价值很高，需要妥善保管。一般来说，应放置在安全、干燥、防潮的地方，避免长时间暴露在阳光下。如需使用，最好使用复印件而不是原件，以免丢失。
综上所述，办理(sdsu毕业证书)圣地亚哥州立大学毕业证【微信：741003700 】是证明身份和学历的高价值文件。外观简单庄重，格式统一，包括重要的个人信息和发布日期。对持有人来说，妥善保管是非常重要的。
WMF 2024 - Unlocking the Future of Data Powering Next-Gen AI with Vector Data...
Vector databases are transforming how we handle data, allowing us to search through text, images, and audio by converting them into vectors. Today, we'll dive into the basics of this exciting technology and discuss its potential to revolutionize our next-generation AI applications. We'll examine typical uses for these databases and the essential tools
developers need. Plus, we'll zoom in on the advanced capabilities of vector search and semantic caching in Java, showcasing these through a live demo with Redis libraries. Get ready to see how these powerful tools can change the game!
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
Enhanced Screen Flows UI/UX using SLDS with Tom Kitt
Join us for an engaging session led by Flow Champion, Tom Kitt. This session will dive into a technique of enhancing the user interfaces and user experiences within Screen Flows using the Salesforce Lightning Design System (SLDS). This technique uses Native functionality, with No Apex Code, No Custom Components and No Managed Packages required.
Orca: Nocode Graphical Editor for Container Orchestration
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
Liberarsi dai framework con i Web Component.pptx
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.
如何办理(hull学位证书)英国赫尔大学毕业证硕士文凭原版一模一样
原版定制【微信:bwp0011】《(hull学位证书)英国赫尔大学毕业证硕士文凭》【微信:bwp0011】成绩单 、雅思、外壳、留信学历认证永久存档查询，采用学校原版纸张、特殊工艺完全按照原版一比一制作（包括：隐形水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠，文字图案浮雕，激光镭射，紫外荧光，温感，复印防伪）行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备，十五年致力于帮助留学生解决难题，业务范围有加拿大、英国、澳洲、韩国、美国、新加坡，新西兰等学历材料，包您满意。
【业务选择办理准则】
一、工作未确定，回国需先给父母、亲戚朋友看下文凭的情况，办理一份就读学校的毕业证【微信bwp0011】文凭即可
二、回国进私企、外企、自己做生意的情况，这些单位是不查询毕业证真伪的，而且国内没有渠道去查询国外文凭的真假，也不需要提供真实教育部认证。鉴于此，办理一份毕业证【微信bwp0011】即可
三、进国企，银行，事业单位，考公务员等等，这些单位是必需要提供真实教育部认证的，办理教育部认证所需资料众多且烦琐，所有材料您都必须提供原件，我们凭借丰富的经验，快捷的绿色通道帮您快速整合材料，让您少走弯路。
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
【关于价格问题（保证一手价格）】
我们所定的价格是非常合理的，而且我们现在做得单子大多数都是代理和回头客户介绍的所以一般现在有新的单子 我给客户的都是第一手的代理价格，因为我想坦诚对待大家 不想跟大家在价格方面浪费时间
对于老客户或者被老客户介绍过来的朋友，我们都会适当给一些优惠。
The Comprehensive Guide to Validating Audio-Visual Performances.pdf
Ensuring the optimal performance of your audio-visual (AV) equipment is crucial for delivering exceptional experiences. AV performance validation is a critical process that verifies the quality and functionality of your AV setup. Whether you're a content creator, a business conducting webinars, or a homeowner creating a home theater, validating your AV performance is essential.
Superpower Your Apache Kafka Applications Development with Complementary Open...
Kafka Summit talk (Bangalore, India, May 2, 2024, https://events.bizzabo.com/573863/agenda/session/1300469 )
Many Apache Kafka use cases take advantage of Kafka’s ability to integrate multiple heterogeneous systems for stream processing and real-time machine learning scenarios. But Kafka also exists in a rich ecosystem of related but complementary stream processing technologies and tools, particularly from the open-source community. In this talk, we’ll take you on a tour of a selection of complementary tools that can make Kafka even more powerful. We’ll focus on tools for stream processing and querying, streaming machine learning, stream visibility and observation, stream meta-data, stream visualisation, stream development including testing and the use of Generative AI and LLMs, and stream performance and scalability. By the end you will have a good idea of the types of Kafka “superhero” tools that exist, which are my favourites (and what superpowers they have), and how they combine to save your Kafka applications development universe from swamploads of data stagnation monsters!
Using Query Store in Azure PostgreSQL to Understand Query Performance
Microsoft has added an excellent new extension in PostgreSQL on their Azure Platform. This session, presented at Posette 2024, covers what Query Store is and the types of information you can get out of it.
WWDC 2024 Keynote Review: For CocoaCoders Austin
Overview of WWDC 2024 Keynote Address.
Covers: Apple Intelligence, iOS18, macOS Sequoia, iPadOS, watchOS, visionOS, and Apple TV+.
Understandable dialogue on Apple TV+
On-device app controlling AI.
Access to ChatGPT with a guest appearance by Chief Data Thief Sam Altman!
App Locking! iPhone Mirroring! And a Calculator!!
Enums On Steroids - let's look at sealed classes !
These are slides for my session"Enums On Steroids - let's look at sealed classes !" - delivered among others, on Devoxx UK 2024 conference
Modelling Up - DDDEurope 2024 - Amsterdam
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.
Operational ease MuleSoft and Salesforce Service Cloud Solution v1.0.pptx
Operational ease MuleSoft and Salesforce Service Cloud Solution v1.0
Manyata Tech Park Bangalore_ Infrastructure, Facilities and More
Located in the bustling city of Bangalore, Manyata Tech Park stands as one of India’s largest and most prominent tech parks, playing a pivotal role in shaping the city’s reputation as the Silicon Valley of India. Established to cater to the burgeoning IT and technology sectors
Kubernetes at Scale: Going Multi-Cluster with Istio
Divine Odazie and Jubril Oyetunji share tips on Going Multi-Cluster with Istio Service Mesh at DevOpsDays Houston.
Recently uploaded (20)
Unlock the Secrets to Effortless Video Creation with Invideo: Your Ultimate G...
Unlock the Secrets to Effortless Video Creation with Invideo: Your Ultimate G...
Why Apache Kafka Clusters Are Like Galaxies (And Other Cosmic Kafka Quandarie...
Why Apache Kafka Clusters Are Like Galaxies (And Other Cosmic Kafka Quandarie...
🏎️Tech Transformation: DevOps Insights from the Experts 👩💻
🏎️Tech Transformation: DevOps Insights from the Experts 👩💻
WMF 2024 - Unlocking the Future of Data Powering Next-Gen AI with Vector Data...
WMF 2024 - Unlocking the Future of Data Powering Next-Gen AI with Vector Data...
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
Enhanced Screen Flows UI/UX using SLDS with Tom Kitt
Enhanced Screen Flows UI/UX using SLDS with Tom Kitt
Orca: Nocode Graphical Editor for Container Orchestration
Orca: Nocode Graphical Editor for Container Orchestration
The Comprehensive Guide to Validating Audio-Visual Performances.pdf
The Comprehensive Guide to Validating Audio-Visual Performances.pdf
Superpower Your Apache Kafka Applications Development with Complementary Open...
Superpower Your Apache Kafka Applications Development with Complementary Open...
Using Query Store in Azure PostgreSQL to Understand Query Performance
Using Query Store in Azure PostgreSQL to Understand Query Performance
Enums On Steroids - let's look at sealed classes !
Enums On Steroids - let's look at sealed classes !
Operational ease MuleSoft and Salesforce Service Cloud Solution v1.0.pptx
Operational ease MuleSoft and Salesforce Service Cloud Solution v1.0.pptx
Manyata Tech Park Bangalore_ Infrastructure, Facilities and More
Manyata Tech Park Bangalore_ Infrastructure, Facilities and More
Kubernetes at Scale: Going Multi-Cluster with Istio
Kubernetes at Scale: Going Multi-Cluster with Istio
Agile Testing - Testboss presentation 02/Oct/14
- 1. Agile: The Death of the Tester? Andrew Palmer - 02/Oct/14 @MRAJPalmer https://www.linkedin.com/in/mrajpalmer
- 2. The Challenges • Am I hiring the right people? • Is the new world going to cost me money? • What does QA mean now?
- 3. Remembering Prince2 • The introduction of PRINCE2 and the standard of gated methodology • Waterfall or V Model - given a spec to test • The Testers had a defined role: • Test Plans, Scripts and Results • Test Environments • Sign Off
- 4. Service Manual - The New Prince 2? • The introduction of the Service Manual and the Digital Service Standard Assessment • User based requirements and acceptance • The Testers part of a delivery team: • Conduct user testing • TDD • Tests are an asset of the product
- 5. What a Tester is now? ‘Waterfall’ ‘Agile’ Test Management Test Plans Test Results Gherkin Kanban Board Manual Testing Test Cases Test Execution Verification of Stories Acceptance Tests Automated Testing Repeatable Tests TDD Non-functional Testing Performance verification Continuous Performance Testing
- 6. What’s the problem? • Do we need to re-train Testers? • Can we trust developers? • Should we change our recruitment policy? • Can we estimate effort? • Can we evaluate team performance?
- 7. Cost • Test Analyst: £35,000 • Agile Test Analyst: £42,000 • ISEB Foundation Course: £1,150 • Certified Agile Tester Course: £1,780