Activity Attributes

A set of descriptive details captured for every scheduled activity in the activity list. These details may include items like activity identifiers or codes; predecessors and successors; the type of dependency between activities; any leads or lags; resource needs; target or imposed dates; constraints; and key assumptions.

Key Points

  • They are metadata about an activity that help define, organize, and control the schedule.
  • Typical items include activity codes, predecessors, successors, relationship types, leads/lags, resource requirements, imposed dates, constraints, and assumptions.
  • They support sequencing, estimating durations and costs, resource planning, and schedule analysis (e.g., critical path and network logic).
  • Attributes can be refined over time as more information becomes available, enabling better filtering, grouping, and reporting.

Example

For activity A-104 “Install Server OS”: activity code A-104; predecessor A-103 “Rack Servers” with a finish-to-start relationship and a 2‑day lag; successor A-105 “Configure Network”; resources: 1 systems engineer and 1 technician; imposed date: start no earlier than May 10; constraint: hardware must pass burn-in; assumption: network VLANs will be available by May 9.

PMP Example Question

Which project document records details such as an activity’s predecessors and successors, dependency type, leads and lags, resource needs, imposed dates, constraints, and assumptions?

  1. Activity List
  2. Activity Attributes
  3. WBS Dictionary
  4. Milestone List

Correct Answer: B — Activity Attributes

Explanation: Activity attributes capture descriptive data for each activity, including codes, logical relationships, leads/lags, resource requirements, imposed dates, constraints, and assumptions.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Lead with clarity, influence, and outcomes.

HK School of Management and Technology offers a practical Leadership for Project Managers course for real projects, tight deadlines, and cross-functional teams. Learn to set direction, align stakeholders, and drive commitment without relying on title. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More