Using examples from his award-winning design consultancy, Alan Cooper shares the secret to his success: working backwards. Working backwards means taking the time to ask the hard questions before wading into unfamiliar territory. It can be scary (and for some, frustrating), but it's the only way to innovate.

Being happy at work makes us 12% more productive, research shows. Happy employees lead to happier customers and better business. In this one-day workshop, Maartje and Fennande share their knowledge and extensive experience with you on how to transform your team into a happier team. Based on the science of happiness at work, their successful approach with teams has helped many teams to better cooperation, better projects, sustainable success and better business. Learn about measuring happiness and practical steps to enhance happiness levels in your team. Train-the-trainer.

Since its founding, Google has created six products that each have at least a billion monthly users. Google continues to innovate rapidly, and in many new areas. The organizing principles and cultural elements that drive this monster of innovation are a hot topic among designers. So what are they? Find out in this engaging talk by Google’s Chief Evangelist, Brand Marketing.

Introduction

Having a clear purpose in both life and work is essential to happiness. Science and business support this view. Companies with a clear purpose perform better than companies without. Purpose is increasingly mentioned as the key to navigate the volatile and complex world we live in. And, people with a purpose in their life, live longer and are healthier. However, finding your purpose, your personal, team and companies purpose, is not an easy task. In this workshop we discuss what purpose means and what the key elements of a sustainable and meaningful purpose are. By playing the Purpose Journey Game, we elaborate the four steps to identify the company or team purpose and build your business around it.

Outline:

After sharing our knowledge, insights from science and best practices, we will immerse in the subject by playing the Purpose Journey Game. We play the game in small groups (pressure cooker experience). By answering questions, role-plays and discussion participants will experience the method and learn how to find the purpose of their company or team.

While microservice architectures allowed teams to scale delivery of independently deployable services, most frontend layers are still run as monolithic applications. Similar to server-side applications, frontend layers often grow into large monoliths that are difficult to maintain and evolve. Building, deploying and consuming frontend components across a diversity of teams and web applications can be a daunting task, especially at scale. To address this issue, at OpenTable we enable fast-moving teams to easily build and deploy front-end components using OpenComponents, an open-source, battle tested, front-end microservice architecture for painless component delivery.

The idea behind micro frontends is to enable multiple teams to work seamlessy together by fostering end-to-end ownership of independently developed, tested and deployed features.

Think about UI as the composition of features which are maintained by independent teams. These teams could be cross-functional allowing them to develop such features end-to-end, from a database to user interface and independently deploy them.

During this session I'll explain how OpenComponents works, how do we use it at OpenTable and how we allows teams to build ship and consume frontend components at runtime across teams and web applications at scale.

The digitalization calls for rapid organizational flexibility and adaptability. This has an impact on all dimensions of a company: its strategy, structure, and the processes. Agile will help implementing some of this flexibility and adaptability yet mainly in terms of processes. Thus, the digital transformation needs companies to change beyond Agile. Beyond Budgeting, Open Space, and Sociocracy provide the missing links for a company to fully embrace digitalization. The combination of these concepts enables a company not only to survive but also to thrive (digital) disruptions.

Infrastructure as a service (IaaS) is an instant computing infrastructure, provisioned and managed over the Internet. Quickly scale up and down with demand and pay only for what you use.

In this demo, we will explain and demonstrate

1. Infrascture as a Code - Key DevOps practice
2. Azure - Key Concepts
3. Script Infrastructure as code
4. Provision Infrastructure
5. Compare and Contrast Azure with other Cloud Providers like AWS / GCP

We all know that innovative organizations are more successful. But how does happiness at work fit into the equation? Definitely, there is a link between happiness, creativity, innovation, and success in organizations. In this interactive workshop, you will learn about Happiness at work and use the method of Design Thinking to enhance Happiness in your team. How can Design Thinking lead to a happier and stronger (agile) team? We will provide practical tips on how to empower your creativity, empathy and thus happiness at work.

As part of organizational digital transformation journeys, CIOs are moving from hierarchical models to 'self organizing' Feature teams, in order deliver efficient and effective IT, but still need to retain the deeper functional expertise. Hence the growing importance of building and sustaining "Communities of Practices" (CoPs), as the traditional functional silos are broken down, with the transformation themes.

