title: Handling conflicting priorities and expectations in project development
body: <p>There are any number of situations in the standard day where priority conflicts exist for projects.  Management wants maximum productivity from employees.  Marketing wants maximum salability and fast turnaround.  Ownership wants maximum profit.  Customers want usability and low cost.  Regardless of the origin of the demands, time and money are always the limiting factor in business.  </p>
  
  <p>Sometimes project elements have intrinsic or goodwill benefits for which there is not a hard, fast way to measure with monetary means (e.g. arguments for an attractive UI appeal vs. functional but plain).  Other elements of software may have a method of providing “mental breaks” or motivating “cool factor” for developers that can get them back on track on other bigger, complex issues.  While they may sidetrack the project short term they may have greater results long term through improved job satisfaction, etc.  Continued training is a must, but working it in can setup back progress.</p>
  
  <ul>
  <li>What are your suggestions for setting priorities?  How do you evaluate requests/demands on your projects?</li>
  <li>What are your suggestions for communicating and passing those on to your team in a way that they stay focused?</li>
  </ul>