A Holistic Approach to Testing in Continuous Delivery

Agile is on everyone’s minds today, as more and more organizations are eager to reap the benefits of rapid iterations using customer-centric approaches. Organizations tend to run to Scrum first because it is the most recognized agile framework. But is Scrum always the right answer for a team and a business? Heidi Araya discusses the types of scenarios and projects in which Scrum may not be a good fit. She shares other frameworks—including Kanban and Scrumban—as potential alternatives to consider to ensure teams and projects select the right fit and can deliver great software efficiently. Some considerations include organizational culture, size of teams, team composition, types of work, industry requirements, overall project size, and type of project. Go back to your organizations and confidently select the right frameworks for your current and future roles and projects—and explain to management why the framework chosen is appropriate.

Lisa Cooney has successfully used Agile Instructional Systems Design (Agile ISD) for 3 years. She developed a two-week course on Agile ISD that was well-received. Now she manages a curriculum of six courses using Agile online tools. Agile ISD is iterative rather than sequential, with early and frequent releases of working software or courseware. It values individuals, collaboration, and responding to change over documentation and plans.

There is no silver bullet for Product and Business Agility. On this talk you will know which are the fundamentals and some of the initiatives in place in the OutSystems Engineering Journey to better responding rapidly and flexibly to ours customers demands.

This document provides an overview of practical scrum. It discusses the three scrum roles of product owner, scrum master, and team. It also describes the four scrum ceremonies and three artifacts. Key principles of scrum include self-organizing teams, empirical process, and delivering working software frequently. The document contrasts command-and-control with self-management and explains how the manager's role changes in an agile environment.

Ryan Ripley relates that during his last agile transformation project, a key stakeholder asked, “Why are we adopting agile?” Ryan talked about increasing quality, delivering software sooner, and fostering a more collaborative relationship with business partners. After a few moments, the stakeholder raised his hand and said, “I get all that. But how is all of this agile stuff any better, faster, or cheaper than what we do today?” Ryan says that leaders must answer the better, faster, cheaper question if they want their agile transformation and associated projects to move forward. To prepare for this critical question, Ryan explores how better, faster, cheaper translates in an agile organization. Take away experiments to use with your agile teams to define better in your organization, an understanding of how agile helps teams deliver value faster to their stakeholders, and how working in an agile way can make business costs cheaper by reducing team turnover, enhancing learning through pairing, and reducing overall costs of product ownership.

This document discusses how to effectively adopt an agile mindset and practices. It begins by looking at the original goals of going agile but finds that in reality, many agile adoptions face problems and challenges. It discusses the "broken windows theory" - how small issues can lead to bigger ones if not addressed. However, instead of focusing on problems, it recommends taking an Appreciative Inquiry approach through retrospective meetings. This focuses the team on successes and strengths, envisioning future improvements through positive dialogue to act as a continuous engine for agile transformation.

This document discusses how to effectively adopt an agile mindset and practices. It begins by noting that while many organizations want to go agile, the reality is that adoption often faces problems and challenges. Drawing on the "broken windows" theory, it suggests that small issues that go unaddressed can undermine agile transformation over time. However, it advocates taking an appreciative inquiry approach to retrospectives, focusing on strengths and successes rather than problems. This positive mindset can act as a "continuous improvement engine" to foster ongoing enhancement of agile ways of working.

This document discusses DevOps and continuous delivery. It begins by introducing the speaker and defining DevOps as applying kanban principles and focusing on reducing lead time from idea to production. It then discusses how continuous integration, continuous delivery, test automation, and breaking work into small batches can help reduce lead time. The document emphasizes that DevOps is not just about tools but also culture and processes.

Bosnia Agile slides from Bosnia Agile Tuzla meetup where attendees had a chance to learn about basics of Scrum, by certified Professional Scrum Product Owner Enis Zeherović, and then to participate in a great "Team Work" training that explains all the soft skills Scrum team or any other team needs to have to work smoothly.