But if you are a Change Agent responsible for the Transformation, you understand how challenging it is to nurture, and especially "sustain" these CoPs.

So join my session, as I will share my experiences in nurturing and especially "sustaining" enterprise wide Communities of Practice (CoPs), while you recognize the key success and failure patterns in your own journey. In this session, you will learn techniques, tips and strategies that you can apply immediately, and in the end will walk away with practical advice on building "long lived" communities.

Want to discuss and share the Manifesto which a group of coaches including myself have written.

Please refer to www.vendormanagementmanifesto.org for details

1.1 The Governance
The delivery team is governed by contracts. There are 2 types of contract we will be considering
•The Master Contract : This is a contract signed between the Customer and Supplier Management teams and governs the entire set of Scrum projects being executed.
•The individual work order level contracts: This is a contract which will govern the detailed work to be done by teams.

This manifesto will take into account both the type of contract

1.2 The Roles
The roles covered under this Manifesto are as follows
The Customer Management This is the management team of the customer
The Vendor Management Team Vendor Management team will work on behalf of the Customer Management team in preparing the contract and negotiating the same with the Supplier’s management
The Team The team will consist of multiple Scrum teams working on the projects governed under the Master Contract. They will end up working under the individual Work Orders signed up with the customer.
The Supplier Management The Supplier Management team will negotiate the terms and conditions of the Master Contract of the contract along with the The Customer Management team (and the Vendor Management team).

1.3 The Objective of this Manifesto

The Objective of this Manifesto is to define guiding principles around the Customer-Supplier working environment with regards to working on Scrum projects. The assumptions made are
•The environment is customer-supplier (i.e. an outsourced environment)
•The environment is distributed and may not be co-located
•The environment involves multiple vendors

The Customers and Suppliers are integrated elements of a working environment in a project. The Customers and Suppliers will work together with a common goal and that is “Producing Value for the End Customer”. This manifesto supports the Agile Manifesto Value “Customer Collaboration over Contract Negotiation”.

There are 12 principles which will support the Agile Value and are presented below in a format of Left over Right. The items on the left are valued more than the ones on the right.

In October 2016 I received a call, "Hey dude, I don’t know nothing about Agile, but I need to become an Agile coach a-s-a-p – my company just got a new contract." I laughed for a second, explained that it takes a bit longer than a week to learn to coach, and wished him luck. I also knew that, shortly, he would be walking into his customer's office in this new role.

Agile Coach is the new black! But how can you, a good coach, stand out from the crowd of less competent peers? Let me offer you this workshop to explore the science of coaching and the ways in which it works. We start with concepts of neuroplasticity and the brain processes of creating new neuron pathways. Then we move to motivation and learn which type is the best. Finally, we finish with the discussion on brain activation states which we practice in a few short exercises. By understanding the new field of coaching psychology, you will become a better practitioner.

I am an affiliate member of the Institute of Coaching at McLean Hospital, the Harvard Medical School affiliate. I studied coaching psychology at Harvard Extension School.

Lies, damned lies and Statistics!

(the phrase is frequently attributed to the British Prime Minister Benjamin Disraeli).

Many of us work in environments that value Agility or are at least attempting to be more Agile.

We frequently turn to data, metrics, reports to help us navigate through our complex software environments, to help make sense of what's happening, to support subjective information we see around us and gain insights about the way we work.

But with the myriad of reports and metrics available to us, it is easy to misinterpret, over-analyze, overlook and generally make a big mess of things.

Through this talk, I will present some of the popular Agile reports and metrics and how they can be misread.

I will also share tips of how to counter some of these "lies".

Product Owners and others responsible for creating and maintaining the Product Backlog often focus on functional items.

With good engagement in the Backlog Management process from the Development Team and Architects, technical and architectural items also find their way into the Product Backlog.

But what about the human-centric items related to accessibility, inclusivity, internationalization and sustainability?

Through the talk and with the help of several supporting examples and a short exercise, I would like to highlight the importance of addressing these aspects in the Product Backlog. The examples will include examples of good and bad backlog items and design decisions.

