Re: When user doesn't exist.
- --- In email@example.com, "chuckspublicprofile" <chuck-
> 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.
> maybe just a well respected team member. It's the PO's job toknowledge
> maximize ROI. Sounds like you might have to fake the ROI for now.
> 2. Do the simplest thing that could POSSIBLY work given the
> you do have about the potential user community. Anything more islike
> potential waste.
> 3. Consider focusing on the most highly demo-able features first.
> i.e. what features do you think your prospective customers would
> to see first, and which features make you different from any otherIn addition to the advice from Charles, I suggest the team and the PO
> product. My guess is user authentication and authorization does not
> make your product unique in any way.
> Charles Bradley
jointly produce an initial product vision, envision user types or
personas and perform a user story workshop where user storuies ar