software engineering Project scheduling

1. Al-Nahrain University
College of Information Engineering
Software Engineering
Project Scheduling
Name : Jaafer Saeed
Department : System

2. Software Project Scheduling
Definitions
Software project scheduling is an activity that
distributes estimated effort across the planed project
duration by allocating the effort to specific software
engineering tasks.
The objective of software project scheduling is to
create a set
of engineering tasks that will enable to complete the job in
time.
When a network of software engineering tasks is
developed, there can be assigned responsibilities for each
task, their execution can be tracked and controlled, and also
there can be adapted the risks if necessary.
Building of large software systems usually involves a
large number of interdependent tasks, which are difficult to
understand and manage without a schedule. The progress of
a software project can not be evaluated in practice without
a schedule.
The steps for performing project scheduling, after
effort and size estimation, include allocation of effort and
duration to each task and design of a task (activity) network
to enable the team to meet the established delivery deadline
What is PROJECT SCHEDULING?
selected an appropriate process model and identified the
software engineering tasks that have to be performedand
we estimated the amount of work and the number of
people, you know the deadline, you’ve even considered the
risks and finally Now it’s time to connect the dots. That is,
you have to create a network of software engineering tasks
that will enable you to get the job done on time.

3. Why it’s Important?
1. In order to build a complex system, many software
engineering tasks occur in parallel.
2. The result of work performed during one task may
have a profound effect on work to be conducted in
another task.
3. These interdependencies are very difficult to
understand without a schedule.
4. lt’salso virtually impossible to assess progress on a
moderate or large software project without a detailed
schedule.
Principlesof SoftwareProject Scheduling
- compartmentalization:the project must be decomposed
into manageable activities and tasks;
- interdependency:the relationships between the tasks
have to be established because some activities will depend
on other, while other activities may occur independently;
- timeallocation:each task must be allocated a number of
time units, also possibly a start date and a completion date;
- effort validation:every project has a defined number of
staff;
- responsibilities:every task should be given to a specific
member;
- outcomes:every task should have a defined result;
- milestones:every task should be associated with a
milestone.

5. Both methods are drivenby informationdeveloped
in earlier project planningactivities:
1- Estimates of effort
2- A decomposition of product function
3- The selection of the appropriate process model
4- The selection of project type and task set
Both methods allowa planer to do:
1- determine the critical path
2- time estimation
calculateboundarytimes for each task Boundary
times:
1- the earliest time and latest time to begin a task
2- the earliest time and latest time to complete a task
3- the total float.
Several ways to track a projectschedule:
1- conducting periodic project status meeting
2- evaluating the review results in the software process
3- determine if formal project milestones have been
accomplished
4- compare actual start date to planned start date for each
task
5- informal meeting with practitioners

6. Project managertakes the control of the schedulein
the aspectsof :
1- project staffing
2- project problems
3- project resources
4- reviews
5- project budget
Format and Benefits of Production Schedule Software :
As far as the format of production schedule template is
concerned, it varies and depends on the type of production
operations. There are some products which are produced in
stages, whereas some are produced in one hand shift. But
mostly, a timeline schedule is made by planting real time
axis at one hand and available task distribution on the other.

7. Production scheduling:
Production scheduling is an essential process of every
manufacturing company. It has an immediate impact both
on the top and the bottom line of any manufacturer. The
complexity of both supply and demand networks and of
production processes has been ever increasing. Hence,
scheduling seems to always face one or more of the four
challenges represented in the graph on the right hand side.
looking forward to the feasible mode of working, a well
aligned and least hectic schedule is drawn. Here are some
of the highlighted benefits of these Software:

8. benefits of these Software:
 Schedule software cater hundreds of factors at the
same time
 Allow you to consider more than one plans by
inserting minor variations
 Save your time of documentation and avoids error
 Help in extreme manipulations
 Let you get quicker results through advance
calculative features

9. Seven Tips on How to Build a Schedule:
1. Realize the importance of the schedule :
Project managers and the project management team
often do not put enough emphasis on the schedule.
However, a good schedule touches every Knowledge
Area and process
2. Identify the availability of team members :
A resource inventory is needed to plan the whole
project and to decide which path you will take to
execute the project.
3. Build the schedule around deliverables :
It is human nature to want to build a schedule around
tasks
4. Include regular milestones :
Establish milestones within the schedule and check
those milestones frequently. That way, if a project
lasts for eight months, you do not get to month four
and realize you are going to be late.
5. Expect that the schedule will change :
Realize that the schedule is not permanent because
project tasks and stakeholder needs constantly
fluctuate. The project schedule is really an assumption
about what might happen and when.
6. Have a process for managing change :
Project managers must be willing to shift gears to help
a project stay on track. Establish a threshold that
triggers the change-control process
7. Watch for “hangers” :
A basic scheduling rule is that every task should have
at least one predecessor and at least one successor.