I will also share some tips on how Product Owners and supporting roles can work these aspects into the Backlog Management process. These will include some ideas from Design Thinking but will not be limited to that.

Business organizations are seeing seismic changes, and the business
landscape is continuing to evolve. In an age of rapid digital
transformation, customers are choosing a myriad of ways to interact
with your organizations. It is thus imperative that organizations stay
ahead of the curve to achieve its strategic goals in service excellence.

The playshop will be dynamic, highly engaging using a Hands-
On, Minds-On Learning approach to producing a deeper, more meaningful understanding through an experiential process.

Building a customer-centric organization by pushing customer-centric
culture to the next level. Customer Centricity is all about a Customer
Centric Culture. The responsibility of Customer Centricity in an
organization is with the employees.

Customer-centric culture aligns your product and service with current and future needs of a defined set of customers to maximize mutual long-term financial value. It depends on an organization’s capability to understand, predict and respond to customer, market and competitor dynamics. A Customer-Centric Culture transcends individual departments and functions; it integrates the way all employees behave and perform.

In Distributed Agile many times, people don't trust members on other shore. My topic will cover few of the aspects which has helped our teams to gain that trust of customer and give co-located results.

In Session I will speak about case study covering below points which helped our customer who is a “first time offshore” to “Trust the Stranger”!

1) Building the Trust

2) Creating Continuous Visibility

3)Rotation of resources between shores

4)XP practices

1)Code Ownership

2)Use of technology to share code/ builds

5) CI CD – tools enhance visibility

6) Test Automation to look at Tested Running Features

7) Speak about my code! - Technical presentations within teams

8) Explore Business Flows!- Business Understanding among Business Owners, Product Owners, Proxy PO, team.

9) Innovations in business areas

10) Distributed Agile – tools techniques

11) Measuring the business Value (using custom Framework)

12) Saying No!

13) Re-Enforcing agile Practices!

The benefits of a high performing team are endless. They are autonomous, empowered, responsible and effective.

At Atlassian, we've pioneered the Team Playbook, which is our way of scaling teams by getting smarter, not bigger, and driving a culture of continual improvement. Utilised by hundreds of teams within Atlassian, we've made our secret sauce not so secret. Don't come to this session for a lesson on theory...come to this session to hear the philosophies and principles of the Team Playbook from Peter Scobie, Program Manager/Team Doctor. You'll leave this session invigorated, engaged and ready to take action.

A lot of organizations don't have version control systems in place for the database. Even if they are, change scripts are being generated manually for deployment process causing significant risks to the releases. In this demo, we will demonstrate patterns that can be used for taking care of database deployments and minimizing the risks

Agile transformations are no child's play. There is inertia, restlessness, impatience and the constant desire to run away. Traits that anyone who has been a parent to little kids has encountered, and learnt in their own way how to handle.

This session looks at parallels between parenting and trying to influence teams through an agile transformation. We look at some of the things that successful parents do that can be done by leaders trying to take their teams through a transformation.

Because if teams sometimes behave like children, the leader needs to be a parent too!

The Key challenge organisations are facing today is having to deal with the exponential rate of change which is happening in the external environment. The extent and pace of change is so disruptive that no organisation, regardless of age or size can take their competitive advantage or even their survival for granted.

The main reason why organisations are struggling to change is that they are modeled as mechanistic or close-ended systems. On the contrary, all natural socio-economic systems essentially which are living systems have dealt with change very effectively since eternity.

This talk is about infusing life into organisations. The speaker will highlight the key characteristics of living systems which enable them to deal with change effectively and also suggest actionable guidelines that will help leaders/influencers to bring their organisations to life. This approach will enable organisations to not only survive but thrive on change.

How can you flourish and be happy in a world that is changing all the time? One of the most important things for success, happiness and resilience is the right mindset. The only one who can make you happy and successful is you. Carol Dweck did a lot of research about fixed and growth mindset. This workshop is based on her work. First participants will rank their feeling of pleasure, flow and purpose in work. After that we will immerse into the subject of fixed and growth mindset. Besides sharing our knowledge, insights from science and best practices, we will do a few tests and exercises so the participants can experience what kind of mindset they prefer. Besides that they get tips and tricks to work agile on a more growth mindset; because that mindset will add to their success and happiness.