Software Project Management Part 1: Organization - Chair for ...

More documents

Recommendations

Info

Time estimates for establishing a WBS • Establishing an WBS in terms of percentage of total effort: • Small project (7 person-month): at least 7% or 0.5 Person Months (PM) • Medium project (300 person-month): at least 1% or 3 PMs • Large project (7000 person-month): at least 0.2 % or 15 PMs Source: Barry Boehm, Software Economics. © 2007 Bernd Bruegge Introduction into Software Engineering Summer 2007 36
Creating Work Breakdown Structures • Two major approaches • Activity-oriented decomposition („functional decomposition“) • Write the book, get it reviewed, do the suggested changes, get it published • Result-oriented decomposition („Object-oriented decomposition“) • Chapter 1, Chapter 2, Chapter 3 • Which one is better? Depends on project type: • Development of a prototype • Development of a product • Project team consist mostly of inexperienced beginners • Project team consists of experienced developers © 2007 Bernd Bruegge Introduction into Software Engineering Summer 2007 37
Page 1 and 2: Software Project Management Part 1:
Page 3 and 4: Software Engineering: Definition
Page 5 and 6: Change • Something becomes clear
Page 7 and 8: Changes in the Business of Software
Page 9 and 10: Rate of Change determines the Proce
Page 11 and 12: Outline of the lecture 7 04 2007
Page 13 and 14: Work Categories in a Software Proje
Page 15 and 16: Project Function • Definition Pro
Page 17 and 18: Tasks • Smallest unit of work sub
Page 19 and 20: Determining Task Sizes • Finding
Page 21 and 22: Activities • Major unit of work w
Page 23 and 24: Work package, Product, Deliverable,
Page 25 and 26: Project Agreement • Project Agree
Page 27 and 28: Problem Statement, SPMP, Project Ag
Page 29 and 30: SPMP Part 0: Front Matter • Title
Page 31 and 32: SPMP Part 2: Project Organization 2
Page 33 and 34: SPMP Part 4: Technical Process 2.1
Page 35: Work Breakdown Structure Work Break
Page 39 and 40: SPMP 5: Description of Work Package
Page 41 and 42: Situated action [Suchman 1990] •
Page 43 and 44: Auckland Project Plan (European Nav
Page 45 and 46: Auckland Project Plan (Polynesian N
Page 47 and 48: Additional Readings • [IEEE Std 1
Page 49 and 50: Backup Slides © 2007 Bernd Bruegge
Page 51 and 52: Project Management Activities in a
Page 53 and 54: “Laws” of Project Management
Page 55 and 56: Examples of Risk Factors • Contra
Page 57 and 58: Hierarchical Organization of the Ac
Page 59 and 60: Example of a Schedule: Building a H
Page 61: Software Lifecycle Activities Requi

Software Project Management Part 1: Organization - Chair for ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?