It depends entirely on what you're building, for whom, and so on. I found quite a lot of the Agile (at least, as it is practiced) business to be unhelpful in s

It depends entirely on what you're building, for whom, and so on. I found quite a lot of the Agile (at least, as it is practiced) business to be unhelpful in several endeavors -- for whatever mysterious reasons administration was unable or unwilling to communicate that mockups are not full products or that the "clients" would be looking at anything but a finished product, rather like needing to have an entire house built before giving input on design. For ETL business, I did most of my people-time up front, before any real code was written. Then came a long period of little interaction, then a period wherein a basically-complete system was displayed. Analysis has a bit more periodic refinement. Then you have the issue of finding users whose input is worth discarding, namely someone who might tell me, six months later, that someone else (who was not named) found something "too hard." I can't really do anything with that. Despite asking for names from this person, or to put be in touch with those with the complaints at the time, it just wouldn't happen, so this became someone to tune out.