"agile scrum" is probably a good way to talk about it. after I go lick my wounds from this thread I'll adopt that one
Interesting. I'm not sure I'd agree with that approach, as I think the distinction between "agile" as a general description of a family of processes, and the specifics of a given implementation within that family, does matter. But maybe I just nit-pick too much.
Then again, I also hate the term "sprint" and try not to use it. I think it's misleading and such an inappropriate metaphor as to be actively harmful. I prefer to use "iteration", even in a Scrum environment.
I also hate "sprints" ...you can't sprint forever. I've not tried to get rid of it though.. maybe I should try.
So, because we can't sprint forever, I built "admin week" into our process - we sprint for 2 weeks, heads down nobody bugs devs (but me). then the 3rd week we "rest", do demo day - show progress and prep for next "sprint".
Exactly! It's a totally broken metaphor, as nobody can sprint, sprint, sprint, sprint, ... forever with no pauses, rest, or slow periods in between.
So, because we can't sprint forever, I built "admin week" into our process - we sprint for 2 weeks, heads down nobody bugs devs (but me). then the 3rd week we "rest", do demo day - show progress and prep for next "sprint".
Yeah, I usually try to do something similar to that. It makes a lot more sense to me, than trying to pretend that you can "sprint" continuously for an indefinite period of time.
EDIT: and I put the agile manifesto outside my cube-wall highlighting Individuals and interactions over processes and tools