(Software Project Management) Answer Key Q. P. Code: 57826
(Software Project Management) Answer Key Q. P. Code: 57826
Q. P. Code: 57826
(2½ Hours)
[Total Marks: 75]
2
53701 (Software Project Management) Answer Key
Q. P. Code: 57826
f. What do you mean by scope and objective of a project? List the activities involved in
identifying project scope and objective.
Objective
• Define what the project team must achieve for project success
• Outcome of project rather than tasks
• Predetermined results to which effort is directed
Scope
• Defines the boundaries of its application
• Output+outcome+benefit+work required to produce them
Steps involved in identifying project scope and objective are
• Identify objectives and practical measures of the effectiveness in meeting those
objectives
• Establish Project Authority
• Stakeholder analysis-Identify all stakeholders in the project and their interests
• Modify objectives in the light of stakeholder analysis
• Establish methods of communication channels amongst stake holders
The term scrum ceremonies is used to denote the meetings that are mandatorily held during
the duration of a project.
• Sprint Planning
o Team members commit to develop and deliver certain features in the
ensuing sprint
o Product owner works with the team to negotiate which product backlog
item the team should work
o Scrum master has to ensure that the team agrees to realistic goals for a
sprint
• Daily scrum
o Stand-up meeting to review the status of progress achieved and major
issues faced on day-to-day basis
o Scrum master track the progress and helps to address any problems that
need immediate attention
• Sprint review meeting
o Team demonstrates the new functionality developed during the sprint
o Feedback taken –Taken into account in the next sprint or added to product
backlog
b. List the advantages and disadvantages of software prototyping.
3
53701 (Software Project Management) Answer Key
Q. P. Code: 57826
Advantages
• Learning by doing
• Improved communication
• Improved user involvement
• Clarification of partially known requirements
• Demonstation of consistency and completeness of specification
• Reduces the need for documentation
• Reduces maintenance costs
• Feature constraint
• Production of expected results
Disadvantages
• Users may misunderstand the role of the prototype
• Lack of project standards possible
• Lack of project control
• Additional expense of building prototype
• Machine efficiency
• Close proximity of developers
c. Explain the five major components of Albrecht Function Point Analysis.
• External input (EI) types – input transactions which update internal computer files
• External output (EO) types – transactions which extract and display data from
internal computer files. Generally involves creating reports.
• External inquiry (EQ) types – user initiated transactions which provide information
but do not update computer files. Normally the user inputs some data that guides
the system to the information the user needs
• Logical interface file (LIF) types – equates roughly to a data store in systems
analysis terms. Created and accessed by the target system
• External interface file types (EIF) – where data is retrieved from a data store which
is actually maintained by a different application
d. What is effort multipliers in COCOMO II model? List the effort multipliers used at
early design.
In COCOMO II the effort multipliers adjust the estimate to take account of productivity
factors. Each of these multipliers is given a rating of very low, low, nominal, high or
very high .Each rating for each em has an associated value.A value grater than 1
increases development effort and value less than 1 decreases it.The nominal value
means that the multiplier has no effect.The multipliers relevant to early design are
• Product reliability and complexity
• Required reusability
• Platform difficulty
• Personnel capability
• Personal experience
• Facilities available
• Schedule pressure
e. Explain eight core principles of Dynamic Systems Development Method.
• Focus on the business need
• Deliver on Time
• Collaborate
• Never Compromise Quality
• Build Incrementally from Firm Foundations
4
53701 (Software Project Management) Answer Key
Q. P. Code: 57826
• Develop Iteratively
• Communicate Continuously and Clearly
• Demonstrate Control
f. State Capers Jones rules of thumb for software estimation.
• Rule 1: SLOC-function point equivalence:
o One function point = 125 SLOC for C programs.
• Rule 2: Project duration estimation:
o Function points raised to the power 0.4 predicts the approximate
development time in calendar months.
• Rule 3: Rate of requirements creep:
o User requirements creep in at an average rate of 2% per month from the
design through coding phases
• Rule 4: Defect removal efficiency:
o Each software review, inspection, or test step will find and remove 30% of
the bugs that are present.
• Rule 5: Project manpower estimation:
o The size of the software (in function points) divided by 150 predicts the
approximate number of personnel required for developing the application
• Rule 6: Number of personnel for maintenance
o Function points divided by 500 predicts the approximate number of
personnel required for regular maintenance activities.
• Rule 7: Software development effort estimation:
o The approximate number of staff months of effort required to develop a
software is given by the software development time multiplied with the
number of personnel required
3. Attempt any three of the following: 15
a. With the help of example explain forward pass and backward pass to calculate activity
duration in network diagram.
The forward pass rule:the earliest start date for an activity is the earliest finish date for
the preceding activity.Where there is more than one immediately preceding activity
take the latest of the earliest finish dates for those activities.
The backward pass rule:the latest finish date for an activity is the latest start date for
the activity that commences immediately that activity is complete.Where more than
one activity can commence take the earliest of the latest start dates for those activities
(Any example)
• Critical path is the path through network with zero floats.Any delay in an activity
on this path will delay whole project
• Float is the measure of how much the start or completion of an activity may be
delayed without affecting the end date of the project. Float=0 implies that any delay
in carrying out the activity will delay the completion date of the project as a whole
• Free Float is time by which an activity may be delayed without affecting any
subsequent activities.It is the difference between the earliest completion date for the
activity and earliest start date of the succeeding activity
• Interfering float is how much the activity may be delayed without delaying the
project end date-eventhough it will delay the start of subsequent activities
• Interfering float = total float – free float
5
53701 (Software Project Management) Answer Key
Q. P. Code: 57826
• Hammock activities are activities which have zero duration and to start at the same
time as the first hammocked activity and to end at the same time as the last one.
They are used to represent overhead costs or other resources that will be incured or
used at a constant rate over the duration of a set of activities
c. Explain Boehm’s top ten software project risks and the different strategies for
reducing it.
Risk Risk reduction techniques
Personnel shortfalls Staffing with top talent; job matching; teambuilding;
training and career development; early scheduling of key
personnel
Unrealistic time and Multiple estimation techniques; design to cost;
cost estimates incremental development; recording and analysis of past
projects; standardization of methods
Developing the wrong Improved software evaluation; formal specification
software functions methods; user surveys; prototyping; early user manuals
Developing the wrong Prototyping; task analysis; user involvement
user interface
Gold plating Requirements scrubbing, prototyping,
design to cost
Late changes to Change control, incremental development
requirements
Shortfalls in Benchmarking, inspections, formal specifications,
externally supplied contractual agreements, quality controls
components
Shortfalls in Quality assurance procedures, competitive design etc
externally performed
tasks
Real time Simulation, prototyping, tuning
performance problems
Development Technical analysis, cost-benefit analysis, prototyping ,
technically too training
difficult
d. Write short note on Project Evaluation and Review Technique.
• PERT is a method to evaluate and estimate the time required to complete a task
within deadlines.
• PERT requires three estimates
o Most likely time (m) the time we would expect the task to take normally
o Optimistic time (a) the shortest time that could be realistically be expected
o Pessimistic (b) worst possible time
• ‘expected time’ te = (a + 4m +b) / 6
• ‘activity standard deviation’ S = (b-a)/6
• z=(T- te)/s where te is the expected date and T is the target date
• The PERT technique uses the following three step method for calculating the
probability of meeting or missing a target date
6
53701 (Software Project Management) Answer Key
Q. P. Code: 57826
o Calculate the standard deviation of each project event
o Calculate the z value for each event that has a target date
o Convert z values to a probabilities
e. Explain the different categories of cost incurred in a software project.
Cost are categorized as
• Staff costs
o Includes salary, social security contributions by the employer, holiday
pay etc.
o Timesheets are often used to record actual hours spent on each project by
an individual
o One issue can be how time when a staff member is allocated and available
to the project, but is not actually working on the project, is dealt with.
• Overheads
o Space rental, interest charges,service charges etc.
o Some overheads might be directly attributable to the project; in other cases
a percentage of departmental overheads may be allocated to project costs
• Usage charges
o some charges can be on a ‘pay as you go’ basis e.g. telephone charges,
postage, car mileage – at the planning stage an estimate of these may have
to be made
f. What is resource smoothing? Explain two different ways of prioritizing activities for
resource allocation.
Resource smoothing is a technique that adjusts the activities of a schedule model such
that the requirements for resources on the project do not exceed certain predefined
resource limits.
There are two main ways of prioritizing activities:
• Total float priority – those with the smallest float have the highest priority
• Ordered list priority – this takes account of the duration of the activity as well
as the float .Burman’s priority list give priority to:
o Shortest critical activities
o Other critical activities
o Shortest non-critical activities
o Non-critical activities with least float
o Non-critical activities
• Planning
o Author submits work product
7
53701 (Software Project Management) Answer Key
Q. P. Code: 57826
o Project manager nominates moderator
• Preparation
o Moderator convenes a brief preparation meeting
o Copies of Work product distributed
o Author presents an overview
o Moderator highlights objective
o Individual observations in review log
• Review Meeting
o Reviewers give their comments
o Moderator ensures that discussion is focussed and productive
o Recorder scribes all the defects
• Rework
o Author carry out necessary modifications
o Corrected work product is circulated among team members
o Final summary report of the review is prepared
10
53701 (Software Project Management) Answer Key
Q. P. Code: 57826
Level 5 (Optimizing)
• Statistics collected from process and product measurements are analyzed:
– Continuous process improvement based on the measurements.
• Lessons learned from specific projects incorporated into the process
d. What is reliability growth model? Explain any two reliability growth models.
• The reliability of a software product essentially denotes its trustworthiness or
dependability.
• A reliability growth model (RGM) models how the reliability of a software
product improves as failures are reported and bugs are corrected.
– An RGM can be used to determine when during the testing phase a given
reliability level will be attained, so that testing can be stopped
• Jelinski and Moranda Model
– Step function model where it is assumed that the reliability increases by a
constant increment each time an error is detected and repaired
– All errors contribute equally to reliability growth
– Instantaneous failure rate (hazard rate) ,
– Z(t)=K(N-i) where K is a constsnt ,N is the total number of errors in the
program and t is any time between the ith and (i+1)th failure
• Littlewood and Verall’s Model
– Negative reliability growth to reflect the fact that when a repair is carried
out,it may introduce additional errors
– As errors are repaired ,the average improvement to the product reliability
per repair decreases
– Error’s contribution to reliability improvement to be an independent
random variable using Gamma distribution
– Error corrections with large contributions to reliability growth are removed
first
• Goel-Okutomo Model
– Execution time between failures are exponentially distributed
– Cumulative number failures at any time can e given in terms of μ(t) ,the
expected value of failures between t and t+Δt
– Number of failures at time t can be given by
– μ(t)=N(1-e-bt) N=no. of defects in code and b is the rate at which the
failurre rate decreases
(Explain any two)
e. What are the steps of conducting a post implementation project review?
• Conduct project survey-The information is collected through a set of questionnaire
that can bring out the important process and management issues that have a strong
bearing on the success or failure of the project.
• Collect objective information
– Post-mortem review --Collect project metrices like cost metrices,schedule
metrices and quality metrices
– Quantitative assessment
• Hold a debriefing meeting-To gain consensus on what was successful and what
was not and identify the best practices and lessons learned.
• Final project review-Addresses various issues arising out of project planning and
tracking, results of various phases ,risk management, configuration management
and quality management.Guided by the information collected in debriefing
meeting ,the project leaders determine the focus of review discusiion only on
relevant topics.
• Prepare post-implementation review report.
• Publish the report.
11
53701 (Software Project Management) Answer Key
Q. P. Code: 57826
f. Explain the different reason for which a project may need to be terminated.
Two reasons for closing a project are
• All project goals have been successfully accomplished
• Project is unlikely to achieve its stated objectives and has to be prematurely
terminated
The reasons for prematurely terminating a project arre
• Lack of resources Eg.Change in top management
• Changed business need of the customer
• Perceived benefits accruing from the project no longer remain valid
Eg.Competing products
• Changes to the regulatory policies
• Key technologies used in the project becoming obsolete during project execution
• Risks have become unacceptably high
o Eg. Unsettling company’s financial soundness,inviting negative publicity
_____________________________
12