The present disclosure relates to systems and methods to provide user-generated project-level graphical user interfaces within a collaboration environment.
Collaboration environments, sometimes referred to as work management platforms, may enable users to assign projects, tasks, or other assignments to assignees (e.g., other users) to complete. A collaboration environment may comprise an environment in which individual users and/or a virtual team of users does its work and may enable users to work in a more organized and efficient manner.
One or more aspects of the present disclosure relates to a system configured to provide user-generated project-level graphical user interfaces within a collaboration environment. In some implementations, a user-generated project-level graphical user interface may be used to brief one or more users about a project. Providing a user interface to brief one or more users may be useful because the project may be associated with a multitude of information. Some of information about the project may be sensitive and unnecessary to give users when briefing them.
One or more implementations presented herein propose a way to provide user-generated project-level graphical user interfaces that act as briefs, and may include information that is not protected by privileges so that sensitive and/or unnecessary information may not be included. Accordingly, these user interfaces may display information in the form of a project brief that contains concise, updated, and/or permissible information. By way of non-limiting illustration, a user-generated project-level graphical user interface may include interactable and dynamic interface elements representing one or more values of project parameters of a project. Users may add content to the brief by interacting with the dynamic interface elements. In some implementations, users may be prompted when attempting to add sensitive information. If permissions are required, the prompt may give users the opportunity to change the content as it appears in the brief and/or override the permissions requirement.
The interface elements representing one or more values of project parameters may be dynamically updated as the values change. Providing these updated values of the project parameters of a project may maintain a project brief in its most current state regardless of when the brief was created in relation to progress made on the project. In some implementations, unstructured data otherwise dispersed in various pages and/or records of the collaboration environment may now become structured by virtue of the arrangement of dynamic interface elements displaying values of project parameters in the user interfaces.
One or more implementations of a system to provide user-generated project-level graphical user interfaces within a collaboration environment may include one or more hardware processors configured by machine-readable instructions and/or other components. Executing the machine-readable instructions may cause the one or more hardware processors to facilitate providing user-generated project-level graphical user interfaces within a collaboration environment. The machine-readable instructions may include one or more computer program components. The one or more computer program components may include one or more of an environment state component, a template component, a user input component, an update component, a user interface component, and/or other components.
The environment state component may be configured to manage environment state information maintaining a collaboration environment and/or other information. The collaboration environment may be configured to facilitate interaction by users with the collaboration environment. The environment state information may include one or more of work unit records, project records, objective records, and/or other records. The work unit records may include work information comprising values of work unit parameters defining units of work managed, created, and/or assigned to the users within the collaboration environment. The project records may include project information comprising values for project parameters associated with projects created, managed, and/or assigned within the collaboration environment. The objective records may include objective information comprising values of one or more objective parameters associated with business objectives defined within the collaboration environment. An individual project may include individual sets of the units of work supporting the individual projects. By way of non-limiting illustration, the project records may include a first project record for a first project, and/or other project records for other projects.
The environment state component may be configured to manage template information defining templates for user-generated project-level graphical user interfaces of the collaboration environment. The individual user-generated project-level graphical user interfaces may correspond to individual projects. The individual templates may include individual sets of interface elements configured to display the values of one or more of the project parameters of the individual projects. By way of non-limiting illustration, a first template may include a first interface element, a second interface element, and/or other interface elements.
The user input component may be configured to obtain input information conveying user input into the templates to generate the user-generated project-level graphical user interfaces. The user input may identify the individual projects. The user interface may specify which of the values of the one or more of the project parameters of the individual projects are to be displayed in individual interface elements in the individual sets of interface elements. By way of non-limiting illustration, the input information may convey first user input from a first user into the first template to generate a first user-generated project-level graphical user interface. In some implementations, the first user input may identify the first project and/or may specify the values of a first project parameter of the first project are to be displayed in the first interface element, and the values of a second project parameter of the first project augmented reality to be displayed in the second interface element.
The user interface component may be configured to effectuate presentation of the user-generated project-level graphical user interfaces based on one or more of the template information, the input information, and/or other information. The individual user-generated project-level graphical user interfaces may include the individual sets of interface elements displaying the values of the one or more of the project parameters of the individual projects. By way of non-limiting illustration, the first user-generated project-level graphical user interface for the first project may be presented to reflect the values of the first project parameter of the first project in the first interface element, and the values of the second project parameter of the first project in the second interface element.
As used herein, any association (or relation, or reflection, or indication, or correspondency) involving servers, processors, client computing platforms, and/or another entity or object that interacts with any part of the system and/or plays a part in the operation of the system, may be a one-to-one association, a one-to-many association, a many-to-one association, and/or a many-to-many association or N-to-M association (note that N and M may be different numbers greater than 1).
These and other features, and characteristics of the present technology, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the invention. As used in the specification and in the claims, the singular form of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.
In some implementations, system 100 may include one or more of one or more servers 102, one or more client computing platforms 104, external resource(s) 126, and/or other components. Server(s) 102 may be configured to communicate with one or more client computing platforms 104 according to a client/server architecture and/or other architectures. Client computing platform(s) 104 may be configured to communicate with other client computing platforms via server(s) 102 and/or according to a peer-to-peer architecture and/or other architectures. Users may access system 100 via client computing platform(s) 104.
Server(s) 102 may include one or more of non-transitory electronic storage 128, one or more processors 130 configured by machine-readable instructions 106, and/or other components. The non-transitory electronic storage 128 may store one or more records and/or other information. Machine-readable instructions 106 may include one or more instruction components. The instruction components may include computer program components. Executing the machine-readable instructions 106 may cause server(s) 102 to facilitate generating project-level graphical user interfaces within a collaboration environment. The computer program components may include one or more of an environment state component 108, a template component 110, a user input component 112, an update component 114, a user interface component 116, and/or other components.
Environment state component 108 may be configured to manage environment state information and/or other information used in maintaining a collaboration environment. The collaboration environment may be configured to facilitate interaction by users within the collaboration environment. The environment state information may include one or more of work unit records, project records, objective records, user records, and/or other records. The work unit records may include work information comprising values for work unit parameters associated with units of work managed, created, and/or assigned within the collaboration environment. The project records may include project information comprising values for project parameters associated with project created, assigned, and/or managed within the collaboration environment. The objective records may include objective information comprising values for objective parameters associated with business objectives defined within the collaboration environment. In some implementations, individual projects may include individual sets of the units of the units of work supporting the individual projects. The project records may include a first project record for a first project.
The work information in the work unit records may include values of one or more work unit parameters. The values of the work unit parameters may be organized in work unit records corresponding to units of work managed, created, and/or assigned within the collaboration environment. A given unit of work may have one or more assignees and/or collaborators working on the given work unit. Units of work may include one or more to-do items, action items, objectives, and/or other units of work one or more users should accomplish and/or plan on accomplishing. Units of work may be created by a given user for the given user and/or created by the given user and assigned to one or more other users. Individual units of work may include one or more of an individual task, an individual sub-task, and/or other units of work assigned to and/or associated with one or more users. Individual units of work may include one or more digital content items. An individual unit of work may include an individual digital content item by virtue of the individual digital content item (and/or a copy or instance thereof) being attached and/or appended thereto. A digital content item may include one or more of an image, a video, an audio file, a PDF, a word document, and/or other digital content items.
In some implementations, units of work created by, assigned to, and/or completed by the users may refer generally to a linking of the units of work with the individual users in the collaboration environment. A unit of work may be linked with a user in a manner that defines one or more relationships between the user and the unit of work. Such a relationship may connote and/or be a result of an action (past, present, and/or future) of the user with respect to the unit of work. Such actions may include one or more of creating a work unit record for a unit of work, being assigned to participate in a unit of work, participating in a unit of work, being granted access to a work unit record of a unit of work, adjusting a value of a work unit parameter of a work unit record of a unit of work, and/or other actions.
Individual sets of work unit records may be defined by a record hierarchy. A record hierarchy may convey individual positions of work unit records (and their corresponding units of work) in the record hierarchy. By way of non-limiting illustration, a position may specify one or more of a work unit record being superior to another work unit record, a work unit record being subordinate to another work unit record, and/or other information. As a result, individual work unit records in the individual sets of work unit records may be subordinate to other individual work unit records in the individual sets of work unit records. For example, a work unit record may define a unit of work comprising a task, and a subordinate work unit record may define a unit of work comprising a sub-task to the task. A record hierarchy may define a relationship between work unit records. A work unit record may have some restrictions placed on it by virtue of having a subordinate work unit record. By way of non-limiting illustration, a work unit record may be restricted from access by one or more users unless and/or until a subordinate work unit record is completed and/or started.
Individual work unit records may include hierarchical information defining a record hierarchy of the individual work unit records. The hierarchical information of a work unit record may include one or more of information identifying other work unit records associated in a record hierarchy the work unit record belongs to, a specification of the position of the work unit record in the hierarchy, restrictions and/or other relationships placed on the work unit record by virtue of its position, and/or other information.
In some implementations, values of work unit parameters may include one or more of a unit of work name, a unit of work description, one or more unit of work dates (e.g., a start date, a due date or end date, a completion date, and/or dates), one or more users linked to a unit of work (e.g., an owner, one or more collaborators, collaborator access information, and/or other information), role information, a status parameter (e.g., an update, a hardcoded status update, a completed/incomplete/mark complete, a measured status, a progress indicator, quantity of sub-work units remaining for a given unit of work, measure of urgency, and/or other status parameter), one or more user comment parameters (e.g., permission for who may make comments such as an assignee, an assignor, a recipient, one or more followers, and/or one or more other interested parties; content of the comments; one or more times; presence or absence of the functionality of up-votes; one or more hard-coded responses; and/or other parameters), one or more interaction parameters (e.g., indicating a given unit of work is being worked on/was worked on, a given work unit of work was viewed, a given unit of work was selected, how long the given unit of work has been idle, a last interaction parameter indicating when and what user last interacted with the given unit of work, users that interacted with the given unit of work, quantity and/or content of comments on the unit of work, and/or other interaction parameters indicating sources of the interactions, context of the interactions, content of the interactions and/or time for the interactions), one or more digital content item attachments, notification settings, privacy, an associated URL, one or more interaction parameters (e.g., sources of the interactions, context of the interactions, content of the interactions, time for the interactions, and/or other interaction parameters), updates, ordering of units of work within a given unit of work (e.g., tasks within a project, subtasks within a task, etc.), state of a workspace for a given unit of work (e.g., application state parameters, application status, application interactions, user information, and/or other parameters related to the state of the workspace for a unit of work), one or more performance/productivity metrics for a given unit of work, hierarchical information, one or more custom fields (e.g., priority, cost, stage, and/or other custom fields), and/or other information.
In some implementations, the one or more work unit parameters may include one or more of a work assignment parameter, work completion parameter, a work management parameter, work creation parameter, and/or other parameters. The values of the work assignment parameter may describe units of work assigned to the individual users. The values of the work management parameter may describe units of work managed by the individual users. The values of the work creation parameter may describe units of work created by the individual users.
The values of the work assignment parameter describing units of work assigned to the individual users may be determined based on one or more interactions by one or more users with a collaboration environment. In some implementations, one or more users may create and/or assign one or more unit of work to themselves and/or another user. In some implementations, a user may be assigned a unit of work and the user may effectuate a reassignment of the unit of work from the user or one or more other users.
In some implementations, values of the work completion parameter may indicate that a status a unit of work has changed from “incomplete” to “marked complete” and/or “complete”. In some implementations, a status of complete for a unit of work may be associated with the passing of an end date associated with the unit of work. In some implementations, a status of “marked complete” may be associated with a user providing input via the collaboration environment at the point in time the user completes the unit of work (which may be before or after an end date).
In some implementations, managing by the environment state component 108 may include maintaining queues of the units of work assigned to the users. The queues may be presented to the users in a user interface of the collaboration environment to facilitate access to the units of work via work unit pages. Individual queues may represent the units of work assigned to individual users organized in an order based on the individual end dates and/or other dates (e.g., start dates) and/or other ordering. Individual queues may be presented in a user interface based on one or more of a list view, a calendar view, and/or other views. The calendar view may be a calendar view by week, by more than one week (e.g., 1st through 15th), by month, by more than one month (e.g., May through July), and/or other calendar views. Units of work may be representing in a calendar view by user interface elements (e.g., icons, calendar entries, etc.).
Project information in project records may define values of project parameters for projects created, assigned, and/or managed within the collaboration environment. The project parameters may characterize one or more projects managed within the collaboration environment and/or via the collaboration environment, and/or the metadata associated with the one or more projects. Individual ones of the projects may be associated with individual ones of the project records. The project information may define values of the project parameters associated with a given project managed within the collaboration environment and/or via the collaboration environment. A given project may have one or more owners and/or one or more collaborators working on the given project. The given project may include one or more units of work assigned to one or more users under the given project heading. In some implementations, projects may include one or more units of work that may directly facilitate progress toward fulfillment of the projects. Accordingly, completion of the set of units of work may directly contribute to progress toward fulfillment of the project. By way of non-limiting illustration, an individual project may be associated with a client and the units of work under the individual project heading may be work directly contributing to the fulfillment of a business relationship with the client.
The values of the project parameters may, by way of non-limiting example, include one or more of: one or more units of work supporting individual ones of the projects (which may include values of work unit parameters included in one or more work unit records), one or more users linked to the project (which may include values of user parameters defined by one or more user records), role information, one or more user comment parameters (e.g., a creator, a recipient, one or more followers, one or more other interested parties, content, one or more times, upvotes, other hard-coded responses, etc.), a project name, a project description and/or background summary, a project problem statement, a project solution statement, one or more risks associated with the project, one or more project dates (e.g., a start date, a due date, a completion date, and/or other project dates), one or more project collaborators (e.g., an owner, one or more other project collaborators, collaborator access information, and/or other information), a status and/or progress (e.g., an update, a hardcoded status update, a measured status, quantity of units of work remaining in a given project, completed units of work in a given project, and/or other status parameter), one or more resources, one or more demonstrable assets associated with a project, one or more business objectives supported by the projects, notification settings, permissions information, an associated URL, one or more interaction parameters (e.g., sources of the interactions, context of the interactions, content of the interactions, time for the interactions, and/or other interaction parameters), updates, ordering of units of work within the given project, state of a workspace for a given task within the given project, and/or other information.
In some implementations, project records may include permissions information for the individual projects. The permissions may specify access restrictions for the individual project. The access restrictions may be specified on a user-basis, user role-bases (e.g., based on one or more of organization role, role in units of work, and/or project-level role), for groups of users, and/or specified in other ways).
Role information may be specified in one or more of the work unit records, project records, user records, and/or other records. The role information may specify roles of the users within the units of work, the projects, and/or a business organization as a whole. The roles may convey expected contribution of the users in completing and/or supporting the units of work and/or the projects. The individual roles of individual users within the units of work may be specified separately from the individual roles of the individual users within the projects. The project parameters may include a project role parameter characterizing the individual roles of the individual users with respect to individual projects.
A role may represent expected contribution of the users in completing and/or supporting the units of work and/or the projects. A role specified with respect to units of work and/or projects may be different from roles traditionally specified with respect to a business organization as a whole (e.g., President, CEO, intern, product designer, legal counsel, etc.). For example, an organization role may be “Product Designer”; a project role may be “Design Lead”; and a role on an individual unit of work may be “Approver.”
A role within a unit of work may be specified based on one or more of a job title, a description of what the user should accomplish and/or plan on accomplishing for the given unit of work, and/or other specifications. By way of non-limiting illustration, a role within a unit of work may include one or more of general assignee, graphic designer, engineer, tester, writer, artist, mechanic, and/or other descriptions.
A role within a project (e.g., a “project-level role”) may be specified based on a description of what the user may be supporting and/or plan on supporting for the given project, and/or other specifications. By way of non-limiting illustration, a role within a project may include one or more of owner, design, marketing, copy, legal, engineering, art director, and/or other descriptions. Although the specification of the role in a project may include the same or similar words as the role in a unit of work, the role in the project may enable and/or disable features within the collaboration environment otherwise not available to users of having roles in individual units of work but not at the project level. In some implementations, roles within a project may take on a more supervisory connotation than the roles within the individual units of work.
In some implementations, project parameters may include one or more of a description parameter, background parameter, problem statement parameter, solution parameter, risks parameter, resources parameter, supporting parameter, supported parameter, supporters parameter, status parameter, design parameter, and/or other parameters.
A description parameter may characterize a description of the individual projects. The description of the individual project may include descriptions about how to use the project. The description of the individual project may be defined when the project is created and may or may not be editable after creation. In some implementations, the description may only be edited by users assigned a given role. By way of non-limiting illustration, a value of a description parameter may include one or more of summary, purpose, and/or other descriptions. A summary of an individual project may include a basic explanation of what the project entails. A purpose of an individual project may include reasons why the project is being pursued and details of the project's innovation.
A background parameter may characterize a background description of the individual projects. In some implementations, the background description may include historical perspectives of the field of the individual projects, comparison of other related individual projects, and/or other background related information. A background description may include a historical overview of the pertinent field of the project and what has been done in the past with respect to the field in which the project is involved in. The background description of the individual project may be defined when the project is created and may or may not be editable after creation. In some implementations, the background description may only be edited by users assigned a given role. In some implementations, background description may be defined during the creation of a user-generated project level graphical user interface.
A problem statement parameter may characterize a problem statement of the individual projects. In some implementations, the problem statement may include the purpose of the individual projects, the failures of other completed individual projects in the same field, and/or other problem statement related information. The problem statement of the individual project may be defined when the project is created and/or may or may not be editable after creation. In some implementations, the problem statement may only be edited by users assigned a given role. In some implementations, problem statement may be defined during the creation of a user-generated project level graphical user interface.
A solution statement parameter may characterize a solution statement of the individual projects. In some implementations, the solution statement may include the solution to the problem statement, solutions that other individual projects have used in the past, theoretical solutions to successfully completing individual projects, and/or other solution statement related information. The solution statement of the individual project may be defined when the project is created and/or may or may not be editable after creation. In some implementations, the solution statement may only be edited by users assigned a given role. In some implementations, solution statement may be defined during the creation of a user-generated project level graphical user interface.
A risks parameter may characterize risks associated with the individual projects. In some implementations, risks may include consequences of not successfully completing an individual project on time, factors to be careful of when completing a project as it might negatively impact other individual projects, and/or other risks information. The risks of the individual project may be defined when the project is created and/or may or may not be editable after creation. In some implementations, the risks may only be edited by users assigned a given role. In some implementations, risks may be defined during the creation of a user-generated project level graphical user in
A resources parameter may characterize resource(s) of the individual projects. In some implementations, resources parameter may characterize internal or external resources that are associated to the project. Resources may include digital assets in the form of a file, a document, an attachment, a link to a project within the collaboration environment that may provide relevant information to the individual project, and/or other content. In some implementations, a resource may include an application program (e.g., word processing application, graphic design application, etc.). External resource(s) 126 may include sources of information outside of system 100, external entities participating with system 100, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resource(s) 126 may be provided by resources included in system 100.
In some implementations, the values of the resources parameter may include instances of digital assets included in individual units of work supporting the individual projects. Instances may include how the digital asset appears on an individual user's unit of work. Digital assets may include one or more of a pdf, image file, online content, and/or other assets. By way of non-limiting illustration, instances of digital assets may include a first pdf document in a first unit of work that began to be worked on by a first user. The instance of the first pdf document may be shared with a second user in a second unit of work, that is to be finalized by a second user.
A supporting parameter may characterize individual units of work supporting the individual projects. The values of the supporting parameter may include the values of one or more of the work unit parameters of the individual units of work supporting the individual projects. In some implementations, one or more units of work may be indicated as milestones for the project and/or may have other tags and/or status associated therewith. In some implementations, milestones may be representative of predetermined progress in the completion of a project. By way of non-limiting illustration, given two milestones within an individual project, the first milestone may indicate 30% project completion, while a second milestone may indicate 60% project completion.
A design parameter may characterize demonstrable assets associated with the individual project. In some implementations, a design parameter may include a video commercial describing individual projects, a slide show presenting an overview of individual projects, and/or other design related information. The demonstrable assets of the individual project may be defined when the project is created and/or may or may not be editable after creation. In some implementations, the demonstrable assets may only be edited by users assigned a given role. In some implementations, demonstrable assets may be created during the creation of a user-generated project level graphical user interface.
A supported parameter may characterize individual business objectives supported by the individual projects. The values of the supported parameter may include the values of one or more of the objective parameters of the individual business objectives supported by the individual projects.
A supporters parameter may characterize the users having project-level roles within the individual projects. The values of the supporters parameter may include the values of one or more user parameters of the users having the project-level roles within the individual projects. Users may be associated with certain user roles within a collaboration environment representing their position. Individual projects may be a scenario where a user's role changes, representing an individual position for the individual project.
The objective information in objective records may include values of one or more objective parameters. The values of the objective parameters may be organized in objective records corresponding to business objectives managed, created, and/or owned within the collaboration environment. A given business objective may have one or more collaborators, and/or team members working on the given business objective. Business objectives may include one or more associated units of work and/or projects one or more users should accomplish and/or plan on accomplishing. Business objectives may be created by a given user for the given user and/or created by the given user and assigned to be owned to one or more other users. Individual business objectives may include one or more of an individual goal, an individual sub-goal, and/or other business objectives assigned to be owned by a user and/or associated with one or more users.
The business objectives may be associated with a set of units of work and/or projects that may indirectly facilitate progress toward fulfillment of the business objectives. The set of units of work and/or projects may not directly contribute to the progress. By way of non-limiting illustration, a connection between the set of units of work and/or projects and a corresponding business objective may be indirect in that completion of at least one of the units of work and/or projects may have no direct impact on progress toward fulfillment of the business objective. The concept of “no direct impact” may mean that completion of the at least one unit of work and/or project may not cause progress toward fulfillment of the business objective without independent action outside of the at least one unit of work and/or project. Instead, the fulfillment of the at least one unit of work and/or project may make such independent action more likely (e.g., through coercion, assistance, education, incentivization, reminder, etc.). However, in some implementations, business objectives may be associated with a set of units of work and/or projects that may directly facilitate progress toward fulfillment of the business objectives. Accordingly, completion of the set of units of work and/or projects may directly contribute to the progress toward fulfillment. Business objectives may be associated with an objectives and key result (OKR) goal-setting framework. Business objectives may be specified on one or more of a team basis, organization basis, and/or other specifications. In some implementations, business objectives may be characterized as user objectives. The user objectives may be associated with a set of units of work and/or projects that may indirectly (and/or directly) facilitate progress toward fulfillment of the user objectives. User objectives may be specified on an individual user basis.
Individual objective records may describe individual business objectives and identify sets of individual ones of the work unit records and/or project records that specify the units of work and/or projects as being associated with the individual business objectives.
Individual sets of objective records may be defined by an objective record hierarchy. An objective record hierarchy may convey individual positions of objective records (and their corresponding business objectives) in the objective record hierarchy. By way of non-limiting illustration, a position may specify one or more of an objective record being superior to one or more other objective records, an objective record being subordinate to one or more other objective records, and/or other information. As a result, individual objective records may be subordinate and/or superior to other individual objective records. For example, the objective records may further include a second objective record. The first objective record and the second objective record may be organized by a first objective record hierarchy specifying that the second objective record is subordinate to the first objective record.
An objective record may define a business objective comprising a progress towards fulfillment, and a subordinate objective record may define a business objective comprising a subordinate progress towards fulfillment to the subordinate business objective. An objective record hierarchy may define a relationship between objective records.
Individual objective records may include hierarchical information defining an objective record hierarchy of the individual objective records. The hierarchical information of an objective record may include one or more of information identifying other objective records associated in an objective record hierarchy the objective record belongs to, a specification of the position of the objective record in the hierarchy, other relationships placed on the objective record by virtue of its position, and/or other information.
In some implementations, as a consequence of the objective record hierarchies, the individual business objectives described in the individual objective records that are subordinate to the other individual objective records may be subordinate to the individual business objectives in the other individual objective records.
In some implementations, the one or more objective parameters may include one or more of an objective definition parameter, an objective owner parameter, an objective management parameter, an objective creation parameter, an objective progress parameter, and/or other parameters. The value of the objective definition parameter may describe the particular business objective. The values of the objective owner parameter may describe business objectives assigned to be owned by an individual user. The values of the objective management parameter may describe business objectives managed as collaborators by the individual users. The values of the objective creation parameter may describe business objectives created by the individual users.
In some implementations, the business objectives may be described based on one or more of a business objective name, a business objective description, one or more business objective dates (e.g., a start date, a due date, and/or dates), one or more members associated with a business objective (e.g., an owner, one or more other project/task members, member access information, and/or other business objective members and/or member information), progress information (e.g., an update, a hardcoded status update, a measured status, a progress indicator, quantity value remaining for a given business objective, completed work units in a given project, and/or other progress information), one or more interaction parameters, notification settings, privacy, an associated URL, one or more custom fields (e.g., priority, cost, stage, and/or other custom fields), and/or other information.
The values of the objective owner parameter describing business objectives owned by the individual users may be determined based on one or more interactions by one or more users with a collaboration environment. In some implementations, one or more users may create and/or assign ownership of one or more business objectives to themselves and/or another user. In some implementations, a user may be assigned to own a business objective and the user may effectuate a reassignment of ownership of the business objective from the user or one or more other users.
The user information in the user records may include values of user parameters. The values of the user parameters may be organized in user records corresponding to users interacting with and/or viewing the collaboration environment. The values of the user parameters may include information describing the users, their actions within the collaboration environment, their settings, and/or other user information; and/or metadata associated with the users, their actions within the environment, their settings, and/or other user information. Individual ones of the users may be associated with individual ones of the user records. A user record may define values of the user parameters associated with a given user.
The values of the user parameters may, by way of non-limiting example, specify one or more of: a user name, a group parameter, a user account, role information, a user department, descriptive user content, a to-email, a from-email, a photo, an organization, a workspace, one or more user comments, one or more teams the user belongs to, one or more of the user display settings (e.g., colors, size, project order, task order, other unit of work order, etc.), one or more authorized applications, one or more interaction parameters (e.g., indicating a user is working on/worked on a given unit of work, a given user viewed a given work unit of work, a given user selected a given unit of work, a timeframe a given user last interacted with and/or worked on a given unit of work, a time period that a given unit of work has been idle, and/or other interaction parameters), one or more notification settings, one or more progress parameters, status information for one or more work units the user is associated with (units of work assigned to the user, assigned to other users by the user, completed by the user, past-due date, and/or other information), one or more performance/productivity metrics of a given user (e.g., how many units of work the user has completed, how quickly the user completed the units of work, how quickly the user completes certain types of work units, the efficiency of the user, bandwidth of the user, activity level of the user, how many business objectives the user has helped fulfill through their completion of units of work, etc.), application access information (e.g., username/password for one or more third-party applications), one or more favorites and/or priorities, schedule information, and/or other information.
Environment state component 108 may be configured to manage information defining user-generated project-level graphical user interfaces corresponding to individual projects of the collaboration environment. By way of non-limiting illustration, the individual user-generated project-level graphical user interfaces may include individual sets of interface elements displaying the values of one or more of the project parameters of the individual projects. A first user-generated project-level graphical user interface may be associated with a first project. The first user-generated project-level graphical user interface may include a first set of user interface elements displaying the values of a first set of project parameters of the first project.
In some implementations, the values of one or more of the project parameters of the individual projects displayed in the individual user-generated project-level graphical user interfaces may be dictated based on a template being used and/or the user input provided by a user into the template (see, e.g., template component 110 and/or user interface component 112). By way of non-limiting illustration, user-generated project-level graphical user interface may include user interface elements displaying values of one or more of a description parameter, background parameter, problem statement parameter, solution parameter, risks parameter, design parameter, resources parameter, supporting parameter, supported parameter, supporters parameter, status parameter, and/or other project parameters.
In some implementations, displaying the values of one or more of the project parameters of the individual projects may include determining visual representations of the values of the one or more project parameters. The visual representations may be one or more of numeric representations, graphical representations (e.g., charts, graphs, etc.), and/or other representations. In some implementations, visual representations may be direct representations. By way of non-limiting illustration, a value of a project parameter may be directly presented in a project-level graphical user interface. For example, a value of a project parameter for a project specifying that the project includes ten tasks may be represented in an interface element as “This project has ten tasks.” In some implementations, visual representations may be indirect representations. By way of non-limiting illustration, a value of a project parameter may be used as a basis for determining a display that represents the value but may not directly and/or explicitly convey the value. By way of non-limiting illustration, a value of a project parameter for a project specifying that the project includes five out of ten tasks already being completed may be represented in an interface element as a pie chart that is half shaded to represent half of the project's tasks being completed.
In some implementations, the values of a supporting parameter may include the values of one or more of the work unit parameters of the individual units of work supporting the individual projects. The supporting parameter may be visually represented as a list of units of work that support a project. The individual units of work may be visually represented by values of work unit parameters including, but not limited to, title, completion state, assignee, and/or other information. The list may be a quick reference to users of individual units of work that have been completed and/or of individual units of work that need to be addressed with respect to the project. In some implementations, individual units of work may be selected from the graphical user interface to take the user to a work unit page for an individual unit of work.
In some implementations, values of a supporters parameter may be visually represented by a roster of users having project-level roles. An individual user may be represented by an icon with an image of a user's face and/or avatar. By way of non-limiting illustration, the image may be accompanied with an interface element presenting a description of the user's project-level role, and/or other descriptors. In some implementations, individual icons representing individual users may provide access to individual user pages for the individual users.
In some implementations, values of a description parameter, background parameter, problem statement parameter, and solution statement parameter may be visually represented by a text display portion showing the text that makes up the values of the parameters.
In some implementations, values of a resources parameter may define instances of digital assets included in individual units of work supporting the individual projects. The resources parameter may be visually represented by an arrangement of one or more icons. Individual icons may represent individual resources. In some implementations, an individual icon may provide a link to a resource and/or may comprise an instance of a resource (e.g., PDF file).
In some implementations, values of a supported parameter may be visually represented as a list of business objectives supported by a project. The business objectives may be visually represented by values of objective parameters including, but not limited to title, status, associated dates, and/or other information. The list may be a quick reference to users of individual business objectives supported by the project. In some implementations, individual business objectives may be selected from the graphical user interface to take the user to a business objective page for the individual business objectives.
In some implementations, values of a risks parameter may be visually represented by a list. In some implementations, the risks parameter may describe the risks related to the completion of the project. By way of non-limiting illustration, if a first project is not successfully completed by a certain first date then a second and/or third project risk being unable to be completed by their second and third due dates.
In some implementations, values of a design parameter may define instances of the demonstrable assets. The design parameter may be visually represented by a video, power point, and/or other methods to present content related to individual projects.
The template component 110 may be configured to manage template information defining templates for user-generated project-level graphical user interfaces of the collaboration environment. In some implementations, individual templates may include the individual sets of interface elements as empty fields. The empty fields are configured to eventually display the values of one or more of the project parameters of the individual projects. By way of non-limiting illustration, a first template may include a first interface element, a second interface element, and/or other interface elements. In some implementations, user may provide input into the templates in order to add information to the interface elements. The user input may include dragging and dropping dynamic interface objects representing suggested values.
By way of non-limiting illustration, the individual sets of interface elements may be organized in many different ways according to the kinds of project parameters being added to the user-generated project-level graphical user interface. In some implementations the values of the project parameters may be in the visual form of textual displays which might appear as a list of values of the project parameters. In some implementations, the values of the project parameters may be in the form of different kinds of content (e.g., timelines, videos, lists, graphs) which can be organized in a visually appealing manner in the user-generated project-level graphical user interface.
In some implementations, the one or more interface elements may be pre-configured on the user-generated project-level graphical user interfaces by the templates, corresponding to predetermined ones of the values of the project parameters that have been impacted the most. This may include values(s) having the relatively most change in relation to other values, value(s) having the relatively most user interaction in relation to the values than other values, and/or other considerations. By way of non-limiting illustration, if monitoring use of the collaboration environment by a set of users shows that the users update the description of a project (e.g., which is a value of a project parameter) on a continuing monthly basis, then the description of the project may be determined to have been impacted the most. Accordingly, a template may be created to include at least one interface element preconfigured to display the project description in a user-generated project-level graphical user interface for that project. By way of non-limiting illustration, if monitoring use of the collaboration environment by a set of users shows that the users frequently view the completed units of work in a project (which is a value of a project parameter) to determine the number of completed units of work compared to complete units of work, then the completed units of work in a project may be determined to have been impacted the most. Accordingly, a template may be created to include at least one interface element pre-configured to display the number of completed units of work (or a chart showing the relationship between completed and incomplete units of work) in a user-generated project-level graphical user interface for that project.
The user input component 112 may obtain input information conveying user input into the templates to generate the user-generated project-level graphical user interfaces. The user input may include identifying the individual projects and/or specifying which of the values of the one or more of the project parameters of the individual projects may be displayed in the individual interface elements in the individual sets of interface elements. In some implementations, the templates may include a “suggested content” portion that includes one or more dynamic user interface elements providing a technique to specify which of the values of the one or more of the project parameters of the individual projects are to be displayed in the individual interface elements. “Dynamic” may mean that they are elements configured to be manipulated by a user. Individual ones of the dynamic user interface elements may represent individual project parameters. A user may provide drag-and-drop input (and/or other input) of the dynamic user interface elements into individual ones of the interface elements on the templates. This input may cause the individual interface elements to take on the values of the project parameters associated with the dynamic user interface elements, thereby generating the user-generated project-level graphical user interfaces.
By way of non-limiting illustration, the input information may convey first user input from a first user into the first template to generate a first user-generated project-level graphical user interface. In some implementations, the first user input may identify the first project, may specify the values of a first project parameter of the first project are to be displayed in the first interface element, and/or that the values of a second project parameter of the first project are to be displayed in the second interface element.
In some implementations, the values of the one or more of the project parameters of the individual projects displayed in the individual user-generated project-level graphical user interface may include values subject to access restrictions in order to view. In some implementations, users may be prompted when attempting to add values of project parameter that violate access restrictions. In some implementations, the user input component 112 may either block the inclusion of values of project parameters violating access restrictions, and/or users may change access restrictions of the values of project parameters to allow their inclusion.
The update component 114 may be configured to monitor use of the collaboration environment by the users to determine change in the values of the one or more of the project parameters of the individual projects. In some implementations, update component 114 may be configured to dynamically update the user-generated project-level graphical user interfaces based on the change the values of the one or more of the project parameters of the individual projects.
In some implementations, change in the values of the one or more of the project parameters of the individual projects may include one or both of user-initiated change in the values and/or automated change in the values. By way of non-limiting illustration, if a first problem statement of a first individual project has changed due to a certain point in the progress of the first individual project (e.g., more problems have arisen to include in the statement) the first problem statement may be updated to display the current problems to be solved in the first individual project.
In some implementations, environment state information may be updated as users continue to interact with the collaboration environment via the user interfaces over time. The environment state component 108 may store and/or archive the environment state information periodically and/or based on user request to archive. In some implementations, the environment state component 108 may store historical environment state information specifying historical user information, historical work information, historical project information, historical objective information, user interaction history, and/or other information.
The user interface component 116 may be configured to effectuate presentation of the user-generated project-level graphical user interfaces based on one or more of the template information, the input information, and/or other information. By way of non-limiting illustration, the first user-generated project-level graphical user interface for the first project may be presented to reflect the values of the first project parameter of the first project in the first interface element and the values of the second project parameter of the first project in the second interface element.
The user interface component 116 may be configured to effectuate presentation of individual project pages displaying the individual projects. The individual project pages may provide access to the individual project records of the individual projects.
In some implementations, the user interface component 116 may be configured to provide access to the individual user-generated project-level graphical user interfaces of the individual projects from the individual project pages. By way of non-limiting illustration, the individual user-generated project-level graphical user interfaces may comprise a subset of the individual project pages. In some implementations, presentation of a subset of individual project pages may be based on selection of tabs at the top of the project pages. These tabs may be organized within the project pages according to different views of the individual projects. By way of non-limiting illustration, a user may provide input to specifically view an individual user-generated project-level graphical user interface from a project page. Other views of project information for the individual projects may include one or more of list views of project information, calendar (or timeline) views of project information, and/or other views.
Referring back to
A given client computing platform may include one or more processors configured to execute computer program components. The computer program components may be configured to enable an expert or user associated with the given client computing platform to interface with system 100 and/or external resource(s) 126, and/or provide other functionality attributed herein to client computing platform(s) 104. By way of non-limiting example, the given client computing platform 104 may include one or more of a desktop computer, a laptop computer, a handheld computer, a tablet computing platform, a NetBook, a Smartphone, a gaming console, and/or other computing platforms.
Server(s) 102 may include electronic storage 128, one or more processors 130, and/or other components. Server(s) 102 may include communication lines, or ports to enable the exchange of information with a network 117 and/or other computing platforms. Illustration of server(s) 102 in
Electronic storage 128 may comprise non-transitory storage media that electronically stores information. The electronic storage media of electronic storage 128 may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with server(s) 102 and/or removable storage that is removably connectable to server(s) 102 via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage 128 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. Electronic storage 128 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Electronic storage 128 may store software algorithms, information determined by processor(s) 130, information received from server(s) 102, information received from client computing platform(s) 104, and/or other information that enables server(s) 102 to function as described herein.
Processor(s) 130 may be configured to provide information processing capabilities in server(s) 102. As such, processor(s) 130 may include one or more of a digital processor, a physical processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s) 130 is shown in
It should be appreciated that although components 108, 110, 112, 114, and/or 116 are illustrated in
In some implementations, method 200 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method 200 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 200.
An operation 202 may manage environment state information maintaining a collaboration environment and/or other information. The collaboration environment may be configured to facilitate interaction by users with the collaboration environment. The environment state information may include one or more of work unit records, project records, objective records, and/or other records. The work unit records may include values for work unit parameters associated with units of work managed, created, and/or assigned within the collaboration environment. The project records may include values for the project parameters associated with projects managed within the collaboration environment. The objective records may include values for objective parameters associated with business objectives managed within the collaboration environment. In some implementations, individual projects may include individual sets of the units of work supporting the individual projects, the project records may include a first project record for a first project, and/or other information. Operation 202 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to environment state component 108, in accordance with one or more implementations.
An operation 204 may manage template information defining templates for project-level graphical user interfaces of the collaboration environment. The individual user-generated project-level graphical user interfaces may correspond to individual projects. In some implementations, individual templates may include individual sets of interface elements configured to display the values of one or more of the project parameters of the individual projects. By way of non-limiting illustration, a first template may include a first interface element and a second interface element. Operation 204 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to template component 110, in accordance with one or more implementations.
An operation 206 may obtain input information conveying user input into the templates to generate the user-generated project-level graphical user interfaces. The user input identifying the individual projects and specifying which of the values of the one or more of the project parameters of the individual projects may be displayed in individual interface elements in the individual sets of interface elements. By way of non-limiting illustration, the input information may convey first user input from a first user into the first template to generate a first user-generated project-level graphical user interface. In some implementations, the first user input may identify the first project and may specify the value of a first project parameter of the first project. The values may be displayed in the first interface element and the values of a second project parameter of the first project may be displayed in the second interface element. Operation 206 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to user input component 112, in accordance with one or more implementations.
An operation 208 may effectuate presentation of the user-generated project-level graphical user interfaces based on the template information and the input information. The individual user-generated project-level graphical user interfaces may include the individual sets of interface elements displaying the values of the one or more of the project parameters of the individual projects. By way of non-limiting illustration, the first user-generated project-level graphical user interface for the first project may be presented to reflect the values of the first project parameter of the first project in the first interface element and the values of the second project parameter of the first project in the second interface element. Operation 208 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to user interface component 116, in accordance with one or more implementations.
Although the present technology has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the technology is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present technology contemplates that, to the extent possible, one or more features of any implementation can be combined with one or more features of any other implementation.
Number | Name | Date | Kind |
---|---|---|---|
5233687 | Henderson, Jr. | Aug 1993 | A |
5524077 | Faaland | Jun 1996 | A |
5530861 | Diamant | Jun 1996 | A |
5548506 | Srinivasan | Aug 1996 | A |
5608898 | Turpin | Mar 1997 | A |
5611076 | Durflinger | Mar 1997 | A |
5623404 | Collins | Apr 1997 | A |
5721770 | Kohler | Feb 1998 | A |
5983277 | Heile | Nov 1999 | A |
6024093 | Cron | Feb 2000 | A |
6256651 | Tuli | Jul 2001 | B1 |
6292830 | Taylor | Sep 2001 | B1 |
6332147 | Moran | Dec 2001 | B1 |
6385639 | Togawa | May 2002 | B1 |
6578004 | Cimral | Jun 2003 | B1 |
6621505 | Beauchamp | Sep 2003 | B1 |
6629081 | Cornelius | Sep 2003 | B1 |
6769013 | Frees | Jul 2004 | B2 |
6859523 | Jilk | Feb 2005 | B1 |
7020697 | Goodman | Mar 2006 | B1 |
7039596 | Lu | May 2006 | B1 |
7086062 | Faour | Aug 2006 | B1 |
7349920 | Feinberg | Mar 2008 | B1 |
7418482 | Lusher | Aug 2008 | B1 |
7428723 | Greene | Sep 2008 | B2 |
7613688 | Wiest | Nov 2009 | B2 |
7640511 | Keel | Dec 2009 | B1 |
7676542 | Moser | Mar 2010 | B2 |
7779039 | Weissman | Aug 2010 | B2 |
7805327 | Schulz | Sep 2010 | B1 |
RE41848 | Daniell | Oct 2010 | E |
7917855 | Satish | Mar 2011 | B1 |
7991632 | Morris | Aug 2011 | B1 |
7996744 | Ojala | Aug 2011 | B2 |
7996774 | Sidenur | Aug 2011 | B1 |
8214747 | Yankovich | Jul 2012 | B1 |
8314809 | Grabowski | Nov 2012 | B1 |
8365065 | Gejdos | Jan 2013 | B2 |
8499300 | Zimberg | Jul 2013 | B2 |
8522240 | Merwarth | Aug 2013 | B1 |
8527287 | Bhatia | Sep 2013 | B1 |
8531447 | Walker | Sep 2013 | B2 |
8554832 | Moskovitz | Oct 2013 | B1 |
8572477 | Moskovitz | Oct 2013 | B1 |
8627199 | Handley | Jan 2014 | B1 |
8639552 | Chen | Jan 2014 | B1 |
8768751 | Jakowski | Jul 2014 | B2 |
8831879 | Stamm | Sep 2014 | B2 |
8843832 | Frields | Sep 2014 | B2 |
8863021 | Bee | Oct 2014 | B1 |
8938690 | Khouri | Jan 2015 | B1 |
9009096 | Pinckney | Apr 2015 | B2 |
9024752 | Tumayan | May 2015 | B2 |
9122834 | Caluya | Sep 2015 | B1 |
9143839 | Reisman | Sep 2015 | B2 |
9152668 | Moskovitz | Oct 2015 | B1 |
9189756 | Gilbert | Nov 2015 | B2 |
9201952 | Chau | Dec 2015 | B1 |
9208262 | Bechtel | Dec 2015 | B2 |
9251484 | Cantor | Feb 2016 | B2 |
9350560 | Hupfer | May 2016 | B2 |
9372596 | Breedvelt-Schouten | Jun 2016 | B2 |
9383917 | Mouton | Jul 2016 | B2 |
9405532 | Sullivan | Aug 2016 | B1 |
9405810 | Smith | Aug 2016 | B2 |
9454623 | Kaptsan | Sep 2016 | B1 |
9514424 | Kleinbart | Dec 2016 | B2 |
9600136 | Yang | Mar 2017 | B1 |
9674361 | Ristock | Jun 2017 | B2 |
9712576 | Gill | Jul 2017 | B1 |
9785445 | Mitsui | Oct 2017 | B2 |
9830398 | Schneider | Nov 2017 | B2 |
9842312 | Rosati | Dec 2017 | B1 |
9949681 | Badenes | Apr 2018 | B2 |
9953282 | Shaouy | Apr 2018 | B2 |
9959420 | Kiang | May 2018 | B2 |
9978040 | Lee | May 2018 | B2 |
9990636 | Lewis | Jun 2018 | B1 |
10001911 | Breedvelt-Schouten | Jun 2018 | B2 |
10003693 | Wolthuis | Jun 2018 | B2 |
10083412 | Suntinger | Sep 2018 | B2 |
10157355 | Johnson | Dec 2018 | B2 |
10192181 | Katkar | Jan 2019 | B2 |
10235156 | Johnson | Mar 2019 | B2 |
10264067 | Subramani | Apr 2019 | B2 |
10308992 | Chauvin | Jun 2019 | B2 |
10373084 | Kurjanowicz | Aug 2019 | B2 |
10373090 | Holm | Aug 2019 | B2 |
10382501 | Malatesha | Aug 2019 | B2 |
10454911 | Hanhirova | Oct 2019 | B2 |
10455011 | Kendall | Oct 2019 | B2 |
10496943 | De | Dec 2019 | B2 |
10586211 | Steplyk | Mar 2020 | B2 |
10594788 | Larabie-Belanger | Mar 2020 | B2 |
10606859 | Smith | Mar 2020 | B2 |
10613735 | Karpe | Apr 2020 | B1 |
10616151 | Cameron | Apr 2020 | B1 |
10623359 | Rosenstein | Apr 2020 | B1 |
10671692 | Koopman | Jun 2020 | B2 |
10684870 | Sabo | Jun 2020 | B1 |
10706484 | Murnock | Jul 2020 | B1 |
10785046 | Raghavan | Sep 2020 | B1 |
10810222 | Koch | Oct 2020 | B2 |
10846105 | Granot | Nov 2020 | B2 |
10846297 | Smith | Nov 2020 | B2 |
10922104 | Sabo | Feb 2021 | B2 |
10956845 | Sabo | Mar 2021 | B1 |
10970299 | Smith | Apr 2021 | B2 |
10977434 | Pelz | Apr 2021 | B2 |
10983685 | Karpe | Apr 2021 | B2 |
11082281 | Justin | Aug 2021 | B2 |
11095468 | Pandey | Aug 2021 | B1 |
11113667 | Jiang | Sep 2021 | B1 |
11138021 | Rosenstein | Oct 2021 | B1 |
11140174 | Patel | Oct 2021 | B2 |
11204683 | Sabo | Dec 2021 | B1 |
11212242 | Cameron | Dec 2021 | B2 |
11263228 | Koch | Mar 2022 | B2 |
11288081 | Sabo | Mar 2022 | B2 |
11290296 | Raghavan | Mar 2022 | B2 |
11327645 | Karpe | May 2022 | B2 |
11341444 | Sabo | May 2022 | B2 |
11341445 | Cheng | May 2022 | B1 |
11443281 | Culver | Sep 2022 | B2 |
11500620 | Scolnick | Nov 2022 | B2 |
11501063 | Norota | Nov 2022 | B2 |
20020065798 | Bostleman | May 2002 | A1 |
20020082889 | Oliver | Jun 2002 | A1 |
20020143594 | Kroeger | Oct 2002 | A1 |
20030028595 | Vogt | Feb 2003 | A1 |
20030036934 | Ouchi | Feb 2003 | A1 |
20030041317 | Sokolov | Feb 2003 | A1 |
20030097406 | Stafford | May 2003 | A1 |
20030097410 | Atkins | May 2003 | A1 |
20030106039 | Rosnow | Jun 2003 | A1 |
20030126001 | Northcutt | Jul 2003 | A1 |
20030200223 | Hack | Oct 2003 | A1 |
20030225598 | Yu | Dec 2003 | A1 |
20030233265 | Lee | Dec 2003 | A1 |
20030233268 | Taqbeem | Dec 2003 | A1 |
20040083448 | Schulz | Apr 2004 | A1 |
20040093290 | Doss | May 2004 | A1 |
20040093351 | Lee | May 2004 | A1 |
20040098291 | Newburn | May 2004 | A1 |
20040122693 | Hatscher | Jun 2004 | A1 |
20040125150 | Adcock | Jul 2004 | A1 |
20040162833 | Jones | Aug 2004 | A1 |
20040187089 | Schulz | Sep 2004 | A1 |
20040207249 | Baumgartner | Oct 2004 | A1 |
20040230447 | Schwerin-Wenzel | Nov 2004 | A1 |
20040268451 | Robbin | Dec 2004 | A1 |
20050027582 | Chereau | Feb 2005 | A1 |
20050210394 | Crandall | Sep 2005 | A1 |
20050216111 | Ooshima | Sep 2005 | A1 |
20050216830 | Turner | Sep 2005 | A1 |
20050222971 | Cary | Oct 2005 | A1 |
20050234886 | Mohraz | Oct 2005 | A1 |
20050262081 | Newman | Nov 2005 | A1 |
20060028917 | Wigginton | Feb 2006 | A1 |
20060047454 | Tamaki | Mar 2006 | A1 |
20060085245 | Takatsuka | Apr 2006 | A1 |
20060095859 | Bocking | May 2006 | A1 |
20060136441 | Fujisaki | Jun 2006 | A1 |
20060143270 | Wodtke | Jun 2006 | A1 |
20060167736 | Weiss | Jul 2006 | A1 |
20060190391 | Cullen, III | Aug 2006 | A1 |
20060200264 | Kodama | Sep 2006 | A1 |
20060218551 | Berstis | Sep 2006 | A1 |
20060224430 | Butt | Oct 2006 | A1 |
20060277487 | Poulsen | Dec 2006 | A1 |
20070016646 | Tendjoukian | Jan 2007 | A1 |
20070025567 | Fehr | Feb 2007 | A1 |
20070038494 | Kreitzberg | Feb 2007 | A1 |
20070041542 | Schramm | Feb 2007 | A1 |
20070050225 | Leslie | Mar 2007 | A1 |
20070073575 | Yomogida | Mar 2007 | A1 |
20070143169 | Grant | Jun 2007 | A1 |
20070147178 | Masuda | Jun 2007 | A1 |
20070150327 | Dromgold | Jun 2007 | A1 |
20070232278 | May | Oct 2007 | A1 |
20070239573 | Tien | Oct 2007 | A1 |
20070255674 | Mahoney | Nov 2007 | A1 |
20070255715 | Li | Nov 2007 | A1 |
20070260499 | Greef | Nov 2007 | A1 |
20070288283 | Fitzpatrick | Dec 2007 | A1 |
20070294344 | Mohan | Dec 2007 | A1 |
20080033777 | Shukoor | Feb 2008 | A1 |
20080033876 | Goldman | Feb 2008 | A1 |
20080034314 | Louch | Feb 2008 | A1 |
20080046471 | Moore | Feb 2008 | A1 |
20080079730 | Zhang | Apr 2008 | A1 |
20080082389 | Gura | Apr 2008 | A1 |
20080082956 | Gura | Apr 2008 | A1 |
20080091782 | Jakobson | Apr 2008 | A1 |
20080120129 | Seubert | May 2008 | A1 |
20080126930 | Scott | May 2008 | A1 |
20080133736 | Wensley | Jun 2008 | A1 |
20080134069 | Horvitz | Jun 2008 | A1 |
20080155547 | Weber | Jun 2008 | A1 |
20080158023 | Chung | Jul 2008 | A1 |
20080167937 | Coughlin | Jul 2008 | A1 |
20080175104 | Grieb | Jul 2008 | A1 |
20080195964 | Randell | Aug 2008 | A1 |
20080221946 | Balon | Sep 2008 | A1 |
20080222566 | Daughtrey | Sep 2008 | A1 |
20080244582 | Brown | Oct 2008 | A1 |
20080268876 | Gelfand | Oct 2008 | A1 |
20080270198 | Graves | Oct 2008 | A1 |
20080281665 | Opaluch | Nov 2008 | A1 |
20080313004 | Ryan | Dec 2008 | A1 |
20080313110 | Kreamer | Dec 2008 | A1 |
20090048986 | Anderson | Feb 2009 | A1 |
20090055796 | Springborn | Feb 2009 | A1 |
20090076878 | Woerner | Mar 2009 | A1 |
20090089133 | Johnson | Apr 2009 | A1 |
20090094623 | Chakra | Apr 2009 | A1 |
20090113310 | Appleyard | Apr 2009 | A1 |
20090133027 | Gunning | May 2009 | A1 |
20090167553 | Hong | Jul 2009 | A1 |
20090187454 | Khasin | Jul 2009 | A1 |
20090199113 | Mcwhinnie | Aug 2009 | A1 |
20090199192 | Laithwaite | Aug 2009 | A1 |
20090204463 | Burnett | Aug 2009 | A1 |
20090204471 | Elenbaas | Aug 2009 | A1 |
20090234699 | Steinglass | Sep 2009 | A1 |
20090235182 | Kagawa | Sep 2009 | A1 |
20090241053 | Augustine | Sep 2009 | A1 |
20090260010 | Burkhart | Oct 2009 | A1 |
20090287523 | Lau | Nov 2009 | A1 |
20090296908 | Lee | Dec 2009 | A1 |
20090299803 | Lakritz | Dec 2009 | A1 |
20090307319 | Dholakia | Dec 2009 | A1 |
20100005087 | Basco | Jan 2010 | A1 |
20100070888 | Watabe | Mar 2010 | A1 |
20100088137 | Weiss | Apr 2010 | A1 |
20100100594 | Frees | Apr 2010 | A1 |
20100106627 | O'Sullivan | Apr 2010 | A1 |
20100114786 | Aboujaoude | May 2010 | A1 |
20100115523 | Kuschel | May 2010 | A1 |
20100122334 | Stanzione | May 2010 | A1 |
20100131860 | Dehaan | May 2010 | A1 |
20100145801 | Chekuri | Jun 2010 | A1 |
20100169146 | Hoyne | Jul 2010 | A1 |
20100169802 | Goldstein | Jul 2010 | A1 |
20100180212 | Gingras | Jul 2010 | A1 |
20100223575 | Leukart | Sep 2010 | A1 |
20100269049 | Fearon | Oct 2010 | A1 |
20100299171 | Lau | Nov 2010 | A1 |
20100306007 | Ganapathyraj | Dec 2010 | A1 |
20100312605 | Mitchell | Dec 2010 | A1 |
20100313151 | Wei | Dec 2010 | A1 |
20110015961 | Chan | Jan 2011 | A1 |
20110022662 | Barber-Mingo | Jan 2011 | A1 |
20110054968 | Galaviz | Mar 2011 | A1 |
20110055177 | Chakra | Mar 2011 | A1 |
20110060720 | Devereux | Mar 2011 | A1 |
20110071878 | Gingras | Mar 2011 | A1 |
20110071893 | Malhotra | Mar 2011 | A1 |
20110072372 | Fritzley | Mar 2011 | A1 |
20110093538 | Weir | Apr 2011 | A1 |
20110093619 | Nelson | Apr 2011 | A1 |
20110113365 | Kimmerly | May 2011 | A1 |
20110154216 | Aritsuka | Jun 2011 | A1 |
20110161128 | Barney | Jun 2011 | A1 |
20110184768 | Norton | Jul 2011 | A1 |
20110270644 | Roncolato | Nov 2011 | A1 |
20110307100 | Schmidtke | Dec 2011 | A1 |
20110307771 | Lok | Dec 2011 | A1 |
20110307772 | Lloyd | Dec 2011 | A1 |
20120030194 | Jain | Feb 2012 | A1 |
20120035942 | Graupner | Feb 2012 | A1 |
20120041983 | Jennings | Feb 2012 | A1 |
20120066030 | Limpert | Mar 2012 | A1 |
20120066411 | Jeide | Mar 2012 | A1 |
20120072251 | Mircean | Mar 2012 | A1 |
20120079449 | Sanderson | Mar 2012 | A1 |
20120110087 | Culver | May 2012 | A1 |
20120117499 | Mori | May 2012 | A1 |
20120123835 | Chu | May 2012 | A1 |
20120131191 | May | May 2012 | A1 |
20120158946 | Shafiee | Jun 2012 | A1 |
20120192086 | Ghods | Jul 2012 | A1 |
20120210247 | Khouri | Aug 2012 | A1 |
20120221963 | Motoyama | Aug 2012 | A1 |
20120226617 | Kay | Sep 2012 | A1 |
20120239451 | Caligor | Sep 2012 | A1 |
20120254218 | Ali | Oct 2012 | A1 |
20120266068 | Ryman | Oct 2012 | A1 |
20120278388 | Kleinbart | Nov 2012 | A1 |
20120296993 | Heyman | Nov 2012 | A1 |
20120304187 | Maresh | Nov 2012 | A1 |
20120317108 | Okazaki | Dec 2012 | A1 |
20130007332 | Teh | Jan 2013 | A1 |
20130013560 | Goldberg | Jan 2013 | A1 |
20130014023 | Lee | Jan 2013 | A1 |
20130018688 | Nudd | Jan 2013 | A1 |
20130021629 | Kurilin | Jan 2013 | A1 |
20130066944 | Laredo | Mar 2013 | A1 |
20130067375 | Kim | Mar 2013 | A1 |
20130067549 | Caldwell | Mar 2013 | A1 |
20130073328 | Ehrler | Mar 2013 | A1 |
20130080919 | Kiang | Mar 2013 | A1 |
20130103412 | Nudd | Apr 2013 | A1 |
20130124254 | Jafri | May 2013 | A1 |
20130124638 | Barreto | May 2013 | A1 |
20130151421 | Van Der Ploeg | Jun 2013 | A1 |
20130151604 | Ranade | Jun 2013 | A1 |
20130173486 | Peters | Jul 2013 | A1 |
20130179208 | Chung | Jul 2013 | A1 |
20130179799 | Savage | Jul 2013 | A1 |
20130198676 | Garrett | Aug 2013 | A1 |
20130215116 | Siddique | Aug 2013 | A1 |
20130227007 | Savage | Aug 2013 | A1 |
20130246110 | Nakhayi Ashtiani | Sep 2013 | A1 |
20130246399 | Schneider | Sep 2013 | A1 |
20130275229 | Moganti | Oct 2013 | A1 |
20130279685 | Kohler | Oct 2013 | A1 |
20130317871 | Kulkarni | Nov 2013 | A1 |
20130321467 | Tappen | Dec 2013 | A1 |
20130339099 | Aidroos | Dec 2013 | A1 |
20130339831 | Gulanikar | Dec 2013 | A1 |
20140007005 | Libin | Jan 2014 | A1 |
20140012603 | Scanlon | Jan 2014 | A1 |
20140012616 | Moshenek | Jan 2014 | A1 |
20140025767 | De Kezel | Jan 2014 | A1 |
20140036639 | Taber | Feb 2014 | A1 |
20140040780 | Brian | Feb 2014 | A1 |
20140040905 | Tadanobu | Feb 2014 | A1 |
20140058801 | Deodhar | Feb 2014 | A1 |
20140059910 | Norton | Mar 2014 | A1 |
20140074536 | Meushar | Mar 2014 | A1 |
20140089719 | Daum | Mar 2014 | A1 |
20140101310 | Savage | Apr 2014 | A1 |
20140143000 | Kay | May 2014 | A1 |
20140156539 | Brunet | Jun 2014 | A1 |
20140165001 | Shapiro | Jun 2014 | A1 |
20140172478 | Vadasz | Jun 2014 | A1 |
20140189017 | Prakash | Jul 2014 | A1 |
20140200944 | Henriksen | Jul 2014 | A1 |
20140208325 | Chen | Jul 2014 | A1 |
20140215344 | Ligman | Jul 2014 | A1 |
20140229609 | Wong | Aug 2014 | A1 |
20140236663 | Smith | Aug 2014 | A1 |
20140244334 | De | Aug 2014 | A1 |
20140257894 | Melahn | Sep 2014 | A1 |
20140279294 | Field-Darragh | Sep 2014 | A1 |
20140288987 | Liu | Sep 2014 | A1 |
20140304836 | Velamoor | Oct 2014 | A1 |
20140310047 | De | Oct 2014 | A1 |
20140310051 | Meng | Oct 2014 | A1 |
20140337279 | Mo | Nov 2014 | A1 |
20140350997 | Holm | Nov 2014 | A1 |
20140364987 | Shikano | Dec 2014 | A1 |
20140372860 | Craven | Dec 2014 | A1 |
20150006448 | Gupta | Jan 2015 | A1 |
20150007058 | Wooten | Jan 2015 | A1 |
20150007336 | Zang | Jan 2015 | A1 |
20150012330 | Sugiura | Jan 2015 | A1 |
20150052437 | Crawford | Feb 2015 | A1 |
20150058053 | De | Feb 2015 | A1 |
20150098561 | Etison | Apr 2015 | A1 |
20150113540 | Rabinovici | Apr 2015 | A1 |
20150134393 | De | May 2015 | A1 |
20150153906 | Liao | Jun 2015 | A1 |
20150193735 | Lavrov | Jul 2015 | A1 |
20150213411 | Swanson | Jul 2015 | A1 |
20150215256 | Ghafourifar | Jul 2015 | A1 |
20150262111 | Yu | Sep 2015 | A1 |
20150312113 | Forutanpour | Oct 2015 | A1 |
20150312375 | Valey | Oct 2015 | A1 |
20150317595 | De | Nov 2015 | A1 |
20150339006 | Chaland | Nov 2015 | A1 |
20150363092 | Morton | Dec 2015 | A1 |
20150363481 | Haynes | Dec 2015 | A1 |
20150363733 | Brown | Dec 2015 | A1 |
20150379472 | Gilmour | Dec 2015 | A1 |
20160012368 | O'Connell | Jan 2016 | A1 |
20160048408 | Madhu | Feb 2016 | A1 |
20160048786 | Fukuda | Feb 2016 | A1 |
20160063192 | Johnson | Mar 2016 | A1 |
20160063449 | Duggan | Mar 2016 | A1 |
20160072750 | Kass | Mar 2016 | A1 |
20160110670 | Chatterjee | Apr 2016 | A1 |
20160124775 | Ashtiani | May 2016 | A1 |
20160140474 | Vekker | May 2016 | A1 |
20160140501 | Figlin | May 2016 | A1 |
20160147773 | Smith | May 2016 | A1 |
20160147846 | Smith | May 2016 | A1 |
20160148157 | Walia | May 2016 | A1 |
20160180277 | Skiba | Jun 2016 | A1 |
20160180298 | Mcclement | Jun 2016 | A1 |
20160182311 | Borna | Jun 2016 | A1 |
20160188145 | Vida | Jun 2016 | A1 |
20160216854 | Mcclellan | Jul 2016 | A1 |
20160224939 | Chen | Aug 2016 | A1 |
20160234391 | Wolthuis | Aug 2016 | A1 |
20160241609 | Xin | Aug 2016 | A1 |
20160275068 | Wenzel | Sep 2016 | A1 |
20160275436 | Kurjanowicz | Sep 2016 | A1 |
20160307210 | Agarwal | Oct 2016 | A1 |
20160313934 | Isherwood | Oct 2016 | A1 |
20160328217 | Hagerty | Nov 2016 | A1 |
20160342927 | Reznik | Nov 2016 | A1 |
20170004213 | Cunico | Jan 2017 | A1 |
20170009387 | Ge | Jan 2017 | A1 |
20170017364 | Kekki | Jan 2017 | A1 |
20170017924 | Kashiwagi | Jan 2017 | A1 |
20170039503 | Jones | Feb 2017 | A1 |
20170061341 | Haas | Mar 2017 | A1 |
20170068933 | Norton | Mar 2017 | A1 |
20170093874 | Uthe | Mar 2017 | A1 |
20170099296 | Fisher | Apr 2017 | A1 |
20170103369 | Thompson | Apr 2017 | A1 |
20170116552 | Deodhar | Apr 2017 | A1 |
20170132200 | Noland | May 2017 | A1 |
20170147960 | Jahagirdar | May 2017 | A1 |
20170153799 | Hoyer | Jun 2017 | A1 |
20170154024 | Subramanya | Jun 2017 | A1 |
20170177671 | Allgaier | Jun 2017 | A1 |
20170185592 | Frei | Jun 2017 | A1 |
20170192642 | Fishman | Jul 2017 | A1 |
20170206217 | Deshpande | Jul 2017 | A1 |
20170206501 | Wang | Jul 2017 | A1 |
20170249574 | Knijnik | Aug 2017 | A1 |
20170249577 | Nishikawa | Aug 2017 | A1 |
20170262294 | Yakan | Sep 2017 | A1 |
20170316358 | Candito | Nov 2017 | A1 |
20170316367 | Candito | Nov 2017 | A1 |
20170317898 | Candito | Nov 2017 | A1 |
20170323233 | Bencke | Nov 2017 | A1 |
20170323267 | Baek | Nov 2017 | A1 |
20170323350 | Laderer | Nov 2017 | A1 |
20170337517 | Defusco | Nov 2017 | A1 |
20170344754 | Kumar | Nov 2017 | A1 |
20170346861 | Pearl | Nov 2017 | A1 |
20170351385 | Ertmann | Dec 2017 | A1 |
20170364214 | Javed | Dec 2017 | A1 |
20180032524 | Byron | Feb 2018 | A1 |
20180052943 | Hui | Feb 2018 | A1 |
20180053127 | Boileau | Feb 2018 | A1 |
20180059910 | Wooten | Mar 2018 | A1 |
20180060785 | Carnevale | Mar 2018 | A1 |
20180060818 | Ishiyama | Mar 2018 | A1 |
20180063063 | Yan | Mar 2018 | A1 |
20180068271 | Abebe | Mar 2018 | A1 |
20180075387 | Kulkarni | Mar 2018 | A1 |
20180082255 | Rosati | Mar 2018 | A1 |
20180088754 | Psenka | Mar 2018 | A1 |
20180089625 | Rosati | Mar 2018 | A1 |
20180095938 | Monte | Apr 2018 | A1 |
20180102989 | Borsutsky | Apr 2018 | A1 |
20180131649 | Ma | May 2018 | A1 |
20180157477 | Johnson | Jun 2018 | A1 |
20180165610 | Dumant | Jun 2018 | A1 |
20180173386 | Adika | Jun 2018 | A1 |
20180189706 | Newhouse | Jul 2018 | A1 |
20180189735 | Lo | Jul 2018 | A1 |
20180189736 | Guo | Jul 2018 | A1 |
20180225795 | Napoli | Aug 2018 | A1 |
20180247352 | Rogers | Aug 2018 | A1 |
20180260081 | Beaudoin | Sep 2018 | A1 |
20180262620 | Wolthuis | Sep 2018 | A1 |
20180285471 | Hao | Oct 2018 | A1 |
20180285746 | Dunwoody | Oct 2018 | A1 |
20180300305 | Lam | Oct 2018 | A1 |
20180316636 | Kamat | Nov 2018 | A1 |
20180331842 | Faulkner | Nov 2018 | A1 |
20180336520 | Davis | Nov 2018 | A1 |
20180349108 | Brebner | Dec 2018 | A1 |
20180357049 | Epstein | Dec 2018 | A1 |
20180367477 | Hariram | Dec 2018 | A1 |
20180367483 | Rodriguez | Dec 2018 | A1 |
20180373804 | Zhang | Dec 2018 | A1 |
20190005048 | Crivello | Jan 2019 | A1 |
20190014070 | Mertvetsov | Jan 2019 | A1 |
20190018552 | Bloy | Jan 2019 | A1 |
20190034057 | Rudchenko | Jan 2019 | A1 |
20190068390 | Gross | Feb 2019 | A1 |
20190079909 | Purandare | Mar 2019 | A1 |
20190080289 | Kreitler | Mar 2019 | A1 |
20190089581 | Purandare | Mar 2019 | A1 |
20190095839 | Itabayashi | Mar 2019 | A1 |
20190095846 | Gupta | Mar 2019 | A1 |
20190102071 | Redkina | Apr 2019 | A1 |
20190102364 | Rochiramani | Apr 2019 | A1 |
20190102700 | Babu | Apr 2019 | A1 |
20190138583 | Silk | May 2019 | A1 |
20190138589 | Udell | May 2019 | A1 |
20190138961 | Santiago | May 2019 | A1 |
20190139004 | Vukovic | May 2019 | A1 |
20190147386 | Balakrishna | May 2019 | A1 |
20190187987 | Fauchère | Jun 2019 | A1 |
20190213509 | Burleson | Jul 2019 | A1 |
20190265821 | Pearl | Aug 2019 | A1 |
20190286462 | Bodnick | Sep 2019 | A1 |
20190318285 | Sebilleau | Oct 2019 | A1 |
20190340296 | Cunico | Nov 2019 | A1 |
20190340554 | Dotan-Cohen | Nov 2019 | A1 |
20190340574 | Ekambaram | Nov 2019 | A1 |
20190347094 | Sullivan | Nov 2019 | A1 |
20190347126 | Bhandari | Nov 2019 | A1 |
20190370320 | Kalra | Dec 2019 | A1 |
20200005241 | Westwood | Jan 2020 | A1 |
20200019907 | Notani | Jan 2020 | A1 |
20200059539 | Wang | Feb 2020 | A1 |
20200065736 | Relangi | Feb 2020 | A1 |
20200145239 | Ghods | May 2020 | A1 |
20200162315 | Siddiqi | May 2020 | A1 |
20200192538 | Karpe | Jun 2020 | A1 |
20200192908 | Smith | Jun 2020 | A1 |
20200193556 | Jin | Jun 2020 | A1 |
20200218551 | Sabo | Jul 2020 | A1 |
20200228474 | Cameron | Jul 2020 | A1 |
20200233879 | Papanicolaou | Jul 2020 | A1 |
20200244611 | Rosenstein | Jul 2020 | A1 |
20200328906 | Raghavan | Oct 2020 | A1 |
20200344253 | Kurup | Oct 2020 | A1 |
20210004380 | Koch | Jan 2021 | A1 |
20210004381 | Smith | Jan 2021 | A1 |
20210035069 | Parikh | Feb 2021 | A1 |
20210049555 | Shor | Feb 2021 | A1 |
20210073697 | Paranjape | Mar 2021 | A1 |
20210097466 | Sabo | Apr 2021 | A1 |
20210097490 | Ratcliff | Apr 2021 | A1 |
20210103451 | Sabo | Apr 2021 | A1 |
20210110347 | Khalil | Apr 2021 | A1 |
20210136012 | Barbitta | May 2021 | A1 |
20210141996 | Agrawal | May 2021 | A1 |
20210149925 | Mann | May 2021 | A1 |
20210157978 | Haramati | May 2021 | A1 |
20210182475 | Pelz | Jun 2021 | A1 |
20210209239 | Robinson | Jul 2021 | A1 |
20210209535 | Tezak | Jul 2021 | A1 |
20210216562 | Smith | Jul 2021 | A1 |
20210232282 | Karpe | Jul 2021 | A1 |
20210248304 | Olivier | Aug 2021 | A1 |
20210320891 | Rosenstein | Oct 2021 | A1 |
20210342361 | Radzewsky | Nov 2021 | A1 |
20210342785 | Mann | Nov 2021 | A1 |
20210342786 | Jiang | Nov 2021 | A1 |
20210382734 | Rosenstein | Dec 2021 | A1 |
20220019320 | Sabo | Jan 2022 | A1 |
20220019959 | Roy | Jan 2022 | A1 |
20220029886 | Hameiri | Jan 2022 | A1 |
20220058548 | Garg | Feb 2022 | A1 |
20220075792 | Koch | Mar 2022 | A1 |
20220078142 | Cameron | Mar 2022 | A1 |
20220101235 | Khalil | Mar 2022 | A1 |
20220158859 | Raghavan | May 2022 | A1 |
20220215315 | Sabo | Jul 2022 | A1 |
20220391921 | Wilner | Dec 2022 | A1 |
20230214509 | Kahawala | Jul 2023 | A1 |
20230252415 | Ackerman-Greenberg | Aug 2023 | A1 |
20230267419 | Beauchamp | Aug 2023 | A1 |
20230306370 | Clifton | Sep 2023 | A1 |
20240013153 | Jiang | Jan 2024 | A1 |
20240171621 | Ye | May 2024 | A1 |
20240220930 | Clifton | Jul 2024 | A1 |
20240310990 | Beauchamp | Sep 2024 | A1 |
Number | Date | Country |
---|---|---|
101305350 | Nov 2008 | CN |
101563671 | Oct 2009 | CN |
102378975 | May 2015 | CN |
3973263 | Sep 2007 | JP |
2008059035 | Mar 2008 | JP |
4315508 | Aug 2009 | JP |
4335340 | Sep 2009 | JP |
2015036817 | Mar 2015 | WO |
2015123751 | Aug 2015 | WO |
2016115621 | Jul 2016 | WO |
2020006634 | Jan 2020 | WO |
Entry |
---|
Klipfoliio. “What is a Project Management Dashboard?”. Jan. 18, 2021. <https://web.archive.org/web/20210128061955/https://www.klipfolio.com/resources/articles/project-management-dashboard> (Year: 2021). |
Creating Tables with Fields from 2 Different Tables, published: 2009, publisher: StackOverflow, pp. 1-2. (Year: 2009). |
“Rules of Data Conversion from Document to Relational Databases”, published: 2014, publisher: Future-processing, pp. 1-8 (Year: 2014). |
Critical chain project management, Wikipedia, archives org, Dec. 17, 2016 https://web.archive.Org/web/20161217090326/https://en.wikipedia.org/wiki/Critical_chain_project_management (Year: 2016) 5 pages. |
Critical Path Method, Wikipedia, archives org, Sep. 19, 2017 https://web.archive.Org/web/20170919223814/https://en.wikipedia.org/wiki/Critical_path_method (Year: 2017) 6 pages. |
Fruhlinger, Joshua. “The Best To-Do ListApps for Feeling Productive; With the right app, feeling productive can be just as gratifying as actually getting things done” Wall Street Journal (Online); New York, N.Y. [New York, N.Y]Nov. 8, 2013 (Year: 2013) 4 pages. |
Helen Mongan-Rallis & Terrie Shannon, “Synchronous Chat,” Aug. 2016, Dept. of Education, Univ. of MN Duluth, web.archive.org/web/20160825183503/https://www.d.umn.edu/hrallis/professional/presentations/cotfsp06/indiv_tools/sync_chat.htm (Year: 2016) (2 pages). |
Wix.com, How to Use Wix Code with Marketing Tools to Create Custom Events, Oct. 18, 2018, YouTube, https://www.youtube.com/watch?v=MTBVykOYGvO&feature=emb_title, 2 pages. |
www.asana.com (as retrieved from https://web.archive.Org/web/20160101054536/https://asana.com/press and https:// web.archive.org/web/20160101054527/https://asana.com/product) (Year: 2016) 15 pages. |
“U.S. Appl. No. 14/584,750, Examiner Interview Summary mailed Feb. 25, 2016”, 3 pgs. |
“U.S. Appl. No. 14/584,750, Non Final Office Action mailed Aug. 28, 2015”, 21 pgs. |
“U.S. Appl. No. 14/584,750, Notice of Allowance mailed Mar. 28, 2016”, 8 pgs. |
“U.S. Appl. No. 14/584,750, Response filed Feb. 29, 2015 to Non Final Office Action mailed Aug. 28, 2015”, 16 pgs. |
“U.S. Appl. No. 14/584,850, Final Office Action mailed Sep. 1, 2017”, 31 pgs. |
“U.S. Appl. No. 14/584,850, Non Final Office Action mailed Jan. 10, 2017”, 9 pgs. |
“U.S. Appl. No. 14/584,850, Response filed Apr. 10, 2017 to Non Final Office Action mailed Jan. 10, 2017”, 13 pgs. |
“How to Asana: Inviting teammates to Asana.” YouTube, Asana, Mar. 21, 2017, https:// www.youtube.com/watch?v=TLOruY1KyxU ( Year: 2017), 13 pages. |
Asana Demo and Product Tour, you tube excerpt, Dec. 7, 2017 https://www.youtube.com/watch?v=IMAFWVLGFyw (Year: 2017) (16 pages). |
Asana integrations, Asana tutorial, youtube, excerpt, Nov. 16, 2016 https://www.youtube.com/watch?v=hBiQ7DJNinE (Year: 2016) (21 pages). |
Asana Workload and Portfolios, youtube, excerpt, Aug. 1, 2019 https://www.youtube.com/watch?v=7XkNcfFDG6M (Year: 2019) (20 pages). |
Asana YouTube channel, list of all product videos, Nov 19, 2014-Aug. 19, 2019 https://www.youtube.com/user/AsanaTeam/videos?disable_polymer=1 (Year: 2019) (5 pages). |
Asana, Task dependencies, archives org, Aug. 25, 2017 https://web.archive.org/web/20170825002141/https://asana.com/guide/help/tasks/dependencies (Year: 2017) (5 pages). |
Asana, Manage your team capacity with Workload, youtube, excerpt, Aug. 1, 2019 https://www.youtube.com/watch?v=2ufXyZDzZnA&list=PLJFG93oi0wJAi UwyOhIGWHdtJzJrzyIBv (Year: 2019) (1 page). |
Biggs, “GateGuru Relaunches With New Ways to Streamline Your Travel Experience”, Techcrunch, (Apr. 26, 2013), 3 pgs. |
Castaneda Samuel, Introduction Manual—Asana, Sep. 25, 2017 https://static1.squarespace.com/static/586d532ae58c6232db243a65/t/5c210c10f950b7fc7a8e3274/1545669658049/Asana+Manual.pdf (Year: 2017) (20 pages). |
Command and control, wikipedia, archives org, Mar. 16, 2018 https://web.archive.org/web/20180316193655/https://en.wikipedia.org/wiki/Command_and_control (Year: 2018), 6 pages. |
How to Asana Asana time tracking, youtube, excerpt, May 24, 2017 https://www.youtube.com/watch?v=z91qlex-TLc (Year: 2017) (1 page). |
How to Asana, Asana project management, youtube, excerpt, Mar. 7, 2017 https://www.youtube.com/watch?v=qqANMTVVpE (Year: 2017) (28 pages). |
How to Asana, Creating your first Asana project, youtube, excerpt, Jan. 31, 2017 https://www.youtube.com/watch?v=L04WmcUdsLo (Year: 2017) (1 page). |
How to Asana, Getting Asana into your workflow, youtube, excerpt, Jul. 17, 2017 https://www.youtube.com/watch?v=7YLrNMdv30 (Year: 2017) (24 pages). |
How to Asana, Planning with Asana calendar, youtube excerpt, Feb. 14, 2017 https://www.youtube.com/watch?v=w816KYiVPyc (Year: 2017) (19 pages). |
How to Asana, Using Asana for task management, youtube, excerpt, Feb. 7, 2017 https://www.youtube.com/watch?v=vwvbgiejhQ (Year: 2017) (8 pages). |
How to Asana, Visualizing work with Asana kanban boards, youtube, excerpt, Feb. 21, 2017 https://www.youtube.com/watch?v=jmZaZGydfPY (Year: 2017) (41 pages). |
How to Asana, Workflow management, youtube, excerpt, May 30, 2017 https://www.youtube.com/watch?v=rk8nPWmXsRo (Year: 2017) (9 pages). |
How to use Advanced Search in Asana, Asana tutorial, May 25, 2016 https://www.youtube.com/watch?v=5VyJ3toPfQM (Year: 2016) (28 pages). |
Justin Rosenstein, Unveiling the Future of Asana, Mar. 28, 2018 https://www.youtube.com/watch?v=nRI?d_WM4Bc (Year: 2018) (2 pages). |
Prioritize My Tasks in Asana, Asana tutorial, youtube, excerpt, May 25, 2016 https://www.youtube.com/watch?v=UbCnMvw01nl (Year: 2016) (3 pages). |
Project views, Asana tutorial, youtube, excerpt May 25, 2016 https://www.youtube.com/watch?v=FYjA8ZH3ceQ (Year: 2016) (5 pages). |
Using Asana Premium, Asana tutorial, youtube, excerpt, Sep. 10, 2016 https://www.youtube.com/watch?v=vMgLtDDmyeo (Year: 2016) (4 pages). |
Where does Asana fit in, archives org, Jul. 8, 2017 https://web.archive.org/web/20170708150928/https://asana.com/guide/resources/infosheets/where-does-asana-fit (Year: 2017) (5 pages). |
www.cogmotive.com/blog/author/alan Alan Byrne: “Creating a company Shared Calendar in Office 365”; pp. 1-17; Sep. 10, 2013. |
Hartmann, “TimeProjectscheduling with resource capacities and requests varying with time: a case study,” 2013, Flexible services and manufacturing journal, vol. 25, No. 1, pp. 74-93 (Year: 2013). |
Paul Minors, How to automate your tasks, youtube excerpts, Oct. 18, 2019 https://www.youtube.com/watch?v=lwF9XyUQrzw (Year: 2019). |
Mauricio Aizawa, Zapier, How to Automate Asana Tasks creation using Evernote, youtube excerpts, Mar. 16, 2018 https://www.youtube.com/watch?v=BjDQ4Gny4WI (Year: 2018). |
Assef, F., Cassius, T. S., & Maria, T. S. (2018). Confrontation between techniques of time measurement. Journal of Manufacturing Technology Management, 29(5), 789-810. (Year: 2018). |
Dawei Li, “Deepcham: Collaborative Edge-Mediated Adaptive Deep Learning for Mobile Object Recognition”, 2016, IEEE/ACM, pp. 64-76. (Year: 2016). |
Macro, computer science, wikipedia, archives org Feb. 11, 2020 http://web.archive.org/web/20200211082902/https://en.wikipedia.org/wiki/Macro_(computer_science) (Year: 2020). |
Lauren Labrecque, “Fostering Consumer-Brand Relationships in Social Media Environments: The Role of Parasocial Interaction”, 2014, Journal of Interactive Markeing, 28 (2014), pp. 134-148 (Year: 2014). |
Tiburca, Andrew) Best Team Calendar Applications for 2018-Toggl https://toggl.com/blog/best-team-calendar-applications-for-2018 (Year: 2017). |
N. C. Romano, Fang Chen and J. F. Nunamaker, “Collaborative Project Management Software,” Proceedings of the 35th Annual Hawaii International Conference on System Sciences, 2002, pp. 233-242, doi: 10.1109/HICSS.2002.993878. |
Shivakumar; Complete Guide to Digital Project Management; 2018; Apress; (https://doi.org/10.1007/978-1-4842-3417-4; last access Mar. 6, 2023). |
Tsung-Yi Chen, Yuh-Min Chen, Hui-Chuan Chu, Developing a trust evaluation method between co-workers in virtual project team for enabling resource sharing and collaboration, Computers in Industry, vol. 59, Issue 6. (Year: 2008) 15 pages. |