[baash05]

Lost me at Which of the following agile method are you using?

TDD is not a method of agile. It has nothing to do with project management or team structure. On a rails/elixir team you TDD as a reflex.

Release cycle is many times a day. On a team of 20 devs, we're releasing to prod about 12 times a day.

The idea of Projects keeps coming up. Often projects are 1 or 2 day features. Customers don't feedback in a day or two long feature.

Then we A/B test the feature, and if it improves the metrics, we move on.

...

Ahh... I see what you did here.

These projects are desk or mobile apps. Clear release cycles and manuals. Web dev's deliver many times a day. There is no major and minor version management in most places. In fact many places have different teams delivering different features on one app at the same time.

"You take the necessary time to document the changes you made to make them traceable, even in crunch time." -> GIT takes care of this, and has been for well over 10 years now. No dev company would go without git or like.

[tvaperi]

Thank you very much for your participation. We try to cover all aspects of agile software development like "TDD", "short release" etc. as describe in the literature. This is the reasons why the questionnaire is so long. Whether those belongs to agility or not we hope to find out during the analysis.

We assume that CMM tool only provide the technical basis for a good documentation but how well it is used depends on the developer.

Thank you again for your participation!

[HelloNurse]

> We assume that CMM tool only provide the technical basis for a good documentation but how well it is used depends on the developer

This comment exemplifies an important potential source of bias in your future analysis: judging how well practices are applied, which is neither objective, feasible, or relevant. Someone's use of a practice shouldn't be considered more (or less) agile on the basis of their success, and you also lack clear measures of success to begin with.