The Diamond model Flashcards

1
Q

A critical view of the ‘iron triangle’?

A

It encourages a strait-jacket mentality and turns the solution to every problem into a request for more money or time or both. I think the triangle is a crutch for poor project management
• Loosening time constraint doesn’t always mean higher quality.
• More money, likely more people = more training, more communication, network effects.
• Scaling quality/scope up or down entails risks. Some projects have simply unfeasible scopes, regardless of cost and time.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Examples

A

Sydney opera house
• Over budget by 1500%

Los Angeles Metro
First phase:
- Completed 8 months ahead of schedule
- No budget overruns
- Construction safety record 50% better than national average
- “Project of the year” award by PMI (1993)
- Remaining phases of project dropped due to low usage.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Project success measures?

A
  1. Efficiency e.g. meeting schedule, meeting budget, Yield, changes, other efficiencies
  2. Impact on customer e.g. meeting requirements, benefit to customer, extent of use, customer satisfaction and loyalty, brand name recognition
  3. Impact on team e.g. team satisfaction, skill development, retention, team morale, team members growth, no burnout.
  4. Business and Direct success e.g. sales, profit, ROI, ROE, market share, cash flow, service quality, cycle-time, organisational measures, regulations approval.
  5. Preparing for future e.g. new technology, new market, new core competencies, new product, new organisational capabilities.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Flexible and adaptive PM approach

A
  • Many projects fail to achieve their expected results or are not completed on time and within budget
  • But failure is not just about bad (project) management
  • Fail often occurs in projects in well-managed projects run by experienced managers and organisations
  • Traditional PM assumes all projects can be managed in the same way - ‘one-size-fits all’
  • Need an approach to project management which is ‘adaptive and flexible’
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Diamond model use

A
  • identifies project type
  • used to access project risks and benefits
  • so right PM approach can be selected
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Novelty?

A

• How new is the product to customer and users (i.e. the market)?
• Uncertainty of a project’s goal and; uncertainty in the marketplace
• May have to create a market if customers don’t know they need it yet e.g. Sony Walkman, created a market.
- The more Novel, the more skills team members will develop/require.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Novelty levels?

A
  1. Derivative - extending or improving existing p/s e.g. developing a new PC
  2. Platform - developing or producing new generations of existing p/s to existing markets e.g. new car generation
  3. Breakthrough - introducing a new product that no one has seen before e.g. Walkman
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Novelty example

A

Airbus A380
• 1st to market
• Break from previous Airbus families (where progress was sequential from A300 to A340)
• Largest passenger airliner in world (in competition with Boing 787 Dreamliner)
• 50% more floor space than second largest airliner (which is the Dreamliner)
• Somewhere between breakthrough and platform.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Technology?

A
  • How much new technology is used? (new to the company)
  • Project’s level of technological uncertainty
  • 4 levels of technological uncertainty
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Design freeze?

A

When you make decision of final design/output/outcome of project.

  1. Early design freeze (do this when there isn’t much uncertainty)
    Freeze the design prior to project initiation and technology integration. Assumes that the final configuration of the system can be fully known or predicted at the outset.
  2. Late design freeze (when there’s lots of uncertainty as need to allow time, throughout earlier stages when not sure of end results may be wasted due to working on different ideas before freezing design, this can very expensive. If design keeps changing, this costs more and can delay project even more). Keep system design as a flexible as possible at the outset to cope with emergent events, changing customer demands, and new technological uncertainties
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Technology levels?

A
  1. Low-tech project
    • No new technology is integrated
    • Examples: bridges, road building, installation of new telephone network
    • Almost no technological uncertainties
    • Design freeze set very early, often before initiation of the project
  2. Medium-tech project
    • Integration of single new technology
    • Example: improvement of existing product (e.g. stretch design of an aircraft)
    • Early design freeze, but some testing, evaluation and corrections in the design or shaping of the product
    • Have to wait a little bit longer to freeze design.
  3. High-tech project
    • Integration of several new technologies (e.g. CGI)
    • Examples: large development project; new product generation specifications must remain
    • flexible for a longer period of time to allow for optimal trade-offs
    Much later design freeze and extended development period. Normally towards middle of project life cycle.
  4. Super high-tech project
    • Integration of several non-existing technologies
    • Examples: Arpanet project (development of internet based on packet switching technologies), Apollo Moon Landing
    • Extensive periods to develop and prove the new, not-yet existing technologies
    • Very rare to have a type D in real life.
    • Very late design freeze planned at the start
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Technology example

