Search Results

The Scrum Guide is intentionally sparse on detailed responsibilities. There are some delineations that are important for Scrum to work properly and it calls those out - all others it leaves up to the …

There are a few points to consider on this. 1) Scrum uses PBIs. Product Backlog Items are all the things that make up the product backlog. Any item that you have to do can be an item in the product b …

This can be confusing because there is no authoritative body that sets terminology for Agile and, therefor, there is not "right" answer. But, these definitions and distinctions should be close. Roadm …

This sounds like a primarily code-oriented problem. You want components of your application to be loosely coupled or completely decoupled. Using good programming principles like single responsibility …

First thing is first: Kanban has no queue columns. This is an anti-pattern. To elaborate, a Kanban board is a visual representation of a workflow. In workflow mapping, we do not represent wait states …

Not surprisingly, I hear that question a lot. The basic problem with the question is that Agile disagrees with the fundamental idea of a fixed-scope/fixed-timeline project. In the question you were as …

Because Kanban is not a full framework for developing products in itself (it's a method to optimize another process), there are many things it doesn't specifically account for. However, teams often tr …