This is not the event year you are looking for. For details of our next event, please visit agilemanchester.net
To view the latest event website please visit agilemanchester.net
For the latest event: agilemanchester.net
In the traditional waterfall software development model, we go for big up-front design. We invest a lot of time in capturing requirements and planning for a future-proof system. However, there is a problem. Most of the time this type of big up-front architecture faces challenges in adapting the real world. This kind of architecture becomes fragile, hard to change and fails to respond to the business needs.
Instead of this, we can try agile architecture that evolves over a period of time. We start designing the system based on the available information, develop the system, get the feedback and improve or add new functionalities. So the team reacts appropriately to changing requirements without excessive attempts to future-proof the system.
Recently, my team in Unibet has developed a new bonus system based on the principles of agile architecture. Our old system is a monolithic system. It is a big system, hard to make any new changes to and time to market new features is very high. So we have divided the existing system into multiple small and simple services. All the services are created in terms of business capabilities to provide business values to our valuable customers. These services have their own bounded context. They talk to each other using sync and async ways. All of these services are not created at the same time. They are created when they are required.
In this experience report, I will share the benefits of creating an agile architecture. I will also share some of practices we have followed in developing these services like having feedback loops from the actual code back to the design, continuous delivery, collaboration, role of tech leadership, etc.
It is challenging journey for the whole team to learn these concepts and create this kind of architecture. In this session I want to share this experience with others.
I have been developing several medium-to-large J2EE based software using different agile processes for the last 10 years. I practice Test Driven Development (TDD) and Behaviour Driven Development (BDD).
In my spare time, I try new technologies, write a blog, read books and do photography.
Need help planning which sessions to attend? We've provided a breakdown of our various session types below.
A presentation and discussion of real-life (not theoretical) experiences of the application (or mis-application) of Agile and Lean practices. Case studies and experience reports include some discussion of lessons learned and an indication of how novel the work is.
Participants learn a new approach, tool or technology through using it to solve one or more practical exercises. Any software/hardware requirements are disclosed in the session description.
A session focused around some specific tool, technique or issue. Primarily led by the speaker, tutorials usually include some elements of interactivity or individual / group exercise.
An in-depth working session on a specific topic. May include paper presentations.