Variations of PM approaches Chapter 2, pages 44-63
description
Transcript of Variations of PM approaches Chapter 2, pages 44-63
CSSE 3729.September.2008
Variations of PM approachesChapter 2, pages 44-63
OutlinePressman modelsWysocki models
Bob Wysocki, from his consulting company web site, http://www.eiicorp.com/seniorteam.cfm#robertwysocki.
Roger S. Pressman, from his consulting company web site, http://www.rspa.com/about/index.html.
A strategic question when we get done: How are these models different from the ones in your requirements book, just because these guys are interested in project management?
ReferencePressman, Roger S., Software Engineering: a
Practitioner’s Approach, 5th edition New York: McGraw-Hill, 2001, pp. 26-41
Pressman – basics & lots of variations: The Linear Sequential Model
Prototyping model
The RAD Model
Discussion…How would you do something like RAD if you didn’t
have a lot of people on your team?
E.g. –Only one lead designerOnly one database personOnly one person who talks to the big customersOnly one project manager
CotD
The Incremental Model
The Spiral Model
The WINWIN spiral model
The Concurrent Development Model
Component-based Development
Before we get to Wysocki…Which of the above Pressman models do you think
our “personas” Shanice and Cody would use the most?
Why?
Shanice
Cody
Wysocki - 5 Management Approaches
Fig 2-2, p. 47
Linear Project Management Approaches
I’m now going to try to sell you on the idea that this works! …
Incremental ProjectManagement Approaches
Iterative Project Management Approach
Adaptive ProjectManagement Approach
Extreme ProjectManagement Approach
Discussion – Extreme vs “No Process”Pick a project you’ve done for class where, being
frank about it, you really didn’t have any project management process.
What went wrong?Now look at the “Extreme Project Management”
approach on the previous page.How would that have improved how it went?Are there any ways it would have been worse?
Variations with TPM
Rapid Development Approach Staged Delivery Approach
Applying quality management to any/all these modelsIt’s all about using a repeatable process with
predictable results.Feedback from each development lets you improve
your project management process, too.You have to be able to analyze what caused what…And predict what changes will improve what…The Process Quality Management model lets you
see what affects what
Process Quality Management ModelHow you know what
fix will mess up what other stuff!
Fig 2-11
Ok, here’s the strategic question… How are these models different from the ones in
your requirements book, just because these guys are interested in project management?
Questions?