One of the PMO managers I had requested to be used at portfolio level. So we had a daily 15 mins meeting around the board, quickly reviewing all projects. While at project level might be useful, at portfolio level we didn t find too many benefits of using it. In most cases the changes were not occurring on daily bases and the image of having 10 projects in testing and other 10 in development did not help us too much to solve the resource conflicts.
That seems to be the consensus Anca; that as projects get bigger, the Kanaban board becomes more redundant. Saving Changes...
To manage and monitor critical BAU issues I used huddle boards and we used to have quick huddle meetings in the morning before business hours. Now the Kanban boards are used for many development projects which use Kanban.
Thanks Girija, sometimes the two names (huddle and Kanban) boards are used interchangeably. Unless it is an actual Kanban project, then the Kanban Board uses the pull system. Saving Changes...
We use simplified Kanban boards (i.e. no WIP limits) all the time in the work environment, but I've also used it personally with my family to cut down on the frustration and nagging related to completing house chores :-)
Kiron
Some might impose WIP limits on the number of kids they have :-) Saving Changes...
We also use JIRA, and I find it to be a great virtual platform to visually show the WIP. The pull-system works great while collaborating with team members. I also appreciate the flexibility of this platform as it allows the integration of additional methodologies like scrum.
Effectively used for Project as well as Program Management. I have used Kanban for IT infrastructure projects as well. I think its very effective due to its visual aspect.
Nikunj, do you find issues with using a Kanban board at the Program level, due to size and complexity? Saving Changes...
