How To Be SMART

Common Team Goals

  • Product:
    • Make the user interface less confusing
    • Speed up the app
    • Clean up the CSS
  • Process:
    • Find a better way to manage the backlog
    • Improve meeting attendance

What's Wrong?

  • You can't tell when you're done
  • You can't tell if you made things better
  • You can't tell if you focusing on the right thing

How to be SMART

  • Set goals that are
    • Specific, i.e., focused, concrete
    • Measurable, i.e., you know where you're at, and when things change
    • Attainable, i.e., "failure is not an option" is not an option
    • Relevant, i.e., about delivering value, not following procedure
    • Timeboxed, i.e., deadlines for re-evaluation
  • SMART goals Agile Flash Card

Example Goal #1, SMART version

  • Make the user interface less confusing
  • Not specific, measurable, or timeboxed
  • Specific: reduce user use of "save" when they mean "submit"
  • Measurable: no more than 10% of new forms left unsubmitted more than 1 day after completion
  • Timeboxed: if target not met by new UI in 2 weeks, re-evaluate UI

Your Turn

  • Make user interface less confusing
  • What would be a SMART goal?
  • Trouble with meeting attendance
  • What would be a SMART goal?

How to be SMART

  • For every goal
    • Define one or relevant metrics
      • things you can measure
    • Set a realistic target
      • something other than perfect
    • Set a time to achieve the target or try something else
    • Start measuring
      • instrument the code or process as needed
    • Repeat while there's still a problem
    • Stop
  • You can't control what you can't measure -- Tom DeMarco

SMART Retrospective Analysis

SMART Retrospective Analysis

http://gifmaker.me/