#kanban — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #kanban, aggregated by home.social.
-
Definition of Ready is an agreement between the Product Owner and the team about what state Product Backlog Items need to be in before the Sprint. As long as it remains a lightweight check, it can be a tool for good.
The trouble starts when it gets rigid. A team with a Definition of Ready isn't optimizing for getting an idea from entering the Product Backlog to Deployed. Instead, they're optimizing for Sprint Backlog to Deployed. Items get held up at the gate for trivial reasons, like incomplete Acceptance Criteria or a missing mockup.
Imagine a Definition of Ready that holds up a feature for 6+ weeks while requirements are gathered. Once the work starts it proceeds at a normal pace, so the team can say they've reduced their cycle time, when all that really happened is the delay was pushed earlier in the system. The team feels good but the customer isn't any happier.
Consider measuring Lead Time and not Cycle Time. Any time spent waiting at the Ready gate is then accounted for, making it harder to sub-optimize.
-
Just made some additions to my Lettering Locations map/bucket list, including the Showa Neon Takamura Kanban Museum in Toyko:
Full map here:
https://umap.osm.ch/en/map/lettering-locations_11682#5/34.987000/-112.211000
-
Scrum, Kanban, SAFe, Lean — кто все эти люди?
У нас Scrum, доска Kanban, а скоро переходим на SAFe. Разбираемся, кто все эти люди: от Waterfall и XP до Lean Six Sigma, Team Topologies и AI. Простые объяснения, схемы и пять вопросов, которые стоит задать до смены процесса. Карта подходов к разработке: от Waterfall и XP до Team Topologies и работы с AI. Что они решают, где помогают и как выбрать без посвящения в тайное общество.
https://habr.com/ru/articles/1079848/
#scrum #kanban #safe #less #team_topologies #Lean #Six_Sigma #управление_разработкой