Skip to main content
Tweeted twitter.com/#!/StackProjects/status/428068088643604480
embarassing typo correction
Source Link
Daniel
  • 16.9k
  • 2
  • 21
  • 49

I'm currently working with a development group that has a variety of project management approaches. They use a Kanban board for tracking work with a constantly re-prioritized backlog, they have iterations and a burn-down chart like scrum, and they have a PMO that wants to know the overall status of the project in a nice, neat timeline.

After working with the project for about a month, it seems like this team delivers sets of functionality that usually take a few weeks to create and the priorities shitshift frequently, making Kanban a great approach for the team. I'd like to get rid of the burndown charts and the long-term project plan, since it changes so often, but there is a real sense of apprehension that some of the long-term goals for the overall project won't be met by their required deadlines.

Does anyone have experience with Kanban metrics to demonstrate progress through work - especially long-term goals that are being worked toward?

I'm currently working with a development group that has a variety of project management approaches. They use a Kanban board for tracking work with a constantly re-prioritized backlog, they have iterations and a burn-down chart like scrum, and they have a PMO that wants to know the overall status of the project in a nice, neat timeline.

After working with the project for about a month, it seems like this team delivers sets of functionality that usually take a few weeks to create and the priorities shit frequently, making Kanban a great approach for the team. I'd like to get rid of the burndown charts and the long-term project plan, since it changes so often, but there is a real sense of apprehension that some of the long-term goals for the overall project won't be met by their required deadlines.

Does anyone have experience with Kanban metrics to demonstrate progress through work - especially long-term goals that are being worked toward?

I'm currently working with a development group that has a variety of project management approaches. They use a Kanban board for tracking work with a constantly re-prioritized backlog, they have iterations and a burn-down chart like scrum, and they have a PMO that wants to know the overall status of the project in a nice, neat timeline.

After working with the project for about a month, it seems like this team delivers sets of functionality that usually take a few weeks to create and the priorities shift frequently, making Kanban a great approach for the team. I'd like to get rid of the burndown charts and the long-term project plan, since it changes so often, but there is a real sense of apprehension that some of the long-term goals for the overall project won't be met by their required deadlines.

Does anyone have experience with Kanban metrics to demonstrate progress through work - especially long-term goals that are being worked toward?

Source Link
Daniel
  • 16.9k
  • 2
  • 21
  • 49

What are some commonly tracked metrics in Kanban?

I'm currently working with a development group that has a variety of project management approaches. They use a Kanban board for tracking work with a constantly re-prioritized backlog, they have iterations and a burn-down chart like scrum, and they have a PMO that wants to know the overall status of the project in a nice, neat timeline.

After working with the project for about a month, it seems like this team delivers sets of functionality that usually take a few weeks to create and the priorities shit frequently, making Kanban a great approach for the team. I'd like to get rid of the burndown charts and the long-term project plan, since it changes so often, but there is a real sense of apprehension that some of the long-term goals for the overall project won't be met by their required deadlines.

Does anyone have experience with Kanban metrics to demonstrate progress through work - especially long-term goals that are being worked toward?