Project Management Software Projects – factors that influence results: –size –delivery deadline –budgets and costs –application domain –technology to be.

Slides:



Advertisements
Similar presentations
Project Management M Taimoor Khan
Advertisements

1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Chapter 3 -- R. A. Volz -- Assistance - David Mar November 2, Project Management Concepts zWhy is project management important? yCost xDod already.
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
Chapter 21 Project Management Concepts
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
‘all aspects of software production’ - Software engineering is not just concerned with the technical processes of software development but also with activities.
Project Management Concepts
1 Chapter 3 Project Management. 2 The 4 P’s  People — the most important element of a successful project  Product — the software to be built  Process.
1 Project Management CIS 375 Bruce R. Maxim UM-Dearborn.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Project Management Instructor: Dr. Jerry Gao. Project Management Jerry Gao, Ph.D. Jan The Management Spectrum - People - The Players - Team Leaders.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Four P’s People – software engineers People – software engineers Product – software to be produced Product – software to be produced Process – framework.
1 Chapter 3 Project Management. 2 Software project management  Concerned with activities involved in ensuring that software is delivered on time and.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Chapter 3: Project Management Omar Meqdadi SE 2730 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
1 Software Process Models-ii Presented By; Mehwish Shafiq.
Chapter 3 Project Management Concepts
1 Chapter 3 Project Management. 2 Project Management Concerns staffing? cost estimation? project scheduling? project monitoring? other resources? customer.
Project Scheduling 1. Why Are Projects Late? An unrealistic deadline established by someone outside the software development group Changing customer requirements.
Lecture 18: Chapter 27 Project Scheduling
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Software Project Management By Deepika Chaudhary.
Project Management Concepts 1. What is Project Management? Project management is the process of the application of knowledge, skills, tools, and techniques.
Lecture 16: Chapter 24 Project Management Concepts
PROJECT MANAGEMENT CONCEPTS. The Management Spectrum The key concept behind the an effective software engineering process is the management spectrum.
Software Project Management Lecture # 2. Outline The 4 Ps in Project Management Detailed Insight of each P.
Project Management Concepts By: Sohaib Ejaz Lecturer,UoS.
Chapter : Project Management Concept
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Software Project Management Lecture # 2 Originally shared for: mashhoood.webs.com.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Dr. Rob Hasker. Avoiding failure  Standish Report, 2014 Standish Report 31% projects cancelled before completion 53% projects ~190% of original estimate.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Management of Software1 Advanced Software Engineering COM360 University of Sunderland © 1998.
Chapter : Project Management Concept
Project Management Concepts zWhy is project management important? yCost xDod already spending $30 billion annually on software in late 80’s xThe US spent.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Monitoring Risk Factors General attitude of team members based on project pressures The degree to which the team is jelled Interpersonal relationships.
Project Management Why do projects fail? Technical Reasons
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
INTRODUCTION: Project management involves the planning, monitoring, and control of the people, process, and events that occur as – software evolves from.
PROJECT MANAGEMENT Software Engineering CSE
1 Supplementary Slides for Software Engineering: A Practitioner's Approach, 6/e Part 4 Supplementary Slides for Software Engineering: A Practitioner's.
Software Project Management
Chapter 34 Project Scheduling
The importance of project management
CMPE 412 Software Engineering
Chapter 3 Project Management
For University Use Only
Software Project Management
Chapter 21 Project Management Concepts
Software engineering Lecture 21.
Software Project Management
Project Management.
For University Use Only
Mumtaz Ali Rajput +92 – SOFTWARE PROJECTMANAGMENT– WEEK 3 Mumtaz Ali Rajput +92 – 301-
Chapter 3 Project Management
SE 3800 Note 10 Project Management
LEADERSHIP Leadership is the manager’s ability to influence subordinates to work towards group goals with confidence. Leadership style is the manner and.
Software Engineering Project Management.
Chapter 27 Project Scheduling
Chapter 34 Project Scheduling
Chapter 21 Project Management Concepts
Presentation transcript:

Project Management Software Projects – factors that influence results: –size –delivery deadline –budgets and costs –application domain –technology to be implemented –system constraints –user requirements –available resources

Software Engineering II Lecture 6 Fakhar Lodhi

Project Management Concerns

Scope ScheduleResources

Why Projects Fail? changing customer requirementschanging customer requirements ambiguous/incomplete requirementsambiguous/incomplete requirements an unrealistic deadline is establishedan unrealistic deadline is established an honest underestimate of effortan honest underestimate of effort predictable and/or unpredictable riskspredictable and/or unpredictable risks technical difficultiestechnical difficulties miscommunication among project staffmiscommunication among project staff failure in project managementfailure in project management

Team Leaders MOI model of leadership - Weinberg –Motivation: The ability to encourage technical people to produce their best –Organization: The ability to mold the existing processes (or invent new ones) that will enable the initial concept to be translated into a final product –Idea or innovation: The ability to encourage people to create and feel creative

The Software Team Organization Democratic decentralized (DD) Controlled decentralized (CD) Controlled centralized (CC)

The Software Team Organization Democratic decentralized (DD) –No permanent leader –Task coordinators are appointed for short duration –Decisions on problems and approach are made by group consensus –Communication among team is horizontal

The Software Team Organization Controlled decentralized (CD) –Defined leader who coordinates specific tasks –Problem solving remains a group activity –Communication among subgroups and individuals is horizontal. Vertical communication along the control hierarchy also occurs.

The Software Team Organization Controlled centralized (CC) –Top level problem solving and internal team coordination are managed by the team leader –Communication between the leader and team members is vertical.

Summary of Today’s Lecture