Organizations, Constraints & Projects

Slides:



Advertisements
Similar presentations
Project Management Basics. By the time we are done…. Attendees should understand –Why project management is worth caring about –What is and isn’t a project.
Advertisements

Computer Engineering 203 R Smith Project Tracking 12/ Project Tracking Why do we want to track a project? What is the projects MOV? – Why is tracking.
Applied Software Project Management Andrew Stellman & Jennifer Greenehttp:// Applied Software Project Management Introduction.
Applied Software Project Management INTRODUCTION Applied Software Project Management 1 5/20/2015.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Why Software.
IT Project Management, Third Edition Chapter 11 Chapter 1: Introduction to Project Management.
This work is licensed under a Creative Commons Attribution 3.0 Unported LicenseCreative Commons Attribution 3.0 Unported License (CC-BY). Project Management.
Project management INTRODUCTION. Information Technology Project Management, Fourth Edition 2 IT projects have a terrible track record. A 1995 Standish.
Leadership & Team Building
1 Chapter 1: Introduction to Project Management. 2 Learning Objectives Understand the growing need for better project management, especially for information.
Resources Performance time. resources Performance time 2.
1. 2 IMPORTANCE OF MANAGEMENT Some organizations have begun to ask their contractors to provide only project managers who have been certified as professionals.
25 PROJECT MANAGEMENT TIPS American Management Association.
DON F. ERWIN BUFFALO STATE COLLEGE BUFFALO, NEW YORK, USA PART 1 – PROJECT MANAGEMENT BASICS Software Project Management.
Metrics 2.0 Rick A. Morris, PMP, OPM3, MCITP
Project Charters Module 3
AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.
Project Cost Management
SE is not like other projects. l The project is intangible. l There is no standardized solution process. l New projects may have little or no relationship.
Management 538: Teams and Projects Session 6: Basics of Project Management.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
CS3100 Software Project Management: Monitoring & Control 1 Software Project Management Week 10: Project Monitoring & control Ian Blackman.
Copyright 2012 John Wiley & Sons, Inc. Chapter 3 The Project Manager.
Planning Extreme programming
1 TenStep Project Management Process ™ PM00.5 PM00.5 Project Management Preparation for Success * Manage Scope *
Practical IT Research that Drives Measurable Results Establish an Effective IT Steering Committee.
PM is a Unique Skill Set Much of its knowledge is particular to the requirements of PM; for example, critical path analysis and work breakdown structures.
Section 14.1 Teamwork Back to Table of Contents. Chapter 14 Teamwork and LeadershipSucceeding in the World of Work Teamwork 14.1 WHAT YOU’LL LEARN How.
Resource Management.
Project Management Business Management.
Organisational Structures
Agile Scrum Management
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Project Integration Management
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Chapter 7: Project Cost Management
The Capacity Constraint
The value of a project-oriented approach to IT and how we do it in IBM
By Kean Tak, MSc, Lecturer at RUPP
Decision Making Process
IFSM 438 Competitive Success/snaptutorial.com
IFSM 438 Education for Service-- snaptutorial.com
IFSM 438 Teaching Effectively-- snaptutorial.com
IFSM 438 Inspiring Innovation-- snaptutorial.com
Project Organization Chart Roles & Responsibilities Matrix
Theory, Tools, and Obstacles
Part II Project Planning © 2012 John Wiley & Sons Inc.
Successful Project Management
FOUNDATIONAL CONCEPTS
Lecture # 3 Software Development Project Management
SEM Operations PE - Utilize project-management skills to improve workflow and minimize costs PI – Develop project plan.
Software Testing and Maintenance Maintenance and Evolution Overview
Tools for Visualization
Partnered or Group Projects
How to keep your Enterprise GIS Project on Track
Welcome W 15 Introduction to Engineering Design II (IE 202)
Applied Software Project Management
Intro to Business Management
Delegation Skills.
Software Project Management
Project Management.
Project Overview.
Employee Task Management Software
Schedule (Major Deliverables and Milestones)
SEM Operations PE - Utilize project-management skills to improve workflow and minimize costs PI – Develop project plan.
Chapter 13: Project Stakeholder Management
Early warning indicators
This is a template for a presentation that you can use to introduce your team to Harvest. You can customize the content of the slides. You’ll want to pay.
Presentation transcript:

Organizations, Constraints & Projects Lecture # 2 Software Development Project Management

Type of Organization Functional Organization Full authority to Functional Managers. Project managers don’t have the authority to make major decisions on projects. The teams working on the project don’t reply directly to the PM. The teams are in departments, and the PM needs to “borrow” them for the project. PMs don’t set the budget. PM need to clear major decisions with department managers PMs spend half their time doing admin tasks. All of the project work typically happens within a particular department, and that department’s manager is completely in charge of everything. PM are assistants to FM in getting the work done. Lecture # 2

