Win Win Concept of Operation and Benefits Barry Boehm USC-CSE Annual Research Review March 11,1996
UICI.*d-Oa
CrrCI l a So*rrwm EnOkrrhO
Outline
..
Motivation for Win Win Approach Win Win Elements -Theory W : a management theory -Win Win Spiral Model : a process model -Win Wln : a groupware support system Win Win Concept of Operation Win Win Benefits
..
Page 1
. ..
Motivation for Win Win Approach Establishes objectives and procedures for Integrated product teams (IPTs) -What should the IPT participants try t o do? - How should they proceed? -How will they know when they're done? The fundamental success condition Some common counterexamples
The Fundamental Success Condition Your project will succeed If and only if You make winners of all the critical stakeholders
..
Usually : Users, customers, developers, maintainers Sometimes : Interfacers, testers, reusers, general public
Ya t m
Page 2
Some Common Counterexamples
I
~ u ~ t~kt ,m psloppy , produc
Lots of bolls and whlrtlor
Drlvlng too hard s brrgrln
I
D.volopor
D
. U.r
I
~
Customr iUsor
Curtomor ~
bvolopor
Acturlly, nobody wlns In l h s o situations
nwtm
Outline Motivation for Win Win Approach
Win Win .Elements -Theory W :a management theory -Win Win Spiral Model :a process model -Win Win :a groupware support system Win Win Concept of Operation Win Win Benefits
Page 3
~
~
~
~
Theory W Management
.
Management Steps
.
Role of Negotiation
.
Examples :F-16,STARS
Theory W Management Steps 1. ldentify success-critical stakeholders 2. Identify stakeholders' win conditions 3. Identify win condition conflict issues 4. Negotiate top-level win-win agreements Invent options for mutual gain Explore option tradeoffs Manage expectations 5. Embody win-win agreements into specs and plans 6. Elaborate steps 1-5 until product Is fully developed Confront, resolve new win-lose, lose-lose risk items
-
Page 4
Stakeholder Role Variations
Ikrrrhd-lhmd.
Cnu lot s0m.n Erq#mdng
Negotiation Principles* Don't bargain over position Use 4-step solution approach -Separate the people from the problem Focus on interests, not positions -Invent options for mutual gain -Insist on using objective criteria
-
*Fisher 6 Ury, Getting To Yea, 1981 Y W1M
Page 5
. Inventing Options for Mutual Gain The four bask steps: Fisher and Uy
Win-Win, Win-Lose, and Lose-Lose Situations
Page 6
Getting to Win-Win: COCOMO F-16 Example
usw wants in 12 month.
in 12 month.
Getting to Win-Win: COCOMO F-16 Example
Product Dovelopw can build in 12 month.
Product usw wmts in 12 month.
Prioritiza Dovelopmant Incrmanb
Add Tuhnology, Key People
Page 7
Win Conditions: STARS Constituencies Primes, commercial counterparts Sottwan Engineering Environment sales Do0 acceptance of commercial SEE product line Leverage on Primes' software buslness Satisfied customers and usen
-
.-
Subs, tool vendors: Profits lrom large tools marketplace Open architecture, multi-platform, polylingual Stable evolution, voice in evolution strategy
-
Win Conditions: STARS Constituencies DoD coftwue contractors: kverage on software businus Opon architoctur* multi-platform, ease of extmsion Rapid .v.ikbility, e a n of us* reasonable cost Stable evolution, voice in evolution stratogy DoD OhM organintiono: lifecycle coftwue support effoctivonr Similr eonarm to DoD soflwue contractors Support of cottwue mod.rniation, Ada trmdtion S.wicoqAg.mk. S i g n i b n t imprwmont in softwue productivity and quality Roducd ri.bof SEE adoption DARPA, OSD, Congrus, othw govornmont agmk. All of tho above U f u y c k affor&bility Ada muldato
-
.
-
Page 8
Some STARS Win-Win Experiences
.. .. -
Ada mandate: Write all STARS software in Ada Commercial vendors: Ada incompatible with non-DoD marketplace No commercial support: Unaffordable SEE'S Win-Win solution: Commercial vendors agree on Ada tool support - OSD agrees to accept Ada waiver for STARS, based on lifecycle cost4fectiveness Process timeconsuming, misunderstanding-prone - 5 months from basic agreement to success plans - Needed groupware support
.-
STARS Win Win Results
Successful largescale demo projects Effective government-industry collaborations - Air Force Space C2: $140 ==> $57/LOC 3 0.35 defects/KLOC - Navy Simulators: $125 =a S65ROC - Army Signal Proc: 50% product line reuse savings
-
.-
Stimulated major product-line reuse initiatives DoD, Services Software Reuse Plans
Page 9
Theory W Extension to Spiral Model
L Romncllo rrln
1. Idmdfy nell-lrvd Sak.hdbm
condltlau. E.taMImh nllb v d objocllvw, oonrtnintm, allenutlvw
7. Revlow, eommitmenl 8. ValMalo product and proenm dennitlam
4. Evalwto product and p m c u m anunrtlv... R..olvo RIakm
\
ma b v o of ~ product and -ma
- lncludlng pmflitlam
Win Win Spiral Model and Major Milestones
Page 10
Win Win as a Requirements Engineering and Architecting Approach
.
Stakeholders use groupwan support system to Identify win conditions, negotiate win-win agreements Schemas tor win conditions, conflicts, agreements Domain taxonomy and glossary Taxonomy-based navigation aids Tradeoff analysis tools Stakeholders supported by system engineering organization ~ n a l y ~ i win n g condition conflicts, generating solution options, coordinating progress Negotiated points of agreement become system specs
-
. .
Outline
..
Motivation for Win Win Approach Win Win Elements -Theory'W :management theory -Win Win Spiral Model :a proces model -Win Win :a groupware support system
*. .
Win Win Concept of Operation Win Win Benefits
Page 11
"Stakeholders" Aren't Homogeneous
..-
May be some general stakeholder patterns Implementation-orientation, risk-aversion, changeaversion But don't a s s u m stakeholders a n homogeneous People represent themselves, projects, organizations, communities to varying degrees Collaboration process implications Getting the right people Involved Empowerment and accountability Incentives to collaborate Teambuilding
.-
-
Collaboration Process Preconditions Appropriate stafflng of stakeholder representathrer, system enginwring function
- Stakaholdor raprmtatlvoo: m p o w r . 6 reountablo, reprrntathn, collaborativa, knowldgoabla
- colkboration Systom nginwrs: undushnding of s b k A d d u domdns, managamant ability, a ~ l y t i c skills System enginearlstakeholder pro-work Characterizeexisting system, nlad concern8 Identify, discuss candidate solutions Clarify collaboration process objectboa, approach Hold stakeholder workshop
-
-
Contut-safflng, turnbuilding, supporl systun balning
Page 12
Related Work
Low
I Low
.. .
-
0
Coordinator, Object Lens
Groupware Support
Lotus Notes, Convers'n Builder
High
Win Win Benefits
Gets key stakeholders involved Provides collaborative operational guidelines Provides criteria for evaluating success Reduces cycle time Especlally for distributed collaboration Complements other key front-end tools and methods
..
Page 13
