Reference: Project Components
Project Components
After you create a project hierarchy, you can assemble a framework for your projects by
defining its components. These components simplify the process of creating a new
project.
Component | Description |
|---|---|
Project Hierarchy | All projects must belong to a primary hierarchy. You can also specify optional
hierarchies to further group your projects. If you
specify an optional hierarchy, you'll disable all of these
hierarchy-level configuration options:
|
Project Plan | Contains the project phases and tasks. Describes the sequences of steps, activities,
and milestones needed for a project. |
Resource Plan | Describes who accomplishes the work detailed in the project and in the project plan.
You can:
|
Phases and tasks | Phases are the high-level sequence of steps to complete a project. Example: A software
implementation project might include these phases: analyze, scope, design,
construct, test, document, deliver, and support. Tasks are the distinct
activities within a phase. Example: The document phase might have a task
to write end-user instructions. All project plans, project plan
templates, and project templates have phases and tasks. When you
assign phases and tasks to a project, Workday creates a specific
instance of them that you can report on for that project. |
Templates | You can create templates for projects and project plans that automatically fill in
configuration settings and other information. Templates help reduce the
manual effort required in configuring these settings every time you create a
new project or project plan. They're also useful in standardizing projects
across your organization. |
Project labor costing | You can define project labor costs based on either:
|
Dates | Workday doesn't require or enforce relationships between start and end dates across
these project areas:
Examples:
|