Type of Organization (cntd.) Matrix Organization Weak Matrix PMs have some authority but they aren’t in charge of the resources on a project. Major decisions still need to be made with the FM’s cooperation or approval. Project expeditors can work in weak matrix organizations. Project coordinators are like expeditors, except that coordinators typically report to higher-level managers and have some decision-making ability. Expeditors have no authority at all Lecture # 2

Type of Organization (cntd.) Matrix Organization (cntd.) Balanced Matrix Shared authority between PM and FM. PMs run their people-management decisions by the FM, but the FM runs his project decisions by the PM, too. Folks who work in a balanced matrix organization report to a PM AND a FM equally Lecture # 2

Type of Organization (cntd.) Matrix Organization (cntd.) Strong Matrix PM have more authority than FM, but the team still reports to both managers. The team might be judged based on performance on their projects, as well as on their functional expertise. In a strong matrix, delivery of the project is most important. Lecture # 2

Type of Organization (cntd.) Projectized Organization Full authority to PM. Teams are organized around projects. PM choose the team members, and release them when the project is over. Contractor/consulting company are usually organized like this. The team reports to the PM. PM estimate and track budget and schedule. PM is responsible for the success or failure of their project. Lecture # 2

BREAK 

Coordinator vs. Expeditor Difference between project coordinator and a project expeditor PE keeps track of status but has no decision-making authority on a project at all. PC has similar duties, but does get to make some of the minor decisions on the project without having to run them by the functional manager. PC reports to higher authority PE are more like assistants to FM Both of them exists is Weak-Matrix Organizations Lecture # 2

Teams: Functional vs. Projectized Difference between the way teams are run in Functional and Projectized organizations In Functional Organization, the team is made up of people who already report to the Admin Manager, so nobody questions his authority. In projectized organization, the team is organized around a project and not around a job function. Lecture # 2

Operational Work vs. Project On going / Day to day work Has no beginning or end Keeps the business running Maintains the product Maintains the core work for projects Represents all the work the business does Temporary Has an expiration date Helps to expand the business Builds new products Changes the way of business Lecture # 2

Stakeholders A stakeholder is anyone who is affected either positively or negatively by the cost, time, scope, resources, quality, or risks of your project. Lecture # 2

Stakeholders (cntd.) Anyone who will be affected by the outcome of the project is a stakeholder. Sponsor Development Team Management Team PM should find all of the stakeholders & keep them updated about the progress of the project. Makes sure that expectations are met Lecture # 2

Stakeholders (cntd.) Negative Stakeholders Who are not rooting for project to succeed. Who thinks the project might bring negative consequences. How to work with them? Manage their expectations. Motivate all stakeholders. Lecture # 2

Stakeholders (cntd.) Identify Stakeholders Figure out the stakeholders. Stakeholder Register Goals. Expectations. Lecture # 2

Managing Project Constraints Time: Projects will need to get done on schedule Cost: Project will always have to stay within a budget. Scope: Need to manage the scope of work for the project. Resources: Have to have the people & materials to get the work done. Quality: Product should do what it is supposed to do Risk: Unexpected obstacles can wreck the project Lecture # 2

Managing Project Constraints (cntd.) If all six constraints are not managed at the same time, risk managing in favor of just one constraint increases. Late / Over budget / Unacceptable to customers / etc. Any time the project changes, the manager will need to know how that change affects all of the constraints. Lecture # 2

BREAK 

Review Scenarios Constraint affected Remark The project was running late, so the PM decided to release it on time even though it was missing some of its features. SCOPE The PM stuck to the original budget & schedule, but released a product that wasn’t complete. The company didn’t have enough money to invest in the project, so they had to draft people from other dept. to work part time to get the job done. RESOURCES Resources are people or materials that you need for your project, and when you cut corners you end up straining them. The team wanted to add more testers to find defects, but the PM overruled them. QUALITY Tests and defects are part of quality. Lecture # 2

Review (cntd.) Scenarios Constraint affected Remark About halfway through the project the PM realized that the money was running out faster than expected. The PM tried to move up the deadline TIME There are lot of ways to change the schedule but sometimes there simply isn’t enough time A construction PM assumed that the weather would cooperate with the plans to complete the job, but thunderstorms have derailed the project RISK Assumptions The PM didn’t take software license fees into account which later increased the budget COST PM should always look into the matter Lecture # 2

Cost Time Scope The Triple Constraint When the scope of a project is changed, time and cost are also affected. The same is true when changes are made to cost or time. Change on one area will have impact on the other two areas. Time Cost Scope Lecture # 2

That’s all Folks  Lecture # 2