What is Planning Practice in Software Engineering ?

The planning activity encompasses a set of management and technical practices that enable the software tam to define a road map as it travels towards its strategic goal and technical objectives. Planning provides guideline for software team to progress very fast in the project development. Some principles of planning practice are as follows :

1. Understand the scope of the project :- It’s impossible to use a road map if you don’t know where you’re going. Scope provides the software.

2. Involve the customer in the planning activity :- The customer defines priority and establish project constraints. While direct interacting with software team ,customer can negotiate on order of delivery ,timeline and other project related issue so customer involvement is important

3. Recognize that planning is iterative :- Project plan is suppose to change or the personal reason so plan must be adjust to accommodate these changes. Incremental model dictate replanting that is  after delivery of each software increment to user feedback is receive and change are made

4. Estimate based on what you know :- The intent of estimation is to provide an indication of effort, cost, and task duration, based on the team’s current understanding of the work to be done.

5. Consider risk as you define the plan :- Risk is event when cause happens some unwanted outcomes because risk may have high impact and high probability on project which will destroy it. so proper management of risk is a required

6. Be realistic : – Project should be a realistic. All the practical aspect has to be considered and plan should be dynamic enough to include all reason like delay, mistake, and wrong decision lagging due to technical reason due to personal reason of team.

7. Adjust granularity as you define the plan :- Granularity means level of detail for particular specification. Some activity are repeated and require longer time required detail plan hence granularity must be adjust in the project plan. So that is why Adjust granularity as you defines the plan.

8. Define how you are going to achieve quality : – The most effective mechanism applied during project development to assure the quality. Formal technical review is meeting conducted by technical staff to find out defects in any stage of development and quality is improved by removing defects that is why it mention very clear to achieve quality.

9. Describe how you intend to accommodate change :- Even the best planning can be obviated by uncontrolled change. The software team should identify how changes are to be accommodated as software engineering work proceeds.

10. Always keep track of the plan and make changes as required : – Track the progress of project development on daily basis all team members should participate in planning activity so that they will accept to recover the lagging schedule.


The Generic task set for Planning practice is given below :

1. Reevaluate project scope.

2. Assess risks.

3. Develop and/or refine user scenarios.

4. Extract functions and features from the scenarios.

5. Define technical functions and features that enable software infrastructure.

6. Group functions and features (scenarios) by customer priority.

7. Create a coarse granularity project plan.
  • Define the number of projected software increments.
  • Establish an overall project schedule.
  • Establish projected delivery dates for each increment.
  • Create a fine granularity plan for the current iteration.
  • Define work tasks for each functional feature.
  • Estimate effort for each work task.
  • Assign responsibility for each work task.
  • Define work products to be produced.
  • Identify quality assurance methods to be used.
  • Describe methods for managing change.

8. Track progress regularly.
  • Not progress areas(e.g., schedule slippage).
  • Make adjustments as required.



Next Topic :

No comments:

Post a Comment