Home | Login | Recent Changes | Search | All Pages | Help

StartingRightSummaryOfPresentations

First Team

Add

  • Robust risk assessment at start of project
  • Access to customers
  • Celebrating the "minor" victories along the way (no such thing as minor victories - teams form around these)
  • Increase meeting productivity
  • Team commitment

Keep

  • Team involvement
  • Great communication between developers, requirement modelers, and architect
  • Review of lessons learned from most recently completed projects (successes and failures)
  • Openness to re-evaluation and redirection
  • Meeting elimination

Remove

  • Blaming sessions
  • Pointy haired boss's "motivational speech" at project kick-off meeting
  • Multiple communication channels between management and team. Give us *one open* forum, with difinitive checkpoints
  • Senior management inconsistency
  • Anger, Frustration, Confusion

  • More ongoing coaching on the agreed-upon development process for those weren't used to it
  • My own behavior
  • Stated goal of what consititutes success
  • Remove personnel problems/conflicts
  • Reduce simultaneous pressure from other projects

Second Team

  1. Communications is critical to all areas
  2. Strategic = Add/Remove things at Sr. Mgmt. level including acceptance of risks (e.g., reorgs), oblivious to risks, detrimental interventions

    Tactical = Happy with our teams

  3. Add/Modify Management enablers (contract acceptance, budget)

  4. Process enabler to id and mitigate risk
  • keep a good process
  • modify or add measures to better implement that process
  1. Communication enablers/disablers
  • distance
  • division of work
  • intergroup coordination
  • peer feedback

Third Group

Fourth Group

  • Management forced people to lie to customers
  • Remove certain individuals who don't fit
  • Don't remove relationships or people who do fit including ones with experience
  • Start testing early and often and effectively (programs/hardware, process)
  • Checkpoints built in from start
    • requirements creep
    • cost creep
    • schedule creep
    • truth about progress
  • We were told "No need to think about this"
  • Choose tools that fit


Updated: Sunday, November 18, 2001