Heraklion Software Craftsmanship Community’s session – Architectural Kata
This time it’s a Kata not on coding, but on Software Architecture!Procedure
Each group is given a project (in many ways, an RFP–Request For Proposal) that needs development. The project team meets for a while, discovers requirements that aren’t in the orignal proposal by asking questions of the “customer” (the Moderator), discusses technology options that could work, and sketches out a rough vision of what the solution could look like.
Then, after they’ve discussed for a while, the project team must present their solution to the other project teams in the room, and answer challenges (in the form of hard-but-fair questions) from the other project teams.
Once that challenge phase is done, the room votes on their results, and the next project team takes the floor.
Organisers![]()
- Yorgos Saslis
- Nikolas Vourlakis
As for the Heraklion Software Craftsmanship Community
This is a community for those who want to take software development one step (at a time) further. Those who believe in not just getting the job done, but want to be proud about the kind of work they produce. It is not a community for experienced, old, senior or advanced developers. Anyone who is passionate about improving on the software development craft is very welcome!From The Software Craftsmanship manifesto:
As aspiring Software Craftsmen we are raising the bar of professional software development by practicing it and helping others learn the craft. Through this work we have come to value:
- Not only working software, but also well-crafted software
- Not only responding to change, but also steadily adding value
- Not only individuals and interactions, but also a community of professionals
- Not only customer collaboration, but also productive partnerships
That is, in pursuit of the items on the left we have found the items on the right to be indispensable.
Gallery
