Savvas has worked on highly scalable, high performance, evolvable systems in industries such as financial services, telecoms, entertainment, gaming, health and lately transportation. Through different positions as tech lead, and architect (and sometimes both), he helped companies solve complex problems by applying process changes, collaborative discovery, design workshops, architecture, and implementation of sociotechnical systems.
Savvas has significant experience with DDD, CQRS, and Event Sourcing and has delivered and maintained such solutions in production. Lately he's interested in the behaviours that enable an organisation to become highly performant, user-focused, and competitive inside the system it lives, and is creating a baseline for a process that will enable organizations to achieve those goals.
This interactive session will talk about the past and future of crafting software and how it is changing the way developers and companies think about software development.
Moderated by Nix Crabtree, join the conversation, share your insights and probe the speakers on the elements of their talks that left you wanting more.
Building software which meets the requirements of the business has been and still remains quite the challenge. So much so in fact, that "build the thing right" and "build the right thing", are both phrases used in software development to emphasize perspectives, and in extent challenges in analysis and development of a product. To our aid, comes Event storming.
Event storming is a workshop which helps everyone in the product-building team to reach a shared understanding of the domain, but also helps us establish what needs to be built and how, by creating a model of the software in a format which is verifiable by our subject matter experts. At the same time, Event Storming can help us discover our inherent service boundaries, which is the biggest source of risk in a microservices architecture.
In this talk Savvas will go through a short history of dysfunctional processes, before explaining how Event Storming addresses them. By the end of the talk you should know:
- What problems does Event Storming solve
- What are the different types of event storming
- Who should be involved in each one
- What is the expected outcome of each level
The Accelerate book (Forsgren, Humble, Kim) succeeded in providing indications of what makes a high-performance organization, along with insight on the science behind the research. The findings are as valuable as they are unsurprising.
However, while there is a lot of information describing the characteristics and indicators of high performers, the actionable information inside of the Accelerate is limited and focused, still leaving gaps for organizations on their way to achieve high performance.
In this talk, I'll be introducing a baseline for a product development process which can help you on your way towards becoming a high-performance organization. I'll cover three topics:
- Process: how requirements should come into a team
- Architecture: using reactive, event-driven systems with event sourcing to achieve low coupling
While the presentation will focus on some of the more important aspects of just three major aspects of a product development process, they form a reasonable baseline of a process which can give you a running start on your journey of becoming a high-performance organization.