This link has been bookmarked by 127 people . It was first bookmarked on 26 Jun 2008, by David Draper.
-
29 Mar 12
-
12 Mar 12
-
05 Jan 12
-
28 Dec 11
-
12 Dec 11
-
01 Dec 11
-
24 Oct 11
-
13 Oct 11
-
A kanban is more than an index card
-
-
20 May 11
-
17 May 11
-
29 Apr 11
-
27 Apr 11
-
05 Apr 11
-
11 Mar 11
-
07 Mar 11
-
30 Nov 10
-
23 Nov 10
-
16 Nov 10
-
08 Nov 10
-
21 Sep 10
-
01 Aug 10
-
31 Jul 10
-
22 Jun 10
Nico CoetzeeAs more people become interested in Lean ideas and their application to knowledge work and project management, it’s helpful to find ways that make it easier to get started or learn a few basic concepts that can lead to deeper insights later. For those tha
agile development kanban projectmanagement lean software_engineering
-
08 Jun 10
-
31 May 10
-
26 May 10
-
24 May 10
-
21 May 10
-
22 Apr 10
-
28 Mar 10
-
23 Mar 10
-
20 Feb 10
-
08 Feb 10
-
04 Feb 10
-
25 Jan 10
-
21 Dec 09
-
07 Dec 09
-
21 Nov 09
-
18 Nov 09
-
17 Oct 09
-
18 Sep 09
-
16 Sep 09
-
27 Aug 09
-
26 Aug 09
-
25 Aug 09
-
17 Aug 09
-
11 Aug 09
-
-
10 Aug 09
-
08 Aug 09
-
29 Jul 09
-
David RousselThis is very similar to what we do at work
-
24 Jul 09
-
08 Jul 09
-
02 Jul 09
-
21 Jun 09
dalehagglundAn introduction to applying kanban concepts to software development.
kanban scrum agile software development methodology lean programming planning estimation
-
05 Jun 09
-
17 May 09
Tim Lossen"For those that are curious about kanban in an office context, it’s not unusual to find people who are either currently using Scrum, or have some understanding of Scrum as representative of Agile thinking. One way or another, Scrum users are an important
-
25 Apr 09
-
08 Apr 09
-
27 Feb 09
-
12 Feb 09
-
27 Jan 09
-
A problem with the basic index-card task board is that there is nothing to prevent you from accumulating a big pile of work in process. Time-boxing, by its nature, sets a bound on how much WIP that can be, but it can still allow much more than would be desirable.
-
then you need another mechanism to regulate the “money supply.” In our case, we simply write the quantity of kanban in circulation on the task board, and allocate new cards according to that limit.
-
You might have a simple principle like: prefer completing work to starting new work, or you might express that as a rule that says: try to work on only one item at a time, but if you are blocked, then you can work on a second item, but no more. In our example, that rule gives us an effective WIP limit of 6.
-
Just because anybody can have more than one item in process doesn’t mean that everybody should have more than one item in process. A problem with our multitasking rule is that it locally optimizes with no consideration of the whole. An implicit total WIP limit of 6 is still more WIP than we should probably tolerate for our three workers. A limit of 4 of 5 total items in process at one time still allows for some multitasking exceptions, but disallows the obviously dysfunctional behavior of everybody carrying two items
-
The ready queue contains items that are pending from the backlog, but have high priority
-
Here we’ve broken down in-process into two states: specify and execute. Specify is about defining whatever criteria are necessary to determine when the work item can be considered complete. Execute is about doing the work necessary to bring that work item into a state which satisfies those criteria. We have split our previous WIP limit of 5 across these two states. Specify is considered to take less time in this case, so it is given a limit of 2. Execute consumes the remaining limit of 3. We might change this ratio as time goes on and our performance changes.
-
Adding the specify-complete column communicates to the team that a work item which was previously in the specify state is now ready to be pulled by anyone who wants to move it to the execute state. Work that is still in the specify state is not eligible to be pulled yet. If the owner of a ticket in the specify state wants to hand it off, he can put it in the complete buffer. If he doesn’t want to hand it off, he can move it directly into the execute state as long as capacity is available.
-
e will also need some agreement about what results to expect at each handoff. We can do that by defining some simple work standards or standard procedures for each state. These do not have to be complicated or exhaustive. Here, they are simple bullets or checklists drawn directly on the task board.
-
The next event we might consider for scheduling planning activities is the concept of an order point. An order point is an inventory level that triggers a process to order new materials. As we pull items from the backlog into the process, the backlog will diminish until the number of items remaining drops below the order point. When this happens, a notice goes out to the responsible parties to organize the next planning meeting. If our current backlog is 10, our throughput is 1/day, and we set an order point at 5, then this planning will happen about once a week.
-
-
19 Jan 09
-
A problem with the basic index-card task board is that there is nothing to prevent you from accumulating a big pile of work in process. Time-boxing, by its nature, sets a bound on how much WIP that can be, but it can still allow much more than would be desirable.
-
a kanban is a kind of private currency
-
Just like money is not about the bills. Kanban is all about the limits, the quantity in circulation.
-
a kanban serves two functions: it is a request to do something in particular, but it is also permission to do something in general.
-
it is not difficult to augment Scrum with a few simple practices that move us towards a more recognizably lean workflow. The most obvious is the reduction of iteration length,
-
-
17 Jan 09
-
07 Jan 09
-
05 Jan 09
-
10 Dec 08
-
12 Nov 08
-
10 Nov 08
-
29 Oct 08
-
23 Oct 08
-
07 Oct 08
Francis Nortonhow to transition from scrum to kanban - also acts as an implicit definition-by-contrast with scrummerfall
-
18 Sep 08
Pedro TrindadeEssays on the Continuous Delivery of High Quality Information Systems
toread software scrum projectmanagement project programming productivity process scrum-ban scrumban
-
10 Sep 08
-
01 Sep 08
Patrick ScheuererAs more people become interested in Lean ideas and their application to knowledge work and project management, it’s helpful to find ways that make it easier to get started or learn a few basic concepts that can lead to deeper insights later. For those tha
lean scrum kanban projectmanagement software agile productivity estimation process development
-
30 Aug 08
-
26 Aug 08
-
20 Aug 08
Yeray DariasAs more people become interested in Lean ideas and their application to knowledge work and project management, it’s helpful to find ways that make it easier to get started or learn a few basic concepts that can lead to deeper insights later. For those tha
-
23 Jul 08
-
15 Jul 08
-
14 Jul 08
-
11 Jul 08
Ed Daniel"Since Scrum can be described as a statement in the language we use to describe kanban systems, it is also fairly easy to elaborate on that case in order to describe Scrum/Kanban hybrids."
agile lean methodology process programming scrum kanban development software
-
26 Jun 08
David Draperscrum to kanban
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.