18
Software Project Management - General Information Adolfo Villafiorita with the generous support of Pietro Molini

Software Project Management - General Informationspmbook.com/course/2015/downloads/slides/0A... · spm 2 Timetable • Schedule: ... (scoring system based on progressive “degradation”

Embed Size (px)

Citation preview

Software Project Management -General InformationAdolfo Villafiorita with the generous support of Pietro Molini

spm 2

Timetable• Schedule:

– Tuesday: 14:00-15:45 (Room 222) – Wednesday: 09:10-11:00 (Room 222)

• Constraints?

spm 3

Exam...• One compulsory:

– written exam: [0, +31] points (scoring system based on progressive “degradation” from optimal or correct answer)

• One of these three optional (grades sum to written exam, you choose what to do): – Project: [0, +3] points – One point or two points essay: [0, +1] [0, +2] points – Development project: [0, +3] points – Interview: [-3, +3] points

• 30L is equal to written exam >= 30 or (written exam = 30 and interview)

spm

Software Project Management• Adolfo Villafiorita

Introduction to Software Project Management CRC Press

• Many other books on specific topics (agile development, managing IT projects, rapid development) with hints and practical suggestions

4

spm

Books: Other Nice References• Robert K. Wysocki

Effective Project Management: Traditional, Agile, Extreme

• Harvey MaylorProject ManagementPrentice Hall

• Various AuthorsA guide to the Project Management Body of Knowledge

5

spm 6

Books: Other Nice References• Catherine A. Tomczyk

Project Manager's Spotlight on PlanningHarbor Light Press

• Rory BurkeProject Management -Planning and Control TechniquesWiley

• Michael DobsonCreative Project ManagementMcGraw-Hill

spm 7

Web Presence• Material:

– http://www.spmbook.com • 2014-2015 specific information:

– http://www.spmbook.com/course/2015 • Project

– http://dev.ict4g.org/redmine/spm-2014-2015 • News, updates and questions

– https://twitter.com/spmbook – http://www.spmbook.com/q_and_a.html

Should you need material, explanations, don’t be shy and ask!

spm 8

Contacts• Adolfo Villafiorita

Fondazione Bruno Kessler – e-mail: [email protected] – web: http://ict4g.net/adolfo – phone: 0461-314311

spm 9

Getting in touch• In order of preference:

– Right after the lesson – By e-mail – By appointment

just showing up doesn’t work

allow for about a weekto get an appointment

(mail to meeting)

spm 10

Who am I and where I work• Adolfo Villafiorita

Researcher at Fondazione Bruno Kessler • Areas of interest

– ICT for Development – Project Management

• Master theses available • https://speakerdeck.com/aaronsama/ict4g-group-official-

presentation-ita • More information

– In person – http://ict4g.fbk.eu

Structure of the Course

spm 12

Software Project Management• The course is an introduction to project management

techniques (and tools), focusing on challenges posed by software development projects

• After the “software crisis” software development and project management developed as independent disciplines

• However, today both disciplines take and give to the other

• Software Project management is an emerging discipline focused on looking at software development mainly from an organizational/managerial point of view

spm 13

Meta-level

Object-level

Project Management defines what you want to achieve and how you can achieve it. Most of the techniques and tools are there to control complexity, by defining goals, organizing work, managing expectations.Project Management sometimes also suggests toolsand techniques that can be used when developing software.

Software Engineering tells you how to build a systemand how you can control complexity.Software Engineering suggests tools and techniquesthat have to be used when developing software.

Often it also prescribes what to do to organize work in software development projects.

spm 14

Structure of the Course• Goals:

– Software development practices (building blocks and processes) – Project management practices (focus on techniques; simulations to get

the flavour of the practical aspects) – Considerations about group management/leaderships – PMBOK, PRINCE2, NASA Standards, Agile methods – Case studies (experts from other areas, case studies of particular interest)

• Means: – Frontal lessons – Projects/essays – Exercises (laptops, anyone?) – Home assignments – Presentations/interaction

Initiating Planning Executing Controlling Closing

Integration D e v e l o p P r o j e c t C h a r t e r ; D e v e l o p Preliminary Project Scope

D e v e l o p P r o j e c t Management Plan

Monitor and Control Project Work; Integrated Change Control

Close Project

Scope Scope Planning; Scope Definition; Create WBS

S c o p e Ve r i fi c a t i o n ; Scope Control

Time A c t i v i t y D e fi n i t i o n , Activity Sequencing; A c t i v i t y R e s o u r c e Estimating; Schedule Development

Schedule Control

Cost Cost Estimating; Cost Budgeting

Cost Control

Quality Quality Planning P e r f o r m Q u a l i t y Assurance

Perform Quality Control

Human Resources H u m a n R e s o u r c e P l a n n i n g ; S t a ff acquisition

Develop Project Team; Manage Project Team

Communications C o m m u n i c a t i o n Planning

Information Distribution Performance Reporting Manage Stakeholders

Risks R i s k M a n a g e m e n t P l a n n i n g ; R i s k Identification; Qualitative and/or Quantitative Risk Analysis; Risk Response Planning

Risk Monitoring and Control

Procurement Plan Purchase and A c q u i s i t i o n s ; P l a n Contracting

R e q u e s t S e l l e r R e s p o n s e s ; S e l e c t S e l l e r s ; C o n t r a c t Administration

Contract Closure

spm 16

Some things you will learn…• Selecting what projects to start (if you can choose) • Planning a project, using WBS, Gantt, and PERT charts • Estimating software projects using algorithmic (FP,

COCOMO, …) and non-algorithmic techniques • Managing risks and monitoring your plan • Monitoring progress in time and cost • Earned Value Analysis • Being agile • Managing people, managing yourself

spm

A final consideration• Becoming really proficient in any discipline requires a mix

skills: inclination, technical proficiency, experience, ... • Of these, we can learn only the techniques (inclination we

are probably born with; experience we get along the way) • You can maybe get along with inclination, luck, or

experience alone • So why learning the techniques?

– provide you with the tools to do your best in any situation – provide a reference framework and methodology to work with – they are essential to become champions

17

spm 18

Organizations and Standards

To encourage the profession and promote standards

• PMI/PMBOK - Project Management Body of Knowledge (USA) • AXELOS/PRINCE2 - Projects in a Controlled Environment (UK)

• International Project Managers Association (IPMA) • Association for Project Management (UK)

• Various public bodies (NASA/ESA/…)