Nimble Blog
Lean, Agile, Digital Transformation, PM, PPM from the Trenches
6 Frameworks Ágeis em Escala — Qual é o Mais Adequado para Você?
Você definiu seus primeiros passos em um desenvolvimento ágil. Talvez você tenha executado um piloto com uma única equipe e queira aproveitar os benefícios para mais
Usando Kanban no Marketing
Em setembro passado, como novo membro da equipe de Marketing da Digité, eu estava me esforçando para entender os produtos da Digité e o espaço em
Desvendando o PI Planning
Personal productivity and time management tools/methods have always been a subject of interest. Numerous methods and tools have been developed over the years. However, few seem to stick over time. Given that any tool or method needs a certain level of discipline at an individual level, is there a method that can really help you manage better, visualize what you need to do and most importantly, stick? In this blog, I am going to share my own experience of tackling this challenge.
10 Fatores a Considerar Para Seu Design de Quadro Kanban
While starting with Kanban may appear simple enough – after all, what can be simpler than ‘start with what you have’?! – modeling your first Kanban board does require some thinking and planning as it depends on a number of factors. Learn how do you design your first Kanban board.
Como Lidar Com os Defeitos Encontrados nas Histórias de Usuários Durante o Desenvolvimento?
We often hear the question – In Kanban, what should we do if a User Story in Test column is found to have a bug that needs to be fixed? Let’s say the workflow is something like this: Todo -> Development -> Test -> Release. If a User Story has completed Development and moved to Test, and a tester finds a bug, what should we do to that User Story? Is it right to leave that User Story in Test and the developer should stop their current development work to fix this Defect first? If so, does this mean that developers must be interrupted all the time to clear the bugs found in Test?
O SAFe (Scaled Agile Framework) é Agile?
Many industry experts have come out and pointed possible flaws in the Scaled Agile Framework. For instance, Ron Jeffries has expressed reservation over SAFe®’s approach to resolve inter-team dependencies by holding a multi-team meeting comprising of over 250 people.
