Why is that? What if you came across the perfect agile tool.. but it was developed with waterfall? I don’t see how that makes it less valuable for the customer.

I’m pretty sure all the agile tool vendors could give good answers to the questions. But at the end of the day, no one want to be agile for the sake of being agile. What really counts is whether you are adding business value for your customer.

A more interesting question to ask is ‘In what way does xyz tool allow my customer to be more agile?’

To answer your questions,

Our main product, Silver Catalyst, started with Scrum but we use Kanban for this project now. Why? As the project context changes, the process needs to change accordingly.

# Your Definition of Done

Coded, unit tested (for the backend), integration tested (for the UI), manually tested

# Whether you use TDD? Or at least Unit Testing?

Backend code is TDD. Some UI code is unit tested in Jsunit. Interaction code is functional tested in Selenium.

# What do you do for Acceptance Testing?

Code has to pass the automated functional tests plus a manual test

# How often do you release?

Once a week. We make lots of small releases. But that doesnt mean that a story takes a week. Since we use Kanban, development is decoupled from the release cadence.

# What did you learn in your last retrospective?

Action point to improve the error reporting capability of the selenium tests so that we get notification failures even while the tests are still running.