How would you describe the approach your (test) team takes to product development?
- Continuous Quality
- Agile
- Waterfall
- Something else
0
voters
Bonus points for sharing experiences
2 Likes
On paper they like to call it all sorts of names. But in reality, it turns out to be waterfall 
3 Likes
“Watergile” or “Agifall” 
Basically wannabe agile so we use the ceremonies but for sure waterfall 
3 Likes
speaking of the ceremonies
I like to call our Sprint Retro Session, a Ranting Session. People let out their frustrations on a whiteboard, the session organizers move some cards here and there, repeat.
2 Likes
is it anything else then? XD
If I don’t host it myself, we don’t even note action points lol
1 Like
I’m afraid I don’t really see a difference between “Agile” and “Continuous Quality”.
Currently I am in small team that develop / maintains software that is deployed by customers (so, not SaaS). Testers are invited to and participate in all important meetings and decisions. Testers also participate in code review and might do at least basic artifact testing, if other priorities leave time for that. We also have automation doing static and dynamic testing for each change before it is merged, and classic dynamic testing nightly and before each release.
4 Likes
Working for a governmental unit that serves a specific kind of research, the customers are very close by. This makes agile ways of working pretty obvious. Being the senior tester (knowing every system) I work with all the teams, and dependent on the products the approaches to more dogmatic agile development is a little different. But all use a mix of kanban and sprints, all have daily standup meetings, all do sprint plannings and all together does long time planning together with the “customers” a number of times per year. So I would say pretty agile.
3 Likes
We do Scrumfall. The content of the sprints for the next half year is already dertermined.
2 Likes