1.

Explain various phases and paths of So6ware Project Life Cycle

Phases (12 Marks)

1. ConceptualizaDon
2. Planning
3. ExecuDon
4. TerminaDon
Paths (8 Marks)
5. S shape
6. J Shape

2. Explain various criteria’s for Project ClassificaDon and list various types of
classified Projects

Criteria’s
1. Nature of Work
2. CompleDon Time
3. Cost
4. Level of Risk
5. Mode of operaDon
Types of Classified Projects
1. Industrial / Commercial Projects
a. Demand based projects
b. Resource / Supply based projects
2. Development Projects
3. Explain the flow of acDviDes involved in project management with neat sketch
4. JusDfy the need of conducDng OpDon analysis and explain the OpDons
Analysis Methodology with neat sketch
5. How to manage the Project Cost effecDvely? Explain the project Cost
Management Processes with an explanaDon for the need of Por]olio
Management

- Basic Principles of Cost Management (3 Marks)

o Profits
o Profit margin
o Life Cycle CosDng
o Cash Flow Analysis
- Performance Measurement Analysis (3 Marks)
o Earned Value Management
o Rate of Performance
o EsDmate at CompleDon
- Benefits of Por]olio management (3 Marks)
6. Write Short notes on Algorithmic methods in So6ware Cost EsDmaDon and
explain each with short notes
Algorithmic Methods
1. Cost Factors
a. Product Factors
b. Computer Factors
c. Personnel Factors
d. Project Factors
2. Linear Models

3. MulDplicaDve Models

4. Power FuncDon Models

Effort = a x Sb
a. COCOMO Models (basic, intermediate and detailed, COCOMO II)
b. Putnam’s Model and SLIM
So6ware EquaDon. S = E x (Effort)1/3 td 3
Effort = D0 x 3 td 3
Combining Effort with S
Effort = (D04/7 x E-9/7) x S9/7 and
Td = (D0-1/7 x E-3/7) x S3/7
5. Model calibraDon using Linear Regression ( Y = A + b x X)
6. Discrete Models
7. Other Models (Price-S, So6Cost)
7. Formulate the steps in Network Analysis in PERT

8. Discuss about various project roles, promoter roles and their

responsibiliDes in Project management. Discuss about various associaDons
in OrganizaDonal structures

- Management Roles
- Development roles
- Cross funcDonal roles
- Consultant Roles
- Promoter Roles
o Power Promotor
o Knowledge Promotor
o Process Promotor
- AssociaDons in Org. structures
o ReporDng AssociaDon
o Decision AssociaDon
o CommunicaDon AssociaDon
- Management Structures
o Hierarchical structures
o Project based structures

9. Narrate in detail about Project management Emphasis based on a

standard 30-day sprint

- DefiniDons for: Scrum, Scrum Master, Sprint, Daily Scrum

- Product backlog for planning
- Scrum and scalability
- Scrum-Queues
- Scrum-management
- Core Roles [Product owner, Development team, Scrum master]
- Sprint {completes sprints]

10. List the various roles in Scrum and explain their responsibiliDes in detail
with diagram. Explain about various terminologies used in scrum with
definiDon.

Scrum Roles: (10)

1. ScrumMaster
2. Product Owner
3. Development Team
Terminologies in SCRUM (10)
4. Story
5. Tasks
6. DefiniDon of Done (DoD)
7. Velocity
8. Impediment
11. What are the best pracDces in scrum? Explain each with their purpose.
1. Adhere to agile scrum ceremonies
2. Get scrum roles idenDfied quickly
3. Make sure to prioriDze user stories before Your Project gets started
4. Focus the daily stand up for a more efficient workflow
5. Run effecDve sprint RetrospecDves MeeDngs
6. Use an agile scrum board to make organizaDon a priority

12. How to control various versions of source codes using DevOps? List down
their benefits and various tools for version control. Explain how build
automaDons in DevOps funcDoning and list its benefits.

- Source Code management definiDon

- Version Control vs source control
- Benefits of Version control
- Version control tools [GitHub, GitLab, BitBucket, Perforce, Apache
Subversion, Mercurial]
- Build AutomaDon in DevOps
- Role of ConDnuous IntegraDon
- Benefits of Build AutomaDon
1. Increases ProducDvity
2. Accelerates Delivery
3. Improves Quality
4. Maintains a Complete History
5. Saves Time and Money
13.Write short notes on Other Agile models
- XP
- FDD
- DSDM
- Crystal

14. Explain software development process

The process of software development services in India goes through a
series of stages in step wise fashion that almost every developing
company follows.
Known as the ‘software development life cycle,’ these six
steps include planning, analysis, design, development &
implementation, testing & deployment and maintenance.
 ∙ Planning: Without the perfect plan, calculating the strengths
and weaknesses of the project, development of software is
meaningless. ∙ Analysis: This step is about analysing the
performance of the software at various stages and making notes on
additional requirements. Analysis is very important to proceed
further to the next step.
∙ Design: Once the analysis is complete, the step of designing
takes over, which is basically building the architecture of the
project. ∙ Development & Implementation: The actual task of
developing the software starts here with data recording going on in
the background.
∙ Testing: The testing stage assesses the software for errors
and documents bugs if there are any.
∙ Maintenance: Once the software passes through all the
stages without any issues, it is to undergo a maintenance process
wherein it will be maintained and upgraded from time to time to
adapt to changes.

15. Explain Risk Management process.

There are following activities involved in risk management process:

∙ Identification - Make note of all possible risks, which may occur in

the project.
∙ Categorize - Categorize known risks into high, medium and low risk
intensity as per their possible impact on the project.
∙ Manage - Analyse the probability of occurrence of risks at
various phases. Make plan to avoid or face risks. Attempt to
minimize their side-effects.
Monitor - Closely monitor the potential risks and their
early symptoms. Also monitor the effects of steps taken to mitigate
or avoid them.

16. Briefly explain the concept of Management tools.

The risk and uncertainty rises multifold with respect to the size
of the project, even when the project is developed according to set
methodologies.
There are tools available, which aid for effective
project management. A few are described -
∙ Gantt Chart
Gantt charts was devised by Henry Gantt (1917). It represents
project schedule with respect to time periods.
It is a horizontal bar chart with bars representing activities and
time scheduled for the project activities.
∙ PERT Chart
PERT (Program Evaluation & Review Technique) chart is a
tool that depicts project as network diagram.
It is capable of graphically representing main events of project
in both parallel and consecutive way. Events, which occur one
after another, show dependency of the later event over the previous
one.

Events are shown as numbered nodes. They are connected by

labeled arrows depicting sequence of tasks in the project.
∙ Resource Histogram
This is a graphical tool that contains bar or chart
representing number of resources (usually skilled staff) required over
time for a project event (or phase).
Resource Histogram is an effective tool for staff planning
and coordination.
∙ Critical Path Analysis
This tools is useful in recognizing interdependent tasks in the project.
It also helps to find out the shortest path or critical path to complete the
project successfully.
 Like PERT diagram, each event is allotted a specific time frame.
This tool shows dependency of event assuming an event can proceed to
next only if the previous one is completed.
The events are arranged according to their earliest possible start
time. Path between start and end node is critical path which cannot be
further reduced and all events require to be executed in same order.

17. Briefly explain about top-down and bottom-up approach.

Top Down Design

Top-down design takes the whole software system as one entity and
then decomposes it to achieve more than one sub-system or component based
on some characteristics.
Each sub-system or component is then treated as a system
and decomposed further. This process keeps on running until the lowest level
of system in the top-down hierarchy is achieved.
Top-down design starts with a generalized model of system and keeps
on defining the more specific part of it.
When all components are composed the whole system comes
into existence.
Top-down design is more suitable when the software solution needs to
be designed from scratch and specific details are unknown.
Bottom-up Design
The bottom up design model starts with most specific and
basic components.
It proceeds with composing higher level of components by using basic
or lower level components. It keeps creating higher level components until
the desired system is not evolved as one single component.
With each higher level, the amount of abstraction is increased.
Bottom-up strategy is more suitable when a system needs to be
created from some existing system, where the basic primitives can be used
in the newer system.
Both, top-down and bottom-up approaches are not practical
individually. Instead, a good combination of both is used.
 18. Discuss about project planning activities.

∙ Determine the project requirements

∙ Determine the condition of the source files and
databases ∙ Determine or revise the cost estimates
∙ Revise the risk assessment
∙ Identify critical success factors
∙ Prepare the project charter
∙ Create a high-level project plan
∙ Kick off the project

Determine the project requirements. You may have already prepared

the objectives for the project and some high-level requirements for the
proposed scope during Step 1, Business Case Assessment.
Determine the condition of the source files and databases. You can
neither complete the project schedule nor commit to a delivery date without
a good understanding of the condition of the source files and databases.
Determine or revise the cost estimates. Detailed cost estimates must
include hardware and network costs as well as purchase prices and annual
maintenance fees for tools.

Revise the risk assessment. Review and revise the risk assessment
performed during Step 1, Business Case Assessment.

Identify critical success factors. A critical success factor is a condition

that must exist for the project to have a high chance for success.

Prepare the project charter. The project charter is similar to a

scope agreement, a document of understanding, or a statement of work.

Create a high-level project plan. Project plans are usually presented in

the form of a Gantt chart that shows activities, tasks, resources, dependencies,
and effort mapped out on a calendar.
Kick off the project. Once you have planned the project, assigned the resources,
and scheduled the training, you are ready to kick off the project.

19. Explain project process.

∙ Project Initiation
∙ Project Planning
∙ Project Execution
 ∙ Control and Validation

Project Initiation
Project initiation is the starting point of any project. In this process,
all the activities related to winning a project takes place. Usually, the main
activity of this phase is the pre-sale.
During the pre-sale period, the service provider proves the eligibility
and ability of completing the project to the client and eventually wins the
business.
During the requirements gathering activity, all the client requirements
are gathered and analysed for implementation.
Project Planning
Project planning is one of the main project management processes.
If the project management team gets this step wrong, there could
be heavy negative consequences during the next phases of the project.
In this process, the project plan is derived in order to address the
project requirements such as, requirements scope, budget and timelines.
Once the project plan is derived, then the project schedule is developed.

Project Execution
During the project execution, there are many reporting activities to
be done. The senior management of the company will require daily or
weekly status updates on the project progress.
Control and Validation
During the project life cycle, the project activities should be
thoroughly controlled and validated.
The controlling can be mainly done by adhering to the initial
protocols such as project plan, quality assurance test plan and
communication plan for the project.
Closeout and Evaluation
Once all the project requirements are achieved, it is time to hand over
the implemented system and closeout the project.
If the project deliveries are in par with the acceptance criteria defined
by the client, the project will be duly accepted and paid by the customer.
Once the project closeout takes place, it is time to evaluate the entire project.
20. Write down the steps for project planning.

Step 0: Select the project

Step 1: Identify project scope and objectives
Step 2: Identify the project infrastructure
Step 3: Analyse project characteristics
Step 4: Identify project products and activities
Step 5: Estimate Effort for each activity
Step 6: Identify activity risks
Step 7: Allocate resources
Step 8: Review/Publicize plan
Step 9&10: Execute plan/lower level planning.

21. Briefly discuss about project tracking.

Project Tracking refers to the management of projects, which includes but

is not limited to measuring and reporting the status of milestones, tasks
and activities required in achieving the pre-defined project results.

Project Tracking can also refer to Project Management software,

which automates the tracking of tasks, assignments, events and activities
related to the project.

A project is a one-time effort to accomplish an explicit objective by

a specific time.
Each project is unique although similar projects may exist. Every
project has a definite beginning and a definite ending. Project management is
the process of overseeing planning, organizing, scheduling, leading,
communicating and controlling of activities to achieve the pre-defined
outcome on time and within budget.

One of the key components of Project Management is controlling.

There are various tools and techniques available to manage and

track projects.

Project management software is frequently used by companies to assist

in managing the initiation, execution, tracking and closing of projects.
 By automating many of the project management tasks such as
scheduling, time and expense reporting, and charge back reporting, project
managers have access to real-time analytics, which ensure the efficient
management of resource allocation and utilization.

Automation also assists project managers in consistent project

execution, improved resource utilization and reduced resource gaps,
operational efficiency and it facilitates communication and decision-making.