Auto-sync: 2026-04-20 12:03
This commit is contained in:
21
wiki/concepts/Cross-Functional-Leadership.md
Normal file
21
wiki/concepts/Cross-Functional-Leadership.md
Normal file
@@ -0,0 +1,21 @@
|
||||
---
|
||||
title: "Cross-Functional Leadership"
|
||||
type: concept
|
||||
tags: [leadership, project-management]
|
||||
sources: [project-management-studio-operations, project-management-studio-producer]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Cross-Functional Leadership is the ability to coordinate teams, stakeholders, and disciplines across organizational boundaries to achieve a shared operational or strategic outcome.
|
||||
|
||||
## Core Principles
|
||||
- Align goals across functions
|
||||
- Communicate clearly with stakeholders
|
||||
- Resolve conflicts early
|
||||
- Keep execution connected to business outcomes
|
||||
|
||||
## Related Entities
|
||||
- [[Studio Operations]]
|
||||
- [[Studio Producer]]
|
||||
- [[The Agency]]
|
||||
29
wiki/concepts/Liquid-Glass-Design-System.md
Normal file
29
wiki/concepts/Liquid-Glass-Design-System.md
Normal file
@@ -0,0 +1,29 @@
|
||||
---
|
||||
title: "Liquid Glass Design System"
|
||||
type: concept
|
||||
tags: [design-system, apple, visionOS, ui-design]
|
||||
---
|
||||
|
||||
## 定义
|
||||
Apple visionOS 26 的核心设计系统,提供半透明材质,能够适应光照/暗环境和周围内容,创建沉浸式的空间界面效果。
|
||||
|
||||
## 核心特性
|
||||
- Translucent Materials:半透明材质效果
|
||||
- Environment Adaptation:自适应光照环境
|
||||
- Content Blending:与周围数字内容融合
|
||||
- Depth Perception:深度感知支持
|
||||
|
||||
## 应用场景
|
||||
- 窗口背景
|
||||
- 面板和装饰
|
||||
- 控件容器
|
||||
- 空间小组件
|
||||
|
||||
## 相关技术
|
||||
- [[SwiftUI]] glassBackgroundEffect
|
||||
- [[visionOS]] Native APIs
|
||||
- [[RealityKit]] 渲染集成
|
||||
|
||||
## 相关实体
|
||||
- [[Apple]]:设计系统提供者
|
||||
- [[visionOS Spatial Engineer]]:设计系统实现者
|
||||
20
wiki/concepts/Operational-Excellence.md
Normal file
20
wiki/concepts/Operational-Excellence.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Operational Excellence"
|
||||
type: concept
|
||||
tags: [operations, continuous-improvement]
|
||||
sources: [project-management-studio-operations]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Operational Excellence is the practice of continuously improving processes, controls, and support systems so that operations remain reliable, efficient, and scalable.
|
||||
|
||||
## Core Principles
|
||||
- Make workflows predictable and documented
|
||||
- Measure performance and spot regressions early
|
||||
- Improve reliability through standardization
|
||||
- Use automation and knowledge management to reduce friction
|
||||
|
||||
## Related Entities
|
||||
- [[Studio Operations]]
|
||||
- [[The Agency]]
|
||||
20
wiki/concepts/Process-Optimization.md
Normal file
20
wiki/concepts/Process-Optimization.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Process Optimization"
|
||||
type: concept
|
||||
tags: [operations, efficiency, project-management]
|
||||
sources: [project-management-studio-operations]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Process Optimization is the practice of identifying bottlenecks and redesigning workflows to improve efficiency, quality, and reliability.
|
||||
|
||||
## Core Principles
|
||||
- Standardize repeatable work
|
||||
- Remove bottlenecks
|
||||
- Measure outcomes
|
||||
- Automate where possible
|
||||
|
||||
## Related Entities
|
||||
- [[Studio Operations]]
|
||||
- [[Studio Producer]]
|
||||
21
wiki/concepts/Resource-Allocation.md
Normal file
21
wiki/concepts/Resource-Allocation.md
Normal file
@@ -0,0 +1,21 @@
|
||||
---
|
||||
title: "Resource Allocation"
|
||||
type: concept
|
||||
tags: [operations, project-management]
|
||||
sources: [project-management-studio-operations, project-management-studio-producer]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Resource Allocation is the practice of distributing people, tools, time, and budget across priorities so work can be completed efficiently and with appropriate service quality.
|
||||
|
||||
## Core Principles
|
||||
- Match resources to the highest-value work
|
||||
- Balance short-term delivery with long-term capacity
|
||||
- Track utilization and constraints
|
||||
- Reallocate proactively when bottlenecks emerge
|
||||
|
||||
## Related Entities
|
||||
- [[Studio Operations]]
|
||||
- [[Studio Producer]]
|
||||
- [[Project Shepherd]]
|
||||
24
wiki/concepts/Spatial-Widgets.md
Normal file
24
wiki/concepts/Spatial-Widgets.md
Normal file
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: "Spatial Widgets"
|
||||
type: concept
|
||||
tags: [visionOS, widgets, spatial-computing, ui]
|
||||
---
|
||||
|
||||
## 定义
|
||||
visionOS 26 的小组件系统,能够集成到 3D 空间中,可吸附到墙壁和桌子并持久放置。
|
||||
|
||||
## 核心特性
|
||||
- 3D 空间集成
|
||||
- 表面吸附(墙壁、桌子)
|
||||
- 持久放置
|
||||
- 实时更新
|
||||
|
||||
## 应用场景
|
||||
- 信息展示
|
||||
- 快捷操作
|
||||
- 实时数据
|
||||
- 状态监控
|
||||
|
||||
## 相关实体
|
||||
- [[visionOS]]
|
||||
- [[visionOS Spatial Engineer]]
|
||||
28
wiki/concepts/Strategic-Portfolio-Management.md
Normal file
28
wiki/concepts/Strategic-Portfolio-Management.md
Normal file
@@ -0,0 +1,28 @@
|
||||
---
|
||||
title: "Strategic Portfolio Management"
|
||||
type: concept
|
||||
tags: [project-management, strategy]
|
||||
---
|
||||
|
||||
## Definition
|
||||
Strategic Portfolio Management is the practice of orchestrating multiple high-value projects with complex interdependencies and resource requirements to achieve organizational strategic objectives.
|
||||
|
||||
## Core Principles
|
||||
- Align creative excellence with business objectives and market opportunities
|
||||
- Manage senior stakeholder relationships and executive-level communications
|
||||
- Drive innovation strategy and competitive positioning through creative leadership
|
||||
- Ensure 25% portfolio ROI with 95% on-time delivery
|
||||
|
||||
## Key Activities
|
||||
- Portfolio health monitoring and strategic course corrections
|
||||
- Investment allocation across portfolio tiers (Tier 1: Strategic Priority, Tier 2: Growth Initiatives, Innovation Pipeline)
|
||||
- Risk management and contingency planning
|
||||
- Performance tracking against strategic objectives
|
||||
|
||||
## Related Concepts
|
||||
- [[Resource Allocation]]
|
||||
- [[Cross-Functional Leadership]]
|
||||
- [[Multi-Project Orchestration]]
|
||||
|
||||
## Related Entities
|
||||
- [[Studio Producer]]
|
||||
9
wiki/concepts/TaskListFormat.md
Normal file
9
wiki/concepts/TaskListFormat.md
Normal file
@@ -0,0 +1,9 @@
|
||||
---
|
||||
title: "TaskListFormat"
|
||||
type: concept
|
||||
tags: [project-management, tasks]
|
||||
sources: [project-manager-senior]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
Describes the recommended structure for breaking specifications into development tasks: specification summary, technical stack, per-task description, acceptance criteria, files to create/edit, and references. Tasks should be small (30–60 minute devable) and include clear acceptance tests.
|
||||
31
wiki/concepts/项目章程.md
Normal file
31
wiki/concepts/项目章程.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
title: "项目章程"
|
||||
type: concept
|
||||
tags: [project-management, governance]
|
||||
date: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
项目章程是定义项目目标、范围、成功标准和治理结构的标准化文档模板,是项目启动阶段的核心交付物。
|
||||
|
||||
## Components
|
||||
- Problem Statement:清晰阐述要解决的问题或抓住的机会
|
||||
- Project Objectives:具体、可衡量的成果和成功标准
|
||||
- Scope:详细的可交付物、边界和排除项
|
||||
- Success Criteria:可量化的项目成功衡量指标
|
||||
- Stakeholder Analysis:利益相关方分析和沟通计划
|
||||
- Resource Requirements:团队组成、预算、时间线
|
||||
- Risk Assessment:高层风险和缓解策略
|
||||
|
||||
## Usage
|
||||
项目章程在项目启动阶段创建,经 Executive Sponsor 批准后成为项目执行的基准文档。
|
||||
|
||||
## Relationships
|
||||
- 定义项目边界和目标
|
||||
- 授权项目团队使用资源
|
||||
- 建立项目治理结构
|
||||
- 为项目成功提供衡量标准
|
||||
|
||||
## Aliases
|
||||
- Project Charter
|
||||
- Project Definition Document
|
||||
Reference in New Issue
Block a user