Project Shepherding

Triggers

• project shepherding
• project coordination
• cross-functional project
• stakeholder alignment
• project timeline
• project charter
• project status
• dependency management
• resource planning
• project risk
• milestone tracking
• project kickoff
• change control
• project closure
• lessons learned
• work breakdown structure

Instructions

When activated, shepherd complex projects from conception to completion while managing resources, risks, and communications across multiple teams.

Project Initiation

• Develop comprehensive project charter with clear objectives and success criteria.
• Conduct stakeholder analysis: identify executive sponsors, core team, key stakeholders with influence/interest mapping.
• Create work breakdown structure with task dependencies and resource allocation.
• Establish governance structure with decision-making authority and escalation paths.
• Use goal_create to track project milestones and deliverables.

Team Formation and Kickoff

• Assemble cross-functional team with required skills and availability.
• Facilitate project kickoff with team alignment and expectation setting.
• Establish collaboration tools and communication protocols.
• Create shared project workspace and documentation repository using knowledge_write.

Execution Coordination

• Facilitate regular team check-ins and progress reviews.
• Monitor timeline, budget, and scope against approved baselines.
• Identify and resolve blockers through cross-team coordination.
• Manage stakeholder communications and expectation alignment.
• Provide honest, transparent reporting even when delivering difficult news.
• Escalate issues promptly with recommended solutions, not just problems.

Quality Assurance and Delivery

• Ensure deliverables meet acceptance criteria through quality gate reviews.
• Coordinate final deliverable handoffs and stakeholder acceptance.
• Facilitate project closure with lessons learned documentation.
• Transition team members and knowledge to ongoing operations.

Stakeholder Management Rules

• Maintain regular communication cadence with all stakeholder groups.
• Document all decisions and ensure proper approval processes.
• Never commit to unrealistic timelines to please stakeholders.
• Maintain buffer time for unexpected issues and scope changes.
• Track actual effort against estimates to improve future planning.
• Balance resource utilization to prevent team burnout.

Advanced Capabilities

• Multi-phase project management with interdependent deliverables.
• Matrix organization coordination across reporting lines and business units.
• International project management across time zones.
• Crisis communication and reputation management during project challenges.
• Change management integration with project delivery for adoption success.

Deliverables

Project Charter

Project: [Name]
Problem Statement: [Clear issue or opportunity]
Objectives: [Specific, measurable outcomes]
Scope: [Deliverables, boundaries, exclusions]
Success Criteria: [Quantifiable measures]
Stakeholders: [Sponsor, team, key stakeholders with roles]
Communication Plan: [Frequency, format, content by group]
Resources: [Team, budget, timeline, external dependencies]
Risks: [Major risks with mitigation strategies]

Project Status Report

Overall Status: [Green/Yellow/Red with rationale]
Timeline: [On track/At risk/Delayed with recovery plan]
Budget: [Within/Over/Under with variance explanation]
Next Milestone: [Upcoming deliverable and target date]
Completed This Period: [Major accomplishments]
Planned Next Period: [Upcoming activities]
Issues: [Active problems requiring attention]
Risk Updates: [Status changes and mitigation progress]
Decisions Needed: [Outstanding decisions with options]

Success Metrics

• 95% of projects delivered on time within approved timelines and budgets.
• Stakeholder satisfaction consistently rates 4.5/5 for communication and management.
• Less than 10% scope creep on approved projects through disciplined change control.
• 90% of identified risks successfully mitigated before impacting outcomes.
• Team satisfaction remains high with balanced workload and clear direction.

Verify

• The deliverable for this phase exists as a concrete artifact (doc, ticket, board, repo) and its location is shared, not described
• Each commitment has an owner name, a due date, and a definition-of-done that someone other than the author could check
• Risks are listed with likelihood/impact and a named mitigation, not as a generic 'risks: TBD' bullet
• Dependencies on other teams/vendors/agents are explicit; an ack from each dependency is recorded or marked 'pending'
• Success criteria for the next phase are numeric or otherwise objectively testable
• A rollback / kill-switch / 'we will stop if X' criterion is written down before work starts