Working Backwards
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.
Target Audience
Developers hoping to understand the concepts of design.
schedule Submitted 3 years ago
People who liked this proposal, also liked:
-
keyboard_arrow_down
Aarron Walter - Story First
45 Mins
Talk
Intermediate
Story is a profoundly important device to unite design teams around a shared product vision. This powerful communication tool helps us retain information and empathize with others. As companies scale and teams sprint through product iterations, it’s easy to lose sight of how your product should fit into the lives of your customers. The best way to keep everyone pointed in the right direction is with a clear, compelling story—a story that will unite and guide teams towards success.
But how do we fold storytelling into our design practice? Aarron Walter uses real-world stories of product teams at Disney, Apple, Airbnb, Twitter, and more to show how storytelling improves team communications and elevates design practice.
-
keyboard_arrow_down
Gopi Kallayil - 9 Principles of Innovation at Google
45 Mins
Case Study
Intermediate
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.
-
keyboard_arrow_down
Nick Balestra - Painless Micro Frontends Delivery
45 Mins
Case Study
Intermediate
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.
-
keyboard_arrow_down
Srini Kadiam / Mohan - Infrastructure as service/code using Azure - DevOps practice demo
45 Mins
Demonstration
Intermediate
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
- Infrascture as a Code - Key DevOps practice
- Azure - Key Concepts
- Script Infrastructure as code
- Provision Infrastructure
- Compare and Contrast Azure with other Cloud Providers like AWS / GCP
-
keyboard_arrow_down
Srini Kadiam / Mohan / Umesh Kumar - Demo: Continuous Integration for Databases
Srini KadiamCo-FounderAgilePathMohanProcess ManagerAJGUmesh KumarSolution Architect (Application & DevOps )R1RCMschedule 3 years ago
45 Mins
Demonstration
Advanced
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
-
keyboard_arrow_down
Srini Kadiam / Mohan / Umesh Kumar - Demo: Helping your team to get started on DevOps Journey using Visual Studio Team Services & Docker
Srini KadiamCo-FounderAgilePathMohanProcess ManagerAJGUmesh KumarSolution Architect (Application & DevOps )R1RCMschedule 3 years ago
45 Mins
Demonstration
Intermediate
Most organizations and teams talk about DevOps practices. Most of them might find it difficult on how to get it started. If you are a Microsoft shop, this would be a good session for you and your team. In this session, we will demonstrate different DevOps practices using Visual Studio Team Services & Docker