In software development, analysis paralysis is getting paralyzed doing only analysis and never coming to a decision. It is quite a common scene during the early stages of the project trying to find out everything in the beginning and lose the time. This would end up in a crunch situation. Agile and eXtreme programming practices preach that some output be generated every day. Which means whatever information is available try and make something out it. Changes are applied incrementally and as and when required. This also makes the team focus on what information is available and only look at that piece of it rather than looking at the whole system in one shot.