ProjectRot
From SPA Wiki
See also http://builder.com.com/article_guest.jhtml?id=u00420020417jmo01.htm
Contents |
total top 13 project rot symptoms
- missing deliveries (11 votes)
- loss of sponsor (11)
- no vision (11)
- silence (9)
- overtime (9)
- bad communication (9)
- cannot demo (8)
- cover your ass (8)
- deviation from process (8)
- no time (8)
- more planning than doing (7)
- process dissonance (7)
- no fun (6)
top 11 symptoms of group 1
- silence
- missing deliveries
- overtime
- lack of sponsor support
- people do their own things
- no vision
- no time
- increasing acceptance of failures
- many decisions reopened
- throwing more resources at the problem
- loss of customer
top 10 symptoms of group 2
- bug list bloom
- increasing frequency of management meetings
- no regular deliveries
- loss of sponsor
- increasing changes
- practices being dropped
- no elevator pitch
- "don't understand the architecture"
- increasing hours
- some tasks, believed easy, become hard
top 10 symptoms of group 3
- visionary leaves
- no communication
- deviation from process
- blame storm
- more planning than doing
- no vision
- long hours
- short hours
- high turnover
- regular meetings stop
top 12 symptoms of group 4
- lack or loss of sponsor (aka lack/sponsor/loss)
- unmanaged risk
- failure to staff correctly
- poor communications
- poor or no planning
- poor morale
- too much new stuff
- scope creep
- inappropriate use of tools
- uncohesive team
- "over the wall"
- poor working environment
top 11 symptoms of group 5
- no time
- meta-meeting
- working long
- dilbert count
- cafeteria
- cover your ass
- cannot demo
- process dissonance
- absenteeism
- not my job
- no fun
causes from group a
more planning than doing
poor planning
reactive management
fear of failure
loss of sponsor
mismatch of vision
anticipated failure
failure to deliver
-> incorrect deliverables
change of sponsor
cannot demo
no integration
no tests
no functionality in focus
poor architecture
-> could result in loss of sponsor
missing delivery
process is too heavy
poor planning
lack of it
no/poor metrics
-> cannot demo
-> more planning than doing
process dissonance
not designed or ad-hoc
wrong process
no buy-in
silence
mis-trust
disappointment
not being heard before
dictating
fear of failure
too busy (time pressure)
-> no fun
-> cover your ass
-> no communication
no fun
no respect
no acceptance
mis-trust
culture
project is going badly, not enjoyable
no sence of being a team
cover your ass
mis-trust
not being heard before
disappointment
head monopoly
repairs of group b
loss of confidence/respect/trust
manage expectations
communicate
lack of clear leadership
introduce leader
blame culture
problem sharing culture
- 0 degree feedback
lack of skills/tools/resources
education/recruitment
no money
cancel
no vision at all
cancel
act of god
deal with devil
solutions of group c
deviation from process
causes
lack of understanding why
too complicated
time pressure
bad morale
solutions
education (two-way)
simplify the process/automate steps
see "better planning" to improve effect of time pressure
cannot demo
causes
poor configuration management
inadequate facilities
scheduling resources
non-incremental (waterfall) delivery
solutions
have versioning strategy
make sure you took work together
internal incremental delivery
schedule regular demos
have dedicated (reference) demo-system
missing deliveries
causes
no time
poor planning
no risk assessment
poor testing
solutions
improve planning by responding to feedback
check check-in intervals
have well-defined features
test-first programming
demo regularly
(do XP)
no vision
causes
no goals
conflicting stakeholders
solutions
publish any arbitrary vision and wait for feedback
help the stakeholders give a simple view
about project repairs
acceptance criteria?
different axes
scale
organisation
team
individual
timescale
nothing we can do
slow influence
slow decisions
quick decisions
immediate
urgency
long term
medium term
now
