Project Planning It occurs to me that part of project planning matches the process of defining requirements. In requirements definition the business requirements, typically defined by the business analyst, define WHAT needs to be done to solve the business problem and the system requirements, typically defined by the systems analyst, define HOW the problem will be solved. In project planning the Work Breakdown Structure (WBS) defines what the project needs to do to solve the problem, and the precedence network, complete with critical path, defines how it is going to be done. The process of defining what needs to be done and then how to do it is not often followed nowadays as, in the rush to get things done to be competitive, often development teams simply rush to doing something without taking the time to really define what needs to be done and then how to do it. Plans are good. And requirements are really nothing but a plan to solve a problem.  ¶ 9:47 AM