Agile teams thrive on continuous improvement, and retrospectives are a key practice that enables teams to refine their processes after every sprint. These structured meetings provide a dedicated space for teams to reflect, identify opportunities for improvement, and implement changes that drive efficiency and collaboration.
What does it take to design, build, and launch a dispatch management system in just six months? This presentation offers a deep dive into the technical and collaborative practices like Scrum and Lean Startup that enabled us to deliver an efficient, working solution to a small organization’s business-critical problem.
The ACE! Conference on Lean and Agile Software Development is a conference that brings together in Krakow (Poland) some of the best-known Agile, Scrum, Lean and Kanban practitioners in Europe and abroad. It is the guaranty of a great networking experience for agile software development practitioners that will come away with new ideas and enthusiasm.
Bas Vodde demystifies what it really takes to adopt Large Scale Scrum (LeSS). Rather than a quick “flip,” Bas Vodde explains four main phases that most organizations experience: education, pre-LeSS planning, the flip, and post-change improvements.
SoCraTes UK is an International Software Craftsmanship retreat for open-minded craftspeople and agile software developers in Great Britain and abroad who want to improve their craft and the software industry as a whole. It’s a great opportunity to speak to and code with many like-minded and talented developers. The conference itself is free.
Agile retrospectives are a cornerstone of continuous improvement, enabling teams to reflect, adapt, and enhance their processes. Whether you call it a Sprint Retrospective, Iteration Retrospective, or Team Retrospective, the goal remains the same-identify what’s working, what’s not, and how to improve.
As a software developer, you know that one of the critical period in a project is when you try to make integrate your code in the overall application and push it towards the final user. It is sometimes a long process that you would like to accelerate so that you could obtain a quicker feedback on the quality of your code.
Scrum Expert Copyright © 2009-2026 Martinig & Associates