Skip to content

DOC: User Stories #2

@westurner

Description

@westurner

For me, the first part of a project is defining the functionalities of the app: creating a specification, developing a spec, spec'ing the app.

For many projects, User Stories and Tests are enough.

Stories can be tracked as separate Issue tickets and grouped together in milestones and project boards (like Kanban); or as a version-controlled document (README.rst, docs/) with references (links (!)) to each issue with a STORY label.

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