Hot answers tagged

7

With respect to testing they are the same. Kanban and Scrum are both iterative Agile development models, the goal is to get the most important tasks fully done (including testing) as soon as possible. The product should be potentially shippable at the end of the iteration. The difference is with Scrum the end is a set date, with Kanban it could be anytime ...


3

You may want to look at TFS 2012. It now has a Kanban board in the tool. There is a preview version of the TFS service in the cloud available if you want to check it out. When I looked into it for TFS 2010, I was only able to find free Kanban tools that did not link to TFS, or paid ones like Urban Turtle that could actually integrate with TFS 2010.


2

Kanban is not a software development methodology. It does not prescribe any method of development or testing. You use Kanban for visualizing - and improving - what you are already doing. So, if you are currently a Scrum team, and have specific testing/ test automation practices, you can continue to use the same with Kanban as well. If you are using ...


1

I'd suggest you look at it as two separate actions: Can I add regression bugs to the product backlog so I don't lose track of them. Can I bring them into the sprint. For the first one, I see no reason not to. I think Jira has a "bug" issue type by default and these are perfectly valid items to have in your backlog. If you want something more specific, you ...


1

During each iteration for each story I like to-do the following: During planning: Are we building the correct feature? I try to look from a user perspective instead of a technical During development: Prepare test-data, pair program with developers and question UX of new developments After development: Risk analyses with a code review, do the unit-test cover ...


1

Unit testing is a great way to test code with specific endpoint values and compare them with expected results, but there are many things that unit testing cannot cover. Unit tests provide you with a linear test, for the software. Automation should cover a more broad approach to what the software actually does. Agile is a difficult space to implement ...


1

It does seem to me that the deployment cadence is almost always of a lower frequency than the delivery (by devs) cadence. Also, that you don't get value to the customer until you pass a critical mass of components. Also, there is often a piece of legacy software that is resistant to automated testing. Also, (but not finally), stuff comes out of the woodwork ...


1

We used to use TFS Workbench before we upgraded to TFS 2012. Its a Windows based application but used to work well.


1

You might take a look at this project on Codeplex for a WIP board that you could use in as a Kanban board. It appears to be process agnostic. It does not appear to have moved out of Beta 2 so I am not sure what the level of stability is or if it is getting any work done on it any longer. It does integrate with TFS 2010 though. Visual WIP http://visualwip....


1

Perhaps no link with TFS, but consider to use Trello: it's free and worth it!


Only top voted, non community-wiki answers of a minimum length are eligible