Presented at Agile Testing Days US 2018 https://agiletestingdays.us/session/refactoring-test-collaboration/ Collective ownership for testing starts with understanding testing. Rework your team dynamics to evolve past duplication and improve performance through whole team testing. Take home practical patterns for improving your team's collaboration on testing. Because teams who own testing have more confidence in the customer value of their results. As the Pragmatic Programmers say, "refactoring is an activity that needs to be undertaken slowly, deliberately, and carefully," so how do we begin? In this session, we will experience the complex interactions of an agile team focused on demonstrating customer value by answering a series a questions: Where do testers get their ideas? How are you planning to accomplish this proposed testing, tester? Why not automate all the things? Who is going to do this manual testing and how does it work? How do we know whether we're testing the right things? Build your own list of TODOs from these various practical collaboration approaches and begin deduping your team's testing for a better first day back at the office.

This document discusses ways to improve product development cycles through effective user acceptance testing and engagement. It describes how one organization achieved targets like reducing production to release cycles from 15 to 10 months by having product owners actively participate in validation testing. Stories from the trenches are shared about having product engineers directly involved in validation testing to better represent customer needs. Exploratory "monkey" testing of system boundaries is also discussed. The key takeaway is how design thinking principles were applied, like creating focus groups, prototyping solutions, and getting faster customer feedback through various iterative testing approaches.

Lesley Wallace presents on challenges with testing within a Scrum sprint and provides solutions. She asks the audience questions about their testing practices. Wallace explains that everyone on the team is responsible for quality and testing. To test within a sprint, stories must have decreased scope and testing must only focus on the story's scope. If more time is needed for regression testing, a "hardening sprint" can be added before release. Automation helps with testing and there are tools for all budgets.

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.

As companies evolve to adopt, integrate and leverage software as the defining element of their success in the 21st century, a rash of processes and methodologies are vying for their product teams' attention. This Session will give you guidelines on how to start an innovative business lean and fast by using design thinking, lean and agile approaches and how to build high-performing digital product teams. The session will finish with discussing Lean Agile meets Design Thinking to give a meaningful conclusion.

Is Agile worth it? What value can being Agile bring to your organization? Done right, Agile software development methodologies can help your organization deliver greater value to customers and other stakeholders more efficiently and with reduced risk. Done wrong, Agile methodologies become an endlessly iterating feature factory, facing an ever-growing backlog. In this interactive session, attendees discussed: - How to identify what’s most valuable to build next - How to ensure that the features you build are not just functional, but used and valued - How to measure and effectively communicate the value that you create Led by Alan Albert of MarketFit, this session at Agile Vancouver explored theory, examples, and exercises showing how to unlock the power of discovering, creating, and communicating value.

This document provides a summary of Raj Kasturi's background and qualifications. It lists that Raj has over 25 years of IT experience including eight years of enterprise Agile experience. It also notes that he has been an adjunct faculty member at Penn State, has 18+ years of teaching experience in areas like Scrum and project management, and has experience in roles like Agile Coach, Scrum Trainer, and Scrum Master. The document provides Raj's contact information and identifies that he is a speaker who volunteers at agile conferences and user groups.

Has your organization's Agile adoption stalled or hit a ceiling? Using his experience working with a diverse set of organizations, David Hawks will share patterns he has discovered that avoid common pitfalls. In this hands-on session you will learn a proven path to agility for many organizations and understand where you fit. Participants will apply this knowledge to create their own customized action plan to make further progress on their Agile journey.

Explore the advantages of integrating AI-powered testing into the CI/CD pipeline in this session from Applitools engineer Brandon Murray. More information and session materials at applitools.com Discover how shift-left strategies and advanced testing in CI/CD pipelines can enhance customer satisfaction and streamline development processes, including: • Significantly reduced time and effort needed for test creation and maintenance compared to traditional testing methods. • Enhanced UI coverage that eliminates the necessity for manual testing, leading to quicker and more effective testing processes. • Effortless integration with the development workflow, offering instant feedback on pull requests and facilitating swifter product releases.