Use case roles（用例角色）¶
Use case roles aim to develop specific analyses or outcomes with the data in Foundry. Organizational domains, program teams, or a single project manager can manage a use case team. Management by a single project manager is especially common in the early phases of the Foundry journey.
Domain lead¶
Domain leads aren't necessarily in a use case team or role, but they are organizational leads who own the success of a particular organizational domain's return on investment (ROI). This includes organizational domains at scale, which often contain multiple work streams. Domain leads work closely with members of the program team to provide strategic input to use case prioritization conversations, which should occur on a regular basis.
Workstream lead¶
Workstream leads are responsible for managing the production of economies of scale (through information sharing, such as developed analyses and models, and ontology tables), and ensuring the appropriate competencies are deployed against adjacent use cases (e.g. deploying a set of applications to the same user base). This role becomes helpful once a given organization's organizational domain contains a considerable number of use cases.
Use case lead¶
Use case leads are project managers who work alongside engineers contributing to a project. Use case leads ensure the alignment of both technical and organizational goals, adherence to best practice standards for development on the platform, and coordination between other project teams.
They are responsible for
- use case ROI, execution, and end-user adoption;
- managing the project-specific permissions and access controls; and
- coordinating the team to ensure project issues, health checks, schedules, and application support is available for end users.
Product owner¶
Product owners are accountable for the development roadmap and implementation of use case features, which should be identified, confirmed, and documented during the planning stage. The product owner is a key stakeholder to involve in the early stages of product development to ensure they're aware of organizational requirements and how the product can best benefit its end-users. Product owners are the main points of contact for individuals who wish to understand the progress and outcomes of product development.
Organizational/subject matter expert¶
Organizational SMEs provide expertise and guidance from their organizational domain to ensure project efforts are aligned with organizational needs. Often this person is a power user of legacy tools who deeply understand the current workflows for a given problem domain, the shortcomings associated with those current operations, and thoughts on how to optimize the user experience and workflow to maximize ROI.
Use case developer¶
Use case developers are engineers and analysts who own the development of a use case. They use data sourced from the ontology layer. Use case developers often have specialties depending on the project scope, including:
- Data analysts:
- Scope, design, and implement both ad hoc and templated analyses, reports, visualizations, and dashboards to answer critical questions.
- Perform one-off quality and consistency checks during pipeline building.
- Data engineers:
- Author transformations, optimizations, and manipulations of datasets to meet the needs of the use case and its outcomes.
- Monitor and curate the most important datasets in one or multiple projects, adhering to the central Program Team’s guidelines.
- Contribute back to Ontology according to defined contribution process.
- Data scientist/machine learning experts:
- Perform modeling, machine learning, classification, and regressions to enrich and visualize data in service of decision-making workflows.
- Application developers:
- Develop decision-driven interfaces in Workshop, Slate, Quiver, and Object Explorer.
- Define object types and their associated actions in the Ontology Manager.
- Build external applications with third-party tools using the Foundry Gateway API.
The number of required use case developers is heavily dependent on the individual use case's goals and requirements and the skillsets of available use case developers.
End user¶
End users and self-service users work in developed workflows, applications, or data artifacts to fulfill their regular organizational responsibilities, including ad hoc analyses, reporting, operational improvements, and daily decision-making.
中文翻译¶
用例角色¶
用例角色旨在利用 Foundry 中的数据开发特定的分析或成果。组织领域、项目团队或单个项目经理可以管理一个用例团队。在 Foundry 使用初期，由单个项目经理管理的情况尤为常见。
领域负责人¶
领域负责人不一定属于用例团队或角色，他们是负责特定组织领域投资回报率（ROI）的组织领导者。这包括规模较大的组织领域，这些领域通常包含多个工作流。领域负责人与项目团队成员密切合作，为用例优先级讨论提供战略意见，此类讨论应定期进行。
工作流负责人¶
工作流负责人负责管理规模经济的产出（通过信息共享，例如已开发的分析和模型以及本体表），并确保将适当的能力部署到相邻的用例中（例如，向同一用户群体部署一组应用程序）。当某个组织的组织领域包含大量用例时，这一角色将变得尤为重要。
用例负责人¶
用例负责人是与参与项目的工程师并肩工作的项目经理。用例负责人确保技术和组织目标的一致性，遵守平台开发的最佳实践标准，并协调其他项目团队之间的合作。
他们负责：
- 用例的投资回报率、执行和最终用户采用；
- 管理项目特定的权限和访问控制；
- 协调团队，确保项目问题、健康检查、日程安排和应用程序支持对最终用户可用。
产品负责人¶
产品负责人负责用例功能的开发路线图和实施，这些功能应在规划阶段进行识别、确认和记录。产品负责人是产品开发早期阶段需要参与的关键利益相关者，以确保他们了解组织需求以及产品如何最好地惠及其最终用户。产品负责人是希望了解产品开发进展和成果的人员的主要联系人。
组织/领域专家¶
组织 SME 从其组织领域提供专业知识和指导，以确保项目工作与组织需求保持一致。此人通常是传统工具的高级用户，深入了解当前针对特定问题领域的工作流程、当前操作相关的不足之处，以及如何优化用户体验和工作流程以最大化投资回报率的想法。
用例开发人员¶
用例开发人员是负责用例开发的工程师和分析师。他们使用来自本体层的数据。用例开发人员通常根据项目范围具有不同的专长，包括：
- 数据分析师：
- 范围界定、设计和实施临时及模板化的分析、报告、可视化和仪表板，以回答关键问题。
- 在管道构建过程中执行一次性质量和一致性检查。
- 数据工程师：
- 编写数据集的转换、优化和操作，以满足用例及其成果的需求。
- 监控和管理一个或多个项目中最重要的数据集，遵循中央项目团队的指导方针。
- 根据定义的贡献流程向本体贡献内容。
- 数据科学家/机器学习专家：
- 执行建模、机器学习、分类和回归分析，以丰富和可视化数据，服务于决策工作流程。
- 应用程序开发人员：
- 在 Workshop、Slate、Quiver 和 Object Explorer 中开发以决策为导向的界面。
- 在 Ontology Manager 中定义对象类型及其关联的操作。
- 使用 Foundry Gateway API 通过第三方工具构建外部应用程序。
所需用例开发人员的数量在很大程度上取决于单个用例的目标和要求以及可用用例开发人员的技能组合。
最终用户¶
最终用户和自助服务用户在已开发的工作流程、应用程序或数据制品中工作，以履行其常规的组织职责，包括临时分析、报告、运营改进和日常决策。