Agile testing

The document discusses Behavior Driven Development (BDD) and how it can help increase quality and prepare an organization for increased business demands. It describes BDD as an industry practice where the whole team collaborates on system testing and definition of done. BDD promotes requirements using examples, collaboration between roles, finding defects earlier and more often through automation, and keeping technical debt low.

This talk was given in March at the CzechTest conference in Prague and at the Testing and Finance conference in London in May.

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 first part of this presentation is a situational assessment of typical challenges in IT project delivery using the SCRAP (Situation, Complication, Resolution, Action, Proof) model. This is essentially a business case for Agile. So if you are looking for ways to get buy-in for Agile, this is the place to be. The second part of this presentation shows you what Agile is from 50,000 ft. From this high up, we'll be covering the essential elements from a business and management perspective. We'll cover what Agile is, what it does, how it works and what it achieves. If you are interested in learning or communicating the value of Agile, then this is the presentation for you! Please email me if you would like a download.

This document summarizes a webinar by Allan Kelly on Agile basics. It discusses 5 key Agile concepts: quality, visualization of work, iterations, working in small batches, and vertical teams. For each concept, it provides details on practices like test-driven development, burn down charts, 2-week iterations, small stories and tasks, and fully staffed cross-functional teams. It emphasizes that following even one of these basics can improve outcomes, and following all 5 provides greater benefits to managing software projects in an Agile way.

This presentation provides an overview of the role of testers on agile teams. In essence, the differences between testers and developers should blur so that focus is the whole team completing stories and delivering value. Testers can add more value on agile teams by contributing earlier and moving from defect detection to defect prevention.

During Quality Jam 2016 I had the privilege of presenting with one of QASymphony's earliest customers, Better Cloud, on how methodologies like BDD, TDD and ATDD scale for the enterprises. Adam Satterfield is the VP of Quality Assurance at Bettercloud and has been in QA for many years; he has taught me a lot about Behavior Driven Development, Test Driven Development, Acceptance Test Driven Development. In the session we share a new way of testing-- what Adam and I believe to be the next generation of testing development. We know that there are several ways to do testing and we are just showing one new way to do it - If this session doesn't inspire action, hopefully it will at least give you and your team something to think about.

A case about how a company (Sectra) is using Exploratory Testing in their agile development organization where testers and developers are sitting together in cross functional teams using Scrum.

Agile Testing: A pragmatic overview and new entry in Intelliware’s Agile Methodology Series. What you’ll learn in this presentation: Intelliware’s Chief Technologist, BC Holmes, provides a pragmatic overview of Agile testing. Complete with many examples, this presentation is ideal for those looking for a practical take on software testing in an Agile environment. The presentation covers: - Why do we use Agile testing? - What Agile testing isn’t - What Agile testing is: unit testing and test-driven development (TDD) - High-level properties of good tests - Testing in different languages - Test suites and code coverage - Using mock objects to help isolate units - Beyond unit testing

Presenter: Anne Hungate President, Daring Systems You’ve heard about Continuous Integration and Continuous Delivery but what’s common as code makes its way through those processes? Testing. With DevOps Testing (also known as Continuous Testing), testing tasks are engineered to be continuously completed end-to-end across the entire development to deployment pipeline. Developers, QA analysts, security professionals, IT Operations analysts…everyone is a tester in a DevOps environment. Join us to learn more about DevOps Testing and the emerging role of DevOps Test Engineer.

Agile Testing involves testing in the context of Agile development. It is done continuously and collaboratively by all members of the team throughout the development process, rather than just by QA/testers at the end. This helps ensure high quality, useful software is delivered iteratively.

Lean principles and practices have long been applied to manufacturing, with Agile arguably the inevitable evolution of Lean applied to knowledge-based work.   When viewed from a customer’s perspective much of software development may be seen as lower value.  How can organizations become lean by eliminating waste and working smarter? This presentation explores Lean principles and practices applied to software beginning with value stream mapping and the 7 (+1) types of waste.  Presented as an Agile 101 session at Agile New England on 5 August 2021.

