On Mon, Oct 19, 2015 at 1:37 PM, Stephen Michel <stephen.mic...@tufts.edu> wrote:
> On Mon, Oct 19, 2015 at 3:29 PM, Jason Harrer <jazzyeagl...@gmail.com> > wrote: > > > If we keep changing everything and second guessing and changing > everything, we're never going to launch. > > > This is a really good point. How do people feel about setting up sprints / > (in)formal deadlines for feature discussion? Or just some procedure for > closing a topic for discussion, as we get closer to finishing the design of > our MVP / beta launch? > > I honestly feel deadlines could be a beneficial thing, not because nothing is getting done (plenty is getting done!), but rather it helps us to focus and determine what truly must get done before we go live. Although these conversations and recommendations are nice, at some point, we need to just stick with a mechanism (and I think at this point we kind of did that) and actually try it out and see how things work. I don't think any particular method will be 100% perfect out of the gate, nor have I heard anyone to claim they will be. In fact, Aaron has talked about the beauty of being able to analyze and tweak things after we go live on a continual basis, in order to find our best practice.
_______________________________________________ Discuss mailing list Discuss@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/discuss
