HKSM

A structured approach to plan, organize, store, share, secure, and retire project information so the right people get the right information at the right time. It aligns repositories, access, metadata, and retention with stakeholder needs, delivery approach, and compliance.

Key Points

• Focuses on the lifecycle of project information: creation, classification, storage, sharing, retrieval, and disposition.
• Tailored to stakeholder needs, delivery approach (predictive, agile, hybrid), and regulatory or contractual obligations.
• Uses governance practices such as ownership, access control, versioning, and retention to protect integrity and traceability.
• Relies on repositories, taxonomies, and metadata so information is searchable, current, and easy to find.
• Integrates with communication, knowledge, configuration, and risk management processes.
• Monitored with simple indicators like information freshness, accuracy, and retrieval time.

Purpose of Analysis

• Determine what information stakeholders need to make timely decisions and perform their roles.
• Design structures and rules that reduce noise, duplication, and version confusion.
• Ensure compliance with privacy, security, audit, and retention requirements.
• Enable efficient collaboration and transparent status visibility across the team.

Method Steps

• Identify stakeholder information needs, frequency, formats, and access constraints.
• Map information types (e.g., plans, requirements, risks, decisions, baselines, change records) and their owners.
• Define governance: roles, permissions, versioning, approval workflows, and retention rules.
• Select repositories and tools (e.g., document library, wiki, backlog tool, dashboard) based on needs and policies.
• Design taxonomy and metadata to label content by project, area, status, version, and sensitivity.
• Establish naming conventions, folder structures, and templates for consistency.
• Implement the setup, migrate content, and train users on where to store and how to tag information.
• Monitor use and quality with simple metrics and audits; adjust structure and rules as needed.

Inputs Needed

• Stakeholder list and information needs assessment.
• Delivery approach and team collaboration norms.
• Organizational policies for security, privacy, records management, and configuration control.
• Compliance or contract requirements for reporting, audit, and retention.
• Existing repositories, tools, and templates (organizational process assets).
• Project artifacts such as the communications approach, risk register, change log, and baselines.

Outputs Produced

• Information management approach or plan section with roles, rules, and tools.
• Repository structure, access matrix, and permissions granted.
• Taxonomy, metadata scheme, and naming conventions.
• Versioning and approval workflows for controlled documents and records.
• Retention and archival schedule, including disposition criteria.
• Dashboards, report schedules, and content templates.
• Metrics and audit checklist for ongoing quality checks.

Interpretation Tips

• Check whether each stakeholder need is covered without overproducing or duplicating content.
• Verify that sensitive information has appropriate controls and auditability.
• Assess how quickly users can find the latest approved version of key artifacts.
• Tailor structures to the delivery cadence: lightweight and visible for agile, formal controls for baselined documents.
• Review metrics and feedback regularly to remove bottlenecks and reduce noise.

Example

A cross-functional project struggles with multiple document versions in email. The project manager consolidates content into a single repository, creates folders for plans, requirements, risks, and decisions, defines naming and versioning rules, and adds metadata for component, status, and sensitivity. Permissions restrict draft baselines to editors, while dashboards pull status from tagged items. Stakeholders can now find the current version in seconds, and audits show clear traceability.

Pitfalls

• Letting tools dictate structure instead of starting with stakeholder needs.
• Over-collecting information that no one uses, creating noise and waste.
• Lack of ownership or unclear permissions leading to uncontrolled edits.
• Poor metadata and naming conventions that make search unreliable.
• Ignoring retention, privacy, or security requirements.
• Not integrating with configuration and change control for baselined items.

PMP Example Question

Mid-project, stakeholders report they cannot find the latest requirements and status reports. What should the project manager do next to improve information visibility and control?

1. Send weekly emails with all updated documents attached.
2. Create a central repository with a taxonomy, metadata tags, and versioning rules, then train users.
3. Ask each team member to upload files to any shared folder they prefer.
4. Schedule a lessons learned workshop to discuss communication issues at project close.

Correct Answer: B — Create a central repository with a taxonomy, metadata tags, and versioning rules, then train users.

Explanation: Effective information management requires a structured repository, clear labeling, and version control aligned to stakeholder needs. Email blasts or ungoverned storage do not solve discoverability or integrity issues.