How to answer on the question: "How much and when?". Requirements gathering is an essential part of any project and project management. Understanding fully what a project will deliver is critical to its success. This may sound like common sense, but surprisingly it's an area that is often given far too little attention. Why process is critical? Is effective communication is more important than hard work? Like any people-centered business activity, software requirements development is difficult. When software pros team up with their business counterparts to specify exactly what the planned application should and should not do, mistakes are hard to avoid. These terms mean essentially the same thing. But requirements elicitation is preferred because it more accurately describes the challenging, back-and-forth conversation that must take place among stakeholders to specify an application's needs effectively. By contrast, requirements gathering suggests that requirements are fully formed and ready to be discovered, which, of course, is not the case. The idea that software requirements development is a simple, linear process is part of an outdated mindset, where "you ask people what they want and then build an application with the requested features". More...