Paying attention to user/customer needs and making sure they are understood helps a lot.
Not trying to do too much at one time (what I think agile really tries to address) also makes a difference.
Keeping iterations short and keeping the customers in the loop seem to be critical and cover a significant chunk of the infamous '35'.
And doing some 'design': thinking (and conversing) about what is to be delivered and about ways to do it before jumping into code. Can take ten minutes or a couple days, but is important.
If I keep going I'll rehash all 35. . .
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Paying attention to user/customer needs and making sure they are understood helps a lot.
Not trying to do too much at one time (what I think agile really tries to address) also makes a difference.
Keeping iterations short and keeping the customers in the loop seem to be critical and cover a significant chunk of the infamous '35'.
And doing some 'design': thinking (and conversing) about what is to be delivered and about ways to do it before jumping into code. Can take ten minutes or a couple days, but is important.
If I keep going I'll rehash all 35. . .