Design Led DevOps adoption using Double Diamond– An approach and Implementation
It’s a common mindset to jump into “Solution to a Problem” without deep thinking about the problem. We know what the solution is but do we really know what the problem is, have we really empathized with customer to solve the wicked problems? That’s where Innovative design practices come into picture.
Many of us have successfully adopted DevOps, some of us have started with the journey and some are still thinking about it. Irrespective of the stage you are in, you will benefit from moving towards “Design-Led DevOps adoption”. An approach which will “help you solve a problem” which “you didn’t know existed”.
Design-Led DevOps adoption first focuses on understanding the problem, understanding customer needs, tap customer emotions and gain insights before designing and prototyping solution.
In this session, We will talk about innovative way to apply design thinking, how it can be implemented and a case study of how it was applied to solve the DevOps problem.
Outline/structure of the Session
- What is Design thinking? 5 Mins
- How does it help? 5 Mins
- Double Diamond model process structure 5 Mins
- DevOps Challenge – Identify a problem – 5 Mins
- An Example of Applying Design Thinking to solve a DevOps challenge- 25 Mins
- Clear understanding of design thinking and how it can help
- Overview of Various DT models and detailed understanding of Double diamond approach
- How to apply DT approach to solve a problem
- Real life example of applying DT to solve a DevOps Problem
Leaders, Managers, Scrum Masters, Agile and DevOps Coaches, Product Owners, Product Managers, Designers, Developers and testers
schedule Submitted 5 months ago
People who liked this proposal, also liked:
vinaya muralidharan - Psst...your data could be lying to you!vinaya muralidharanAgile CoachSelf-employed
schedule 5 months agoSold Out!
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".
vinaya muralidharan - Dear Product Owner, does your Product Backlog include these?vinaya muralidharanAgile CoachSelf-employed
schedule 5 months agoSold Out!
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.