HKSM

Activity attributes are detailed descriptors recorded for each activity, such as predecessors, leads/lags, constraints, resource needs, assumptions, and calendars. They support sequencing, estimating, resource planning, and schedule control throughout the project.

Key Points

• Activity attributes are structured fields that describe each activity so the team can sort, filter, analyze, and control the schedule.
• They are developed alongside the activity list and refined iteratively as more information becomes available.
• They enable network sequencing, duration and resource estimating, risk analysis, and schedule model development.
• Typical fields include dependency details, leads/lags, constraints and deadlines, effort or duration type, required skills, calendars, and owners.
• The level of detail should match project complexity and be guided by consistent data definitions and codes.
• They are maintained as a living register and synchronized with scheduling and resource tools throughout delivery.

Purpose of Analysis

Analyzing activity attributes ensures the schedule logic is complete, realistic, and traceable. It clarifies how activities relate, what resources are needed, and what constraints or risks affect timing and sequencing.

Method Steps

• Define the attribute categories and data standards (names, codes, allowed values, data owners).
• Start with the approved activity list and assign unique IDs for traceability.
• Elicit and capture dependencies, leads/lags, resource needs, calendars, constraints, assumptions, and risk notes with SMEs.
• Record attributes in a structured template or scheduling tool and keep fields concise and unambiguous.
• Validate logic: check dependency types, direction, and lags; detect circular or open-ended links.
• Use attributes to support estimating (effort-driven vs fixed-duration, required skills, availability calendars).
• Review with stakeholders, resolve conflicts, and baseline when appropriate; apply version control.
• Continuously update attributes as changes occur and align them with the schedule model and resource plans.

Inputs Needed

• Activity list and unique activity IDs.
• WBS and WBS dictionary for scope context.
• Assumption log and constraints list.
• Resource breakdown structure, team assignments, and calendars.
• Risk register and risk responses affecting logic or buffers.
• Organizational process assets (templates, coding standards) and enterprise environmental factors (policies, time zones, tools).
• Lessons learned from similar projects.

Outputs Produced

• Completed activity attributes register with standardized, validated fields.
• Clarified dependencies, relationship types, and leads/lags ready for network diagramming.
• Documented resource requirements and calendar assignments for each activity.
• Basis-of-estimate notes linked to assumptions and constraints.
• Updates to the schedule model and related logs (assumptions, risks) and potential change requests.

Interpretation Tips

• Differentiate mandatory, discretionary, external, and internal dependencies to understand flexibility.
• Use attribute codes to filter the schedule (e.g., by skill, location, calendar, risk level) for targeted analysis.
• Watch for calendar mismatches and time zone differences that can distort float and dates.
• Tag effort-driven vs fixed-duration activities to choose the right estimating and resource-loading behavior.
• Highlight constraints and deadlines to assess their impact on criticality and schedule risk.
• Track attribute completeness and quality; missing fields often signal hidden assumptions.

Example

Sample attributes for an activity "Conduct training sessions":

• ID: A-210; Owner: Training lead.
• Predecessor: A-200 "Training materials approved"; Relationship: Finish-to-Start with 3-day lag.
• Type: Fixed-duration; Duration: 2 days; Effort-driven: No.
• Resources: 1 trainer (skill: facilitation), 1 room, 20 participants.
• Calendar: Business days; Time zone: PST; Location: On-site.
• Constraint: Must finish before release date 30 Jun; Assumption: Venue available.
• Risk: Medium (potential attendee availability conflicts).

Pitfalls

• Overcomplicating with excessive fields that no one maintains.
• Inconsistent naming or codes that prevent reliable filtering and reporting.
• Omitting dependencies or lags, creating broken or unrealistic schedule logic.
• Failing to update attributes after scope, resource, or calendar changes.
• Burying critical assumptions or constraints in notes instead of structured fields.
• Copy-paste errors when syncing between spreadsheets and scheduling tools.

PMP Example Question

Which artifact should the project manager update to capture an activity's predecessor, relationship type, calendar, resource needs, and constraints?

1. Activity list
2. Activity attributes
3. Milestone list
4. WBS dictionary

Correct Answer: B — Activity attributes

Explanation: Activity attributes store detailed properties for each activity, including dependencies, calendars, and resource needs. The activity list and milestone list contain names and key dates, while the WBS dictionary focuses on deliverable scope.