28-08-2014, 03:30 PM
Planning before doing is always a successful criterion. So making a plan before starting a project is also very beneficial. In this, objectives are made clear so that we can meet our target at time. Generally in planning project we need to follow few planning guidelines because some software projects span a broad range of application domains. It is valuable but risky to make specific planning independent of project context. It is valuable because most people in management positions are looking for a starting point, a thing they can flesh out with project-specific details. They know that initial planning guidelines capture the expertise and experience of many other people. Such guidelines are considered as the credible bases of estimates and instill some confidence in the administrator. Project-independent planning advice is also risky. There is the risk that the guidelines may be adopted blindly without being adapted to specific project circumstances. It comprises of knowing the objectives which we have to meet while making a project. Considering the objectives is the main thing during planning of a project. In this we elaborate that what is our project’s work that is what will be the output provided by us the vender, and regarding this concern we plan the input of the project. Like in our project we simply made clear in our mind that it will work something like Forum, and thereafter we decided the input or requirements of the project.