The document discusses moving to a behavior-driven development (BDD) approach. It outlines challenges with traditional software development processes, such as requirements getting lost in handoffs. BDD aims to address these by shifting testing to the beginning through acceptance tests written in a "Given-When-Then" format. This allows teams to build testable code, catch issues earlier, and deploy features incrementally. Adopting BDD requires training, champion support, and patience. Metrics should track success, and teams can start small before a full rollout.

A retrospective is a meeting to look back over an iteration, release, or project, specifically to discuss what worked well, what could be improved, and most importantly, how to translate the lessons learned into actionable change. Retrospectives are a forum for the team to improve upon their process. They’re an integral part of Scrum and Extreme Programming (XP).

Many companies are currently going through Agile Transformation or thinking about making the transition to agile. While moving to agile can create great opportunity for organizations, the journey to get there can be highly challenging. If you don’t have the right people, process and tools in place, the true benefits of agile may not be recognized. In this webinar, Andrew Stickland, Head of Client Services, for Clearvision and Kevin Dunne, VP of Business Development and Strategy for QASymphony will discuss the best practices for making the agile transformation. In this webinar, we will try to answer the following questions: - Who are the people I need in place? - What are the core processes that I need to change? - What tools do I need? View the On-Demand webinar here: http://pi.qasymphony.com/agile-transformation-best-practices-webinar-lp060?utm_source=slideshare&utm_medium=slideshare&utm_campaign=Agile%20Transformation%20Webinar

This document discusses various metrics that can be used to measure agile processes. It begins by defining what a metric is and explaining common process improvement cycles. It then outlines different categories of metrics including business, process, code, design, testing, and automation metrics. Examples are provided for each category. The document notes that choosing the right metric is important and should encourage desired behavior, be easy to measure, and provide periodic feedback. It emphasizes that both leading and lagging metrics should be considered to measure productivity, predictability, quality, and value.

The document provides guidance for managing a team of junior testers. It discusses challenges such as lack of skills and experience in junior testers. It recommends setting clear expectations, providing frequent communication and feedback, ensuring knowledge sharing, and protecting the team to help them succeed. Patience and structure are important, as is repeating key messages, to help junior testers learn and improve. The goal is for the team to work cooperatively toward a common objective.

The document provides information to help a project manager transitioning to a ScrumMaster role. It begins with an exercise to define the roles of project manager and ScrumMaster. It then compares their responsibilities, with the project manager focusing on planning and tracking tasks while the ScrumMaster facilitates processes like the daily scrum and removes impediments. The document outlines the Scrum framework and roles of product owner, ScrumMaster and team. It provides examples of how the ScrumMaster helps with planning, daily standups, reporting tools and retrospectives. It concludes with an overview of the ScrumMaster's new responsibilities.

This document provides an overview of scaling agile development in an organization. It discusses why organizations scale agile, such as to improve organizational agility. It then outlines a four phase approach to jumpstarting scaling: assess the current state, align initiatives, accelerate progress incrementally, and reflect and progress further. Specific techniques are discussed for each phase, such as establishing agile champions, piloting programs, limiting work in process, growing stable teams, and selecting a scaling framework. The presentation concludes by emphasizing an iterative scaling strategy and finding support to move forward.

Agile Trends in Government: Lean and Agile Method Adoption and Delivery in the Public Sector Presented by Arlen Bankston PMI 2014 Symposium

The document provides an overview of a facilitation guide for workshops focused on techniques and exercises for specific goals and outcomes, introducing the facilitator Beth Wong and covering topics such as brainstorming exercises, trends in agile adoption, challenges in engagement and retention, agile assessment practices, and a continuous improvement exercise.

Our presentation from Agile Africa on the Agile Testing Mindset. If you like what we have to say here and would like some more techniques - check our our book: https://leanpub.com/AgileTesting To get exclusive access to a new techniques from us each month, sign up to our newsletter: http://bit.ly/W1dP3o

This document summarizes a session on becoming a better agile tester. It discusses removing barriers between teams through shared activities like pair programming and testing. This leads to benefits like improved product quality, efficiency, understanding, trust, and empathy. It also notes that testers need new skills to work collaboratively, and emphasizes curiosity, communication, respect, empathy, and willingness to see others succeed over purely technical skills.

