Loading ...
Sorry, an error occurred while loading the content.

Re: [chicago-agile-dev] Why can't you use XP with multiple customers?

Expand Messages
  • extreme-programming@m.gmane.org
    Brad Appleton writes: ... Working in a shop where it is projects/person rather than the other way around, I have thought about
    Message 1 of 6 , Nov 8, 2002
    • 0 Attachment
      Brad Appleton <brad@...> writes:

      <snip/>
      > what worked well for us to get 'one voice' from those
      > customers was something called "Normative Voting". everyone
      > gets "100 points" to "vote" with. They have to distribute their
      > 100 points across the existing hot-list items plus any newly
      > requested (petitioned) items. They may split up their points
      > across these items however they see fit (but no 'fractional'
      > splits are allowed - whole numbers of points only - The number
      > of points they assign to an item represents the percentage of
      > their overall priority that it is.) All the points are tallied
      > up and a new priority order is defined by the results of the
      > weighted votes. Whatever is at the bottom, and/or below a
      > certain threshold falls off the list.
      >
      > That assumes every customer rep has equal weight/influence. We
      > actually considered letting each rep have a number of points
      > proportional to their financial contribution - but we decided
      > not to do that. Maybe it would have been good, or maybe it
      > would have been awful. (I dunno)

      Working in a shop where it is projects/person rather than the other
      way around, I have thought about similar ideas.

      Has anyone experimented with letting "less equal" voters save up their
      votes from iteration to iteration so they can occasionally get on the
      hot list.

      -Jason

      <snip/>

      --
      Jason L. Almeter
      Not speaking for my employer.
    Your message has been successfully submitted and would be delivered to recipients shortly.