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

Re: When user doesn't exist.

Expand Messages
  • Arne Ahlander
    ... Or, ... knowledge ... like ... In addition to the advice from Charles, I suggest the team and the PO jointly produce an initial product vision, envision
    Message 1 of 9 , Sep 24, 2008
    • 0 Attachment
      --- In scrumdevelopment@yahoogroups.com, "chuckspublicprofile" <chuck-
      lists2@...> wrote:
      >
      > My advice.
      >
      > 1. Find someone to take the role of the Product Owner, who can make
      > executive decisions about what to develop. Surely a boss could do
      > this, or someone on your team could proxy to the boss to do this.
      Or,
      > maybe just a well respected team member. It's the PO's job to
      > maximize ROI. Sounds like you might have to fake the ROI for now.
      >
      > 2. Do the simplest thing that could POSSIBLY work given the
      knowledge
      > you do have about the potential user community. Anything more is
      > potential waste.
      >
      > 3. Consider focusing on the most highly demo-able features first.
      > i.e. what features do you think your prospective customers would
      like
      > to see first, and which features make you different from any other
      > product. My guess is user authentication and authorization does not
      > make your product unique in any way.
      >
      > Charles Bradley
      >
      >

      In addition to the advice from Charles, I suggest the team and the PO
      jointly produce an initial product vision, envision user types or
      personas and perform a user story workshop where user storuies ar
      produced.

      Arne Ã…hlander
    Your message has been successfully submitted and would be delivered to recipients shortly.