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.
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.