Skip to content

Define MVP #12

@leesharma

Description

@leesharma

We should decide on the scope of our MVP and start tracking the issues that will get us there.

I know the list will change, but by laying out more or less what we need to accomplish to hit that first milestone, we'll be able to gauge our progress and estimate release dates. It'll also be easier to grab a new task when we're done with out current one–less explicit communication needed.

To complete this task, we need to do three things:

  • Come to a consensus on our MVP scope
  • Break that down into tasks
  • Put them into issue tracking

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions