tag:blogger.com,1999:blog-8951904624959546499.post9141133436330709283..comments2024-02-22T05:36:59.121-05:00Comments on Test This Blog - Eric Jacobson's Software Testing Blog: Jumping On The KanbandwagonEric Jacobsonhttp://www.blogger.com/profile/08216361684596485033noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-8951904624959546499.post-50209772179711485232012-03-01T06:12:29.519-05:002012-03-01T06:12:29.519-05:00Heya Eric!
We are using Kanban in my team. I am t...Heya Eric!<br /><br />We are using Kanban in my team. I am test leader, we got four developers and one product owner. One of the developers is the team leader (a SCRUM master).<br /><br />It is working really well for us. We use daily standups cause we find that useful and we have modified our Kanban board over time to include the following columns (in order):<br /><br />- Analysis<br />- Selected<br />- Development<br />- Ready for test<br />- In test<br />- Done<br /><br />The Selected column can have max 4 items, Development can have max 6 items, Ready for test max 3, In test can have max 3.<br /><br />We do not use any estimation for managed items (user stories), but we try to size them to around 1 work days worth of work for 1 person.<br /><br />Its a low-stressful way to work and bottlenecks become visible very quickly. Sometimes testers help out getting testing done if testing starts to bottle up.<br /><br />I think the best advice is to not expect everything to work at once and keep modifying the process as you go over time. Identify what works and what doesn't and adjust accordingly.<br /><br />Good luck :)<br /><br />StianStianhttps://www.blogger.com/profile/02615796562742792748noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-39838690246662032922012-02-17T13:01:41.291-05:002012-02-17T13:01:41.291-05:00Ha ha! Good to see your comment here, Matt. Perh...Ha ha! Good to see your comment here, Matt. Perhaps we'll wait to see how it goes for a bit. But yeah, I would love to hear about your experiences. <br /><br />Also, that Alex guy (AKA "Wiggly") seems to talk a pretty good talk.Eric Jacobsonhttps://www.blogger.com/profile/08216361684596485033noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-62900064145334804892012-02-16T17:10:37.103-05:002012-02-16T17:10:37.103-05:00A couple of times at a couple of places, Eric. Le...A couple of times at a couple of places, Eric. Let's talk; maybe it's time to have you back on the podcast? :-)Matthewhttps://www.blogger.com/profile/05956714498778698672noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-71603283387114216082012-02-16T10:17:33.764-05:002012-02-16T10:17:33.764-05:00Good luck! Two important things with Kanban - Cyc...Good luck! Two important things with Kanban - Cycle Time and Work in Process. You're still going to need to do a good job of sizing the inputs into your Kanban in order to get a Cycle Time that has a low variance. Only then will you get the predictablitly you want. I'm afraid you'll still need to work on that story planning.<br />Also, WIP means you'll have to inject serious discipline into the process. You'll quickly find, I suspect, that your development team can work on many items at the same time but the test team can work on less, creating a bottleneck. You will have to deal with that!<br />And remember - there are no silver bullets - you'll have to work to continuously improve.Alexhttps://www.blogger.com/profile/07298916960841993037noreply@blogger.com