Traditionally, testing and quality assurance activities were left to the end of the software lifecycle, often to be squeezed for time. In the mid-1990s agile teams started to perform such activities earlier in the lifecycle, something called “shifting left.” This significantly improved the quality outcomes of the solutions being produced by the teams. Disciplined Agile (DA) teams take this strategy one step further, realizing that planning and modeling activities are similarly “shifted right” in the life cycle. At the same time, with the advent of DevOps, many teams are evolving away from Scrum’s sprints towards a leaner, more streamlined approach. The implication is that DA teams choose to adopt a more continuous way of working (WoW). This presentation walks through why and how this is done.

Scott is the Vice President, Chief Scientist of Disciplined Agile at Project Management Institute. Scott leads the evolution of the Disciplined Agile (DA) tool kit and is an international keynote speaker. Scott is the (co)-creator of the Disciplined Agile (DA) tool kit as well as the Agile Modeling (AM) and Agile Data (AD) methodologies. He is the (co-)author of several books, including Choose Your WoW!, An Executive’s Guide to the Disciplined Agile Framework, Refactoring Databases, Agile Modeling, and The Object Primer 3 rd Edition. Scott blogs regularly at ProjectManagement.com and he can be contacted via pmi.org .

Scott is the Vice President, Chief Scientist of Disciplined Agile at Project Management Institute and co- creator of Disciplined Agile. Scott leads the evolution of the Disciplined Agile (DA) tool kit and can be contacted via pmi.org

Teams in the Dojo work in “hyper sprints” with abbreviated ceremonies, so a 6-week challenge would consist of 12 sprints — and all the learning that entails, includes test automation pair programming, and CICD. The fast-paced Dojo environment enables teams to recognize old habits

If your teams are creating separate stories for testing, this session is for you? If your teams constantly push out the testing part of stories to the next sprint, this session is for you. If your teams are giving estimates for development and testing effort separately, this session is for you! Come join Abrar Hashmi, founder and Chief Evangelist of Agile Brains share Do's and Don't of Agile testing!

Abrar Hashmi is the Chief Agile evangelist . He has assisted in value-based delivery transformations in various Fortune 500 companies and spoken at multiple Agile conferences as well. Agile Brains was listed as Top 10 Agile Solution Provider by CIO Applications for their customer centric focus approach to help achieve business agility.
Their award-winning proprietary framework "ABC" starts with an organizational assessment (A) followed by brainstorming (B) solutions with Coaching (C) support to help deliver business value to customers. He has trained thousands of students in over sixty cities and is focused on organizations embrace a culture of fearlessness and innovation. Abrar holds numerous Agile certifications (SPC, RTE, CLP, ICP-FDO, ICP-IDO, ICP-EPO, ICP-ATF, ICP-ACC, CSM, TBR) and believes in building the new generation of Agile leaders. Abrar was listed in the Drexel 40 under 40 list for leaders to look out for in 2021. Agile Brains was listed as an INC 5000 winner for one of the fastest growing private companies in the United States. He was listed by Forbes in the Next 1000 leadership list for 2021.

Digital Transformation is here to stay, and if there is something we have learned from today’s world is that this trend is not going to change and it is here to stay. What is your company doing right now? is it a cosmetic or deep transformation?
This session will cover how big and small companies can adapt and embrace Design Thinking and Agile to influence the Strategy, to not only survive but thrive and delight customers while navigating through uncertain times.

Pepe Valiente is an experienced Offering Manager who has worked on a range of large and complex projects in multiple industries and countries. He has undertaken lead business and technical roles, managing teams with highly talented individuals, delivering value immediately for the organizations he has collaborated with.
He is currently leading the Growth Platform for the Digital Growth and Commerce organization, focusing on data initiatives to improve the user journey and drive revenue, adoption and engagement through best in class experiences for IBM products.

How to successfully conduct test automation process improvement (TAPI) for continuous development, consisting of iterative software development, continuous testing, and delivery, is the challenge faced by many software organizations. In this paper, we present an experience report on TAPI in one DevOps team in F-Secure (a Finnish software company). The team builds Windows application software and exists in F-Secure’s TAPI culture. The team self-reports high satisfaction and maturity in test automation for continuous development. To study their TAPI, we reviewed a collection of experience notes, team reflection reports and telemetry result reports. Then several meetings were held to discuss the details. We found that based on the understanding of the team, test automation maturity for continuous development is defined as a set of indicators, e.g., the increasing speed to release, improving the productivity of the team, high test efficiency. Second, the team indicated that a set of critical success factors have a major impact on successfully carrying out its TAPI, e.g., incremental approach, the whole team effort, test tool choice and architecture, telemetry. Third, we compare the TAPI practices in the observed team with the practices described in prior literature. The team believes that the existing test automation maturity approaches should include the identified practices like the whole team effort to build a more comprehensive test automation improvement model for the software Industry

