How the pieces fit together
To build conference registration, a team might create an epic called “Let attendees book workshops”. One story could be “As an attendee, I can choose a workshop when I register”. A technical task supporting that story could be “Store each workshop’s capacity in the database”.
This hierarchy connects a broad outcome to work small enough to finish.
The labels are not universal laws
Teams use these labels differently. Some add initiatives above epics or features between epics and stories; others use tasks for all work. What matters is knowing the outcome, breaking work into manageable pieces, and deciding how each piece will be considered done.