Fact sheet: Kanban for test organizations

Together with a client I was discussing the advantages that kanban can have for his test team. He was really interested. In order to help him communicate our ideas within his organization and get people informed and motivated I made a fact sheet.

Afterwards I made it more generic and translated it to English so others can benefit from it. Click on link for a high-resolution PDF in both Dutch and English: Kanban fact sheet (UK and NL)

Advertisements
This entry was posted in Agile, Getting more out of..., kanban, lean. Bookmark the permalink.

4 Responses to Fact sheet: Kanban for test organizations

  1. Nice – hopefully it really works like that for some, but feedback I get is: waste of time in too many meetings, and stories are not refined enough nor reviewed properly ahead of time.
    I’m not even starting to talk about regression in companies with large features legacy.

    (BTW – English version need some additional review)

    Like

  2. Hi Kobi, Thanks for your reply.

    I believe the kanban meeting can replace the ordinary daily meeting that is often being held. And like when the meeting is kept short (e.g. like scrum meeting) that should not be a problem should it? Or do you have experience otherwise?

    Regarding the stories that are not refined enough. Do you mean that testing is hindered by the lack of detailed design? That is of course a problem, but will be a problem if you manage your work flow in a traditional way, would it not?
    If you would like to elaborate on that, please do.

    I will do a language check as you suggested….
    Looking forward to your response,

    Cheers.Derk-Jan

    Like

    • Hi,

      Yes, I guess some of these might not work well on other working methods too,
      An of course what I experience might be wrong implementation – that is why I am interested to hear from others – how does it work for them.

      As to stories, I guess in some cases no one reviews stories in the backlog, till these are assigned to a sprint, and by then it might be too late to improve,
      the other hand reviewing these too early might mean a waste of work on items which will never be developed.
      How would you tackle that?

      Cheers,
      Kobi

      Like

  3. Pingback: Belgium Testing Days | Derk-Jan de Grood

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s