Visar inlägg med etikett kanban. Visa alla inlägg
Visar inlägg med etikett kanban. Visa alla inlägg
tisdag 16 februari 2010
Kanban myself
We've started to use a Kanban-board at the office... we'll see where it takes us. The fuzzy picture is quite intentional... maybe there are secrets on the board, who knows?
torsdag 28 januari 2010
torsdag 14 januari 2010
Kanban & architecture
Just paused for a minute with a fresh cup of coffee and wandered off towards architecture in my mind.
Can Kanban be used by an architecture team? I tend to believe so even though I haven’t had a chance to prove the theory in practice (would be interesting though to hear anyone who has). Working with architecture has a very service-oriented side to it and tends to be somewhat interrupt driven. Additionally in large organizations it is easy to swamp the architecture team with work and as the stack in the inbox gets higher the focus and completion rate decline. Additionally other tasks, part of the normal process, are chunked in so big pieces that it is very easy to lose track of the target.
With Kanban you could get a tool to prioritize between the “service jobs” and “normal tasks”. Additionally you would have to create more tangible chunks of work which give you a sense of progress.
And if you still fail and are just drenched in work the Kanban-board would be a good visualization of just how much you and your team are trying to do… or maybe you are doing things you shouldn't?
Would be interesting to try at some point.
Can Kanban be used by an architecture team? I tend to believe so even though I haven’t had a chance to prove the theory in practice (would be interesting though to hear anyone who has). Working with architecture has a very service-oriented side to it and tends to be somewhat interrupt driven. Additionally in large organizations it is easy to swamp the architecture team with work and as the stack in the inbox gets higher the focus and completion rate decline. Additionally other tasks, part of the normal process, are chunked in so big pieces that it is very easy to lose track of the target.
With Kanban you could get a tool to prioritize between the “service jobs” and “normal tasks”. Additionally you would have to create more tangible chunks of work which give you a sense of progress.
And if you still fail and are just drenched in work the Kanban-board would be a good visualization of just how much you and your team are trying to do… or maybe you are doing things you shouldn't?
Would be interesting to try at some point.
torsdag 12 november 2009
Scrum and Kanban
Here’s just a quick link to a paper written by Henrik Kniberg at Crisp… hm misspelled it Crips at first, guess they are not affiliated.
Scrum vs Kanban.
It is an easy-to-read paper which gives a good introduction to both Scrum and Kanban.
I’ve always liked the simple idea behind Kanban… but Kanban Jedi can be one of the most ridiculous titles invented and just give me a bitter after-taste of “let’s invent a title we can sell”. It’s almost as frustrating as reading headlines like “Kanban, the new Scrum”. Titles and phrases like these just diminish what comes next since they take away all credibility. Almost.
Henrik K also wrote the well-known and good paper XP from the trenches.
Scrum vs Kanban.
It is an easy-to-read paper which gives a good introduction to both Scrum and Kanban.
I’ve always liked the simple idea behind Kanban… but Kanban Jedi can be one of the most ridiculous titles invented and just give me a bitter after-taste of “let’s invent a title we can sell”. It’s almost as frustrating as reading headlines like “Kanban, the new Scrum”. Titles and phrases like these just diminish what comes next since they take away all credibility. Almost.
Henrik K also wrote the well-known and good paper XP from the trenches.
Prenumerera på:
Inlägg (Atom)