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

More documents

Recommendations

Info

Polynesian Navigation Event: “Birds seen” “We need a new place for living. Let’s go to Auckland” Lima (Current Location) Action: “Follow the birds” Tahiti “Empty island, great place for living” © 2007 Bernd Bruegge Introduction into Software Engineering Summer 2007 44
Auckland Project Plan (Polynesian Navigation) Project Goal: Auckland Desired Outcome: A new place Team: Captain and 50 sailors Organization: Flat hierarchy Tools: Stars for navigation, hand for measuring temperature Methods: A set of event-action rules. When an event occurs, determine action in the current context. Work breakdown structure: • Task T1 (Set direction): Determine new course for ship • Task T2 (Check Clouds): Look for clouds in the distance • Task T3 (Check Birds): Look for birds, determine their direction • Task T4 (Change course): Change direction to follow new course Process: • Start with T1 and T4. Then execute T2 and T3 regularly. Interpret task results (cloud detected, birds detected) in the current context. If the interpretation makes a new course more promising, execute tasks T1 and T4. Schedule: None © 2007 Bernd Bruegge Introduction into Software Engineering Summer 2007 45
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 and 40: SPMP 5: Description of Work Package
Page 41 and 42: Situated action [Suchman 1990] •
Page 43: Auckland Project Plan (European Nav
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?