Some factors that cause projects to fail?

Kom i gang. Det er Gratis
eller tilmeld med din email adresse
Some factors that cause projects to fail? af Mind Map: Some factors that cause projects to fail?

1. RIGID PLANS: timeline/budget is not adapted when new insights into problem/solution are uncovered

1.1. initial estimate is too low and plan is not sufficiently corrected with new insights

1.1.1. Some agile remedies: adaptive planning plans are not static but adapted accordingly test early your assumptions and use tight inspect/learn/adapt loop front-load high risk exposure front-load highest customer value seek the 20-80 zone early

1.2. estimates and reestimates are continually on low side

1.2.1. Some agile remedies: Use reference class forecasting instead of absolute effort estimation to move us statistically into the middle Reduce the (absolute) size of the estimation variation by working on smaller projects Make estimation assumptions more visible/transparent what has been accounted for and what hasn't which should provide justification for more or less contingency

2. INDECISION & DENIAL: excessive time taken to realise that cost of suitable solution > org budget appetite or > projected benefits

2.1. desired solution keeps growing or morphing

2.2. black swans are uncovered

2.3. Some agile remedies:

2.3.1. Reward/celebrate decisions to stop projects that going west early

3. INEFFECTIVE PROGRESS: progress is slower than expected

3.1. quality problems cause rework and failure demand

3.1.1. due to poor foundational work and rigour Some agile remedies: simple but malleable foundation

3.1.2. due to legacy technical debt Some agile remedies: build quality in (BQI) plan

3.2. people don't have the right skills/experience

3.2.1. Some agile remedies: don't commit until you have the right people onboard

3.3. people aren't given the right access to systems, tools, environments, etc. needed

3.3.1. Some agile remedies: aggressively address impediments proactive risk mitigation thin end-to-end slices to ensure everything is in order

3.4. people are disengaged

3.4.1. Some agile remedies: sustainable pace seek to grow individual and team intrinsic motivation self-organising teams servant leadership clear and inspiring mission shared ownership trust, relatedness and psychological safety competency and mastery sufficient focus time (personal flow) ability to make meaningful progress and few setbacks continuity of work stable goals stable teams

3.5. people turnover

3.5.1. Some agile remedies:

3.6. ineffective operating model

3.6.1. slow decisions Some agile remedies: decentralised decision making structure

3.6.2. too much waiting time between tasks Some agile remedies: alignment of teams to customer value stream too many hand-offs Some agile remedies:

3.6.3. competition/disharmony between teams/mgmt information hording within teams uneven spread of information among teams lack of alignment between teams in fighting Some agile remedies: shared ownership of a single prioritised backlog a clear view on the upcoming pipeline of work effective leadership collaboration over competition values

3.6.4. slow/difficult communication between teams Some agile remedies: information radiators collaboration over contract negotiation values

3.6.5. information distortion (e.g, effects of chinese whispers) Some agile remedies: remove the middleman information radiators

3.6.6. information and capability loss Some agile remedies: information and capability redundancy (2 bus rule)

3.7. lack of focus

3.7.1. people are time-sliced Some agile remedies: reject time-slicing as a valid option

3.8. lack of a clear and common direction

3.8.1. competing priorities

3.8.2. people not working on most important things first disregarded plan vague plan

3.8.3. Some agile remedies:

3.9. Some agile remedies:

3.9.1. continuous learning mindset

4. UNSUITABLE SOLUTION: delivered solution is not fit for purpose

4.1. lack of early/often feedback loops

4.1.1. technical

4.1.2. customer/market

4.1.3. Some agile remedies: tight test and learn loops close customer collaboration early technical exploration