Can't see a team's current workload, so people use Kanban charts elsewhere

Bug #914854 reported by Matthew Paul Thomas on 2012-01-11
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned

Bug Description

Often a team of finite size works on a software project, but it is not easy to see how many things the team is trying to do at once, or what they are scheduled to do next.

To work around this, Canonical Launchpad developers, and some Canonical Ubuntu teams, separately use Kanban boards hosted on leankitkanban.com. Unfortunately, this causes a lot of bureaucracy in copying issues from bug reports or blueprints to kanban cards. To the extent that developers make cards only for large issues, not small ones, this may nudge software towards becoming unpolished. And time is lost when people don't know about the Kanban board, or have trouble finding it.

This could be fixed in Launchpad by providing a Kanban view of bug reports for a team, as a toggle with the existing List view. (See also bug 914835, about providing a Burndown view for a milestone.)

Implementing this may first require making a team's assigned bug listing include all bugs assigned to members of the team (bug 307572).

Curtis Hovey (sinzui) wrote :

This was discussed in 2010 by sinzui and thumper. We proposed that milestone/series views would permit you to provide a team to filter the work items on. This principle could be applied to other views where managers need to see only a subset of the data listed for users and teams.

tags: added: milestones series
Changed in launchpad:
status: New → Triaged
importance: Undecided → Low
tags: added: bugs specifications
Robert Collins (lifeless) wrote :

I'd be wary of conflating 'show the workload for a team' with the UI around bug searches. Workload includes merge proposals, specifications, bugs, answers, translation reviews...;

There is lp-kanban which removes the administrative overhead - point it at a project and get back a kanban board for it.

Oh, and that is the other thing; probably want a way to separate out 'something $person is doing in their spare time' and 'something they are doing for $commercial effort. One way would be to specify team-in-project(s); another would be to actually model team work-and-planning (as separate from project work-and-planning).

Matthew Paul Thomas (mpt) wrote :

As far as I know, Kanban boards as currently used don't show specifications, answers, and translation reviews anyway. So my premise here is that n task lists is better overall than n+1 task lists, even if n > 1.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers