Module - 1 Part 1

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 24

CSE3050 – Software Project

Management

SCHOOL OF CSE & IS,


PRESIDENCY UNIVERSITY,
BANGALORE

1
MODULE 1

Project Management Fundamentals

2
CONTENTS
• Introduction to Software Project Management
- all life cycle activities,
• Project Initiation Management
- scope, objective, size and factors.
• Software Project Effort and Cost Estimation
- COCOMO, artifacts.
• Risk Management
- Perform the risk analysis for the given case study.
• Configuration Management –
- Techniques.
• Project Monitoring and Control
- measuring task, status report, EVM.
• Project Closure
- closure steps

3
INTRODUCTION TO SOFTWARE PROJECT
MANAGEMENT
In this introduction the main questions to be addressed will be:

• What is software project management?

• Is it really different from ‘ordinary’ project management?

• How do you know when a project has been successful?

• For example, do the expectations of the customer/client match


those of the developers?

4
What is management?
• Management is achieving goals in a way that makes the best use of all resources

This involves the following activities:


• Planning – It is the basic function of management. “Planning is deciding in
advance - what to do, when to do & how to do. It bridges the gap from where we
are & where we want to be”. “deciding what is to be done”
• Organizing – It is the process of bringing together physical, financial and human
resources and developing productive relationship amongst them for achievement
of organizational goals. “making arrangements”
• Staffing – It is the function of manning the organization structure and keeping it
manned. Manpower, training“selecting the right people for the job”
• Directing – Supervision, Motivation, Leadership, Communication. “giving
instructions”

5
What is management?
(continued)

• Controlling –The purpose of controlling is to ensure that everything occurs in


conformities with the standards.
• Monitoring – checking on progress

• Innovating – coming up with solutions when problems emerge

• Representing – liaising with clients, users, developers and other stakeholders

6
What is a project?
• A project is a temporary effort to create a unique
product or service. Projects usually include constraints
and risks regarding cost, schedule or performance
outcome.

• A project is Planned set of interrelated tasks to be


executed over a fixed period and within certain cost and
other limitations.

7
What is Project Management?
• Project Management is the discipline of planning,
organizing, motivating, and controlling resources to
achieve specific goals

• Project management is a methodical approach to


planning and guiding project processes from start to
finish.

8
Why Project Management?

• Better control of financial, physical, and human resources


• Improved customer relations
• Shorter development times
• Lower costs
• Higher quality and increased reliability
• Improved productivity
• Better internal coordination

9
Characteristics of projects

• Non-routine
• Planned
• Aiming at a specific target
• Work carried out for a customer
• Involving several specialises
• Made up of several different phases
• Constrained by time and resources
• Large and/or complex

10
Management approaches
• Traditional culture, managers think and employee do what they are
told, the role of the manager in a traditional management model is to
solve problems at the top level
• Quality culture, managers are coaches of the team they do:
- communicate the vision, mission, and goals
- Provide resources
- Remove barriers
- Seek employee input and feedback
- Build trust
- Provide training
- Reward and recognize performance

11
Management Styles

• Situational management, is a method whereby the current state of


the organization determines what operational procedures will be
implemented to achieve desired outcomes. Situational
management emphasizes a very adaptive management style.

• Change management, is a systematic approach to dealing with


change, both from the perspective of an organization and on the
individual level.
To define Change Management, you could say that it is about
managing this transition from the old position to the new one.
Change management has at least three different aspects, including:
adapting to change, controlling change, and implementing change

12
Suggested Skills for Project Managers

• Project managers need a wide variety of skills.


• Comfortable with change
• Understand the organizations they work in
• Able to lead teams to accomplish project goals
• Need both “hard” and “soft” skills
• Hard skills - product knowledge, knowing the
various PM tools and techniques
• Soft skills - being able to work with people

13
Suggested Skills for Project Managers
• Suggested Skills…
• Communication skills: Listens, persuades.
• Organizational skills: Plans, sets goals, analyzes.
• Team-building skills: Shows empathy, motivates,
promotes esprit de corps.
• Leadership skills: Sets examples, provides vision (big
picture), positive, energetic.
• Coping skills: Flexible, creative, patient, persistent.
• Technology skills: Experience, project knowledge.

14
What is Project Management?
• Project Management is the discipline of
• planning,
• organizing,
• motivating, and
• controlling resources to achieve specific goals

• Project management is a methodical approach to


planning and guiding project processes from start to
finish.

15
Activities covered by project management

Feasibility study
Is project technically
feasible and worthwhile
from a business point of
view?
Planning
Only done if project is
feasible
Execution
Implement plan, but
plan may be changed as
we go along

16
Project management life-cycle

1. Initiation
2. Planning
3. Executing
4. Closure

17
Initiation of a project
1. Create an idea
2. Identify the project vision and objectives
3. Define the complete scope of the project
4. List all of the critical project deliverables
5. State the customers and project stakeholders
6. List the key roles and their responsibilities
7. Create an organizational structure for the project
8. Document the overall implementation plan
9. List any risks, issues and assumptions
10. Appoint the project team
11. Set up the project office
12. Perform a phase review

18
Planning of a project

1. Create a Project Plan


2. Create a Resource Plan
3. Create a Financial Plan
4. Create a Quality Plan
5. Create a Communication Plan
6. Create a Risk Plan
7. Contact the Supplies

19
Different types of projects and its life cycle
(construction project)

20
Different types of projects and its life cycle
(pharmaceuticals project)

21
Different types of projects and its life cycle
(pharmaceuticals project)
Pharmaceuticals project
• Discovery and Screening—includes basic and applied research to
identify candidates for preclinical testing.
• Preclinical Development—includes laboratory and animal testing to
determine safety and efficacy as well as preparation and filing of an
Investigational New
Drug (IND) application.
• Registration(s) Workup—includes Clinical Phase I, II, and III tests as
well as preparation and filing of a New Drug Application (NDA).
• Postsubmission Activity—includes additional work as required to
support Food and Drug Administration review of the NDA.

22
Different types of projects and its life cycle
(software project)

23
Different types of projects and its life cycle
(software project)
Proof-of-concept cycle—capture business requirements, define goals
for proof-of-concept, produce conceptual system design, design and
construct the proof-of-concept, produce acceptance test plans,
conduct risk analysis and make recommendations.
• First build cycle—derive system requirements, define goals for first
build, produce logical system design, design and construct the first
build, produce system test plans, evaluate the first build and make
recommendations.
• Second build cycle—derive subsystem requirements, define goals for
second build, produce physical design, construct the second build,
produce system test plans, evaluate the second build and make
recommendations.
• Final cycle—complete unit requirements, final design, construct final
build, perform unit, subsystem, system, and acceptance tests.

24

You might also like