This is an introduction to Architectural Katas, rules for forming team and rules to contribute in team. It also specifies the expected output from this activity.

1. Architectural Katas
Muhammad Ali

2. Architectural Katas
“How do we get great designers? Great designers design, of course.”
Fred Brooks
So how are we supposed to get great architects, if they only get the chance to
architect fewer than a half-dozen times in their career?
Ted Neward

3. Architectural
Katas
 Kata is a detailed choreographed pattern of movement
made to be practice alone or in groups.
 Architects needs chance to practice, similar to how
programmer needs chance to practice
 Architectural Katas are architectural problems that needs
to be run in a group of 2-3 people.
 There are usually 4-10 groups
 Katas are generally run by a moderator

4. Expected output
Entities Value Objects Aggregates
Bounded
Contexts
Event Storming
Diagrams
End to end high
level architecture
diagram

5. Preparation
Co-workers may not be in
a group together
Make sure you’re sitting a
little distance from any
other project team
None of you will really
need a laptop
Precure supplies
Notepads
Pen/Pencil
Whiteboard (if available)

6. Discussion Phase
YOUR PROJECT TEAM
SHOULD SPEND ‘X’
MINUTES(FIXED BY
MODERATOR) EXAMINING
REQUIREMENTS
YOU MAY ASK QUESTIONS
TO MODERATOR ABOUT
THE PROJECT
ANY TECHNOLOGY IS A
FAIR GAME
YOU CAN TAKE
ASSUMPTIONS W.R.T
TECHNOLOGY BUT MAKE
THEM EXPLICIT
YOU MAY NOT ASSUME
YOU HAVE HIRING/FIRING
AUTHORITY OVER THE
DEVELOPMENT TEAM.

7. Peer Review Phase
Present
Present your solution to the
rest of group(teams)
Answer
Answer questions asked from
others
Ask
Ask questions to the team
presenting their architecture

8. Voting Phase
 Thumbs up
 Thumbs "meh" (out to the side)
 Thumbs down

9. Questions?