Using Behavioral & Gaming Strategies to Evolve Team Performance & Engagement Presented by Arlen Bankston Innovate Virginia 2011

Wielu Scrum Masterów nie ma pomysłu lub ma trudności z prowadzeniem wartościowych Retrospekcji Sprintu. Młodzi, niedoświadczeni adepci tej sztuki często ograniczają się do jednej dobrze przećwiczonej metody. Najgorzej, kiedy jest to wariacja oparta na plusach i minusach lub ćwiczeniu rozgwiazda. Każdy zespól to widział i szybko się znudzi. Z tego powodu, retrospekcja staje się "koniecznym złem” dla zespołu, nudnym spotkaniem, które nie przynosi żadnej wartości. Zespół przestaje się angażować. Dlatego warto poszerzać warsztat i sprawdzać inne metody. Dzisiaj chciałabym Ci przedstawić Retrospekcję z wykorzystaniem niedawnej zmiany w Scrum Guide - dodanych Wartości Scrum.

CBIZ and Mayer Hoffman McCann P.C. (MHM) are pleased to invite you to our 2016 Executive Education Series™ online training courses. This webinar-based training is designed to educate and inform our clients and the public on complex accounting and tax subject matters and current events. Continuing Professional Education (CPE) credit will be offered. Online registration and more details about these free courses can be found at http://www.cbiz.com or http://www.mhmcpa.com.

Slide presented at Better Sofware conference in June 2016. The talk was about how facilitation, change managment and coaching, are essentials in guiding Agile Transition program

This document provides tips for helping developers and system administrators improve communication and collaboration. It recommends bringing the teams together both physically and through knowledge sharing. Celebrating successes and sharing systems and data can help break down silos. Regular communication through meetings and open discussions can also help build understanding and trust between the roles. The overall goal is establishing common values and a shared purpose to help the teams work together effectively.

This document discusses strategies for growing a distributed product owner team at Siemens for their medical software development. It describes how the product owner team is distributed across multiple sites to be close to feature teams. Growing the team requires selecting people with the right skills and knowledge, investing in closing knowledge gaps, and facilitating communication through regular virtual and in-person meetings. Maintaining connections with customers also requires travel to events and customer sites. While challenging, distributing the product owner team can work with the right approaches for communication, collaboration, and skills development.

How organizations nowadays could innovate and transform themselves, to catch up with this faster-moving world? How is possible to incrementally change the organization from within? How to leverage self-organization, collaborative leadership and motivation to involve people from the whole organization to reach the Big-Opportunity?

Structured organizations today are not keeping pace with a changing world incessantly. The Business Triathlon (Lean Strategy/Start-up, Agile and Change Management) could be the solution.

This document provides an introduction to agile development methods over the course of 1.5 hours. It begins with background on the presenter and an outline of topics to be covered, including an overview of traditional waterfall development practices, lean software development principles, agile principles and the Scrum framework. Key aspects of Scrum like roles, meetings, estimations and visualizing work are defined. Kanban principles and how it compares to Scrum are also introduced. The document emphasizes adopting agile practices to improve productivity, deliver value frequently and welcome changing requirements.

Scrum, XP, and Kanban have been proven to provide step changes in productivity and quality for software teams. However, these methods do not have the native constructs necessary to scale to challenges of building enterprise class software systems. What the industry desperately needs is a solution that moves from a set of simplistic, disparate, development-centric methods, to a scalable, unified approach that addresses the complex constructs and additional stakeholders in the organization- and enables realization of enterprise-class product or service initiatives via aligned and cooperative solution development. In this talk, Dean Leffingwell describes how to accomplish this with the Scaled Agile Framework, a publicly - accessible knowledge base of proven Lean and Agile practices for enterprise-class software development. He approaches the problem from the perspectives of Lean thinking and principles of product development flow, illustrating how these core principles help deliver business results at scale, while keeping the development system - and the enterprise - lean and responsive to rapidly changing market needs. And since winning is more fun, he’ll also describe some of the personal benefits that come when teams master the art of delivering better enterprise-class software, at an ever faster pace.