This session will cover recent trends/challenges in testing the Internet of Things (IoT). Next, we will discuss the components that go into a proper test strategy, such as building a test lab, test coverage, test data, test management, tools, and automation. Lastly, Costa will walk participants through the top 5 IoT testing challenges, followed by solutions to address each.
Key Takeaways:
- Create a proper IoT test strategy
- Learn how to address nuances of IoT/Mobile for testing teams
- Review how to design a world class multi-technology test environment
- Explore sample frameworks and methodologies for multi-technology environments

Costa is a recognized thought leader with over 28 years experience in mobile, Cloud, and IoT technologies. He has managed all aspects of software development and taken on roles at Fortune 500 companies such as Developer, Release Manager, Automation Engineer, QA Director, Product Manager, VP, and CTO.
A visionary innovator, he has devoted much of his career to emerging and disruptive technologies, culminating with a breakthrough invention, a patented mobile technology in 2011 that was also nominated for the top innovation award at the Technology Association of Georgia

How to Build and Implement Your Salesforce Test Automation Strategy
Today enterprise applications like Salesforce are now at the heart of your business processes and 59% of organizations deploy a new software build daily. But as a test automation professional unfamiliar with the complex Salesforce ecosystem, it can feel daunting to build a Salesforce test automation strategy from the ground up.

In our session, will share 3 core principles for building and implementing a Salesforce test automation strategy for you and your delivery teams. Key takeaways include:
- How to create a checklist of prerequisites needed before your framework implementation, including tool evaluation, test data hygiene, and balancing business and tech requirements.
-A roadmap to navigating common challenges in Salesforce test automation, including functionality, how to create configurable lowcode/highcodes solutions, and a deeper understanding of Dynamic Elements.
-Discovering a new approach to building Salesforce scalable test automation architecture for all.

If you have ever wanted to understand how to create and implement a Salesforce test automation strategy, you will not want to miss this leadership session.

“These tests should never have been written. They provide no or little value.” -ME
Testing code has been described as an "art form." It is, but it should not be. There are many good patterns that should be followed when writing tests. There is even a lifecycle of tests that should be paid some attention. There are also many BAD patterns that developers should be aware of so that they can be avoided (or cleaned up).
This session will provide a series of examples of bad front-end tests and how to write them correctly.
* Tests Should Not Be "Well-Factored"
* Keep The Reader In The Test
* Violate The DRY Principle
* Testing Too Much
* Duplication Of Code Logic
* Bad Test Double
* Testing The Mock
* False Positives
* Testing Private Functionality Directly
* Excessive Setup

Senior Solutions Developer with Leading EDJE: Husband, father, and programmer.
My focus is on front-end development:
* JavaScript
* CSS
* SVG
* AngularJS and Angular
* React
* Ionic

More and more companies are using Progressive Delivery to get all types of changes – new features, configuration changes, bug fixes, and experiments – into production in a safer, faster, and most importantly, a sustainable way.
Software companies that shift to Progressive Delivery benefit from low risk releases, faster time to market, higher quality, and in general happier teams. Sounds great right? But what happens when your system isn’t implemented correctly, or worse, tested properly?
This talk takes you on a journey of why teams use Progressive Delivery, and the path from basic to advanced feature flag usage.
Make sure you build the right product, and build the product right!
How to decide what testing strategies should be implemented (how to setup your unit test, end to end automation, etc)
What tactics are most effective for keeping your implementation healthy and effective (feature flag governance!).

Jeff is a Quality Leader who has been in the testing industry for over 15 years. During this time, he has built automation frameworks, test strategies, and executed quality initiatives for fields such as medical devices, infrastructure security, web identification, and experimentation and progressive delivery.
Jeff has most recently joined Iterable to build out a QA organization and orchestrates Iterable’s quality control plan utilizing a combination of automated testing, implementing QA procedures, and acting as our customer experience champion to ensure Iterable remains the world’s leading customer engagement platform.
Before Iterable, Jeff was at Optimizely (a Gartner Magic Quadrant company in Experimentation and Progressive Delivery). Here, he wrote and executed the governance policy to tackle the unique challenges of quality control for a non-deterministic codebase built on feature flags and experiments.

Dr. Annika Steiber is a Faculty and the Director of Partnerships and Innovation and the Director for the Rendanheyi Silicon Valley Center at Menlo College. She is also the founder and CEO of A.S. Management Insights, a firm focused on excellence in Corporate Innovation and Management Models for the digital era. Dr. Steiber has a long track record of executive positions in the tech industry. In the last ten years she has published 7 management books and many awarded research papers on Management for Entrepreneurship and Innovation in a digital, connected world. In her research, teaching, and consultancy work she collaborates with several world- leading academics within the field of Management and with both local and global innovation consultancy firms.