DECK_001 Flashcards
1
Q
5 chg programs n projects: + Summing up to: (w 2 dims) + What to do if overfull n unaffordable?
A
- migration - polit n legal reqs - curr projects - chg reqs out of curr biz - M&A Sum = Proj portfolio (ManYears & $) > If unaffordable, sell Co!
2
Q
5 types of strategies:
A
- Owner strategy > is your biz optimally structured (risk n rewards) as compared to inv alternatives?
- Corp strat > which biz are / should we be in? w what resources n alliances?
- Biz strat > w whom n how we compete? And grow? > Porter 5 forces & generic strats
- Config strat > how to design Value Added Engine?
- Functional strat > principles & standards within functions
3
Q
Biz architecture n Corp Transf: 3 stratified interacting components + Interpretation of Corp Transf n its 2 challenges
A
Strategies Processes Systems + CT = from curr to target; though immaterial n cannot be stopped
4
Q
Change strategies (classification)
A
Radical. Evolutionary Top-down. Bold strokes. (Unusual) High involvement. (Unusual). Long marches
5
Q
Companies usually die due to… How? 4 Sequential stages:
A
…internal reasons (unless de-privatised) 1-Strategic crisis > lack of vision 2-Earnings crisis > less investing > getting worse (3-)Banks’ pressure > restructuring (shrink to healthy core) 4-Liquidity crisis > bankruptcy
6
Q
StG DEF enterprise, company, firm
A
A productive social system.
7
Q
Ease of change “formula” =
A
= f ( Dissatisfaction [0…1] x ModelOfFuture x ProcessOfChg )
8
Q
Longest lasting Cos: why
A
- Coz congruence in identity bw CEO n Co Eg family owned biz, Church. CEOs of public listed Cos often need to be brutal > yearly results Family biz can think long term.
9
Q
Rough process costing: (yearly total)
A
h/activity * activity/day * days/years / h/years * total_cost_of_1 employee/y
10
Q
StG DEF mgmt / leadership
A
- start ~ create
- run / grow ~ steer
- change ~ develop
productive social systems, on two levels:
- mechanical
- psychological
11
Q
The 3 main mgmt levels: + usual career direction
A
Top->down - normative - strategic - operational Career usually proceeds bottom up.
12
Q
Transformation management “beer formula” =
A
= Project mgmt (general discipline, domain independent) + Process model (domain dependent: what steps?) + Change mgmt (psy… often badly w money incentives)
13
Q
3 stakeholders groups in a Co
A
- executive board 2. middle mgmt 2.1. operational 2.1.1. front 2.1.2. back 2.2. staff functions 3. employees
14
Q
How to treat ppl in org
based on 2 dims
A
2 dims:
- Performance
- Value-compliance
Treatment to apply:
- high-high –> promote
- low-low –> let go, because there is no person-org fit
- low-high –> teach & re-check
- high-low –> difficult cases of unbalanced high-perf: personality training, if they are willing; or constrain within limits
15
Q
trust “beer formula”
A
contact –> relationship / negotiation
+
communication –> material (interest)
=
trust
+
outcome
16
Q
A target process architecture answers the following 5 Qs:
A
- Identification of the processes
- Structuring of customer relationship interactions
- Process outputs
- Quality levels
- Definition of process flow
- Definition of organizational chart and sizing
- Setup of process management
- Definition of key performance indicators
- Process target
17
Q
(outdated) BCG matrix for corp strat:
A
(low/high growth) x (low/high market share)
18
Q
3 economic sectors, in order f dev, as GDP grows + correl. f 3rd + maybe next one
A
1- agriculture 2- industries 3- services ~ urbanization > deindustrialization in UK eg (4- maybe next: repair env damage)
19
Q
3 surprising sources of increased value added:
A
1- (repair of) env damage 2- (measures against) terrorism 3- regulation => CONTROLLED VALUE ADDED
20
Q
3 types of psychology:
A
1- analytical > focus on what’s wrong (< childhood) 2- behavioral > rituals (to improve) 3- systemic > optimize your resources (strength) w social perspective
21
Q
4 Characteristics of adaptable Cos =
A
- adaptable vs traditional - considers all stakeholders - perf. n leadership oriented - collaborative, low hierarchy (-> check controller’s cost center structure!)
22
Q
4+1 big strategies of biz segmentation: (As a taxonomy)
A
(Positioning): Products + (Markets): Regions Channels Customer segments + Value Chain Functions -> CRI
23
Q
Auto referentiality of systems n premature aging of systems =
A
Successful Co wants to conserve! -> Goes on failure path
24
Q
B2B vs B2C n brand
A
brand B2C. love B2B. CR,services
25
4 Biggest factors of failure of (strategic) projects: (n typical scapegoats)
1- resistance to change from the changed (psy) 2- insufficient support from (strategic) managers 3- unrealistic expectations 4- bad project management (can't learn as you go \> project/change consulting!) + Often IT ppl are scapegoated.
26
Bw 4 salary quartiles of mngrs, who will boards hire? N therefore?
-\> Q2 (choose best ones but avoid press n malpractice accusation) -\> Q2 salaries go up
27
Challenge for Cos by large sing. Mkts:
Be there! In each country
28
Character = Character Dev. =
= sum of your unquestioned beliefs; shows under pressure; Character Dev. = Revising beliefs; leaders (should) have more
29
Chg strats n culture: Nations n what matters
BS \< Us,Uk,LatAm,China LM \< DE,Jp,Scandi but (international) Co culture trumps!
30
Co life: Span Death Typical longest good spell
- short n decreasing (avg 14y in CH) based on registered name change - typically die by being bought (otherwise bad for board members) - rarely more than 12y spell w good VA
31
Combining dims: best n worst quadrants: run vs chg biz n mechanical vs psy
best is mech chg only, w already adaptive co culture; worst is when psy chg is needed b4 all else
32
Common segmentation vs variants
(local) variants are fine if they add value, otherwise kill them
33
Company culture =
= norms, (unquestioned) beliefs
34
corp strat nowadays: 1. old, why? 2. one big, yielding billions 3. 4.
1. portfolio mgmt \> diversify thru acquisitions w/o merging... today useful only for familiy offices, coz fin mkts are so efficient today 2. restructuring biz \> eg GS: buy sick biz, infuse it w knowledge & industry veterans, then resell it 3. transfer skills in value chain activities \> eg GE: let bizs f Co learn from each others, based on similarities 4. (most common today) "sharing activities in VC" \> share HR, R&D, ... shrink bizs as much as possible
35
cost leader strat = goal, when it works?
try to use your deep pockets to starve your competitors... re-raise prices when you have become dominant enough (but not so much as antitrust!) \> Works in consolidating markets.
36
cultural fit bw individual n co in time
Co needs to evolve w world: there is no right to stability!
37
Degree of vertical integration: -def - trend n conseq in econ cycle
= VA / REVENUE = (REV - SOURCE) / REV Trend: decreasing due to integrated supply chains -\> makes it more difficult to survive economic cycle downturns coz always interacting w suppliers
38
Distribution of VA:
5 directions: - investment (sustains n keeps alive Co) - salaries - boni - dividends / interest - taxes
39
Excellent Cos n Entrepreneurs w strategic crises: (strat n psy)
They anticipate crises cognitively, expecting deterioration upon stagnation. Entrepreneurs live in t future: Change when you are at the best, coz then you can afford it!
40
GDP: def. rel w econ policies
Sum VA All national economic policies aim to increase GDP.
41
How BS / LM chg strats combine w mechanical / psy:
BS. LM Mech. Mech transf. Incr. improv. Eg 6 sigmas Psy. Replace mgmt team leadership program.
42
Investment:
Recycling VA into projects. It's a vital cycle.
43
IT n standardization
standardization should precede IT implementation eg f ERP, as IT does not standardize
44
key to strat SWOT analysis
summarizing to key SWOTs
45
Normative mngrs provide: what 2 things otherwise...
- provide energy n identification otherwise ppl leave the system
46
Operational level creates...
... the current VA.
47
Operational mngr does what? goals Development in time psy
- manage against deviation - towards targets, revised up bw cycles - depressive fear-driven job
48
Phases f globalization:
1- world trade of products n raw materials 2- global sourcing incl labour \< unions dislike!
49
Process view for biz design:
TO DO from slide 26 of part 1b
50
Product view for biz design (Taxonomy w 4 main branches)
product 1- range \> produces complexity -- breadth -- depth = variants 2- modularization \> fights complexity -- component structure n standardization -- product data mgmt structure 3- degree f vert integration (aka manufacturing depth) \< outsource based on competencies f suppliers 4- Differentiation
51
product x market biz strat advice: (2)
(old,new prod) x (old,new mkt) = (penetration, prod dev, mkt dev, diversification) 1\> go to boring high VA biz! the grass is NOT greener where you don't know 2\> diversify only reusing core skills (don't go too far from your core)
52
Measure unit of Productivity of 1- countries 2- Cos
1- GDP per capita 2- VA per employee High in (inv) banking, pharma... down to pizzerias!
53
Project: What's career decisive?
Implementing strategies (more career decisive than knowing good ones) Thus changing the operational VA setup
54
(3 Reasons for consolidation)
- increase growth - exit market where not competitive - overcapacity \> decreasing price
55
Return On Equity = (Decomposed into 3 factors, on which you can separately act) -measures what?
= profit/sales (profit margin) \* sales/totAssets (capital turnover) \< e.g. pay late, cash early \* totAssets/shareholderEq (financial leverage) \> Lehman profits SALES TOT.ASSETS capital -measures financial success.
56
Segmentation: def + 4 things you can segment:
"language" to analyze things + Biz, finance, HR, IT
57
St Gallen def of Business Model: + where most capex goes
Triangle Value Proposition Products CUSTOMER SEGMENTS Earning mechanism. Value Chain config. \< capex!
58
Stovepipe model = + Consequently.
each product line in a division (Maybe coming from M&A) + causes desynchronization f efforts \> projects fail
59
Strategic mngr does: task challenge psy
- change op through projects - designer/designed problem: the designed push against change - also psy draining
60
SWOT St Gallen way:
Inside view (SW) x Outside view (OT) = (SO=winning the princess, ST, WO, WT=killing the dragon) strats
61
Taxonomy of product differentiation:
Diff 1- brand -\> psy! 2- product 2.1 function 2.2 design ~ look n feel 3- client relationship INTERACTION = CRI
62
Technological innovation: - goal - 3 dimensions
- increase Value Added - Dim1: product vs process - Dim2: internal vs external in:function,efficiency vs ex:design,effectiveness - Dim3: incremental vs radical (All 8 combinations! Give examples!)
63
The 3 MKTS of an economy:
1- products n services 2- capital market 3- labour market regulated by Gov to let them function as a precondition.
64
To whom do div n int go? generally n conspicuously
To us the ppl. Households. Pension funds.
65
Today's 4 (5) big transformation forces:
1- globalization 2- technology 3- customer-orientation 4- Government (5- M&A)
66
Transformation vs implementation: (Typical) directions
Top down vs bottom up
67
Types of technology + correl n conseq f 2nd
1- product tech 2- process tech ~ phase 2 globalization -\> integrated supply chains
68
Typical change pattern in 3 phases:
1- mechanical bold stroke 2- behavior/psy long March w leadership program 3- process improvement long March (and it overlaps w previous cycle)
69
Unions goal:
Increase salary
70
Value added:
Output (revenue) - input (all you source; but no salaries!) Value may be just availability! \> added by commerce
71
What happens to whom in a price war? (for each f 2 generic competitive strats & then both)
- Cost leaders win - Differentiators suffer coz f pathologically high cost structure (high fixed costs) - All forced to participate even doing bad biz (=low profit) just to cover fixed costs (need enough revenue)
72
What psy characteristics in a startup?
Belief, identification, energy
73
Why important to have independent board members?
Coz so they can shut down (sell) biz PROJECTED to be unprofitable.
74
Why prod function trends to less important?
Coz globalization phase II n integrated supply chains make all products functionally homogeneous
75
4 levels of competences
in 2 dims
2 dims:
1. influenceability
2. importance over time in career
4 levels of competences - from high influenceabilty + low importance to high importance + low influenceabilty:
1. professional competence
2. managerial competences
MECHANIC LEVELS
----------------------------------------------
PSYCHOLOGICAL LEVELS
3. social competences
4. personality competence
76
a good leader does what 2 things:
and avoid what 2 things:
DO's
1. clearly separate material & communication levels
2. always start from relationship (and keep it)
DON'T's
1. sacrifice relationship for material interest
2. sacrifice material interest for relationship
77
Advice on communication
1. communicate as early as possible
* i.e. as soon as there is systemic cohesion
- -\> so you can add **product** to **project** info*
2. make sure all parties understand it correctly
3. test it on test groups, if need be, before sending it out
78
Communication & influence/negotiation over 2 dims
Dims:
- Style: directive \<\> consultative \<\> collaborative
- Form of contact/communication: virtual \<\> physical
Communication (of decisions taken) happens from virtual+directive to physical+collaborative (with no change on material results)
Influence & negotiation happens from virtual/physical+consultative to physical+collaborative
79
essence f designer/designed dilemma in big Cos: \> solution + biggest danger?
not all can be involved in designing \> identification! + very bad if top mgrs are not cohesive! like immature parents
80
how to be an entrepreneur in a big Co?
by being networked!
81
less vs more adaptive Cos & stakeholder groups
less adaptive \> front op ppl are heros only more adaptive \> everyone is considered
82
Negotiation & projects:
what about, where, how (1 attribute + 4 phases)?
* it is about material level, delegated
* it takes place in project committees
* how?
* the committees must be culturally diverse
* phases:
1. contact/comm. --\> bonding, agree on problem def
2. influence --\> ask Qs to understand interests
3. contractual variables --\> identify alternatives out of stakeholders' perceptions
4. negotiation --\> use time pressure for collective solution
83
systemic cohesion def=
the elders of the system are taking decisions with the interests and preferences of the system (individual members) in mind = compromises
84
The 3 attributes a leader needs to have on the relational level in order to create trust
1. authenticity --\> true to yourself
2. empathy
3. esteem
85
Typical cost of a good corp transformation
1 year of profits
86
typical reactions of the designed, when affected by sthg you were not the author of:
+ characteristics of reslilient people
+ lessons for managers
+ phylosophical implication
stability \> immobilization \> denial \> anger (cortisol & adrenaline)
\> bargain \> depression (not important or strong enough to revert decision)
\> testing \> acceptance (seeing the good aspects)
+ resilient people do it faster
+ lessons: it is good to have internal spaces, like forums, to vent anger... or let people exit a system that has no fit at all for them!
**+ the world is constructed, there is no right or wrong**"There is nothing either good or bad, but thinking makes it so." ― William Shakespeare, Hamlet
87
3 (+1) architecture layers
1. Business Architecture
2. Process Architecture
3. Information Systems / Information Technology Architecture
* Information Systems --\> domain- & context specific applictions
* Information Technology --\> contextless tech
88
5 (2+3) project types in project portfolio
+ 2 key aspects to focus on
* Migration (biggest)
* Political & reg. reqs
* Current projects
* Change requests out of curr biz
* M&A
Focus on reducing complexity & own capabilities
89
Mgmt: 5 main tasks (3 + 2)
* Running biz
* core processes
* monitoring & control processes
* support processes
* Changing biz
* designing new "product"
* implementing new "product"
90
Microprocess def=
how you implement the macroprocesses of your CRI
91
one important criterion of segmentation for CRI macroprocesses + properties of one
B2C
vs
B2B sales
--\> tough negotiations (it's like a dance...)
--\> IS value added & switching costs are an important negotiation pressure factor
92
process mgmt def=
monitoring & improving the running processes
93
A target business architecture answers the following 5 questions:
* Which products do I sell and how broad and deep is my product range?
* To which customer segments do I sell them?
* On which regional markets do I sell?
* Via which distribution channelsdo I sell?
* And most important: **How does the mix** of the four dimensions "product – customer segment – regional market – distribution channel" **looks like?**
94
Total Cost of Ownership of IT:
determinants
Determinants:
* IS application
* residing on:*
* IT Production Set =\> *standardize and keep just few eg 3!*
* = bundle of IT components
95
Where do Agile methods fit?
suggestion:
be dynamic towards the client interface, drawing on the backbone, but beware of becoming too complex, otherwise you cannot change the next time
96
3 levels of project management - w 3 considerations!
3 levels of project management:
* project portfolio mgmt:
board wonders: can we afford all of the projects that we need? (NO=\>SELL)
* external project mgmt:
like client controlling their own architect
* internal project mgmt:
like the architect running the construction project
3 considerations:
* Just like there are 5 types of strategies!
* They need different types of skills & EXPERIENCE
* a Co must correctly identify levels & skills, or it fails
97
How to increase acceptance for a corp standardization process?
involve geographical units with competitions to define the standards
+ work on identity: clarify & highlight advantages
98
industrial complexity: driver?
diversity (in the 4 segmentation dimensions)
99
Macro-Processes:
* def=
* how many
* for how long
* strategic bundles of CRIs X biz fields
* from 6 to 18
* don't change them for a long time: this is standardization for stability
100
Resource allocation: responsibilities
* board =\> think of how to change the biz =\> first allocate resources to strategic programs/projects, then allocate money to run the biz based on biz cases
* key: use psy & social competencies to make top managers feel not like individual representatives of BUs, but like "team members" of the system
* BU top managers should put forward only honest biz cases, for a constructive discussion in the Co's interest
* in most companies every BU just lies
101
steering committee
def=
hierarchical structure
committee dealing w strategic programs / projects
Structure:
* ***program manager*** =\> looks across projects
* for each project:
* **project owner*** (sometimes aka sponsor) =\> allocates the project budget, prepares "**project request**"
* people taking material decisions:
* **project committee*** + ***project manager***
* sub-project manager
* sub-project team
102
Step 3 of transformation:
+ 2 typical models therein
map biz field X Customer Relationship Interactions to find Macro Processes!
(think how to bundle them, considering your strategy & customer experience)
2 typical models for bundling in here:
* a cost leader "is oriented horizontally" with its MPs, i.e. bundles horizontally across biz fields =\> looking for synergies
* a differentiator "is oriented vertically" with its MPs, i.e. bundles vertically =\> looking for "intimacy"
103
Step 4:
* what?
* how?
* goals?
* go from strategic planning to operations
* going from Biz Process Architecture to to project portfolio
* then implementing those projects with experienced project managers
* keep value added activities, outsource the rest (incl. problems)
104
Taxonomy of Co resource allocation
resource allocation \<= at top, controlled by board
* resources for operations
* investments
* incremental improvement
* strategic programs / projects
105
Two outcomes of Macro-Processes:
* synergies
* found in shared activities, either primary or secondary
* org chart
* can be reverse-engineered to the biz segmentation
* nowadays it is typically structured by processes, rather than as a matrix
106
usual planning technique by CFOs:
just use avg of analysts' projections
LOL brilliant!
107
What are the characteristics of a strategic biz fields?
biz field def=
the homogeneity of the environment (incl. competition)
def= product X customer segment
108
What is step 2 of transformation?
what is the outcome?
Medium- to long-term planning for the Co, done properly:
estimate growth prospects, and then decide how much to invest, for every segment of the 4D segmentation matrix resulting from step 1.
The outcome is the (target) positioning.
109
What is the 1st step to do it?
Why is it key?
1st segmentation step is to map these taxonomies:
* products
* costomer segments
* regions
* distribution channels
with their relationships, i.e. which subcategory is related with which subcategory (it is a 4D-matrix)
It is key to agree on 1 common Co segmentation because it provides a common language, which must then be enforced by the Co.
110
What is the key transformation activity where most time & effort are spent?
Key effort-heavy activity is to map the new Co strategy into processes, implement them & then keep them evolving
111
why do projects always take longer than anticipated?
because of disagreements =\>
negotiations =\>
cycles of revisions
112
2 models to explain...
to explain relationships bw strategy, process architecture & IT systems implementations, it takes 2 models:
* a meta data model
* a project process model
113
3 analysis types in the project process model of strat dev
* external analyses by consultants = number crunching
* internal analyses (many types)
* **gap analysis**
114
3 perspectives on info sys dev
+ typical problem
1. org / biz mger --\> focused on CRI
2. SW dev --\> focused on robust SW --\> identify modular components reusable across transaction
3. biz analyst --\> should be able to translate & mediate, thinking in terms of **activities** & **transactions**
+ often levels 1 & 2 ~ external & internal proj mgmt are missing!
115
4 stages of CorpDev&IT
1. strategy dev -\> positioning
2. process dev -\> macro-processes
3. information system integration
4. implementation
116
Ansoff matrix of basic strategies
current VS new markets
X
current VS new products
=
market penetration --\> core strats = best, most profitable
product dev
market dev
diversification --\> most risky (blue ocean strategies ~ American dream)
117
benefit of ISO certification
signals that someone put effort in process design (hopefully, that is also followed... but the certifiers do not check that)
118
classification of data (transfer) errors
* 3 types of errors
* rel w cutover
* 3 types of errors
* A errors = catastrophic
* B errors = needing workarounds
* C errors = nice to have for comfort
* rel w cutover:
* A errors must be solved by cutover
* proj mgr pushes for no delay, to save big costs
* requesting activation of fallback plan is dangerous for career
119
costs of transformation: spent where
* strat dev --\> very little
* proc dev --\> little
* info sys integration --\> most!!!
120
customer buying cycle
def=
including...
inventory of clients' touchpoints
...including needs ==\> CRI
121
effectiveness VS efficiency
effectiveness --\> external --\> CRI
efficiency --\> internal --\> macroprocess delivering the CRI
strat development goes from external to internal
122
efficiency:
* measured how
* often achieved how
* #hours spent for CRIs
* efficiency is often achiavable through incremental improvement
123
Generic product / market growth strats (how) according to Lechner
X internal organic, alliances & network, M&A
core
adjacent to core
diversification based on core comp.
unrelated div.
creation of new industries
**==\> both dims are ordered by increasing risk**
***==\> be disciplined & focus your effort adjacent to core, especially if you are small***
124
information system integration: content & methods
information system planning
1. standard software implementation
"European way"
2. process & system integration for legacy systems
"American way"
3. proprietary development
"Japanese way"
there should actually be a rational choice!
125
IS support def=
suggested structure & why
mgmt of incremental change
* change needs
* --\> chg requests
* --\> evaluation/acceptance/denial
* --\> bundling into release
* --\> release
lack of structured approach leads to unstable applications
126
IT applications def=
tech aids showing users some data & providing minitools to manipulate that data (let them do work for you, whether they are employees or customers)
127
Key to strategic analysis:
**identify & reduce yourself to 3 to 5 most important gaps** to fill in the next few years, even if we do not know how to fill them
=\> you gotta fight the psy tendency to only think of problems that you can cope with
=\> the top performing managers are those who can do this
128
macroprocess
* def
* rel. w product / service
* composition
* rel. w IT system
* rel. w project management
* the macroprocess is defined by its output, i.e. a certain client relationship interaction
* customers pay for the product / service, but they more often decide based on the CRI!
* each composed of microprocesses, typically 3 to 7
* microprocesses are implemented in the information system
* to be implemented in parallel
129
meta data model for systems & tech planning: scope
many decisions about applications
like: strat: first mover / fast follower / follower...
choice of outsourcers
skills needed
130
Meta data model "Strat dev"
strat biz field
* serves cust segment
* serves regional market
* provides product
* uses distrib channel
131
next question after generic prod/mkt growth strats: choose biz strat in Porter matrix of generic strategies
scope (narrow VS broad) X comp. adv. (cost VS unique VP)
= 4 options
132
project process model for systems & tech planning: scope
many components, such as:
strategic planning, org planning, topology planning, release planning etc.
133
project process model "implementation" / rollout:
4 higher-level compoments
* resources concept
* training concept
* fallback plan
* data transfer concept
* authorization plan
* who has authorizations to use what... --\> org structure planning
* downtime plan
* (data) bacukup plan
* install test system
* integration plan
134
SW-OT strategies
= using internal factors to deal with environmental factors
135
typical Nrs on data & transactions
in a Co in general & in bank Lione case study
* SAP offers abt 30k transaction types
* ZKB executes ~N\*100m transaction runs (instances)
* typical Nr of data types for a Co ~ N\*1k
* Bank Lione case study:
cost & time for transforming Co & IT w 3k employees
* 300 to 500m & 5y
* 3k transaction types
* 300 projects
136
value of standard application packages
since most is prebuilt, you can do many more phases in parallel rather than sequentially
137
what IS need to be managed?
5 levels
* IS concepts = what kind of tech?
* IS architecture = portfolio of applications?
* IS project portfolio?
* IS project
* IS support
138
you cannot afford the projects to fill your top gaps?
2 alternatives
either **recalibrate** (to smaller vision) or **sell** / merge / go together with other ppl
139
Client proj mgmt org: 4 components
* project owner (not sponsor) = 1 manager
* project committee
* review team (experts)
* client project leader
140
3 signs of bad projects
+ why & =\> conseq
* project team must come up w the project process themselves
* there are project stars taking all decisions
* ppl work permanently long hours
+ coz you need both good proj mgmt & a specific proj proc model
=\> consultancies exist so that you can buy this kind of expertise with **repeatability**
141
3 x 2 tasks of Quality Assurance: who
& what to look at
* review
* SU internal --\> check formal consistency!
* *CL external*
* test
* SU internal
* *CL external*
* audit
* *CL method audit*
* *CL project leadership audit*
142
general project mgmt VS project process model
+ how to cope
general contentless discipline (set goals & deadlines; identify components; test...)
VS
specific domain knowledge allowing you eg to identify the correct components
+ how to cope: w a 2-party contract having 2 levels
(does not matter if inside or outside)
* client perspective: manage cost, time, scope of the product
* supplier perspective: manage the process
143
ISO 9001:
2 targets
* regulation of client-supplier-rel = 2-party contract rel.
* self-enforcement of supplier to quality orientation
144
proj mgmt quality def=
magic triangle:
* cost
* time
* scope / benefits
=\> on DESIGN you can do **analytical quality assurance**, but this is not enough because you need to also think of the process
=\> you also need **constructive quality assurance** which relates to the type of process: CAN THIS ACTUALLY BE BUILT & WORK?
145
* project mgmt psychologically
* proj mgmt quality level & why
* but: re. deviations from project...
* depressing, because it is mgmt!
* quality is normally low coz Co has less experience there as compared to operations
* ...are an unacceptable conseq. of insufficient experience
146
SEI-process-maturity-scheme:
5 levels
SEI = SwEngInstitute
1. chaotic
2. repeatable
3. defined
4. quantitatively managed
5. optimizing
147
Supplier proj mgmt org
+ key distinctions of responsibilities
* supplier
* supplier proj leader
* team 1
* team 2
* team N
***the supplier proposes but does not take design decisions******: commixtures are wrong***
148
typical sources of project deviations
* client org negotiations are very political
- -\> this is quite normal
* supplier org did not know what they were doing
- -\> this is very bad and should not be so
149
3 levels of proj mgmt & associated actors & committees
1. proj portfolio mgmt --\> Co board / steering committee, if external ppl are involved for strategic reasons
2. ext proj mgmt --\> project owner / "sponsor"
3. int proj mgtm --\> supplier
NB: it does not make a big diff whether the ppl involved are internal or external
150
5 types of projects
* migration
* political & legal requirements
* curr projs
* change requests out of curr biz
* M&A
151
beer formula of
transformation mgmt
transformation mgmt
=
proj mgmt --\> mechanics/intellect, non-specific
+
proj process model --\> mechanics/intellect, domain-specific
+
change mgmt --\> psy
152
best nr for proj committee
5-6; never more than 9, otherwise they position themselves in discussions!
153
Co task taxonomy
tasks
* run
* change
* incremental changes
* programs / projects
- -\> typically w info sys new releases
154
consultants in proj:
when to call, what for (2 ways) & who
call them if you don't have know how to do proj
in order to either:
* get right process (small consultantcies)
or
* also let them run proj (big consultancies)
155
good vs bad proj risk mgmt
good: anticipate risks, then report problems early & have corrective plans ready --\> makes a very good impression!
bad: unrealistic optimism, then keep problems hidden and then report huge problems late --\> fired!
156
how should a manager handle late deliveries of deliverables?
reassign a new date to the late ppl, but leave this always visible, so that peer pressure takes care of that and makes true problems emerge!
DO NOT compensate by taking over the late task, otherwise you get overloaded.
157
levels of proj mgmt
1. proj portfolio mgmt --\> strategic mgmt of curr & planned projects; typically done by the board in the morning
2. external proj mgmt, involving / supervising middle level managers
3. internal proj mgmt, including domain-specific mgmt process, w matrix structure of subprojects X phases
158
program vs project
program \>\> projects
typically transformative, and mostly max 2 of them at a time
159
proj method audit **vs** proj leadership audit
proj method audit --\> quality (deviations?)
proj leadership audit --\> which org is responsible for the deviations? client or supplier?
160
project artifacts
==\> go through slides & compile a nice list
161
role of agile in proj mgmt
agile is for detail breakdown in SW development, which is a small chunk of a big corp transf project
162
small vs big projects
typically used thresholds: 50 days or 50(0)k expense
163
strategy ***vs*** proj outputs
studies ***vs*** changes effectively changing the Co's value added engine
164
time sheet: purpose
document if someone is responsible for a task & has resources assigned, but is not really receiving them (eg ppl do not show up or do not deliver to them)
--\> do we have the Co capacity?
165
what is a proj steering decision log?
goal?
= log of all (collective) decisions in a proj
==\> documents all decisions taken and **_changes_** made which made proj more expensive, thus avoiding recriminations
(accountability for design, scope & cost is in the client org!)
166
* what is a study or proj request?
* what is a submarine project and what happens?
* why is RM important?
= basically a request for investment money, according to a structured formalism
= hidden projects, that die when they emerge
Because assessing & communicating possible risks in advance keeps trust & cohesion b/w supplier & client organization!
167
beer formula of dissatisfaction of current state
D = A x G
A = acceptance of the problem
G = extent of the problem
168
coaching: how, what for
take from slides
169
duality of fear & love
trick in leadership
* doing / fear / ego / transactional leadership / cocaine / "material world"
* being / love / relationships / transformational leadership / wine, LSD / "spiritual world"
==\> balance the 2 sides!
& live here & now also in corp world, w/o split personality;
**_develop your personality as you go_**
==\> use a coach, but a qualified psychologist
170
empower people =
= teach ppl to be authors of their lives, rather than victims!
171
fitness: def & breakdown in 4 categories
= having reserves
* physical ==\> control your sleep, eating & drug taking
* emotional ==\> plan your social life & relationships
* mental ==\> learn work & personal focus
* spiritual ==\> personal orientation for others
172
how to coach opponents in 3 steps
1. call & listen
2. meet for lunch
3. agree on the issue (def), because that creates warmth!
173
leadership dev:
* goal
* making org more adaptive
174
modes / levels of leadership
* positional power --\> fine for emergency situations
* trust --\> normally better
175
purpose of Change Management (CM)
solve designer-designed problem by minimizing conflict potential & resistance
eg involving some middle mgrs as designer
176
stakeholder map
internal or external circle of impact on me
+
opinion leader / stakeholder / critical stakeholder
+
category:
* promotors
* supporters
* hoppers --\> rel ppl who compromise on material aspect
* opponents
177
the 2 leadership themes
* Me = my beliefs & needs
collective psy; determines how social I am
* We = relationships ==\> energy & warmth
individual psy; determins how adaptive we are
* It = material aspects
mechanics & facts
178
trust building level 2 formula
contact = authenticity + empathy + esteem (of other ideas, w/o accepting them)
+
communication
=
trust
+
outcome
179
what to do when you are unhappy in an org?
accept it if you can, or leave it and find your place in the world!
