Time Is Money
The schedule takes shape
XR Platform Scope Statement v1.0
Project: Kurosawa Digital XR Experience Platform
Prepared by: Aoyama Ren (Pulse Works) & Sakurai Saki (Kurosawa Digital)
Version: 1.0 | Status: Baselined
Project Description
Design, develop, and deploy an immersive XR platform enabling Kurosawa Digital's enterprise clients to visualize products in augmented and virtual reality environments.
In Scope
- Core XR rendering engine (AR + VR modes)
- Product catalog integration API
- User analytics dashboard
- Admin portal for content management
- iOS and Android client applications
- Pilot deployment with two enterprise clients
Out of Scope
- Hardware procurement for end users
- Third-party marketplace integrations
- Multi-language localization (deferred to Phase 2)
- Custom 3D asset creation (client-supplied)
Constraints
Budget ceiling: ¥48M. Target launch: 9 months from project start. Tetsu's rendering engine team is shared across three active projects. All deliverables require Kurosawa Digital sign-off before deployment.
Assumptions
Client-side hardware meets minimum XR specifications. Kurosawa Digital provides test accounts within 2 weeks of each sprint completion. Dedicated QA resources available from Month 3.
Schedule
Definition A model showing planned dates for project activities and milestones.
Components Start/end dates, activity sequencing, resource assignments, calendar constraints.
Related Terms milestone, deliverable, scope baseline
Example After reviewing the scope statement above, Ren and Tetsu must translate each in-scope item into dated activities — the resulting timeline becomes the project schedule.
Activity
Definition A distinct unit of work performed during the project.
Components Description, duration estimate, assigned resources, predecessor activities.
Related Terms work package, milestone, dependency
Example "Build product catalog API" is a single activity within the XR platform WBS — it has a clear start, end, and output.
Dependency
Definition A logical relationship between two activities.
Components Finish-to-start (most common), start-to-start, finish-to-finish, start-to-finish.
Related Terms WBS, activity, lead time
Example The admin portal can't begin integration testing until the catalog API is complete — a finish-to-start dependency.
Lead Time
Definition The amount of time a successor activity can be advanced.
Components Expressed as a negative value (e.g., FS −2 days), applied to overlapping activities.
Related Terms dependency, lag time, schedule
Example Tetsu can start the VR rendering module 3 days before the AR module is finalized, since the shared engine code is already stable — that overlap is lead time.
Lag Time
Definition The amount of time a successor activity is delayed.
Components Expressed as a positive value (e.g., FS +5 days), represents mandatory waiting periods.
Related Terms dependency, lead time, schedule
Example After the pilot deployment, there's a 5-day lag before user feedback collection can start — the client needs time to configure their test environment.
While reviewing the scope statement's constraints section, Tetsu mentioned — almost as an aside — that the rendering engine team is shared across three active projects. Ren nodded and moved on to the next line item. He would remember this moment later.