3 ms·
> Individuals and Interactions over processes and tools Indeed, it's my experience this is often ignored, along with "ditch what doesn't work for you". I've se
by the_af 8y ago
> Individuals and Interactions over processes and tools
Indeed, it's my experience this is often ignored, along with "ditch what doesn't work for you". I've seen countless articles (and job descriptions!) claiming, for example, that "pair programming" is the sine qua non of Agile; if you don't do it, you're doing something wrong. Or "sure, use what works for you, except if you don't follow these guidelines you are on your own".
I, for example, consider pair programming extremely exhausting. It works for me in very short spans and very limited applications; pushed too far it makes me consider switching jobs.