1. DesOps + DevOps – A Practical
Approach
Jas Chong Agile Paris 2021 November
2. Dual track model is used to iterate faster, not
increment faster.
Dave Malouf – Tri-Track Model - https://www.designbetter.co/designops-handbook/introducing-designops
Additional track
for
Understanding
business needs
Waterfall
or
Water
Scrum
Fall
3. When continuous exploration meets continuous
development, it’s fireworks or explosion.
Design Operations (DesOps)
Design@scale
Imagine possibilities
Human center
The orchestration of individuals, processes and
tools to amplify creativity and impact at scale.
Development Operations (DevOps)
Development@scale
Solve problems
Code center
Practices that combines software development
and IT operations to shorten development life
cycle and provide continuous delivery.
Someone
said Dual
not Duel
Building the foundation in Continuous Integration of dual track is key to avoid duelling.
4. Building continuous integration by experimenting on
people, process & technology – 2 Case Studies
A Teleco Company
(Over 50 people in programme, Single Country)
An Insurance Company
(Over 100 people in programme, Multi-Country)
People (with
cross over)
Exploration Team
Business Owner, PO, CX, Architect
Design Team
UX, Design Developers
Development Teams
UI, Developers
Process Design Authority
Design Lead - Desirability
Tech Lead - Feasibility
Business Lead - Viability
Scrum for all teams
Plan together
Review together
Technology Common Tools
Jira & Confluence
Design Tools
UX Pin integrated with Jira
Design System
Development Tools
Bitbucket integrated with Jira
Zephyr for test case
People (with
cross over)
Leadership Team
Business owner, PO Leaders, Programme
Management
Exploration Team
PO, Solution Managers, Platform Manager
Development Teams
UI, Developers
Process PO Prioritisation
Group
Business refinement
Story refinement
Scrum for all teams
Plan with leads
Review together
Technology Common Tools
Jira & Confluence, Trello (painfully
removed)
Design Tools
Figma not integrated
Development Tools
Github not integrated
Excel for test case
Continuous Integration with usability testing every 2 weeks and working product every 2 weeks
MVP > 8 months
MVP in 4.5 months
Release every 2 months
5. @scale, interactions and cross points requires structured
orchestration and discipline
Discipline is necessary for Flexibility: The right people in the right meetings. Every thing else, self organise.
Monday
Programme & Scrum
Master
All Leaders (Future
releases)
By Country (This &
next release)
Exploration Goals
(next sprint)
Planning Together
(this sprint)
Tuesday
Product, Solution,
Platform
Business
Refinement
(next sprints)
Product, Solution &
Platform (next
release)
Design / Usability
Review
(next sprint)
Wednesday
Programme, Scrum
Master, Tech
Scrum of Scrum
(this release)
Tech Solutioning
(next release)
Thursday
Scrum Master, Dev
teams
Story Refinement
(next sprint)
Friday
Customers, Users,
Everyone
Usability Testing
(next sprint /
release)
Review Together
(this sprint)
Retrospective
(this sprint)
Planning Understanding Solving Fixing Realising
Every Day
Removing blockers
Daily Scrum
• Exploration Team
• Country Team
• Component Team
6. Everyone speaks a different language, make tooling the
common currency or suffer the exchange rates
Business, Product Owner
• Requirements
• Prioritisation
Exception
Epics, Stories
Ideas, all others
Designer, UX, UI
• User research
• Usability testing
• Prototyping
• Wireframes
Product subpages
Architect, Infra, IT
• Solution Architecture
• Sequence Diagram
• Environment set up & endpoints
Definition of Ready
Carbon
Design
7. Consider an ecosystem of people, their tools and
processes to find connectivity for transparency
Prgramme, Scrum Master
• Release Plan
• Management report
• Kanban & Scrum board
Exception
Burndown charts
Version report
Developers & QA
• Code
• Test cases
Definition of Done
Common Depository, Different View – An epic and a story is traced from exploration to done by different teams.
8. When DesOps lead, design is not realised,
When DevOps lead, development is not utilised
Design (Continuous Exploration)
Component design aligned to a release.
Eg. A button can have many different styles, focus on what’s
needed first.
Usability testing to know design works.
User research to know design is great.
They don’t have the same frequency.
Eg. Spend time on user research before and after product
release but release a product.
Component design aligned to a release.
Eg. A button can have many different styles, focus on what’s
needed first.
Development (Continuous Delivery)
APIs & Microservices are great but
sometimes, we use lists and objects.
Eg. A list of hospitals can change, API can link to data source but a
list is more practical.
Components completion by sprints
and planned by release.
Eg. A list of hospitals can change, API can link to data source but a
list is more practical.
Sometimes design has to change to fit
solution, sometimes, solution has to
change to fit experience.
Eg. To fit a smaller size screen or long languages, some design
components have to change.
Focus on the User’s Needs
Nobody likes rework.
It’s called Iteration
Nobody likes deadline
It’s called Respect
Nobody likes compromise
It’s called Collaboration
Continuous Integration – User needs is both speed and experience.
9. As applications become platform, understanding
requirements and design requires redefinition
Product Owner ?
Solution Manager
• Experts in specific solutions.
• Considers solutions end to end (sales to operations)
• Consider solutions across channels (digital and non
digital
• User service oriented
Platform Manager
• Experts in digital platforms (mobile, web, watch etc)
• Considers solutions on digital platforms
• Considers usability and feasibility of solutions
• User experience oriented
Product Owner
• Overall placement and adoption of platform
• Prioritisation of needs considering all requirements
• Product oriented (depending on the product)
Product Manager
Risk
Compliance
Works With
Architect & IT
Designers
Developers
Management
Business
Programme