Farewell testingreflections!
Submitted by Ainars Galvans on Thu, 18/06/2009 - 07:48.
Yes, the decision to move my blog to a new location is made. That was not an easy decision because testing reflections has become my blogging motto. Thank you Antony for everything.
There are different reasons for the decision. One of the reasons is that I feel I don’t belong here, not any more or perhaps never had. I feel like testingreflections lives primary under the agile banner. I’ve been inspired a lot by agile ideas, but I never adopted them. I reclaim my personal method .
If you are more interested in my agile skepticism you could follow this link. However the reason for that will be described here in my
last reflection on this site
I have been lucky. Most of my career I’ve worked with great developer teams and context-driven managers. By that I mean that they don’t follow a single defined software development method, not because they are not aware of them. Just the opposite – they adopt this or that method depending on feature to be implemented, developer skills, risks, etc. For example tiny features have tiny life-cycle, little to no documentation (design, etc). For medium size features design documents are created and carefully reviewed. For large – investigations, pilots, prototypes…
However we used to have an umbrella covering the process and method complexity. We had changed the umbrella recently. The blue umbrella with “Gate 1, Gate 2… ” on it is in recycling bin. We have the pink “Sprint 1, Sprint 2,…” umbrella now. So what has changed? An umbrella. Anything else? Nothing worth to mention.
There are different reasons for the decision. One of the reasons is that I feel I don’t belong here, not any more or perhaps never had. I feel like testingreflections lives primary under the agile banner. I’ve been inspired a lot by agile ideas, but I never adopted them. I reclaim my personal method .
If you are more interested in my agile skepticism you could follow this link. However the reason for that will be described here in my
last reflection on this site
I have been lucky. Most of my career I’ve worked with great developer teams and context-driven managers. By that I mean that they don’t follow a single defined software development method, not because they are not aware of them. Just the opposite – they adopt this or that method depending on feature to be implemented, developer skills, risks, etc. For example tiny features have tiny life-cycle, little to no documentation (design, etc). For medium size features design documents are created and carefully reviewed. For large – investigations, pilots, prototypes…
However we used to have an umbrella covering the process and method complexity. We had changed the umbrella recently. The blue umbrella with “Gate 1, Gate 2… ” on it is in recycling bin. We have the pink “Sprint 1, Sprint 2,…” umbrella now. So what has changed? An umbrella. Anything else? Nothing worth to mention.