Planning guidelines are generally written statement that contains guidance to be referred before any development and establishing take place of a project. Planning guidelines are often used for purpose of uniformity, comfort, and safe development. These planning guidelines should be followed by any party for development. These are initial planning guidelines that are made on basis of experience of many other people. Planning guidelines creates a convenient living environment. These guidelines are therefor considered credible bases of estimates and build some amount of confidence in the stakeholders.
There are generally two planning guidelines that should be followed for development of a project. These guidelines are given below :
- Give Advice for default allocation of costs among all elements of first-level WBS.
Below is a table is given. In this table, you will see default allocations for budgeted costs of all elements of first-level WBS. Values might change or vary across various projects, but allocation generally plays an essential role by providing a good benchmark for evaluating plan by completely understanding and knowing rationale for deviations from these guidelines. It is actually a cost allocation, not an effort allocation.
First-Level WBS Element Default Budget Management 10 % Environment 10 % Requirements 10 % Design 15 % Implementation 25 % Assessment 25 % Deployment 5 % Total 100 %
- Give Advice for allocation of effort and schedule across all phases of a life-cycle.
Below is a table is given. In this table, you will see allocation of effort and schedule. Value might change or vary across various projects, but allocation generally plays an essential role by providing an average expectation across a spectrum of domain of application.
Domain Inception Elaboration Construction Transition Effort 5 % 20 % 65 % 10 % Schedule 10 % 30 % 50 % 10 %
All guidelines simply translate broad framework into fully explained principles of development. They play a major role in achieving high quality of development of a project. But sometimes, advice regarding project independent planning is also risky. It can be that these guidelines can be adopted blindly without any adaptation to circumstances of a specific project. Another risk can be interpretation in a wrong way.
Attention reader! Don’t stop learning now. Get hold of all the important CS Theory concepts for SDE interviews with the CS Theory Course at a student-friendly price and become industry ready.
- Software Engineering | Project Planning
- Software Engineering | Testing Guidelines
- Iteration Planning Process in Software Project Management
- Distribution Requirement Planning (DRP)
- PERT Planning Process
- Milestones and Deliverable in Project Planning Activities
- Software Engineering | Introduction to Software Engineering
- Coding Standards and Guidelines
- Guidelines to establish Defect Life Cycle
- Software Engineering | Requirements Engineering Process
- Software Engineering | Re-engineering
- Software Engineering | Reverse Engineering
- Difference between Software Engineering process and Conventional Engineering Processs
- Difference between Forward Engineering and Reverse Engineering
- Software Engineering | Halstead’s Software Metrics
- Software Engineering | Classification of Software Requirements
- Software Engineering | Classification of Software
- Software Engineering | Software Project Management Complexities
- Software Engineering | Role and Responsibilities of a software Project Manager
- Software Engineering | Seven Principles of software testing
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to firstname.lastname@example.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.