A

Airbus A380
• Several new technologies integrated
• Composite materials (e.g. carbon fibre reinforced plastic)
• Final design configuration not frozen until as late as Spring 2001
• (April 2005 – First flight)
• High tech and in between platform and breakthrough.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Complexity?

A
  • How complex is the system and its subsystems?
  • Measures the complexity of the project (not product)
  • 3 levels of complexity
  • Complexity affects the project organisation (level of bureaucracy and formality needed to manage it).
  • Key challenge is ‘systems integration’.
  • The more complex the system, the bigger the challenge.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Complexity levels?

A
  1. Assembly - self contained component e.g. post it notes
  2. System - single system with multiple functions but a common goal e.g. aircraft
  3. Array - systems with independent functions but each with a common goal e.g. airport
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Complexity example: Heathrow terminal 5

A

Array project:
• 16 major projects
• 147 sub-projects
• Biggest construction at the time in Europe
• 4 ½ billion pounds
• At peak nearly 6000 workers on site
• Redesigned roof to update security system after 9/11
• Workers had iris scans and finger scans to get onto construction site
• delivered on time and on budget (3 days early)
• No one died
• From quality perspective, won a few awards, one of top 10 terminals in the world in regard to shopping and quality standards.
• Planned for 20/26 years
• Up until now everything was good un till, during transition period moving from pm state to operational state, issues occurred with baggage and staff.
• Cost them over 40 million
• 40,000 bags lost
• Took 20 days to sort out
• 300 flights cancelled
• Terminal 2 learnt from this and gradually increased numbers of passengers.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Pace

A
  • How critical is the time frame?
  • 4 levels of pace
  • Every day you’re late costs money.
  • Things can obviously change, you could think it’s a regular project and then competitor starts working on same thing so end up becoming a fast project.
  • Olympics was originally time-critical but then got so behind it led to a blitz project.
17
Q

Pace levels?

A
  1. Regular - time not critical to organisational success e.g. Public works
  2. Fast/competitive - completion on time is important to competitiveness e.g. business related projects
  3. Time critical - time is critical for success e.g. Olympics
  4. Blitz - Must be completed asap e.g. Natural disaster
18
Q

Pace: Impact on PM style

A
  • The planning and reviews (Need stakeholder meetings. In blitz would have to rely on previously made contingency plans)
  • The autonomy of the project team
  • Involvement of top management (particularly on urgent projects) – more senior involved
19
Q

Diamond Model in action

A

• Model is normally used internally, to get a clear understanding of project. You would then discuss with key stakeholders if they agree because this would obviously have impact on how you manage project. E.g. do you draw up on design and freeze it or consider many designs and freeze later.

  • Unsuccessful projects (‘level of fit’)
  • Gaps between the diamond shape of the project’s required characteristics and
  • The diamond shape of the actual management style used (perceived, conceptualised)
  • Gaps (partly) explain why projects fail or do not achieve their full potential
20
Q

Evaluating the DM:

A
  • Would need to actually have a discussion about the model – not just a process of drawing it
  • May not perfectly fit within the sub-dimensions
  • Needs to be used in a dynamic way, not static
21
Q

Novelty benefits/risks

A

+ exploding new markets
+1st mover advantage

  • difficult to predict exact market needs
  • attracting competitors to copy ideas
  • missing sales targets
22
Q

Pace benefits/risks

A

+ mounting quick response
+ gaining early market introduction

  • missing deadlines
  • making haphazard mistakes
23
Q

Complexity benefits/risks

A

+ bigger programs, bigger pay offs

  • difficult to coordinate and integrate
24
Q

Impacts of each?

A
  • More technology the later design freeze and more design cycles
  • More novel the less market data and later required design freeze
  • More complex the more complex the org and formality in decision making and communication
  • Faster pace the more autonomy of pm from firm
25
Q

Technology benefits/risks

A

+ improving performance functionality

  • lacking needed skills
  • experiencing technology failure
26
Q

(Shenhar, 2001) findings:

A
  • projects have many variations its not one size fits all.
  • as scope increases projects are managed with additional attention to planning.
  • management should adopt a more specific approach to to PM.
  • should add a more formal step of project classification, that should affect choice of PM, team members and skills needed.
27
Q

(Davies et al, 2008) findings:

A
  • T5 collaborated with BAA (Birstish airport authority) (IT systems) and Laing O’Rourke.
  • BAA’s continuous improvement project process (CIPP) was developed to provide a set of standardised and reputable time sequenced tasks.