Agile Common Ontology

Agile – Functional Data Structure

1. Agile Project will have many releases.

Release 2. Each Release will have many Sprints (Iterations)

3. Each Sprint will be delivering many cards

Sprint
4. Cards will have different relationships and relevant hierarchies
(Theme – Epic – User Story , Defects Traced To User Story)
Cards Cards
5. Each card will have many ToDos (Tasks to be performed)

Resource ToDo Value Stream 6. Each ToDo will have many timelogs in terms of daily Actuals and
remaining hours

TimeLog 7. Cards flows through defined value stream (Lanes/Stages)

8. Cards are owned by Resource and they work on individual ToDos

Release May or May not be there. (Tasks) and updates actuals hours and remaining hours on a daily
Sprint May or May not be there. basis
If Both Release and Sprint are there then 1 release 9. On Completing the work relevant to a given stage , the cards
can have multiple sprints are moved to the next stage (queue)
 Release
Attribute Type Description
Release ID Direct Release Identifier
Project ID Direct Project Identifier to which release belongs
Release Name Direct Name Of the Release
Release Start Date Direct Start Date For the Release
Release End Date Direct End Date For The Release
Release Capacity Direct Capacity Of the Release Planned in Story Points (Or Equivalent Effort
(Planned) Number ???)
Release Actual Derived Actual Number of Story Points (or equivalent effort number) delivered in the
Velocity release
No. Of Sprints Derived Number Of Sprints Planned For the release
Release Duration Derived Number of days for Release (End date – start date)
 Sprint
Attribute Type Description
Sprint ID Direct Sprint Identifier
Release ID Direct Release Identifier to which this sprint belongs
Project ID Derived Project Identifier to which release belongs
Sprint Name Direct Name Of the Sprint
Sprint Start Date Direct Start Date For the Sprint
Sprint End Date Direct End Date For The Sprint
Sprint Capacity Direct Capacity Of the Sprint Planned in Story Points (Or Equivalent Effort Number
(Planned) ???)
Sprint Actual Derived Actual Number of Story Points (or equivalent effort number) delivered in the
Velocity Sprint
Sprint Duration Derived Number of days for sprint (End date – start date)
 Cards
