Talk Idea: Kanban - evolving a workflow using common sense

[railsnut]

This isn't directly ruby related obviously, but if there's interest
I'll see if I can come up with a talk that shows how the workflow
approach called Kanban evolves out of applying common sense to typical
workflow problems.

Any takers ?

Andy

[botanicus]

I think this may be really interesting talk. I've been working with
Andy (author of this thread) and Kanban worked for us pretty well. It
has potential to replace SCRUM, I believe, so you guys should be
interested :)

Cheers,

Jakub Stastny
http://twitter.com/botanicus

[Matthew Rudy Jacobs]

I'd like to know how you deal with deployment.

My current client has quite a lot of machinery in place for change requests.

So, deciding on what we should do kind of does happen on a daily basis (its not supposed to)
but it always has to fit into a regular release cycle...

2009/11/17 railsnut <bigbe...@hotpop.com>

[railsnut]

The current deploy cycle we use is weekly.

So deploy will be wednesday evening, and at the cut-off time for
deploy planning (say wednesday lunchtime) we pick the most recent
commit where everything below it (in the master branch) has passed
UAT and base the deploy branch there. Then if there's a fix in a
later commit that absolutely must be released at the same time, we
cherry-pick that fix into the deploy branch. (We try to persuade
people that shouldn't happen, because it's possible we may have to
remember to cherry-pick that into the next deploy branch too). We make
sure the deploy branch passes CI, and the chances are we'll do a test
deploy to our 'edge' server too.

We could also, on any other day of the week, under pressure, build a
deploy branch and then deploy, I guess.

Is that what you wanted to know ?

Andy

On Nov 17, 5:13 pm, Matthew Rudy Jacobs <matthewrudyjac...@gmail.com>
wrote:

> I'd like to know how you deal with deployment.
>
> My current client has quite a lot of machinery in place for change requests.
>
> So, deciding on what we should do kind of does happen on a daily basis (its
> not supposed to)
> but it always has to fit into a regular release cycle...
>

> 2009/11/17 railsnut <bigbeat...@hotpop.com>

[railsnut]

'Replacing Scrum' is interesting. In some ways, Scrum is a variety of
Kanban with some of the good kanban/lean ideas ignored (e.g. work-in-
progress limits) and with some things made mandatory rather than
optional (e.g iterations, impediment backlog).

If you did scrum but additionally added work-in-progress limits within
the iteration (e.g. no more than 2 items in 'coding' no more than 4 in
'UAT'), the chances are that Kanban people would say 'yes, that's
kanban'. The thing is ... workflow without iterations IS
possible :)

Andy

On Nov 17, 5:02 pm, botanicus <stas...@101ideas.cz> wrote:
> I think this may be really interesting talk. I've been working with
> Andy (author of this thread) and Kanban worked for us pretty well. It
> has potential to replace SCRUM, I believe, so you guys should be
> interested :)
>
> Cheers,
>

> Jakub Stastnyhttp://twitter.com/botanicus

[Martin Sadler]

Sounds good to me. We've been practicing Kanban for a few months now
so I'd be interested to hear how JGP are applying it and likewise any
other
companies.

..potential for a panel style discussion at the conf if there is
enough interest. thoughts?

> --~--~---------~--~----~------------~-------~--~----~
> http://rubymanor.org
> Group home: http://groups.google.com/group/ruby-manor?hl=en
> Unsubscribe at ruby-manor+...@googlegroups.com
> -~----------~----~----~----~------~----~------~--~---
>

[Jonathan Conway]

+1 I'd definitely be up for learning a bit more about Kanban even though it's not

Ruby related.

Cheers

Jonathan

--

http://rubymanor.org
Group home: http://groups.google.com/group/ruby-manor?hl=en
Unsubscribe at ruby-manor+...@googlegroups.com

--
---------------------
www.jaikoo.com

[edavey]

yes to this talk or discussion. SCRUM is working for us, but it would
be good to hear about other methodologies which work too...

ED

On Nov 18, 8:51 am, Jonathan Conway <jai...@gmail.com> wrote:
> +1 I'd definitely be up for learning a bit more about Kanban even though
> it's not
> Ruby related.
>
> Cheers
>
> Jonathan
>
> On Tue, Nov 17, 2009 at 11:12 PM, Martin Sadler <mts...@googlemail.com>wrote:
>
>
>
>
>
> > Sounds good to me. We've been practicing Kanban for a few months now
> > so I'd be interested to hear how JGP are applying it and likewise any
> > other
> > companies.
>
> > ..potential for a panel style discussion at the conf if there is
> > enough interest. thoughts?
>
> > On 17 Nov 2009, at 14:43, railsnut wrote:
>
> > > This isn't directly ruby related obviously, but if there's interest
> > > I'll see if I can come up with a talk that shows how the workflow
> > > approach called Kanban evolves out of applying common sense to typical
> > > workflow problems.
>
> > > Any takers ?
>
> > > Andy
>
> > > --~--~---------~--~----~------------~-------~--~----~
> > >http://rubymanor.org
> > > Group home:http://groups.google.com/group/ruby-manor?hl=en

> > > Unsubscribe at ruby-manor+...@googlegroups.com<ruby-manor%2Bunsubscribe@googlegrou ps.com>

> > > -~----------~----~----~----~------~----~------~--~---
>
> > --
> >http://rubymanor.org
> > Group home:http://groups.google.com/group/ruby-manor?hl=en

> > Unsubscribe at ruby-manor+...@googlegroups.com<ruby-manor%2Bunsubscribe@googlegrou ps.com>
>
> --
> ---------------------www.jaikoo.com

[railsnut]

I'd be happy to have a panel thing about Kanban, whether I participate
from the floor or the panel. Zero preparation compared to a talk.

So I'll volunteer for the Panel if there's going to be one.

If anyone wants an explanation of Kanban besides that let us know
here.

Andy

[Roland Swingler]

+1 if it isn't an intro to Kanban but focused on problems that come up
applying it in practice and some approaches to solving them. A panel
could be good as long as it was a *bit* planned - most panels I've
seen before have lacked direction and get lost in sidetrack arguments.

On a side note I'm personally not at all bothered about whether the
talks/discussions have anything to do with ruby at all - I guess I'm
approaching ruby manor from the angle of "anything that would be of
interest to ruby/otherwise-enlightened developers" rather than "ruby
things that are interesting" - but others will certainly have a
different take on it.

Roland