Skip to main content
Project Management

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 1
    Ok so what you are proposing is to jump into dev as it is and eventually the undiscovered user-stories will appear. Understood, that was in fact my initial thought. Commented Mar 7, 2019 at 8:58
  • 2
    @TiagoMartinsPeres I wouldn't say "jump right into dev". You should do some work up-front to understand the user problems and needs and translate those into some kind of requirements (such as user stories, with acceptance criteria, that are at a sufficient level to build). You can order those by priority or importance or relative value to users and then look at adding in technical dependencies (which may reorder some of the work) and now that you have a backlog of work, start iterating on that. Commented Mar 7, 2019 at 10:18