ProjectRot

From SPA Wiki

Jump to: navigation, search

See also http://builder.com.com/article_guest.jhtml?id=u00420020417jmo01.htm


Contents

total top 13 project rot symptoms

  1. missing deliveries (11 votes)
  2. loss of sponsor (11)
  3. no vision (11)
  4. silence (9)
  5. overtime (9)
  6. bad communication (9)
  7. cannot demo (8)
  8. cover your ass (8)
  9. deviation from process (8)
  10. no time (8)
  11. more planning than doing (7)
  12. process dissonance (7)
  13. no fun (6)

top 11 symptoms of group 1

  1. silence
  2. missing deliveries
  3. overtime
  4. lack of sponsor support
  5. people do their own things
  6. no vision
  7. no time
  8. increasing acceptance of failures
  9. many decisions reopened
  10. throwing more resources at the problem
  11. loss of customer

top 10 symptoms of group 2

  1. bug list bloom
  2. increasing frequency of management meetings
  3. no regular deliveries
  4. loss of sponsor
  5. increasing changes
  6. practices being dropped
  7. no elevator pitch
  8. "don't understand the architecture"
  9. increasing hours
  10. some tasks, believed easy, become hard

top 10 symptoms of group 3

  1. visionary leaves
  2. no communication
  3. deviation from process
  4. blame storm
  5. more planning than doing
  6. no vision
  7. long hours
  8. short hours
  9. high turnover
  10. regular meetings stop

top 12 symptoms of group 4

  1. lack or loss of sponsor (aka lack/sponsor/loss)
  2. unmanaged risk
  3. failure to staff correctly
  4. poor communications
  5. poor or no planning
  6. poor morale
  7. too much new stuff
  8. scope creep
  9. inappropriate use of tools
  10. uncohesive team
  11. "over the wall"
  12. poor working environment

top 11 symptoms of group 5

  1. no time
  2. meta-meeting
  3. working long
  4. dilbert count
  5. cafeteria
  6. cover your ass
  7. cannot demo
  8. process dissonance
  9. absenteeism
  10. not my job
  11. 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
  1. 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