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

More documents

Recommendations

Info

How much planning should you do? • Two styles of navigation [Gladwin 1964] • “European navigation” • Current Location and Desired Location • Planned Route • Route Deviation and Route Correction • “Polynesian navigation” • Goal • Reaction to unexpected: Change the route The main difference is the reaction to events This leads us to the notion of situated action © 2007 Bernd Bruegge Introduction into <strong>Software</strong> Engineering Summer 2007 40
Situated action [Suchman 1990] • Situation Action: Selection of action depends on type of event, situation and skill of developer • Events: Course deviation, Birds seen, Clouds seen • European Navigation is context independent: • Event: “Course deviation in the morning” => Action: “Course correction towards planned route” • Event: “Course deviation in the evening” => Action: “Course correction towards planned route” • Polynesian Navigation is context dependent: • Event: “Birds seen”, Context: It is morning => Action: “Sail opposite to the direction the birds are flying” • Event: “Birds seen”, Context: It is evening => Action: “Sail in the direction the birds are flying. © 2007 Bernd Bruegge Introduction into <strong>Software</strong> Engineering Summer 2007 41 46
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 and 36: Work Breakdown Structure Work Break
Page 37 and 38: Creating Work Breakdown Structures
Page 39: SPMP 5: Description of Work Package
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 ...

Create successful ePaper yourself

Delete template?

Save as template?