System and method for managing end to end agile delivery in self optimized integrated platform
US-2019243644-A1 · Aug 8, 2019 · US
US12327097B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12327097-B2 |
| Application number | US-202418430529-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 1, 2024 |
| Priority date | Sep 18, 2019 |
| Publication date | Jun 10, 2025 |
| Grant date | Jun 10, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A software project management system can store object data about components of a software development project, such epics, features, and stories. The software project management system can also store dependency objects that reflect dependency relationships between two or more components of the software development project. The dependency objects can track status information about the dependency relationships, including expected completion dates, acceptance criteria, and state indicators. The information stored in the dependency objects can be updated over time as information about the dependency relationship changes. The software project management system can also use the dependency objects to display information in a user interface about one or more dependency relationships, such as to indicate which dependency relationships are on track or behind schedule.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method, comprising: maintaining, by a software project management system, a plurality of dependency data objects that respectively represent dependency relationships between components of a software development project, wherein: the plurality of dependency data objects are distinct from component data objects, maintained by the software project management system, that respectively represent the components of the software development project, and an individual dependency data object of the plurality of dependency data objects; represents an individual dependency relationship between two or more of the components of the software development project; identifies the component data objects that represent the two or more of the components; and comprises a state indicator that indicates a current state of the individual dependency relationship; detecting, by the software project management system, changes to the dependency relationships over time; automatically updating, by the software project management system, data stored in the plurality of dependency data objects based on the changes to the dependency relationships; and displaying, by the software project management system, and based on the plurality of dependency data objects, information associated with one or more of the dependency relationships in a user interface, wherein the information displayed in the user interface indicates current states of the one or more of the dependency relationships based on state indicators of the plurality of dependency data objects. 2. The computer-implemented method of claim 1 , wherein the information displayed via the user interface in association with a particular dependency relationship, based on a corresponding dependency data object of the plurality of dependency data objects, comprises one or more data types comprising at least one of: a name of the particular dependency relationship, a project identifier associated with the particular dependency relationship, portfolio information associated with the particular dependency relationship, an owner of the particular dependency relationship, progress information associated with the particular dependency relationship, or a date associated with the particular dependency relationship. 3. The computer-implemented method of claim 2 , wherein: the user interface displays instances of the one or more data types associated with multiple dependency relationships, and the information displayed via the user interface is at least one of filterable or sortable based on the one or more data types. 4. The computer-implemented method of claim 1 , wherein the user interface displays the information in association with at least one of: program increments associated with the one or more of the dependency relationships, or suppliers associated with the one or more of the dependency relationships. 5. The computer-implemented method of claim 1 , wherein the user interface displays visual representations of multiple dependency relationships, in association with multiple groups corresponding to multiple possible states of the dependency relationships, based on the state indicators of the plurality of dependency data objects. 6. The computer-implemented method of claim 5 , wherein at least one of the visual representations, associated with a particular dependency relationship, presents a warning indicator of an issue associated with the particular dependency relationship. 7. The computer-implemented method of claim 1 , wherein: the user interface displays visual representations of: the components, and the dependency relationships between the components, and the visual representations are associated with corresponding program increments. 8. The computer-implemented method of claim 1 , wherein the information displayed via the user interface: comprises one or more data types, and is displayed as a timeline representation of instances of the one or more data types, associated with at least one of the dependency relationships, based on date information indicated by the plurality of dependency data objects. 9. The computer-implemented method of claim 1 , wherein the changes include at least one of: a changed date associated with a dependency relationship, a changed state of the dependency relationship, or a division of a component associated with the dependency relationship into multiple components. 10. The computer-implemented method of claim 1 , further comprising: identifying, by the software project management system, types of the changes, and sending, by the software project management system, notifications of the changes to entities, identified by the plurality of dependency data objects, associated with the types of the changes. 11. A computing system, comprising: one or more processors; and memory storing computer-executable instructions that, when executed by the one or more processors, cause the computing system to: maintain a plurality of dependency data objects in association with a software project management system, wherein: the plurality of dependency data objects represent dependency relationships between components of a software development project, the plurality of dependency data objects are distinct from component data objects, maintained by the software project management system, that respectively represent the components of the software development project, and an individual dependency data object of the plurality of dependency data objects: represents an individual dependency relationship between two or more of the components of the software development project; identifies the component data objects that represent the two or more of the components; and comprises a state indicator that indicates a current state of the individual dependency relationship; detect changes to the dependency relationships over time; automatically update data stored in the plurality of dependency data objects, based on the changes to the dependency relationships; and display, based on the plurality of dependency data objects, information associated with one or more of the dependency relationships in a user interface associated with the software project management system, wherein the information displayed in the user interface indicates current states of the one or more of the dependency relationships based on state indicators of the plurality of dependency data objects. 12. The computing system of claim 11 , wherein the information displayed via the user interface in association with a particular dependency relationship, based on a corresponding dependency data object of the plurality of dependency data objects, comprises one or more data types comprising at least one of: a name of the particular dependency relationship, a project identifier associated with the particular dependency relationship, portfolio information associated with the particular dependency relationship, an owner of the particular dependency relationship, progress information associated with the particular dependency relationship, or a date associated with the particular dependency relationship. 13. The computing system of claim 11 , wherein the user interface displays the information in association with at least one of: program increments associated with the one or more of the dependency relationships, or suppliers associated with the one or more of the dependency relationships. 14. The computing system of claim 11 , wherein the user interface displays visual representations of multiple dependency relationships, in association w
Requirements analysis; Specification techniques · CPC title
Structural analysis for program understanding · CPC title
Workflow collaboration or project management · CPC title
Dependency analysis; Data or control flow analysis · CPC title
Resource planning, allocation, distributing or scheduling for enterprises or organisations · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.