Models provide are beneficial when the solution has a perceived complexity, and may be used as a shared understanding when the project is composed by distributed teams. However, the use of models needs contextualization for agile-oriented backlog items. This paper proposes a process for modeling in UML a set of "just-enough" requirements and a candidate architecture, ending with a set of user stories included in a team backlog.