Attribute Type Description
Card ID Direct Card Identifier
Card Type Direct Type Of Card (User Story , Issue, Defect , EPIC, Theme, Feature , Ticket etc.)
Sprint ID Direct Sprint Identifier in which the card is planned
Release ID Direct Release Identifier to which card belongs
Project ID Derived Project Identifier to which card belongs
Card Name Direct Name Of the Cards
Card Tags Direct Tags available on card for classification ..Not available in SwiftEnterprise
Card Size Direct Size Of the Card (T-Shirt Size or Normalized Effort ???)
Card Priority Direct Urgency Of the card
Card Owners Direct Resources who are owning the card (one to Many)
Card Service Classification Direct Classifying the service offered (Expedite, Normal etc.- TBD0 ..Not available
in SwiftEnterprise
Card Estimates Direct Effort Estimated For completing the card
Card Remaining Effort Derived Remaining Effort of all the ToDos belonging to Card
Card Actuals Derived Actual Effort Spent in completing the card
 Cards
Attribute Type Description
Card Rank Direct Rank Assigned to the Card
Card due Date Direct Expected completion date for the Card
Card Block Count Derived Number of times the card was blocked
Card Work Time Derived Time spent when the card was in “In Progress” lane/stage ..Not available
in SwiftEnterprise
Card Wait time Derived Time spent when the card was in “Wait/Ready” lane/stage ..Not
available in SwiftEnterprise
Card Block Time Derived Time Spent when the Card was in “Blocked” State
Card Cycle Time Derived Time Taken to complete the card once started
Card Status Direct Status = Backlog, Started , Blocked, Done , Archived, Aborted
Card Defect Count Derived Number Of Defects/Issues identified for the card
Card Defect Resolution Effort Derived Effort Spent on resolving Defects/Issues related to the card
Card Progress Percentage Derived Based on ToDo completion or Child Card completion
Card Description Direct Description of the card
Parent Card ID Derived Parent Card to which this card belongs ..(Avaiable only for Userstory, not
available for custom agile forms)
 Card
Note : Parent Cards derive progress indicators, effort and time rollups from child cards
Sprint Cards = User Stories, Defects , Issues, CR , Ticket etc
Non Sprint Cards = EPIC, Theme , Feature
Sprint Cards can have a Parent
 ToDos
Attribute Type Description
ToDo ID Direct ToDo Identifier
Card ID Direct Card Identifier to which ToDo Belongs
Sprint ID Derived Sprint Identifier in which the card is planned
Release ID Derived Release Identifier to which card belongs
Project ID Derived Project Identifier to which card belongs
ToDo Name Direct Name Of the ToDo
ToDO Owner Direct Resource working on the ToDo
ToDo Lane Direct Value Stream Lane Name to which ToDo Belongs ..Not available in
SwiftEnterprise
ToDo Estimates Direct Estimated Effort For ToDo
ToDo Remaining Direct Remaining Hours for the ToDo
ToDo Actuals Direct Actual Effort Spent For the ToDo
ToDo Due Date Direct Expected Completion Date for the ToDo ..Not available in SwiftEnterprise
ToDo Status Direct/Derived Status Of the ToDo – Pending , Started , Completed ..Derived in SE
 TimeLogs
Attribute Type Description
Timelog ID Direct Timelog Entry Identifier
ToDo ID Direct ToDo Identifier for which the timelog entry belongs
Card ID Derived Card Identifier to which ToDo Belongs
Sprint ID Derived Sprint Identifier in which the card is planned
Release ID Derived Release Identifier to which card belongs
Project ID Derived Project Identifier to which card belongs
TimeLog Date Direct Date Of the Timelog
Resource ID Direct Resource Identifier who is filling the Timelog
Actual Effort Direct Actual Effort filled for that timelog
Remaining Effort Direct Remaining Effort Filled For that timelog
 Card Value Stream Data
Attribute Type Description
Card ID Direct Card Identifier
Sprint ID Direct Sprint Identifier in which the card is planned
Release ID Direct Release Identifier to which card belongs
Project ID Direct Project Identifier to which card belongs
Value Stream Direct Swim Lane Name
Queue Name Direct Name Of the Lane/Queue
Queue Type Direct Ready/Work/Wait/Done ..Not available in SwiftEnterprise
Entry Time Direct/Derived Time when the Card arrived in this queue..Derived in SE
Exit Time Direct/Derived Time When the card Exited from this Queue..Derived in SE
Time Spent Derived Time Spent in the Queue by card
Effort Spent Derived Effort spent in the queue by resource – derived from ToDo Queue..Not
available in SwiftEnterprise
Block Count Direct/Derived Number Of Times Card was blocked when in this Queue..Derived in SE
Block Time Derived Amount of Time Card was blocked in this queue
 Card Flag Data
Attribute Type Description
Card ID Direct Card Identifier
Sprint ID Direct Sprint Identifier in which the card is planned
Release ID Direct Release Identifier to which card belongs
Project ID Derived Project Identifier to which card belongs
Value Stream Direct Swim Lane Name
Queue Name Direct/Derived Name Of the Lane/Queue..To be derived
Queue Type Direct Ready/Work/Wait/Done..Not available in SwiftEnterprise
Flag Type Direct Block/Issue/RisK/Flag..Not available in SwiftEnterprise
Flagged On Direct/Derived Time when the card was flagged..To be derived
Unflagged On Direct/Derived Time when the card was flagged..To be derived
Time Spent Derived Time Spent in the Flagged state
Flagged By Direct/Derived Resource Who flagged the card..To be derived
Unflagged By Direct/Derived Resource who unflagged the card..To be derived