You can achieve project goals in different ways, therefore only the presence of a certain process allows to make it controllable and reproducible (the so-called mature process). The process determines terminology, use of particular project artifacts, their lifecycles, relationships between artifacts, metrics, and reporting.
Lifecycle of the primary requirements or their enhancements (implementation) reflects production technology of software products. Distribution of requirements into production stages makes project progress transparent, and you can see it on issue boards, story boards, and charts. Standard stages: Backlog, Analysis, Design, Development, Testing, Documenting. New useful project artifacts are created on each of these stages.
Lifecycle of the business and system requirements, as well as lifecycle of the test and operational documentation reflect preparedness of these project artifacts used on different production stages of software product. Standard stages: New, In progress, Waits for approval, Approved, Finished.
Lifecycle of the tasks reflects progress of work on project artifacts and usually contains next stages: New, In progress, Completed. Sometimes a control stage is also used, which allows leader or senior colleague to check quality of task implementation.
Stages of different project artifacts are interconnected (synchronized) by means of system actions. For example, you can automatically transfer the custom requirement to its next status when the certain tasks are completed. Or, for example, you can mark a requirement as implemented if all its enhancements are completed.