Академический Документы
Профессиональный Документы
Культура Документы
Software managers are responsible for planning, scheduling, Estimation and Risk
Analysis. They monitor the work that it is carried out according to the
requirements and Standards. The most important thing in the development is
that it’s done on time and within the budget. It is not like good project
management can bring the Fruitful results but they might be far better than the
poor management.
Software engineers does the same kind of job like other engineers does but there
are many issues that makes the software engineering difficult and compare to
other tasks, this may include.
This might include the Following topics which might be discussed in detail, and
the report is for the purpose to discuss all these activities and provide the
Solutions required to carry these Steps in an organized manner.
• Management Activities.
• Project Planning.
• Project Scheduling.
• Risk Management.
REPORT FORMAT
• Proposal Writing.
• Project Planning and Scheduling.
• Project Costing.
• Project monitoring and reviews.
• Personnel selection and evaluation.
• Report writing and presentation.
The first stage includes the proposal to win the project; this includes the
objective and goals of the project. Mostly it contains cost and schedule
Estimates, it might be critical task due to the competition in the market.
Staff selection is a great issue in order to continue with the Project, this might
include following reasons:
• Project budget may not allow for the use of highly-paid staff;
• Staff with the appropriate experience may not be available;
• An organisation may wish to develop employee skills on a software
project.
• Managers have to work within these constraints especially when there are
shortages of trained staff.
Manager is also responsible for to keep the customer party informed with the
Details, and it can be more difficult, if we are dealing with time taking software’s.
This might include number of presentations and Report writing to make the client
understand the technicalities of the Project. Mostly Prototypes is the best
presentation activity to make the Client Comfortable with the work done.
Project Planning
The most time consuming project management activity that has to be carried
throughout the development cycle. In short it’s the continuous activity from
initial concept through to system delivery. Plans must be regularly revised as
new information becomes available. Various different types of plan may be
developed to support the main software project plan that is concerned with
schedule and budget.
PSEUDO-CODE
The Project Planning Pseudo code which lets us understand how to handle the
complexity of the Project,
Firstly the project requires getting its constraint set up so that things should be
developed accordingly; initial assessments are taken place for the project
parameters. Accordingly Deliverables and milestones are decided. This Plan
structure is responsible to take the things in order and according to the
schedules. However all this task depends upon the manager, that how better he
can make the work done? Project Schedule is made and activities takes place
according to it similarly all reviews and re-negotiating task occurs continuously
to look out for the holes and get the holes fixed. And if the Problem arises then
proper risk management activities are brought in to use.
STRUCTURE OF PLANINNG
The Structure of the Planning lets one know to how to carry out the Process. This
includes the Following Activities,
• Introduction (to set the constraints and basic objectives of the Project).
• Project organisation (describes the way in which team is organised, i.e.
setting the works).
• Risk analysis (describe the possible project risks).
• Hardware and software resource requirements (hardware and software
support).
• Work breakdown (break down of the Projects in to activities or
milestones).
• Project schedule (Shows the dependencies).
• Monitoring and reporting mechanisms (Describes the management
reports that must be produced).
ACTIVITIES
MILESTONES
FAILURE
• Split project into tasks and estimate time and resources required to
complete each task.
• Organize tasks concurrently to make optimal use of workforce.
• Minimize task dependencies to avoid delays caused by one task waiting
for another to complete.
• Dependent on project manager’s intuition and experience.
The more clear understanding of this activity can be feasible through below
diagram. It tells each activity to be carried in the particular way.
These are the graphical notations used to illustrate the project schedule. Bar
Charts show project breakdown into tasks. Tasks should not be too small. They
should take about a week or two. Activity charts show task dependencies and the
critical path. Bar charts show schedule against calendar time.
Dependency diagram Activity Diagram
The Above Diagram shows the dependency diagram which tells us about the
arrangement and dependency of the work, Similarly Bar chart and Activity
network diagrams are shown.
SCHEDULING PROBLEMS
Following are the problems that manager face while creating the schedule,
Risk
Staff turnover
RISK MANAGMENT PROCESS
Risk Risk
Risk analysis Risk planning
identification monitoring
Risk avoidance
List of potential Prioritised risk Risk
and contingency
risks list assessment
plans
• Risk identification
○ Identify project, product and business risks;
• Risk analysis
○ Assess the likelihood and consequences of these risks;
• Risk planning
○ Draw up plans to avoid or minimise the effects of the risk;
• Risk monitoring
○ Monitor the risks throughout the project;
RISK IDENTIFICATION
It’s the first stage of risk management. It’s concerned with discovering possible
risks to the project. Risk identification can be carried out as a team process using
a brainstorming Approach pr may simply be based on experience. There are at
least six types of risk that can arise. It can be understood able through this table.
RISK ANALYSIS
Assess probability and seriousness of each risk. Probability may be very low, low,
moderate, high or very high. Risk effects might be catastrophic, serious,
tolerable or insignificant.
Key staff are ill at critical times in the project. Moderate Serious
• Avoidance strategies
○ The probability that the risk will arise is reduced;
• Minimisation strategies
○ The impact of the risk on the project or product will be reduced;
• Contingency plans
○ If the risk arises, contingency plans are plans to deal with that risk;
Risk Strategy
RISK MONITORING
Risk monitoring involves regularly assessing each of the identified risks to decide
whether or not that risk is becoming more or less probable and whether the
effects of the risks have been changed. This might include following steps.
• Assess each identified risks regularly to decide whether or not it is
becoming less or more probable.
• Also assess whether the effects of the risk have changed.
• Each key risk should be discussed at management progress meetings.