These slides describe rules for running Architectural Katas, essential for running architectural katas. This was created as part of Software Architecture Meetup January 2019 session.

1. SOFTWARE ARCHITECTURE
MEETUP
JANUARY 2019

2. Architectural Katas
Muhammad Ali
SOFTWARE ARCHITECT
VENTUREDIVE
& Asad Rasheed
SOFTWARE ARCHITECT
NISUM

3. 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

4. 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

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 your solution to the rest of group(teams)
• Answer questions asked from others
• Ask questions to the team presenting their architecture

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

9. • You can find more about katas here https://archkatas.herokuapp.com
• Most of the phases and rules are pretty much standard, taken from
Neal Ford & Ted Nowards site.
Architectural Katas

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

11. Questions?