Back
NotesComplete set

Course summary

Complete course materials for Digital Project Management in the Computer Engineering degree programme at Politecnico di Milano. The document covers: 1 RIASSUNTO DPM FUNDAMENTALS 1. Project: A project is a temporary endeavor undertaken to create a unique product or service. Is progressively elaborated: with repetitive elements. 2. Program: A program often consist in a number of related projects; a program is no longer than a

Digital Project ManagementComplete set

Document information

What's included in this study material

Complete course materials for Digital Project Management in the Computer Engineering degree programme at Politecnico di Milano. The document covers: 1 RIASSUNTO DPM FUNDAMENTALS 1. Project: A project is a temporary endeavor undertaken to create a unique product or service. Is progressively elaborated: with repetitive elements. 2. Program: A program often consist in a number of related projects; a program is no longer than a

Import quality: text was extracted directly from the original document.

Extracted content from the document

Representative passages recognised in different parts of the material. The full extracted text remains available to search, while this compact preview makes the page easier to read.

Page 1

1 RIASSUNTO DPM FUNDAMENTALS 1. Project: A project is a temporary endeavor undertaken to create a unique product or service. Is progressively elaborated: with repetitive elements. 2. Program: A program often consist in a number of related projects; a program is no longer than a project 3. Product: the result 4. McConnell’s four dimension [~Pillars] (interest in RAPID DEVELOPMENT) o Classic Mistake Avoidance ▪ These mistakes have Seductive Appeal: everyone keep doing them over and over ▪ Divided in the four project’s dimension: • People-Related: o Weak Personell: difference between weak and junior - weak==no skills o Adding people to a late project: new people are not aware of the project so they have to be trained ➔ late o Noisy, crowded offices o Lack of stakeholder buy-in: the stakeholders don’t recognize your efforts: i.e. not giving extra-time when due… • Process o Optimistic schedules: puts unnecessary pressure o Abandonment of plan under pressure: stop planning lead to code- and-fix, that is not good o Omitting necessary tasks from estimates: you don’t consider something and then you have to adapt to the new situation➔late • Product o Requirements gold-plating: too fine grain requirements o Feature creep: changing in the requirements during the implementation o Push-me, pull-me negotiation: asking for more time bring a slip in the schedule, but add other features • Technology o Lack of automated source-code control: new feature come up and nobody knows from where o Overestimated savings from new tools and methods o Switching tools in mid-project o Development Fundamentals o Risk Management o Schedule-Oriented Practices 2 5. Project Stakeholders: Project sponsor, Executives, Team, Customers, Contractors, Functional managers 6. Project Manager: is the person in…

Preview

First page of the document.

First page: Course summary