The Tech Stack
Canvas
TECHNOLOGY DAY / 13.11.2023
Create, Document,
Communicate
JOERG MUELLER
PRINCIPAL CONSULTANT
Slide 2
Slide 2 text
Challenges
Slide 3
Slide 3 text
New Team Member
How to provide an initial overview?
Slide 4
Slide 4 text
New Project
How do we define the main elements?
Slide 5
Slide 5 text
Many Independent Teams
How to get a big picture?
Slide 6
Slide 6 text
The Canvas
Slide 7
Slide 7 text
https://techstackcanvas.io/
Slide 8
Slide 8 text
No content
Slide 9
Slide 9 text
Product Context
•
•
•
•
•
•
Influencing factors for the selected stack
As Context
No need to be complete
On the contrary → Little space forces you to
focus on the essentials
E.g. 10 or 10000 requests/second?
Essential SLAs
Slide 10
Slide 10 text
Classic Layers
•
•
•
•
Programming languages
Frameworks
Important libraries
Databases
Slide 11
Slide 11 text
Supporting
Elements
•
•
•
•
•
•
•
APIs
internal
external
focus on the essentials
Auth*
Compliance rules (e.g. GDPR)
Testing
Slide 12
Slide 12 text
Infrastruktur & Tools
•
•
•
•
Foundation of the product
Cloud providers and most important services
Don't forget analytics
Also includes IDEs, Issue Trackers, VCS and even Chat
Slide 13
Slide 13 text
Creating a Canvas
Slide 14
Slide 14 text
Document an Existing Stack
•
•
•
•
•
•
Simple interview of the team
Takes usually 30-60 minutes
Keep it simple
Miro-Template, if online
PDF Printout, if offline
Post-It notes on a wall also work
Slide 15
Slide 15 text
Create a New Stack
•
•
•
•
•
Very useful in Scoping Workshops
Sometimes an hour is already enough
If you really need to create it from ground up:
see: https://techstackcanvas.io/#create
Important: start with constraints
Slide 16
Slide 16 text
Try it!
The canvas is quickly created → then benefit
Slide 17
Slide 17 text
https://www.comicagile.net/comic/the-canvas-canvas/
Next
Level: