1264
Comment:
|
1383
|
Deletions are marked like this. | Additions are marked like this. |
Line 5: | Line 5: |
* 2022 - [[https://youtu.be/uETgdK8qRWs|YouTube-JoeJustice]] | |
Line 6: | Line 8: |
* https://www.agilealliance.org/glossary/three-qs/ |
Agile
2022 - YouTube-JoeJustice
https://blog.polyverse.io/how-we-build-software-at-polyverse-49bbd86d817
- Symantic versioning view.
Ticket / Task types
- Epic: uppermost unit of work that can span several months and many development teams. Examples of Epics are "PWA mobile app" and "new framework"
- Feature: a child of an Epic, it is typically used to deliver a self-contained set of features that can be delivered in a Sprint or two
- User Story: a child of a Feature, it represents a complete "story" of a user as they interact with our platform (e.g. As a user of Vigor, I wish to have a logout link so that my session remains secure). It should be fully implemented within a Sprint
- Task: a child of a User Story, it represents the smallest unit of work assigned to a single individual. It an span no more than 2 days.
- Issue: any bug that requires remediation. An issue is a means of tracking abnormalities
- Security Event: a piece of work that relates to mitigating a security-related matter that was reported by a user and that may compromise the security of their account.
...