0% found this document useful (0 votes)
23 views20 pages

Project Management

software engineer project managment slide

Uploaded by

Awais Javed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
23 views20 pages

Project Management

software engineer project managment slide

Uploaded by

Awais Javed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 20

PROJECT

MANAGEMENT
What is a project?
A unique undertaking composed of interrelated
activities which has a well defined beginning and end,
often involving staff from cross functional groups
that operates under specific constraints of resources,
schedule and requirements.
Examples???
What is Project Management?
A set of skills, methods of planning, organizing and
managing a project from beginning to its
successful completion.

PROJECT MANAGER
A role responsible for leading and coordinating the project
effort from inception to its successful completion.
What is an IT Project?
IT projects can be any type of project that deals with
IT Infrastructure
Information system
Software development
Web development
What is ITPM?
ITPM is the sub discipline of project
management in which IT projects are planned,
monitored, executed, controlled, organized and
supervised.
The resultant product is effective and efficient.
What are the typical IT Project
management activities?
The early stages of any IT project management efforts involves
assessing, prioritizing and planning IT projects.
This includes determining the scope of work and available resources,
assigning resources and setting expectations for project milestone.
This also includes coordinating the project’s workload, managing the
actual work, facilitating communication between team members,
producing deliverables & measuring product’s result.
What is an ITPM Methodology?
IT project methodologies are all about
specifying the best way to initiate, plan and
execute IT projects.
Waterfall and agile are the two most prominent
methodologies used in IT project development.
4 P’s
ITPM or SPM is all about 4 P’s:
People
Process
Product
Project
People…
The most important factor in success of software project.
“Companies That sensibly manage their investment in
people will succeed in the long run” .
Cultivation of motivated and highly skilled software people
has always been important for software organizations.
The “people-factor” is so important that has developed
People Management Capability Maturity Model (PM-CMM).
PM-CMM
◦In simple words - to enhance the people’s
capabilities through personnel development
Organizations that achieve high levels of
maturity in PM-CMM have a higher likelihood of
implementing effective software engineering
practices
CM-PMM(cntd)
Key Practice Areas of PM-CMM
◦Recruiting
◦Selection
◦Performance Management
◦Training
◦Compensation
◦Career development
◦Organization and work design
◦Team/culture development
People Involved in Software Process
The Stakeholders
◦They can be categorized into one of the following
◦Senior Managers
◦ they define business issues that often have significant influence on business
◦Project (technical) managers
◦ they must plan, motivate, organize and control the practitioners who do software work
◦Practitioners
◦ They deliver the technical skills necessary to engineer a product or application
◦Customers
◦ They specify the requirements for the software to be engineered
◦End Users
◦ They interact with the software after it is released for production use
Product
The product and the problem it is intended to solve must be
examined at very beginning of the software project.
The scope of product must be established and bounded.
◦Bounded scope means
◦establishing quantitative data like no. of simultaneous users, max. allowable
response time.
etc.
◦Constraints and limitations
Software Scope
Scope is defined by
◦ Context (1st step in scope determination)
◦Functional location of the software product into a large system, product or business context
◦Constraints involved
◦ Information Objectives (2nd step)
◦What data objects are required as i/p or o/p
◦ Function and Performance (3rd step)
◦What function does the software system perform on i/p to produce o/p
◦What level of performance is required
Process
These characterize a software process and are applicable to all
software projects
◦Communication
◦Planning
◦Modeling
◦Construction
◦Deployment
These are applied to software engineering work tasks (e.g., different
product functions)
Process Models
Different process models:
◦Linear sequential, Prototyping, RAD, Spiral, Formal …
Project manager must decide about which model to use depending
on
◦Customers who have requested the product
◦People who would work on project
◦Product characteristics
◦Project environment
Project planning begins once model is selected
Process Decomposition
The way a process is decomposed depends on
project complexity
Decomposition involves outlining of work tasks
involved in each process framework activity
Projec

 Product scope is poorly defined
t
Software people don’t understand customer needs

 Changes are managed poorly


 The chosen technology changes
 Business needs change
 Deadlines are unrealistic
 Users are resistant
 Sponsorship is lost
 Team lacks skills
 Managers avoid best practices
How to avoid problems?
Start on the right foot
◦Involves detailed understanding of project
◦setting realistic objectives & expectations
◦Selecting the right team
◦Facilitating the team

Maintain Momentum
◦Provide incentives
◦Reduce bureaucracy and give autonomy to team members but with supervision

Track Progress
◦Assess progress as work products are produced
How to avoid problems?
Make smart decisions
◦When possible, use existing software components / COTS software
◦Choose standard approaches and keep it simple
◦Avoid risks and allocate more time than needed for complex/risky tasks

Conduct a postmortem analysis


◦Compare planned and actual schedule
◦Collect and analyze project metrics (standards)
◦Get feedback from team and customers
◦Establish record of lessons learnt for each project

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy