Do you want to make your releases safer, faster, and less effort? Lots of us now have microservices, kubernetes, maybe even a service mesh. So why are released still banned on fridays? Why is it so hard even know what version is running in production?

In this practical talk, Matt will talk through progressive delivery. This is an approach, and a set of tools, which give us automated, safe, observable deployments and releases.

There’ll be a lot of demos, during which we’ll see:

• Canary deployments and automated rollbacks
• The separation of Deployment and Release
• Traffic mirroring, comparison of results between versions, and other neat network tricks in Kubernetes

And lots more!

Is your agile transformation just another restructure?  Is everyone being shuffled around into Tribes?  Villages?  Crews?  Are people reporting horizontally into Chapters?  Is there talk of how we need to go faster?  Were decisions made behind closed doors?  Was the focus on structure as if that will change everything?  Consultants engaged who created lots of PowerPoint presentations with lovely motherhood statements about how our people are our greatest asset and the new structure will break down silos and allow us to go faster?

Then it’s announced, teams are shuffled around into squads, tribes, chapters, etc..  As the transformation builds up speed, everyone gets some training and there is a massive amount of change management comms, presentations, and events.

Big up front plans,… Big bang change,… Heavy Change Management,… Does that sound like waterfall?

In this talk we’ll discuss a better way by actually being agile about the way we approach agile!

Simulating real-user scenarios as part of your automation is a solved problem. You need to understand the domain, the product, the user, and then define and implement your scenario.

But there are some types of scenarios that are complex to implement. These are the real-world scenarios having multiple personas (users) interacting with each other to use some business functionalities. These personas may be on the same platform or different (web / mobile-web / native apps / desktop applications).

Example scenarios:

• How do you check if more than 1 person is able to join a zoom / teams meeting? And that they can interact with each other?
• How do you check if the end-2-end scenario that involves multiple users, across multiple apps works as expected?
  • Given user places order on Amazon (app / browser)
  • When delivery agent delivers the order (using Delivery app)
  • Then user can see the order status as "Delivered"

Even though we will automate and test each application in such interactions independently, or test each persona scenarios independently, we need a way to build confidence that these multiple personas and applications can work together. These scenarios are critical to automate!

In this session, I will demonstrate teswiz, an open-source framework that can easily automate these multi-user, multi-app, multi-device scenarios. I will also mention how to run these tests on local and in CI pipelines.

Example: Multi-user, Multi-device test scenario

Example: Multi-user, Multi-app, Multi-device test scenario

Teswiz enables, and guides you to implement your automated tests while adhering to the principles of test automation, like - independent tests that run in parallel, against multiple environments using environment-specific-test-data and generate rich and contextual reports (and test execution trends) in reportportal. 

Test coverage is increased by using Applitools Visual AI, along with Applitools Ultrafast Test Cloud. 

In addition, teswiz takes away the pain of managing your browsers, and android / ios / windows devices for automation. The automated tests can run on local browsers / devices, or against any cloud provider, such as HeadSpin, BrowserStack, SauceLabs, pCloudy.

The following features makes teswiz unique:

The ability to do:

• Multi-user scenario automation between all platforms (android, iOS, Web, Windows desktop applications)
• Managing browsers / devices and parallel execution automatically
• Completely configurable options - means no code change required to run different combinations of tests, on demand
• Integration with Applitools Visual AI and Applitools Ultrafast Test Cloud
• Rich contextual reports (including screenshots, browser / device logs) and trend analysis via ReportPortal.io

The following features are relatively new in teswiz:

• Ability to run test orchestration across different platforms, using different app(s) and different users
• Integration of Applitools Ultrafast Grid for scaling
• Support for Firefox & Safari (earlier it was only Chrome)
• Better driver management & cleanup

Consumers rely heavily on mobile to access digital content and services. Consumers are more demanding than ever before and rate you against the services they consume daily. Performance plays a vital role in customer retention against your competitors, Customer Retention is also crucial for improving conversions for any application. 

Performance is foundational for a good user experience. As the site begins to load consumers wait for the content to load. Consumers are forced to wait on slower connections than those of faster network connections. When you are building a modern web experience, it's important to measure and optimize to get faster.

