Project visualization system
Patent Information
- Application Number
- IN202244043122
- Authority / Receiving Office
- IN · IN
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2022-01-04
- Filing Date
- 2022-07-27
- Publication Date
- 2026-09-30
- Estimated Expiration
- 2042-07-27
AI Technical Summary
Existing project management visualization tools are limited in their ability to handle complex multi-level dependencies, lack support for hybrid delivery methodologies, and fail to clearly visualize dependencies and impacts across project phases, making it difficult for project managers to effectively plan and coordinate resources.
A project visualization system that uses a data fabric to store and synchronize project data, generating graphical views using data structures that represent project elements and associations, and supports workflows for real-time data updates and customized visualizations, including a view recommendation engine that uses artificial intelligence to suggest suitable views based on natural language problem statements.
Enables project managers to understand and manage complex dependencies, derive insights into project progress, and make data-driven decisions by providing detailed and customized visualizations that are adaptable to various project methodologies and phases.
Abstract
Description
BACKGROUND
[0001] Project management generally refers to techniques to apply processes, methods, skills,knowledge, and experience to lead one or more teams to achieve specific project objectives orgoals within given constraints. For example, the main constraints in project managementtypically relate to scope, time, and budget, and additional challenges may include optimizinghow inputs are allocated and applied to satisfy predefined objectives. Project management maydiffer from routine operations in that project management has final deliverables (e.g., a newproduct launch, an update to a version or feature of an existing product, offering a new service,and / or developing internal work product, among other examples) that are constrained to a finitetimescale and budget. Accordingly, because a project is a complex endeavor designed toproduce a unique product, service, or result with a defined scope (usually time-constrained, andoften constrained by funding or staffing), project management requires significant planning andcoordination, including estimations about project complexity, a quantity and type of resourcesneeded to carry out the project, and / or current and forecasted availability of resources tocomplete the project. To make these estimations accurately and effectively, project professionalswho are tasked with planning the project and coordinating resources to carry out the projecttypically rely upon various project management tools to plan or organize tasks, track progress,and manage time to deliver a successful project.SUMMARY
[0002] Some implementations described herein relate to a method. The method may includereceiving, by a device, project management data that includes information related to projectelements associated with one or more projects and information related to associations among theproject elements associated with the one or more projects. The method may include generating,by the device and based on the project management data, one or more data structures thatrepresent the project elements associated with the one or more projects and the associationsamong the project elements associated with the one or more projects. The method may includereceiving, by the device, a request to visualize project data, where the request indicates a view touse to visualize the project data and specifies criteria related to the project data to be visualizedin the view. The method may include searching, by the device, the one or more data structures toobtain the project data to be visualized based on the criteria specified in the request. The methodmay include rendering, by the device, the project data using the view indicated in the request.
[0003] Some implementations described herein relate to a device. The device may include oneor more memories and one or more processors coupled to the one or more memories. The devicemay be configured to receive project management data that includes information related toproject elements associated with one or more projects and information related to associationsamong the project elements associated with the one or more projects. The device may beconfigured to generate, based on the project management data, one or more data structures thatrepresent the project elements associated with the one or more projects and the associationsamong the project elements associated with the one or more projects. The device may beconfigured to receive, from a client device, a natural language description related to a problemstatement associated with project data to be visualized. The device may be configured toidentify, using an artificial intelligence model, one or more recommended views to visualize theproject data based on an intent associated with the problem statement and one or more projectelements or associations relevant to the intent. The device may be configured to provide, to theclient device, information indicating the one or more recommended views. The device may beconfigured to initiate one or more workflows to render the project data using a view that isselected from the one or more recommended views.
[0004] Some implementations described herein relate to a non-transitory computer-readablemedium that stores a set of instructions. The set of instructions, when executed by one or moreprocessors of a device, may cause the device to receive project management data that includesinformation related to project elements associated with one or more projects and informationrelated to associations among the project elements associated with the one or more projects. Theset of instructions, when executed by one or more processors of the device, may cause the deviceto generate, based on the project management data, one or more data structures that represent theproject elements associated with the one or more projects and the associations among the projectelements associated with the one or more projects. The set of instructions, when executed by oneor more processors of the device, may cause the device to receive a request to visualize projectdata. The set of instructions, when executed by one or more processors of the device, may causethe device to search the one or more data structures to obtain the project data to be visualizedbased on the criteria specified in the request. The set of instructions, when executed by one ormore processors of the device, may cause the device to render the project data using the viewindicated in the request.
[0005] In some implementations, a method comprises: receiving, by a device, projectmanagement data that includes information related to project elements associated with one ormore projects and information related to associations among the project elements associated withthe one or more projects; generating, by the device and based on the project management data,one or more data structures that represent the project elements associated with the one or moreprojects and the associations among the project elements associated with the one or moreprojects; receiving, by the device, a request to visualize project data, wherein the requestindicates a view to use to visualize the project data and specifies criteria related to the projectdata to be visualized in the view; searching, by the device, the one or more data structures toobtain the project data to be visualized based on the criteria specified in the request; andrendering, by the device, the project data using the view indicated in the request.
[0006] In further implementations, the one or more data structures include one or more graphsin which each node represents a project element and in which each edge or connection representsan association between two project elements.
[0007] In yet further implementations, the one or more data structures are searched using arecursive depth-first search technique.
[0008] In yet further implementations, the information included in the project managementdata includes only delta data since a most recent iteration in which the project management datawas pulled from a data fabric that stores the project management data.
[0009] In yet further implementations, the method comprises: receiving, from a client device, anatural language description related to a problem statement associated with the project data to bevisualized in the view; identifying, using an artificial intelligence model, one or morerecommended views to visualize the project data based on an intent associated with the problemstatement and one or more project elements or associations relevant to the intent; and providing,to the client device, information indicating the one or more recommended views.
[0010] In yet further implementations, one or more of a first workflow to generate the one ormore data structures or a second workflow to render the view are initiated based on an inputfrom the client device selecting the view from the one or more recommended views.
[0011] In yet further implementations, the view indicates potential problem areas associatedwith the project data that is rendered in the view or warnings based on the project data renderedin the view having dependencies on other project elements that are associated with one or morepotential problem areas.
[0012] In yet further implementations, the view indicates a composition including directconnections or indirect connections associated with project elements included in the project datathat is rendered in the view.
[0013] In yet further implementations, the view indicates a strength of coupling between typesof project elements included in the project data that is rendered in the view.
[0014] In yet further implementations, the view indicates one or more target project elementshave an impact on a source project element.
[0015] In some implementations, a device comprises: one or more memories; and one or moreprocessors, coupled to the one or more memories, configured to: receive project managementdata that includes information related to project elements associated with one or more projectsand information related to associations among the project elements associated with the one ormore projects; generate, based on the project management data, one or more data structures thatrepresent the project elements associated with the one or more projects and the associationsamong the project elements associated with the one or more projects; receive, from a clientdevice, a natural language description related to a problem statement associated with project datato be visualized; identify, using an artificial intelligence model, one or more recommended viewsto visualize the project data based on an intent associated with the problem statement and one ormore project elements or associations relevant to the intent; provide, to the client device,information indicating the one or more recommended views; and initiate one or more workflowsto render the project data using a view that is selected from the one or more recommended views.
[0016] In further implementations, the one or more data structures include one or more graphsin which each node represents a project element and in which each edge or connection representsan association between two project elements.
[0017] In yet further implementations, the one or more workflows include a first workflow togenerate the one or more data structures for the view that is selected from the one or morerecommended views and a second workflow to render the one or more data structures on a userinterface according to the view that is selected from the one or more recommended views.
[0018] In yet further implementations, the view indicates potential problem areas associatedwith the project data that is rendered in the view or warnings based on the project data renderedin the view having dependencies on other project elements that are associated with one or morepotential problem areas.
[0019] In yet further implementations, the view indicates a composition including directconnections or indirect connections associated with project elements included in the project datathat is rendered in the view.
[0020] In yet further implementations, the view indicates a strength of coupling between typesof project elements included in the project data that is rendered in the view.
[0021] In yet further implementations, the view indicates one or more target project elementshave an impact on a source project element.
[0022] In some implementations, a non-transitory computer-readable medium stores a set ofinstructions, the set of instructions comprises: one or more instructions that, when executed byone or more processors of a device, cause the device to: receive project management data thatincludes information related to project elements associated with one or more projects andinformation related to associations among the project elements associated with the one or moreprojects; generate, based on the project management data, one or more data structures thatrepresent the project elements associated with the one or more projects and the associationsamong the project elements associated with the one or more projects, wherein the one or moredata structures include one or more graphs in which each node represents a project element andin which each edge or connection represents an association between two project elements;receive a request to visualize project data, wherein the request indicates a view to use to visualizethe project data and specifies criteria related to the project data to be visualized in the view;search the one or more data structures to obtain the project data to be visualized based on thecriteria specified in the request; and render the project data using the view indicated in therequest.
[0023] In further implementations, the one or more instructions further cause the device to:receive, from a client device, a natural language description related to a problem statementassociated with the project data to be visualized in the view; identify, using an artificialintelligence model, one or more recommended views to visualize the project data based on anintent associated with the problem statement and one or more project elements or associationsrelevant to the intent; and provide, to the client device, information indicating the one or morerecommended views.
[0024] In yet further implementations, one or more of a first workflow to generate the one ormore data structures or a second workflow to render the view are initiated based on an inputfrom the client device selecting the view from the one or more recommended views.BRIEF DESCRIPTION OF THE DRAWINGS
[0025] Figs. 1A-1G are diagrams of an example implementation described herein.
[0026] Fig. 2 is a diagram of an example environment in which systems and / or methodsdescribed herein may be implemented.
[0027] Fig. 3 is a diagram of example components of one or more devices of Fig. 2.
[0028] Fig. 4 is a flowchart of an example process relating to intelligent dependencymanagement.DETAILED DESCRIPTION
[0029] The following detailed description of example implementations refers to theaccompanying drawings. The same reference numbers in different drawings may identify thesame or similar elements.
[0030] Project management is typically a complex task with many facets, which requiresdistinct technical skills and management strategies. For example, as described above, projectmanagement requires significant planning and coordination, including estimations about projectcomplexity, resources needed to carry out the project, and / or current and forecasted availabilityof resources to complete the project, among other examples. Another challenging issue thatoften arises in project management relates to project dependencies, which are pervasive intechnical and non-technical industries. In a project management context, a dependency is alogical, constraint-based, or preferential relationship between two project elements (which maybe referred to herein interchangeably as work items, tasks, and / or activities, among otherexamples) such that starting and / or finishing a first project element is dependent on a secondproject element starting and / or finishing. For example, a given project will typically involvevarious project elements that need to be started, completed, or otherwise performed in aparticular order (possibly including some project elements that can be performed in parallel),whereby setting out the dependencies in a project is usually crucial to the project succeeding.For example, effectively managing dependencies within a project generally helps both theproject manager(s) and project team(s) work and manage tasks in the best possible order, whichhelps to ensure that a project will be completed on time (or early), within budget (or underbudget), and / or in a manner that satisfies objectives.
[0031] Accordingly, in order to manage increasingly complex large-scale projects that mayinclude hundreds or thousands (or more) of project elements and associations (e.g.,interconnections, links, and / or dependencies) among project elements, project professionals aretypically reliant upon project management tools and applications to help plan, manage, andoptimize resources to satisfy project objectives. For example, to facilitate project managementprocesses, many project management applications incorporate visualization tools (e.g.,flowcharts, timelines, and / or visual planning boards, among other examples) to help projectmanagers and project team members to complete a project on-time, on-budget, and with theexpected quality. For example, existing project management visualization tools include aKanban board that visually depicts project elements at various stages using cards that movebetween columns that represent different stages, a Scrum board that includes data organized incolumns and rows to plan work in sprints (e.g., repeatable time-boxes in which a project teamcreates deliverable work in increments), and a Gantt chart that visually depicts a project scheduleusing a bar chart that also illustrates dependencies between activities.
[0032] However, existing tools to visualize project management data suffer from variousdrawbacks. For example, existing tools to visualize project management data are typicallyspecific to a particular delivery type (e.g., a Scrum board is only used for software developmentor other projects that are carried out based on the iterative and incremental agile methodology).Accordingly, visualization tools that are developed to support specific delivery types aregenerally unavailable or unsuitable for other projects that may use a different delivery type toprovide similar functionality (e.g., the Scrum board may be unsuitable for a project that isimplemented using sequential and linear waterfall methodology). Furthermore, existing projectmanagement visualization tools typically lack support for hybrid delivery methodologies (e.g.,the Scrumban methodology that combines Scrum and Kanban) are limited to visualizing datathat depends on a project phase, lack capabilities to track dependencies across project phases, failto clearly visualize the various dependencies and impacts in a project, and / or fail to capturemulti-level dependencies, among other examples.
[0033] Some implementations described herein relate to a project visualization system thatmay be used to graphically depict project data (e.g., project elements and links, dependencies,relationships, or other associations among project elements) in a way that may enable projectmanagers to understand complex multi-level dependencies between various project elements.For example, in some implementations, the project visualization system may include a datafabric that stores and / or synchronizes project data that may be distributed across one or moreproject management systems, and the project visualization system may support variousworkflows to generate graphical views that depict project data in a way that may allow projectprofessionals to view, discover, and derive insights into planned, ongoing, or completed projects.For example, in some implementations, the project visualization system may support a backendprocessing workflow to pull project management data from the data fabric and generate datastructures that represent different project elements and links or other associations among theproject elements. In this way, the backend processing workflow may ensure that the projectvisualization system is continuously updated with real-time or near real-time projectmanagement data from the data fabric. Furthermore, as described herein, the projectmanagement visualization system may support a frontend processing workflow to retrieveproject data to be visualized from the generated data structures and render the project data in acustomized view. In this way, the frontend processing workflow may provide detailed andcustomized project data visualizations to enable data-driven decision-making at every step in aproject management lifecycle. Furthermore, in some implementations, the project managementvisualization system may support a view recommendation workflow in which an artificialintelligence model may recommend one or more suitable views to depict project data based on anatural language description related to a problem statement provided by a user. In this way, theview recommendation workflow may use the artificial intelligence model to continuously learnand recommend the view(s) best suited to visualize project management data that is relevant toan intent of a natural language problem statement.
[0034] Figs. 1A-1G are diagrams of an example implementation 100 associated withvisualizing project management data. As shown in Figs. 1A-1G, example implementation 100includes a project visualization system, one or more project management systems, and a clientdevice. The project visualization system, the project management system(s), and the clientdevice are described in more detail below in connection with Fig. 2 and Fig. 3.
[0035] In some implementations, as shown in Fig. 1A and described in further detail herein,the project visualization system may include an architecture with various components to supporta backend processing workflow, a frontend processing workflow, and a view recommendationworkflow. For example, as shown in Fig. 1A, the project management system may include adata fabric that is synchronized with the one or more project management systems, a viewgeneration engine that may pull raw project management data from the data fabric and generateview data including data structures to represent project elements and associations extracted fromthe raw project management data, and a user interface (UI) layer that may obtain andappropriately render project data to be visualized from the data structures stored as the view data.Furthermore, in some implementations, the project visualization system may include arecommendation engine that may receive a natural language problem statement from a clientdevice, use an artificial intelligence model to indicate one or more recommended views based onan intent of the natural language problem statement, and / or interact with the view generationengine and / or the UI layer to initiate the backend and / or frontend processing workflows that maybe needed to request and / or render project data associated with a recommended view.
[0036] As shown in Fig. 1A, and by reference number 102, the project visualization systemmay include a data fabric that is synchronized with project management data stored or otherwisemanaged in one or more project management systems. In some implementations, the projectmanagement data may include data related to project elements that are associated with one ormore projects. For example, as described herein, the project elements may generally include oneor more requirements, user stories, epics, sprints, features, tasks, risks, issues, defects, bugs, testcases, code commits, actions, decisions, change requests, feedback, iterations, milestones, and / ordeliverables, among other examples. Furthermore, in some implementations, the projectmanagement data may include data related to associations (e.g., links, interconnections, and / ordependencies) among the project elements. In some implementations, the project elements andthe associations among the project elements may be specified or derived from projectdocumentation, such as one or more technical documents and / or functional documents thatdescribe various requirements associated with a project. In some implementations, the projectdocumentation may be created and uploaded to the project management system(s) during anysuitable phase in a project, such as an initial planning phase and / or during an execution phase.The project documentation may generally include text descriptions that relate to all relevantproject details, including objectives, constraints, and / or work items to be performed. The projectdocumentation may therefore include various textual data sources that describe the project planand ongoing project efforts, which may be referenced to ensure that project requirements arefulfilled and provide traceability with regard to which work items have been performed, whoperformed the work items, when the work items were performed, which work items arescheduled to be performed in the future, and / or when the future work items are scheduled to beperformed, among other examples. For example, the project management system(s) may includeone or more devices executing a Jira software product used for issue tracking and agile projectmanagement, an application lifecycle management (ALM) tool used for software developmentlifecycle management, an Azure DevOps Server or Team Foundation Server (TFS) product (e.g.,enabling project management for agile, waterfall, and / or iterative software development), and / orany other suitable project management software or project management utility.
[0037] Accordingly, in some implementations, the project management data that is stored inthe data fabric and synchronized with the project management system(s) may provide the projectvisualization system with detailed real-time or near real-time information related to the projectelements and associations among project elements for planned, ongoing, and / or completedprojects. Furthermore, as described herein, synchronizing the data fabric with the projectmanagement system(s) may enable backend processing workflow that is used to pull projectmanagement data and generate data structures that can be used to easily visualize the projectmanagement data and enable robust data analytics to provide insights to project professionals.
[0038] In particular, as further shown in Fig. 1A, and by reference number 104, the backendprocessing workflow may include the view generation engine receiving, from the data fabric,raw project management data (e.g., substantially unprocessed project management data that issynchronized with the project management system(s)). For example, in some implementations,the view generation engine may periodically pull the raw project management data from the datafabric, and may pull only delta project management data in each pull iteration (e.g., in each pull,the view generation engine may only transfer raw project management data that is new ormodified since a most recent pull). Furthermore, as described in further detail herein, the viewgeneration engine may pull the delta project management data from the data fabric based on arequest from the UI layer and / or the recommendation engine to obtain project management datato support a requested and / or recommended view. In this way, by periodically pulling the deltaproject management data in each pull iteration and / or upon request, the project visualizationsystem may operate on real-time or near real-time project management data and / or efficientlyupdate project management view data even in cases where there may be many hundreds orthousands (or more) of project elements and associations among project elements.
[0039] As shown in Fig. 1B, and by reference number 106, the view generation engine mayconvert the raw project management data obtained from the data fabric into data structures thatrepresent the project elements and the associations among project elements in a view-friendlyformat. For example, in some implementations, the view generation engine may pre-process theraw project management data to strip or otherwise remove unwanted attributes (e.g., attributesthat are not relevant to a project element or an association between project elements), and theview generation engine may then store remaining attributes associated with the raw projectmanagement data in the view data. Furthermore, in some implementations, the view generationengine may extract information related to project elements and links, relationships,interconnections, dependencies, and / or other associations among project elements based on thestored attributes. The view generation engine may then generate the data structures to representthe project elements and the associations among project elements based on existing linkages thatare defined in the project management data obtained from the data fabric. For example, asdescribed in further detail herein, the view generation engine may generate the data structures torepresent the project elements and the associations among project elements using a graphmethodology, which may format the project management data in a way that translates to apictorial and easy-to-understand representation of the project management data.
[0040] For example, in some implementations, the view generation engine may identify, basedon the project management attributes that are stored with the view data, project elements andexisting associations among project elements. Accordingly, the data structures generated by theview generation engine may include various graph data structures, where each project element isrepresented by a node and each link, dependency, relationship, or other association between twoproject elements is represented as an edge or connection between two nodes. For example, theview generation engine may generate the graph data structures using an adjacency listimplementation in which all nodes in the graph data structures are defined as keys and a valueassociated with each key is an array that represents one or more connected nodes. For example,in Fig. 1B, reference number 108 illustrates an example graph data structure that represents auser story project element that has associations with various other project elements, including adefect, a test case, a risk, an issue, and a code commit. In the adjacency list approach, the viewgeneration engine may convert each project element to a node and may convert each associationbetween two project elements to an edge or connection between the two corresponding nodes.For example, as shown, the defect project element may be represented as a key, and a valueassociated with the key may be an array that includes the user story and test case projectelements. Accordingly, the defect, user story, and test case project elements are represented asseparate nodes, and the defect project element has edges pointing to the user story and test caseproject elements to represent the associations that are defined for the defect project element.Similarly, the user story project element includes associations with the issue, code commit, andtest case project elements, whereby the node representing the user story project element hasedges pointing to the nodes that represent the issue, code commit, and test case project elements.
[0041] In this way, by processing various key-value pairs to generate the graph data structuresthat represent the project elements and the associations among the project elements (e.g., usingan adjacency list implementation), the view recommendation engine may readily translate thegraph data structures to various view formats, as described in further detail below. Furthermore,using the key-value pairs to represent the project elements and the associations among the projectelements can be used to quickly determine how many nodes and edges are included in aparticular graph data structure. For example, the number of nodes in a graph data structure maycorrespond to a number of keys in a dictionary associated with the graph structure, and thenumber of edges may correspond to the sum of the lengths of the arrays associated with all of thekeys. Furthermore, graph data structures that are formatted as adjacency lists may be easy toupdate when there is a need to add or remove one or more nodes due to changes in the projectmanagement data synchronized at the data fabric, and graph data structures that are formatted asadjacency lists may be easy to traverse when needed to search for project data to be visualized.Accordingly, as shown in Fig. 1B, and by reference number 110, the backend processingworkflow may include storing the attributes associated with the project management data and thedata structures that represent the project elements and the project element associations as viewdata that may be formatted for quick display and rendering via the UI layer (e.g., a Data-DrivenDocuments (D3) layer that can render dynamic and interactive data visualizations in a browser).
[0042] Referring again to Fig. 1A, as shown by reference number 112, the frontend processingworkflow may include receiving, at the UI layer, a request to view or otherwise visualize projectdata. For example, in some implementations, the request may indicate a particular view to beused (e.g., a galaxy view, a problem areas view, an impact analysis view, a composition view,and / or another suitable view) and may indicate one or more criteria associated with the projectdata to be visualized. For example, a user at the client device may utilize a suitable applicationor interface to access the project visualization system, and the UI layer may display informationthat enables the user at the client device to specify various parameters associated with the projectdata to be visualized and / or the particular view to be used. Accordingly, as shown by referencenumbers 114-1 and 114-2, the UI layer may issue the request to the view generation engine, andthe view generation engine may pull customized project data to support the requested view fromthe view data. For example, as described above, the view data may include various graph datastructures that represent project elements and associations among project elements, whereby theview generation engine may search the graph data structures for the project data requested by theuser at the client device. For example, in some implementations, the view generation enginemay use a recursive depth-first search to traverse the graph data structures.
[0043] In particular, the recursive depth-first search may support backtracking, whereby nodesin a graph may be exhaustively searched by moving ahead to a child node, if one exists, andotherwise backtracking to a parent node. In other words, if there are no more child nodes when agraph is traversed along a current path, the recursive depth-first search may backtrack by movingbackwards along the current path in order to find more nodes with child nodes to traverse.Accordingly, the recursive depth-first search may visit all nodes on the current path until allvisited nodes have been traversed, and the recursive depth-first search may subsequently select anext path to traverse. In some implementations, the recursive depth-first search may be enabledusing stacks, where a starting node is initially selected and all nodes that are adjacent to thestarting node are pushed into a first stack. To select a next node to visit, a node may be poppedfrom the first stack, and all nodes that are adjacent to the popped node may be pushed into asecond stack, and this process may be repeated until the first stack is empty. Furthermore, eachnode that is visited during the recursive depth-first search may be marked to prevent therecursive depth-first search from visiting the same node multiple times and / or avoid infiniteloops.
[0044] As further shown in Fig. 1A, and by reference number 116, the UI layer may receivethe requested project data (e.g., after the view generation engine performs one or moreformatting changes, decrypts one or more attributes, and / or performs any other processing thatmay be needed to pass the requested project data to the UI layer), and the UI layer may renderthe data at the client device (e.g., in a browser) using one or more visualization libraries (e.g., aD3.js JavaScript library that uses Scalable Vector Graphics, HTML5, and Cascading StyleSheets standards to create dynamic and interactive data visualizations in a web browser).Furthermore, in some implementations, the UI layer may apply additional processing andfiltering logic to create custom views of the project management data based on the criteriaspecified in the request from the client device. Furthermore, the UI layer may render the projectdata in a way that enables scalability for projects that may have a very large number of projectelements and associations. For example, the UI layer may adapt the visualizations that arerendered for the client device to display only a partial subset of the project elements and / orassociations that are included in a particular view. In this way, the UI layer may present thepartial subset of the project elements and / or associations that are most relevant to the criteriaspecified in the request from the client device, and the user of the client device may navigateand / or expand the graph data structures that are depicted in the current view based on user inputs(e.g., the UI layer may render additional data to provide more context around a project elementor association with which a user interacts). In this way, the project visualization system canscale the visualization data to hundreds or thousands (or more) of project elements (e.g., byupgrading a supporting infrastructure, such as storage and processing resources allocated to theproject visualization system in a cloud computing, to an appropriate tier).
[0045] In some implementations, as described herein, the view rendered by the UI layer maygenerally utilize the graph data structures that are generated from the project management data(e.g., after any pre-processing performed by the view generation engine), which may enable theproject elements and associations among project elements to be plotted, depicted, or otherwisevisualized in various ways (e.g., based on an intensity of connections between project elements,based on a proximity to a similar type of project element, and / or on a timeline, among otherexamples). For example, the graph data structures that are used to represent the project elementsand associations among project elements may enable the project visualization system to createand render views that depict project elements as nodes in an interactive graph with associationsrepresented as links to enable users to analyze dependencies or other associations among projectelements. For example, in a context related to a software development project, the view renderedat the client device can depict one or more releases, features and user stories that are associatedwith the one or more releases, test cases and defects associated with the user stories, risksassociated with any of the foregoing project elements, and / or any other suitable types of projectelements that may be connected or otherwise associated.
[0046] For example, referring to Fig. 1C, reference number 118 illustrates an example of aview that may be created and rendered by the project visualization system to represent areaswithin a project that have high risks, issues, and / or bugs. For example, the view illustrated byreference number 118 is a galaxy view graphically depicting various project elements that areassociated with risks, issues, and / or bugs that could potentially impact release quality. In otherexamples, reference number 120 illustrates an example of a view that may be created andrendered by the project visualization system to graphically depict disconnected project elements,which could lead to missed dependencies and / or an incorrect representation of an impact, andreference number 122 illustrates an example of a view that may be created and rendered by theproject visualization system to depict highly loaded releases (e.g., where each release is a node orbubble with a size that is based on a number of user stories contained in or otherwise associatedwith the release).
[0047] In some implementations, using the graph data structures described herein to representproject elements and associations among project elements may enable various algorithms toevaluate and conduct data analytics to provide insight into connected project elements. Forexample, in some implementations, the graph data structures can be used to create and renderviews that visually depict potential problem areas in a project (e.g., showing project elementsassociated with large numbers of risks, defects, issues, or impediments) and / or views thatvisually depict early warnings for project elements that may have dependencies on other projectelements that are delayed or at risk, among other examples. Furthermore, the graph datastructures representing the project elements and the associations among project elements may beindependent of project type, whereby the project visualization system may support projectscarried out using agile, waterfall, or other suitable methodologies, and the graph data structuresmay be used to depict dependencies between project elements regardless of a number of degreesof separation there may be between project elements. The graph data structures may beunconstrained by a hierarchy or a connection type between nodes (e.g., associations may bedirectional and / or bidirectional, among other examples), whereby a view created and rendered bythe project visualization system may depict any number of connections in any direction.Furthermore, in some implementations, the views that are created and rendered by the projectvisualization system may enable interactive control over associations among project elements,where a user at the client device may interact with the view (e.g., in a browser) to provide inputsto add, remove, modify, or otherwise customize links or associations between project elements.
[0048] Referring again to Fig. 1A, as shown by reference number 124, the project visualizationsystem may support a view recommendation workflow in which the recommendation enginereceives a natural language description of a problem statement (e.g., a business problem, aresource planning problem, or another suitable problem to be solved or investigated based onproject data). In some implementations, the recommendation engine may use an artificialintelligence model trained to extract an intent from the problem statement and to recommend oneor more views that are relevant to the intent of the problem statement (e.g., the recommendedviews may depict project elements and / or associations in a visual format, such as a galaxy viewformat, a composition view format, an impact analysis view format, or another suitable viewformat that lends itself to resolving or providing insight into the problem statement). Forexample, in some implementations, the artificial intelligence model may include a knowledgebasedrecommendation model trained using historical data related to different view formats thatare available through the project visualization system and problem statements that wereassociated with historical usage of the different view formats (e.g., the knowledge-basedrecommendation model may store mappings between problem statements, intents and / or projectdata, and corresponding views, which may be used to determine the recommended views).
[0049] Accordingly, in some implementations, an end user at the client device may define aproblem statement in natural language terms to express what project data the end user desires tovisualize and / or how the end user desires to visualize the project data, and the recommendationengine may use natural language processing to identify the intent of the problem statement andthe project elements, associations, and / or view formats suited to the intent of the problemstatement. For example, in some implementations, the natural language processing maygenerally use syntax and semantic analysis techniques to determine how different words in thenatural language problem statement are contextually related to one another and / or may identify agrammatical structure of the natural language problem statement (e.g., using tokenizationtechniques) to organize the natural language problem statement into smaller semantic units (e.g.,individual words, phrases, and / or punctuations, among other examples). In this way, therecommendation engine may determine the intent of the natural language problem statement,which may generally refer to what data the end user desires to obtain (e.g., visualize) and / or whatproblem the end user desires to solve (e.g., via a suitable view that visualizes project data).
[0050] As shown by reference number 126, the view recommendation workflow may furtherinclude indicating the recommended views to solve the problem statement to the client device.Accordingly, the end user at the client device may select one or more recommended views to berendered, which may cause the recommendation engine to communicate with the viewgeneration engine to initiate the backend processing workflow to pull, aggregate, obtain and / orotherwise process the project data needed to support the requested view, as shown by referencenumber 128. Furthermore, as shown by reference number 130, the end user selecting therecommended view(s) to be rendered may cause the recommendation engine to communicatewith the UI layer to initiate the frontend processing workflow in order to create and render theselected view(s) based on the project data that is obtained in the backend processing workflow.Furthermore, user inputs to select a recommended view or choose a different view may be usedas feedback to the recommendation engine to enable continuous learning by the artificialintelligence model, which may result in more accurate view recommendations over time.
[0051] In some implementations, in addition to using artificial intelligence models and / oralgorithms to recommend one or more views to the client device, the project visualization systemmay leverage artificial intelligence models and / or algorithms to recommend potential linkagesbetween project elements. In general, the project visualization system may use machine learningalgorithms such as natural language processing to inspect project data stored in the data fabricthat relates to various project elements and / or attributes associated with the project elements andpredict associations between project elements. For example, when a change request is created ina project management system, which may be detected when the backend processing workflowpulls delta project management data that includes data related to the change request, the artificialintelligence models and / or algorithms may be used to predict other project elements (e.g., userstories) that may be impacted by the change request. Accordingly, the project visualizationsystem may render, at the client device via the UI layer, an interface that provides the end userwith an option to accept or reject the recommended linkages, and the recommended or predictedlinkages may also be stored in the data fabric. In some implementations, the projectvisualization system may use data indicating whether the user accepted or rejected therecommended linkages to further train the machine learning algorithms for better accuracy overtime. For example, depending on whether the end user accepts, rejects, or modifies arecommended association between project elements, the project visualization system maymodify appropriate data prediction output labels and save the modified output labels back to thedata fabric. Accordingly, the artificial intelligence models used in the project visualizationsystem may utilize the modified output labels for retraining to increase accuracy.
[0052] In some implementations, as described herein, the various workflows supported in theproject visualization system may support various functional use cases and / or data analytics usecases. For example, as shown in Fig. 1D, and by reference number 132, the client device mayinteract with the project visualization system to create and render a galaxy view to visualize linksand / or associations between project elements. For example, in Fig. 1D, reference number 134illustrates an example galaxy view that depicts associations between project elements at differentlevels, where nodes corresponding to closely related project elements may be clustered togetherin galaxy-like structures to illustrate an intensity of connections between project elements. Inthis way, the end user may interact with (e.g., click on) a node that corresponds to a projectelement to view more details related to the attributes of the project element and / or the otherproject elements that are associated with the project element. Furthermore, in someimplementations, the end user may continue to select different nodes that correspond to differentproject elements to form a traversal chain and view other project elements impacting the chain.
[0053] In one example, the galaxy view supported by the project visualization system mayenable a functional use case that provides an ability to discover and prioritize deliverables with ahigh impact. For example, an end user at the client device may be following up on a decisionthat was discussed at a meeting, and the end user may have a limited view and disparate datapoints to discover impact areas and / or deliverables linked to the decision. Accordingly, the enduser may access the project visualization system via the client device, and may indicate thedecision to be explored in an interface associated with the galaxy view. Additionally, oralternatively, the end user may provide a natural language problem description related to thedecision to the recommendation engine, which may recommend the galaxy view based on theintent of the natural language problem description. In either case, the project visualizationsystem may create and render the galaxy view to represent the project elements impacted by thedecision, and the end user may interact with the galaxy view to find that the impacted projectelements are associated with various other project elements. Accordingly, the end user may usethe galaxy view to make an actionable decision, such as prioritizing closure of the projectelements (e.g., deliverables) impacted by the decision to minimize the impact.
[0054] In another example, as shown in Fig. 1E, and by reference number 136, the clientdevice may interact with the project visualization system to create and render a composition viewto visualize relative allocations associated with one or more project elements. For example, inFig. 1E, reference number 138 illustrates an example composition view that depicts resources(e.g., owners) assigned to different project elements, where nodes in the composition viewcorrespond to project elements and sub-nodes correspond to resources assigned to the projectelements. For example, the graph data structures used to represent the project elements and theassociations among project elements may be used to evaluate a composition of project elements,including whether composed project elements are directly connected by one degree of separationor indirectly connected via multiple degrees of separation. In this way, the end user at the clientdevice may compare project elements based on composition (e.g., the end user may comparereleases based on composed user stories, compare resources based on assigned project elements,and / or compare and balance release life cycles across multiple releases, among other examples).
[0055] In one example, the composition view supported by the project visualization systemmay enable a functional use case that provides an ability to view resource loading in a project.For example, an end user at the client device may be working on a staffing plan for a project, andthe end user may not have a definite approach to assess how team members are loaded acrossdifferent metrics. Accordingly, the end user may access the project visualization system andopen an interface associated with the composition view, or the end user may provide a naturallanguage problem description related to the staffing problem to the recommendation engine,which may recommend the composition view based on the composition view historically beingused to solve staffing problems or solve problems related to resource loading. In either case, theproject visualization system may create and render the composition view to represent groups byresources and sizes using one or more criteria (e.g., owner and / or approver) that provide detailedinformation related to work that each team member is handling. In this way, the end user mayobtain an informative view of the team workload to decide on a staffing plan that achieves abalanced work distribution among team members working on the project.
[0056] In another example, as shown in Fig. 1F, and by reference number 140, the clientdevice may interact with the project visualization system to create and render an impact view tovisualize links and / or associations between project elements. For example, in someimplementations, the impact view may be generated by traversing the graph data structures,starting from a selected root node corresponding to a source project element, to one or more leafnodes in the graph, which may be used to generate an impact view that can highlight the impactor dependency of the leaf nodes relative to the root note. For example, if the root nodecorresponds to a release and the leaf nodes represent risks, the graph traversal techniquesdescribed herein may highlight the impact of all risks that are impacting the release, irrespectiveof how many degrees of separation are between the risk(s) and the release. For example, in someimplementations, the impact view may be generated using an algorithm that crawls through aweb of associations defined in the graph data structures to find all the paths that start from a rootnode and reach out to a target entity that has an impact on the selected root node. In this way,the end user can clearly visualize the main project elements in the path of the selected root nodeand assess the impact on the selected root node. For impacting project elements such as risks,the impact view may also show the associated business cost in a rolled up manner.
[0057] For example, in some implementations, the algorithm used to generate the impact viewmay create a Sankey view (or Sankey diagram), which is a type of flow diagram used toemphasize major transfers or flows within a system. For example, in Fig. 1F, reference number142-1 illustrates an example of an impact view that represents various downstream projectelements impacting a release at varying degrees of separations, with bands connecting differentnodes to represent the associations between project elements. In the example illustrated in Fig.1F, the size of each node may be proportional to a number of upstream and / or downstreamproject elements that are associated with the respective node. Referring to Fig. 1G, referencenumber 142-2 illustrates another example impact view that represents a path between a root nodeand various leaf nodes to depict various paths that are impacting the root node. For example, asdescribed herein, the associations and links among project elements may be discovered from theproject management data pulled from the data fabric, which may result in creation of graph datastructures including a large web of links. In order to generate the impact view, the projectvisualization system may receive information indicating a source (root) node and one or moretarget nodes for which path tracing is requested. Accordingly, starting from the root node, theproject visualization system may recursively expand the source node for associations, inspect thenodes in the recursive collection for target nodes to be included in the impact view, verify thatthe recursive expansion does not cross a boundary through sibling nodes, and then prune thecollected associations to avoid included single-ended nodes (e.g., thereby preserving the shortestpath among multiple parallel paths with different lengths).
[0058] In one example, the impact view supported by the project visualization system mayenable a functional use case that provides an ability to identify risks, issues, bugs, changerequests, and / or other project elements impacting one or more releases. For example, an enduser at the client device may desire to monitor the progress of an upcoming set of releases, butthe end user may not have a detailed and / or consolidated view of each release and the risk,issues, and / or bugs impacting the releases. Accordingly, the end user may access the projectvisualization system and open an interface associated with the impact view, or the end user mayprovide a natural language problem description related to the desire to monitor the progress ofupcoming release to the recommendation engine, which may recommend the impact view toprovide a holistic view of the project elements impacting the releases. In either case, the projectvisualization system may use the algorithm described above to obtain project management datafrom all relevant data sources to generate an impact analysis view starting from a root node thatcorresponds to a release to be monitored. In this way, the impact view may show all directand / or indirect risks, issues, bugs, change requests, and / or other project elements impacting therelease along with other relevant information (e.g., a mitigation cost) such that the end user cantake proactive steps to avert or mitigate project elements that may block the release.
[0059] As indicated above, Figs. 1A-1G are provided as an example. Other examples maydiffer from what is described with regard to Figs. 1A-1G. The number and arrangement ofdevices shown in Figs. 1A-1G are provided as an example. In practice, there may be additionaldevices, fewer devices, different devices, or differently arranged devices than those shown inFigs. 1A-1G. Furthermore, two or more devices shown in Figs. 1A-1G may be implementedwithin a single device, or a single device shown in Figs. 1A-1G may be implemented as multiple,distributed devices. Additionally, or alternatively, a set of devices (e.g., one or more devices)shown in Figs. 1A-1G may perform one or more functions described as being performed byanother set of devices shown in Figs. 1A-1G.
[0060] Fig. 2 is a diagram of an example environment 200 in which systems and / or methodsdescribed herein may be implemented. As shown in Fig. 2, environment 200 may include aproject visualization system 201, which may include one or more elements of and / or mayexecute within a cloud computing system 202. The cloud computing system 202 may includeone or more elements 203-212, as described in more detail below. As further shown in Fig. 2,environment 200 may include a project management system 220, a client device 230, and anetwork 240. Devices and / or elements of environment 200 may interconnect via wiredconnections and / or wireless connections.
[0061] The cloud computing system 202 includes computing hardware 203, a resourcemanagement component 204, a host operating system (OS) 205, and / or one or more virtualcomputing systems 206. The cloud computing system 202 may execute on, for example, anAmazon Web Services platform, a Microsoft Azure platform, or a Snowflake platform. Theresource management component 204 may perform virtualization (e.g., abstraction) ofcomputing hardware 203 to create the one or more virtual computing systems 206. Usingvirtualization, the resource management component 204 enables a single computing device (e.g.,a computer or a server) to operate like multiple computing devices, such as by creating multipleisolated virtual computing systems 206 from computing hardware 203 of the single computingdevice. In this way, computing hardware 203 can operate more efficiently, with lower powerconsumption, higher reliability, higher availability, higher utilization, greater flexibility, andlower cost than using separate computing devices.
[0062] Computing hardware 203 includes hardware and corresponding resources from one ormore computing devices. For example, computing hardware 203 may include hardware from asingle computing device (e.g., a single server) or from multiple computing devices (e.g., multipleservers), such as multiple computing devices in one or more data centers. As shown, computinghardware 203 may include one or more processors 207, one or more memories 208, and / or oneor more networking components 209. Examples of a processor, a memory, and a networkingcomponent (e.g., a communication component) are described elsewhere herein.
[0063] The resource management component 204 includes a virtualization application (e.g.,executing on hardware, such as computing hardware 203) capable of virtualizing computinghardware 203 to start, stop, and / or manage one or more virtual computing systems 206. Forexample, the resource management component 204 may include a hypervisor (e.g., a bare-metalor Type 1 hypervisor, a hosted or Type 2 hypervisor, or another type of hypervisor) or a virtualmachine monitor, such as when the virtual computing systems 206 are virtual machines 210.Additionally, or alternatively, the resource management component 204 may include a containermanager, such as when the virtual computing systems 206 are containers 211. In someimplementations, the resource management component 204 executes within and / or incoordination with a host operating system 205.
[0064] A virtual computing system 206 includes a virtual environment that enables cloudbasedexecution of operations and / or processes described herein using computing hardware 203.As shown, a virtual computing system 206 may include a virtual machine 210, a container 211,or a hybrid environment 212 that includes a virtual machine and a container, among otherexamples. A virtual computing system 206 may execute one or more applications using a filesystem that includes binary files, software libraries, and / or other resources required to executeapplications on a guest operating system (e.g., within the virtual computing system 206) or thehost operating system 205.
[0065] Although the project visualization system 201 may include one or more elements 203-212 of the cloud computing system 202, may execute within the cloud computing system 202,and / or may be hosted within the cloud computing system 202, in some implementations, theproject visualization system 201 may not be cloud-based (e.g., may be implemented outside of acloud computing system) or may be partially cloud-based. For example, the project visualizationsystem 201 may include one or more devices that are not part of the cloud computing system202, such as device 300 of Fig. 3, which may include a standalone server or another type ofcomputing device. The project visualization system 201 may perform one or more operationsand / or processes described in more detail elsewhere herein.
[0066] The project management system 220 includes one or more devices capable of receiving,generating, storing, processing, providing, and / or routing information associated with projectelements, associations, links, dependencies, and / or other suitable information associated with aproject, as described elsewhere herein. The project management system 220 may include acommunication device and / or a computing device. For example, the project management system220 may include a data structure, a database, a data source, a server, a database server, anapplication server, a client server, a web server, a host server, a proxy server, a virtual server(e.g., executing on computing hardware), a server in a cloud computing system, a device thatincludes computing hardware used in a cloud computing environment, or a similar type ofdevice. As an example, the project management system 220 may store information associatedwith project elements, associations, links, dependencies, and / or other suitable informationassociated with a project, which may be used by the project visualization system 201 to generateone or more data structures that represent project elements and / or associations among projectelements such that the project visualization system 201 can render one or more views to visualizeproject data using the one or more data structures, as described in more detail elsewhere herein.The project management system 220 may communicate with one or more other devices ofenvironment 200, as described elsewhere herein.
[0067] The client device 230 includes one or more devices capable of receiving, generating,storing, processing, and / or providing information associated with visualizing projectmanagement data, as described elsewhere herein. The client device 230 may include acommunication device and / or a computing device. For example, the client device 230 mayinclude a wireless communication device, a mobile phone, a user equipment, a laptop computer,a tablet computer, a desktop computer, a wearable communication device (e.g., a smartwristwatch, a pair of smart eyeglasses, a head mounted display, or a virtual reality headset), or asimilar type of device. The client device 230 may communicate with one or more other devicesof environment 200, as described elsewhere herein.
[0068] The network 240 includes one or more wired and / or wireless networks. For example,the network 240 may include a cellular network, a public land mobile network (PLMN), a localarea network (LAN), a wide area network (WAN), a private network, the Internet, and / or acombination of these or other types of networks. The network 240 enables communicationamong the devices of environment 200.
[0069] The number and arrangement of devices and networks shown in Fig. 2 are provided asan example. In practice, there may be additional devices and / or networks, fewer devices and / ornetworks, different devices and / or networks, or differently arranged devices and / or networksthan those shown in Fig. 2. Furthermore, two or more devices shown in Fig. 2 may beimplemented within a single device, or a single device shown in Fig. 2 may be implemented asmultiple, distributed devices. Additionally, or alternatively, a set of devices (e.g., one or moredevices) of environment 200 may perform one or more functions described as being performedby another set of devices of environment 200.
[0070] Fig. 3 is a diagram of example components of a device 300, which may correspond tothe project visualization system 201, the project management system 220, and / or the clientdevice 230 shown in Fig. 2. In some implementations, the project visualization system 201, theproject management system 220, and / or the client device 230 include one or more devices 300and / or one or more components of device 300. As shown in Fig. 3, device 300 may include abus 310, a processor 320, a memory 330, an input component 340, an output component 350,and a communication component 360.
[0071] Bus 310 includes one or more components that enable wired and / or wirelesscommunication among the components of device 300. Bus 310 may couple together two ormore components of Fig. 3, such as via operative coupling, communicative coupling, electroniccoupling, and / or electric coupling. Processor 320 includes a central processing unit, a graphicsprocessing unit, a microprocessor, a controller, a microcontroller, a digital signal processor, afield-programmable gate array, an application-specific integrated circuit, and / or another type ofprocessing component. Processor 320 is implemented in hardware, firmware, or a combinationof hardware and software. In some implementations, processor 320 includes one or moreprocessors capable of being programmed to perform one or more operations or processesdescribed elsewhere herein.
[0072] Memory 330 includes volatile and / or nonvolatile memory. For example, memory 330may include random access memory (RAM), read only memory (ROM), a hard disk drive,and / or another type of memory (e.g., a flash memory, a magnetic memory, and / or an opticalmemory). Memory 330 may include internal memory (e.g., RAM, ROM, or a hard disk drive)and / or removable memory (e.g., removable via a universal serial bus connection). Memory 330may be a non-transitory computer-readable medium. Memory 330 stores information,instructions, and / or software (e.g., one or more software applications) related to the operation ofdevice 300. In some implementations, memory 330 includes one or more memories that arecoupled to one or more processors (e.g., processor 320), such as via bus 310.
[0073] Input component 340 enables device 300 to receive input, such as user input and / orsensed input. For example, input component 340 may include a touch screen, a keyboard, akeypad, a mouse, a button, a microphone, a switch, a sensor, a global positioning system sensor,an accelerometer, a gyroscope, and / or an actuator. Output component 350 enables device 300 toprovide output, such as via a display, a speaker, and / or a light-emitting diode. Communicationcomponent 360 enables device 300 to communicate with other devices via a wired connectionand / or a wireless connection. For example, communication component 360 may include areceiver, a transmitter, a transceiver, a modem, a network interface card, and / or an antenna.
[0074] Device 300 may perform one or more operations or processes described herein. Forexample, a non-transitory computer-readable medium (e.g., memory 330) may store a set ofinstructions (e.g., one or more instructions or code) for execution by processor 320. Processor320 may execute the set of instructions to perform one or more operations or processes describedherein. In some implementations, execution of the set of instructions, by one or more processors320, causes the one or more processors 320 and / or the device 300 to perform one or moreoperations or processes described herein. In some implementations, hardwired circuitry is usedinstead of or in combination with the instructions to perform one or more operations or processesdescribed herein. Additionally, or alternatively, processor 320 may be configured to perform oneor more operations or processes described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry and software.
[0075] The number and arrangement of components shown in Fig. 3 are provided as anexample. Device 300 may include additional components, fewer components, differentcomponents, or differently arranged components than those shown in Fig. 3. Additionally, oralternatively, a set of components (e.g., one or more components) of device 300 may performone or more functions described as being performed by another set of components of device 300.
[0076] Fig. 4 is a flowchart of an example process 400 associated with a project visualizationsystem. In some implementations, one or more process blocks of Fig. 4 are performed by aproject visualization system (e.g., project visualization system 201). In some implementations,one or more process blocks of Fig. 4 are performed by another device or a group of devicesseparate from or including the project visualization system, such as a project management system(e.g., project management system 220) and / or a client device (e.g., client device 230).Additionally, or alternatively, one or more process blocks of Fig. 4 may be performed by one ormore components of device 300, such as processor 320, memory 330, input component 340,output component 350, and / or communication component 360.
[0077] As shown in Fig. 4, process 400 may include receiving project management data thatincludes information related to project elements associated with one or more projects andinformation related to associations among the project elements associated with the one or moreprojects (block 410). For example, the project visualization system may receive projectmanagement data that includes information related to project elements associated with one ormore projects and information related to associations among the project elements associated withthe one or more projects, as described above.
[0078] As further shown in Fig. 4, process 400 may include generating, based on the projectmanagement data, one or more data structures that represent the project elements associated withthe one or more projects and the associations among the project elements associated with the oneor more projects (block 420). For example, the project visualization system may generate, basedon the project management data, one or more data structures that represent the project elementsassociated with the one or more projects and the associations among the project elementsassociated with the one or more projects, as described above.
[0079] As further shown in Fig. 4, process 400 may include receiving a request to visualizeproject data, wherein the request indicates a view to use to visualize the project data andspecifies criteria related to the project data to be visualized in the view (block 430). Forexample, the project visualization system may receive a request to visualize project data, whereinthe request indicates a view to use to visualize the project data and specifies criteria related to theproject data to be visualized in the view, as described above. In some implementations, therequest indicates a view to use to visualize the project data and specifies criteria related to theproject data to be visualized in the view.
[0080] As further shown in Fig. 4, process 400 may include searching the one or more datastructures to obtain the project data to be visualized based on the criteria specified in the request(block 440). For example, the project visualization system may search the one or more datastructures to obtain the project data to be visualized based on the criteria specified in the request,as described above.
[0081] As further shown in Fig. 4, process 400 may include rendering the project data usingthe view indicated in the request (block 450). For example, the project visualization system mayrender the project data using the view indicated in the request, as described above.
[0082] Process 400 may include additional implementations, such as any singleimplementation or any combination of implementations described below and / or in connectionwith one or more other processes described elsewhere herein.
[0083] In a first implementation, the one or more data structures include one or more graphs inwhich each node represents a project element and in which each edge or connection representsan association between two project elements.
[0084] In a second implementation, alone or in combination with the first implementation, theone or more data structures are searched using a recursive depth-first search technique.
[0085] In a third implementation, alone or in combination with one or more of the first andsecond implementations, the information included in the project management data includes onlydelta data since a most recent iteration in which the project management data was pulled from adata fabric that stores the project management data.
[0086] In a fourth implementation, alone or in combination with one or more of the firstthrough third implementations, process 400 includes receiving, from a client device, a naturallanguage description related to a problem statement associated with the project data to bevisualized in the view; identifying, using an artificial intelligence model, one or morerecommended views to visualize the project data based on an intent associated with the problemstatement and one or more project elements or associations relevant to the intent; and providing,to the client device, information indicating the one or more recommended views.
[0087] In a fifth implementation, alone or in combination with one or more of the first throughfourth implementations, one or more of a first workflow to generate the one or more datastructures or a second workflow to render the view are initiated based on an input from the clientdevice selecting the view from the one or more recommended views.
[0088] In a sixth implementation, alone or in combination with one or more of the first throughfifth implementations, the view indicates potential problem areas associated with the project datathat is rendered in the view or warnings based on the project data rendered in the view havingdependencies on other project elements that are associated with one or more potential problemareas.
[0089] In a seventh implementation, alone or in combination with one or more of the firstthrough sixth implementations, the view indicates a composition including direct connections orindirect connections associated with project elements included in the project data that is renderedin the view.
[0090] In an eighth implementation, alone or in combination with one or more of the firstthrough seventh implementations, the view indicates a strength of coupling between types ofproject elements included in the project data that is rendered in the view.
[0091] In a ninth implementation, alone or in combination with one or more of the firstthrough eighth implementations, the view indicates one or more target project elements have animpact on a source project element.
[0092] Although Fig. 4 shows example blocks of process 400, in some implementations,process 400 includes additional blocks, fewer blocks, different blocks, or differently arrangedblocks than those depicted in Fig. 4. Additionally, or alternatively, two or more of the blocks ofprocess 400 may be performed in parallel.
[0093] The foregoing disclosure provides illustration and description, but is not intended to beexhaustive or to limit the implementations to the precise forms disclosed. Modifications may bemade in light of the above disclosure or may be acquired from practice of the implementations.
[0094] As used herein, the term "component" is intended to be broadly construed as hardware,firmware, or a combination of hardware and software. It will be apparent that systems and / ormethods described herein may be implemented in different forms of hardware, firmware, and / ora combination of hardware and software. The actual specialized control hardware or softwarecode used to implement these systems and / or methods is not limiting of the implementations.Thus, the operation and behavior of the systems and / or methods are described herein withoutreference to specific software code - it being understood that software and hardware can be usedto implement the systems and / or methods based on the description herein.
[0095] As used herein, satisfying a threshold may, depending on the context, refer to a valuebeing greater than the threshold, greater than or equal to the threshold, less than the threshold,less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.
[0096] Although particular combinations of features are recited in the claims and / or disclosedin the specification, these combinations are not intended to limit the disclosure of variousimplementations. In fact, many of these features may be combined in ways not specificallyrecited in the claims and / or disclosed in the specification. Although each dependent claim listedbelow may directly depend on only one claim, the disclosure of various implementationsincludes each dependent claim in combination with every other claim in the claim set. As usedherein, a phrase referring to "at least one of" a list of items refers to any combination of thoseitems, including single members. As an example, "at least one of: a, b, or c" is intended to covera, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiple of the same item.
[0097] No element, act, or instruction used herein should be construed as critical or essentialunless explicitly described as such. Also, as used herein, the articles "a" and "an" are intended toinclude one or more items, and may be used interchangeably with "one or more." Further, asused herein, the article "the" is intended to include one or more items referenced in connectionwith the article "the" and may be used interchangeably with "the one or more." Furthermore, asused herein, the term "set" is intended to include one or more items (e.g., related items, unrelateditems, or a combination of related and unrelated items), and may be used interchangeably with"one or more." Where only one item is intended, the phrase "only one" or similar language isused. Also, as used herein, the terms "has," "have," "having," or the like are intended to beopen-ended terms. Further, the phrase "based on" is intended to mean "based, at least in part,on" unless explicitly stated otherwise. Also, as used herein, the term "or" is intended to beinclusive when used in a series and may be used interchangeably with "and / or," unless explicitlystated otherwise (e.g., if used in combination with "either" or "only one of").
Claims
1. A method, comprising: receiving, by a device, project management data that includes information related to project elements associated with one or more projects and information related to associations among the project elements associated with the one or more projects; generating, by the device and based on the project management data, one or more data structures that represent the project elements associated with the one or more projects and the associations among the project elements associated with the one or more projects; receiving, by the device, a request to visualize project data, wherein the request indicates a view to use to visualize the project data and specifies criteria related to the project data to be visualized in the view; searching, by the device, the one or more data structures to obtain the project data to be visualized based on the criteria specified in the request; and rendering, by the device, the project data using the view indicated in the request.
2. The method of claim 1, wherein the one or more data structures include one or more graphs in which each node represents a project element and in which each edge or connection represents an association between two project elements.
3. The method of claim 1, wherein the one or more data structures are searched using a recursive depth-first search technique.
4. The method of claim 1, wherein the information included in the project management data includes only delta data since a most recent iteration in which the project management data was pulled from a data fabric that stores the project management data.
5. The method of claim 1, further comprising: receiving, from a client device, a natural language description related to a problem statement associated with the project data to be visualized in the view; identifying, using an artificial intelligence model, one or more recommended views to visualize the project data based on an intent associated with the problem statement and one or more project elements or associations relevant to the intent; and providing, to the client device, information indicating the one or more recommended views.
6. The method of claim 5, wherein one or more of a first workflow to generate the one or more data structures or a second workflow to render the view are initiated based on an input from the client device selecting the view from the one or more recommended views.
7. The method of claim 1, wherein the view indicates potential problem areas associated with the project data that is rendered in the view or warnings based on the project data rendered in the view having dependencies on other project elements that are associated with one or more potential problem areas.
8. The method of claim 1, wherein the view indicates a composition including direct connections or indirect connections associated with project elements included in the project data that is rendered in the view.
9. The method of claim 1, wherein the view indicates a strength of coupling between types of project elements included in the project data that is rendered in the view.
10. The method of claim 1, wherein the view indicates one or more target project elements have an impact on a source project element.
11. A device, comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to: receive project management data that includes information related to project elements associated with one or more projects and information related to associations among the project elements associated with the one or more projects; generate, based on the project management data, one or more data structures that represent the project elements associated with the one or more projects and the associations among the project elements associated with the one or more projects; receive, from a client device, a natural language description related to a problem statement associated with project data to be visualized; identify, using an artificial intelligence model, one or more recommended views to visualize the project data based on an intent associated with the problem statement and one or more project elements or associations relevant to the intent; provide, to the client device, information indicating the one or more recommended views; and initiate one or more workflows to render the project data using a view that is selected from the one or more recommended views.
12. The device of claim 11, wherein the one or more data structures include one or more graphs in which each node represents a project element and in which each edge or connection represents an association between two project elements.
13. The device of claim 11, wherein the one or more workflows include a first workflow to generate the one or more data structures for the view that is selected from the one or more recommended views and a second workflow to render the one or more data structures on a user interface according to the view that is selected from the one or more recommended views.
14. The device of claim 11, wherein the view indicates potential problem areas associated with the project data that is rendered in the view or warnings based on the project data rendered in the view having dependencies on other project elements that are associated with one or more potential problem areas.
15. The device of claim 11, wherein the view indicates a composition including direct connections or indirect connections associated with project elements included in the project data that is rendered in the view.
16. The device of claim 11, wherein the view indicates a strength of coupling between types of project elements included in the project data that is rendered in the view.
17. The device of claim 11, wherein the view indicates one or more target project elements have an impact on a source project element.
