In these days of remote work, distributed teams, and time zones that stretch across multiple continents, can be more challenging to implement agile successfully or not?
Halloween is upon us and yes, this is another spooky article leveraging this seasonal time of the year to talk about horror stories of project management that our colleagues have shared with us. We bet you've encountered some of them yourself!
Reflecting on the 20th anniversary of the Agile Manifesto might easily lead to nostalgic or vindictive thoughts. This short post will stay away from that and instead distill the two principles and the corollary which we have taken from almost 15 years of Agile experience.
When teams all over the world try to adopt agile methodologies, sooner or later they will be faced with a key question - Is KANBAN the right technique for us? Sometimes, they have known and experienced other agile techniques like SCRUM but most often they are new to agile to begin with. In this article I will try to explain what are some of the pros and cons of KANBAN and what common mistakes are unknowingly made so you can self-diagnose your particular use case, whether you're new to KANBAN or new to agile altogether.
Retrospectives are a well-known tool used by teams that work in product development. In Kaleidos we usually do it as the culmination of a sprint, just after the Sprint Demo. In this post we show examples and methods that we try, it does not mean that they are set in stone :)
In any transition to agile methodologies there is a risk of maintaining old practices that survive in disguise as “agile adaptations”. In the medium term they become structural blocks, agile antipatterns that gradually reinforce this involution. I summarize four of these identified thanks to the involuntary help of Taiga users.
In this interview, Pablo Ruiz-Múzquiz, one of our co-founders, explains the motivation for creating Taiga, how it compares to the other options in the market, and how you can use it for your own projects.