Resiliency and production readiness have come sharply into focus in the last decade as key areas of technical investment to enable organizations to build trust with their customers and scale/deliver innovation rapidly. The criticality of verifying cloud readiness of code prior to deploy as well as conducting resiliency experiments in cloud-native application ecosystems has resulted in Resiliency becoming a key strategy in many engineering team playbooks. Drawing from my previous experiences with Chaos Engineering at Netflix and Walmart, this talk will focus on how any team can begin investing iteratively in reliability and observability and build a "Minimum Viable Resiliency" plan.

In this talk, we will discuss setup, running and planning stages of a Chaos/Resilience testing discipline as a means to achieving the "Minimum Viable Resiliency". Using learnings from the industry, we will list out ways to plan small incremental changes in production readiness and KPIs to measure improvement. These steps will help engineering teams of all sizes to get more confidence in their software delivery and delight their customer base. 

Building on the work undertaken over the last two years producing a Code of Ethical Conduct for Agile Coaching, this workshop invites participants to explore the latest version of the Code and then examine a variety of ethical scenarios to see how the code plays out in real life situations.
Participants are invited to add their own examples to the scenarios which can serve as learnings for future readers of the code and associated scenarios.

From a waterfall caterpillar to an agile butterfly that’s my journey and also what I am doing at my organization.

Agile transformation in KPOs(Knowledge Processing Operation) is a big challenge due to the nature of the work.

Join my session to find ways to do agile transformation of this industry based on my decade of agile coaching experience and recently transformation of a 600 strong team. I would like to share the opportunities and challenges faced while transforming the knowledge industry of an B2B whole seller.

The talent war remains heated, especially for Digital and analytics talent.  But a skills inventory, expanded talent pipeline and cool sourcing can only get managers so far when it comes to hiring.  Hiring & retention programs need design thinking treatment — a human-centric problem-solving approach that explores a wide range of possible solutions, extensive prototyping and testing.   How organizations reimagine hiring and talent management processes in an persona based  talent-centric way that’s delightful is going to be the unlock.  How do we make our processes and experiences engaging?  We live in an experience-based world – and individual customer-centric experience has been the true driver behind massive improvements in key journeys like how we pay taxes, how we order our morning coffee, how we shop online.  However, hiring people – or looking for a job- often still feels like a root canal – complicated and painful. How organizations hire and manage our technology talents will be a key differentiator.

What do all project managers and other leaders fear?  Delays! Delays can come in multiple forms and the astute project manager needs to be able to identify and anticipate where delays may come.

The Kanban Method is focused on improving flow by reducing delays. Where are all the delays that are impacting your project or service delivery?  Join Todd as he shares a personal story of repairing his fence during COVID times and some of the delays that he encountered.  These 8Ds of delay are items that can occur on any service delivery and are areas to target to improve overall flow and the most important D, Delivery!

• Dawdle
• Defect
• Discovery
• Distractions
• Dependency
• Decisions
• Departures
• Derailed

As people leaders, we have been great at managing other people, their opinions, their work, and their lives. Having a sense of power and authority to tell others what's right or wrong, is misconstrued as the highest form of leadership. But, how about ourselves? How do we know if we are doing the right thing in the right way?

Through the Reflective Thinking and Cognitive Strategy of this talk, you will be able to experience and understand your true potential as a leader. 

Are you ready to travel and explore within?

Drawing on the research and content published on InfoQ.com over the last 12+ months, this talk summarises the state of play in engineering culture in 2022.
Key points that will be explored in the talk are:

• Hybrid work needs careful redesign and reassessment of the workplace and will be a
  significant challenge going forward
• Culture matters more than ever before as people are reassessing their options around
  workplaces and styles
• Culture can and should be made visible and tangible
• IT teams are tired, and burnout is a serious problem the industry needs to tackle
• Team topologies and being deliberate about team formation are aspects of culture design
  that can support better outcomes
• The gaps between good and bad workplaces are widening and people are voting with their
  feet (or video conferencing cameras)
• Leadership styles and approaches need to evolve to support the needs of teams and
  individuals today
• Paying attention to physical and mental wellness matters and can’t be treated as an
  afterthought