This 2021 summer is a time for big changes here at Taiga. Your beloved open source agile project management platform is on a path to reach a new level in 2022. Let this be a teaser of what's to come and what's the impact that matters in the short term.
It's no longer a matter of cloud versus non-cloud. On-demand, flexible and elastic resources are now the norm. What does remain is the question regarding how you operate a platform like Taiga which deals with your organisation's projects and users.
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.
A year in the making! We spent the best part of 2020 figuring out what the future of Taiga and agile project management should look like. Even if this new journey has just started, we couldn't wait to share with you a glimpse of that feature. Behold Taiga6!
The Taiga Team is super excited to share all the great news about the upcoming Taiga6 release. Taiga6 dwarves Taiga5 and Taiga4 combined! and sets course to consolidate its position as one of the major players in the Agile Project Management arena. Also, it's open source!
Year 2020's unexpected plot twist has left many of us still in shock but among other things, we made sure we would continue to work to deliver a great agile platform for cross-domain teams. We even missed Taiga 5 announcement deadline and so we have decided to announce Taiga 5.5 instead. Taiga Seed, new fresh theme, Taiga App partnership and quite a number of changes make up for a wonderful release.
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.
Which methodology is best for a tech startup? We discuss different implementations of agile methodologies (scrum or kanban?), how and when to implement them and which are some of the most common misconceptions.