Ammar - Human resources tutor - Montreal
1st lesson free
Ammar - Human resources tutor - Montreal

One of our best tutors. Quality profile, experience in their field, verified qualifications and a great response time. Ammar will be happy to arrange your first Human Resources lesson.

Ammar

One of our best tutors. Quality profile, experience in their field, verified qualifications and a great response time. Ammar will be happy to arrange your first Human Resources lesson.

  • Rate $30
  • Response 2h
  • Students

    Number of students Ammar has accompanied since arriving at Superprof

    50+

    Number of students Ammar has accompanied since arriving at Superprof

Ammar - Human resources tutor - Montreal
  • 5 (17 reviews)

$30/h

1st lesson free

Contact

1st lesson free

1st lesson free

  • Human Resources
  • Corporate strategy
  • Management and Organization
  • Business Analysis
  • Project management

Master Project Management, Primavera P6, Jira, Microsoft Project, and Agile with a PhD Engineer and Professor | 25+ Years’ Expertise | Beginner to University, Research and Professional Levels

  • Human Resources
  • Corporate strategy
  • Management and Organization
  • Business Analysis
  • Project management

Lesson location

    • At Ammar's house: Montreal

    • online
    • at home or in a public place : will travel up to 50 km from Montreal

Ambassador

One of our best tutors. Quality profile, experience in their field, verified qualifications and a great response time. Ammar will be happy to arrange your first Human Resources lesson.

About Ammar

A- PROFESSIONAL PROFILE
I am a PhD Engineer, Professor, Researcher, Project Management and Project Controls Educator, Trainer, and Consultant with more than 25 years of experience in Engineering projects, planning and scheduling, management systems, professional training, organizational decision-making, and applied project delivery.
I help students, engineers, planners, schedulers, analysts, project coordinators, managers, researchers, consultants, executives, and career-transition professionals connect strategy, value, requirements, scope, schedules, resources, costs, risks, contracts, stakeholders, execution, controls, change, transition, and benefits within one coherent project-management system.
My approach combines management theory, Engineering execution, project controls, business analysis, leadership, software tools, analytical reasoning, and real project applications rather than focusing only on terminology, templates, or software commands.

B- EDUCATIONAL AND PROJECT-MANAGEMENT BACKGROUND
My multidisciplinary academic background includes Engineering, a Master’s degree in Management Information Systems, and a PhD in Knowledge Management and Artificial Intelligence.
My Engineering education developed rigorous capabilities in technical scope definition, systems thinking, work sequencing, resource and productivity analysis, cost awareness, quality, risk, design and construction interfaces, commissioning, multidisciplinary coordination, and systematic problem-solving.
My Master’s degree in Management Information Systems strengthened my expertise in requirements, Business Analysis, project information systems, digital workflows, organizational processes, reporting, governance, systems implementation, databases, and technology-supported decision-making.
My PhD in Knowledge Management and Artificial Intelligence further developed my work in organizational learning, knowledge transfer, analytical reasoning, forecasting, intelligent tools, decision support, lessons learned, and responsible AI-assisted project workflows.
This combination enables me to integrate technical delivery, organizational strategy, project information, human leadership, analytical control, and technology within one complete project-management framework.

C- DELIVERY APPROACHES
My experience spans predictive, Agile, iterative, incremental, and hybrid delivery approaches.
I help learners determine which approach is suitable according to the project’s objectives, uncertainty, product, industry, contractual environment, governance requirements, team structure, stakeholder needs, and organizational capability.
Predictive methods may be appropriate when scope, sequence, deliverables, and contractual obligations can be established in advance.
Agile or iterative approaches may be more suitable when requirements evolve, frequent feedback is needed, uncertainty is high, and value can be delivered progressively.
Hybrid approaches may combine formal governance, budgets, milestones, dependencies, and reporting with iterative product development and adaptive team practices.
I emphasize that no delivery method should be applied mechanically or treated as universally superior.

D- COMPLETE PROJECT LIFECYCLE
I support the complete project lifecycle, including:
• Identifying the business need, opportunity, problem, or strategic objective
• Evaluating feasibility, alternatives, constraints, risks, and expected value
• Developing the business case and project justification
• Preparing the charter and establishing authority
• Defining governance, decision rights, roles, responsibilities, and escalation paths
• Identifying stakeholders and communication requirements
• Eliciting and analysing requirements
• Defining scope, deliverables, assumptions, constraints, and acceptance criteria
• Developing the Work Breakdown Structure
• Planning activities, schedules, resources, costs, quality, risks, procurement, and communications
• Executing and coordinating the work
• Monitoring progress, cost, schedule, risk, quality, issues, and changes
• Forecasting outcomes and recommending corrective actions
• Managing transition, handover, adoption, and operational readiness
• Closing contracts, accounts, documentation, and project records
• Capturing lessons learned and evaluating benefits
I teach learners to understand the relationships among these stages rather than treating each knowledge area as an isolated document.

E- PROJECT PLANNING AND WORK BREAKDOWN STRUCTURES
I help learners translate a project objective into deliverables, work packages, activities, responsibilities, milestones, resources, costs, and measurable completion criteria.
Work Breakdown Structure development may include:
• Product-, phase-, deliverable-, system-, location-, discipline-, or responsibility-based structures
• Decomposition and work-package definition
• WBS dictionaries
• Control accounts
• Responsibility Assignment Matrices
• Organizational Breakdown Structures
• Cost Breakdown Structures
• Milestone structures
• Coding and reporting hierarchies
I emphasize that a schedule cannot compensate for an unclear scope or poorly structured WBS.
The planning process must establish what will be delivered, how completion will be measured, who is responsible, and how work will be controlled.

F- SCHEDULING AND CRITICAL PATH METHOD
For scheduling, I support activity definition, sequencing, dependencies, leads, lags, constraints, calendars, durations, milestones, resources, logic networks, and Critical Path Method analysis.
I help learners understand:
• Finish-to-start, start-to-start, finish-to-finish, and start-to-finish relationships
• Total and free float
• Critical and near-critical paths
• Driving relationships
• Open ends and broken logic
• Hard and soft constraints
• Calendar effects
• Resource dependencies
• Schedule compression
• Fast-tracking and crashing
• Milestone analysis
• Baseline comparison
• Progress updating
• Forecast completion
• Schedule sensitivity and risk
I emphasize that the critical path is produced by the network logic, durations, calendars, constraints, and status—not by manually labelling activities as critical.

G- PRIMAVERA P6
With Primavera P6, I support professional planning, scheduling, resource, cost, progress, and Project Controls workflows.
Topics may include:
• Enterprise Project Structure
• Organizational Breakdown Structure
• Calendars
• Work Breakdown Structures
• Activities and milestones
• Relationships, leads, and lags
• Constraints
• Activity codes
• Project and global codes
• Roles and resources
• Resource assignments
• Expenses and costs
• Baselines
• Layouts, filters, grouping, sorting, and columns
• Progress updating
• Data dates
• Remaining duration and physical progress
• Critical and near-critical paths
• Float analysis
• Resource loading and levelling
• Cost loading
• Earned Value foundations
• S-curves
• Reports
• Import and export
• Schedule-quality review
• Forecasting and recovery scenarios
I help learners understand how Primavera P6 calculations respond to calendars, logic, constraints, progress settings, resource assignments, baselines, and data-date decisions.
The objective is to develop schedules that are logically sound, traceable, updateable, and useful for decision-making.

H- MICROSOFT PROJECT
With Microsoft Project, I support the development and control of small, medium, and complex schedules.
Work may include:
• Project calendars
• Tasks and summary tasks
• Milestones
• Dependencies
• Constraints
• Deadlines
• Recurring tasks
• Work, duration, and units
• Resources and assignments
• Resource calendars
• Costs and rates
• Baselines
• Critical paths
• Tracking methods
• Actual and remaining work
• Earned Value foundations
• Resource levelling
• Custom fields
• Tables, views, filters, groups, and reports
• Master projects and subprojects where appropriate
• Imports, exports, and integration with Excel or reporting environments
I explain how Microsoft Project’s scheduling engine calculates dates and why apparently simple changes to task mode, calendars, assignments, constraints, or progress data may substantially alter the plan.
I teach learners to use the software as a planning and forecasting system rather than merely as a Gantt-chart generator.

I- PROJECT CONTROLS
My Project Controls approach integrates scope, schedule, cost, resources, progress, risk, change, forecasting, performance measurement, and management reporting.
I support:
• Baseline development and control
• Progress measurement systems
• Rules of credit
• Quantity- and milestone-based progress
• Planned-versus-actual analysis
• Variance analysis
• Trend analysis
• Forecasting
• Estimate to Complete
• Estimate at Completion
• Schedule Performance Index
• Cost Performance Index
• Earned Value Management
• S-curves
• Cash-flow foundations
• Resource histograms
• Productivity analysis
• Exception reporting
• Change logs
• Risk-adjusted forecasts
• Corrective-action tracking
I emphasize that control is not limited to reporting historical variances. Effective Project Controls must identify causes, predict consequences, evaluate alternatives, and support timely decisions.

J- EARNED VALUE MANAGEMENT
For Earned Value Management, I support:
• Planned Value
• Earned Value
• Actual Cost
• Schedule Variance
• Cost Variance
• Schedule Performance Index
• Cost Performance Index
• Budget at Completion
• Estimate at Completion
• Estimate to Complete
• Variance at Completion
• To-Complete Performance Index
• Forecasting formulas
• Control accounts
• Work-package progress
• Performance Measurement Baselines
I explain the assumptions and limitations of each indicator.
For example, a favourable Schedule Performance Index does not necessarily prove that the project will complete on time, particularly when earned-value measures are not connected carefully with critical-path and milestone analysis.

K- RISK AND UNCERTAINTY
I support qualitative and quantitative project-risk management, including:
• Risk identification
• Cause–risk–effect statements
• Risk categories and breakdown structures
• Probability and impact assessment
• Risk matrices
• Risk owners
• Avoidance, mitigation, transfer, acceptance, and exploitation
• Contingency and management reserves
• Opportunity management
• Risk triggers
• Response plans
• Residual and secondary risks
• Risk reviews
• Schedule-risk foundations
• Cost-risk foundations
• Expected Monetary Value
• Decision trees
• Sensitivity analysis
• Scenario analysis
• Monte Carlo simulation foundations where appropriate
I distinguish risks from issues, assumptions, constraints, uncertainties, dependencies, and normal project variation.
Risk management is connected with schedules, costs, procurement, stakeholders, governance, and decision thresholds.

L- JIRA AND AGILE PROJECT DELIVERY
With Jira and related Agile tools, I support:
• Product and project backlogs
• Epics
• Features
• User stories
• Tasks and subtasks
• Acceptance criteria
• Story points and estimation
• Prioritization
• Sprint planning
• Scrum and Kanban boards
• Workflows and statuses
• Releases and versions
• Dependencies
• Impediments
• Components
• Labels
• Filters
• JQL foundations
• Dashboards
• Burndown and burnup charts
• Velocity
• Cumulative-flow diagrams
• Cycle time and lead time
• Defect tracking
• Traceability
• Team and stakeholder reporting
I explain how Jira configurations should reflect the actual delivery process rather than force teams into unnecessary administrative complexity.

M- SCRUM, KANBAN, LEAN, AND HYBRID DELIVERY
For Scrum, I support Product Owner, Scrum Master, Developer, and stakeholder responsibilities; product and sprint backlogs; sprint planning; Daily Scrum; review; retrospective; increments; Definition of Done; acceptance criteria; and empirical inspection and adaptation.
For Kanban, I support visualization of work, workflow policies, work-in-progress limits, pull systems, cycle time, lead time, throughput, bottleneck analysis, flow efficiency, service classes, and continuous improvement.
Lean concepts may include value, waste reduction, flow, pull, quality at the source, small batches, feedback, and continuous improvement.
For hybrid projects, I help learners connect Agile teams and Jira work with formal milestones, budgets, contracts, governance, executive reports, procurement, interproject dependencies, and Primavera P6 or Microsoft Project schedules.

N- BUSINESS ANALYSIS AND REQUIREMENTS
My Management Information Systems background enables me to integrate Project Management with Business Analysis.
I support:
• Stakeholder identification and analysis
• Elicitation planning
• Interviews and workshops
• Observation
• Document analysis
• Surveys
• Current- and future-state analysis
• Process modelling
• Business rules
• Functional and non-functional requirements
• Use cases
• User stories
• Acceptance criteria
• Prototypes and models
• Prioritization
• Requirements validation
• Traceability
• Change assessment
• Solution evaluation
• Benefits and value analysis
I emphasize that poor requirements frequently produce scope disputes, rework, delays, cost growth, quality problems, and dissatisfied stakeholders.

O- GOVERNANCE AND STRATEGIC ALIGNMENT
I help learners connect individual projects with organizational strategy, investment decisions, governance, authority, and accountability.
Topics may include:
• Strategic objectives
• Business cases
• Project selection
• Feasibility
• Benefits
• Sponsorship
• Governance boards
• Steering committees
• Stage gates
• Tolerances and thresholds
• Decision rights
• Escalation
• Assurance
• Audits
• Portfolio alignment
• Ethical decision-making
Governance is presented as a framework for effective decisions and accountability rather than unnecessary bureaucracy.

P- STAKEHOLDER MANAGEMENT, LEADERSHIP, AND COMMUNICATION
I support stakeholder identification, analysis, engagement planning, communication, negotiation, facilitation, conflict management, influence, team leadership, and executive reporting.
Learners may work with:
• Power–interest and influence–impact analyses
• Stakeholder registers
• Engagement assessments
• Communication matrices
• Meeting structures
• Decision logs
• Action logs
• Issue escalation
• Negotiation strategies
• Conflict-resolution approaches
• Team charters
• Responsibility matrices
• Leadership styles
• Motivation and team development
• Cross-functional and multicultural teams
I emphasize that successful Project Management requires both analytical systems and human leadership.
A technically accurate schedule cannot deliver a project when responsibilities, decisions, communication, trust, or stakeholder support are weak.

Q- QUALITY MANAGEMENT
I support quality planning, assurance, control, acceptance, verification, validation, inspections, tests, audits, checklists, non-conformance management, root-cause analysis, corrective action, and continuous improvement.
Methods may include:
• Pareto analysis
• Cause-and-effect diagrams
• Five Whys
• Flowcharts
• Control-chart foundations
• Check sheets
• Histograms
• Lessons learned
• Acceptance criteria
• Definition of Done
I help learners distinguish product quality from project-process quality and prevention from correction.

R- PROCUREMENT, CONTRACTS, AND COMMERCIAL INTERFACES
For procurement and contract-related projects, I support:
• Make-or-buy analysis
• Procurement planning
• Statements of Work
• Requests for information, quotations, and proposals
• Supplier evaluation
• Contract types
• Fixed-price and cost-reimbursable arrangements
• Time-and-materials contracts
• Incentives and penalties
• Payment milestones
• Deliverables and acceptance
• Claims and changes
• Supplier performance
• Contract closeout
• Commercial risk
• Interface management
I explain how contractual obligations influence schedules, reporting, risk allocation, change processes, approvals, documentation, and stakeholder behaviour.

S- CHANGE CONTROL AND CONFIGURATION
I support integrated change-control processes involving:
• Change identification
• Impact assessment
• Scope, schedule, cost, risk, quality, contract, and benefit impacts
• Alternatives
• Approval authority
• Change Control Boards
• Decision documentation
• Baseline updates
• Configuration control
• Implementation
• Verification
• Communication
• Traceability
I emphasize the distinction between approved change, unauthorized scope growth, corrective action, defect repair, rework, contingency response, and normal execution.

T- ORGANIZATIONAL CHANGE AND ADOPTION
Projects often deliver systems, processes, structures, policies, technologies, or behaviours that require organizational adoption.
I support:
• Change-impact analysis
• Stakeholder readiness
• Communication
• Training
• Resistance management
• Role transition
• Operational preparation
• Knowledge transfer
• Adoption metrics
• Reinforcement
• Benefits realization
A project is not successful merely because a technical output has been completed. The intended users must be prepared, capable, willing, and supported in using the new result.

U- PROJECT AUDIT AND DIAGNOSTIC REVIEW
Throughout my academic, consulting, Engineering, research, and professional career, I have contributed to, supervised, and supported hundreds of technical, organizational, analytical, and multidisciplinary projects.
I support project audits and diagnostic reviews involving:
• Scope clarity and requirements
• Work Breakdown Structures
• Schedule logic and quality
• Baselines
• Data dates and progress
• Critical and near-critical paths
• Float
• Resources and productivity
• Costs and Earned Value
• Risks and issues
• Changes
• Contracts
• Governance
• Stakeholders
• Dashboards and reporting
• Documentation
• Forecasts
• Project controls
The objective is to determine whether the project information is reliable, whether controls are functioning, and whether management decisions are supported by evidence.

V- DELAYED-PROJECT RECOVERY
For delayed, over-budget, or underperforming projects, I help learners identify:
• Root causes
• Critical constraints
• Unrealistic assumptions
• Poor logic
• Scope instability
• Resource shortages
• Productivity problems
• Procurement delays
• Decision bottlenecks
• Design or approval interfaces
• Contractual restrictions
• Control weaknesses
• Data-quality problems
• Recovery alternatives
Potential responses may include resequencing, additional resources, scope prioritization, procurement acceleration, improved decisions, interface resolution, alternative methods, schedule compression, milestone renegotiation, or revised delivery strategies.
Every recovery option is evaluated through time, cost, risk, quality, contractual, stakeholder, and feasibility considerations.

W- PROGRAMS, PORTFOLIOS, AND PMOS
My broader management perspective includes program, portfolio, and Project Management Office principles.
I support:
• Project interdependencies
• Program roadmaps
• Shared resources
• Benefits management
• Cross-project risks
• Strategic alignment
• Project selection and prioritization
• Portfolio balance
• Capacity
• Governance
• Stage gates
• Standards
• Templates
• Assurance
• Reporting
• Lessons learned
• Knowledge repositories
• Capability development
I explain how managing a group of connected projects differs from controlling one project in isolation.

X- DASHBOARDS, ANALYTICS, AND EXECUTIVE REPORTING
I help learners design reporting systems that focus attention on decisions, exceptions, causes, trends, forecasts, actions, and business impact.
Project reporting may involve:
• Milestone status
• Critical-path movement
• Schedule and cost variance
• Earned Value indicators
• Forecast dates and costs
• Resource and productivity trends
• Risks and issues
• Changes
• Procurement
• Quality
• Benefits
• Decisions and actions
• Root-cause explanations
Where appropriate, project information may be connected with Excel, Power BI, databases, Primavera P6, Microsoft Project, Jira, and other analytical or reporting environments.
A dashboard should not merely display attractive charts. It should present reliable evidence that supports timely and accountable management action.

Y- AUTOMATION AND RESPONSIBLE ARTIFICIAL INTELLIGENCE
My background in Artificial Intelligence allows me to introduce responsible automation and AI-assisted Project Management where these genuinely improve productivity or decision quality.
Potential applications may include:
• Drafting preliminary project documents
• Summarizing meetings and actions
• Organizing knowledge and lessons learned
• Reviewing schedule or risk information
• Developing initial checklists or scenarios
• Supporting reporting and dashboard commentary
• Retrieving information from approved project sources
• Identifying patterns or exceptions
• Assisting with documentation and communication
I emphasize verification, confidentiality, data security, source reliability, bias, accountability, transparency, and human approval.
AI cannot assume the responsibilities of the sponsor, Project Manager, planner, cost controller, technical expert, or decision authority.

Z- CERTIFICATION PREPARATION
Where relevant, I can support learning aligned with current PMP, CAPM, Agile, Scrum, Primavera P6, or Microsoft Project objectives after reviewing the applicable official syllabus and the learner’s experience.
Certification support may include:
• Concept review
• Application of frameworks
• Scenario-based questions
• Terminology
• Process relationships
• Agile and hybrid concepts
• Practice questions
• Knowledge-gap identification
• Study planning
• Examination strategies
• Ethical and professional responsibilities
I distinguish clearly between teaching the subject and claiming official certification authority or guaranteeing examination success.

AA- CAREER AND PROFESSIONAL DEVELOPMENT
I support professionals seeking to enter, strengthen, or advance within Project Management, planning, scheduling, Project Controls, Business Analysis, Agile delivery, or coordination roles.
Professional support may include:
• Résumé positioning
• Translation of existing experience into project terminology
• Technical and behavioural interview preparation
• Scenario questions
• Role expectations
• Workplace documentation
• Current-project coaching
• Stakeholder communication
• Reporting improvement
• Software-transition support
• Portfolio development
I help learners connect their previous Engineering, business, technical, operational, or administrative experience with realistic Project Management responsibilities.

AB- PROJECT PORTFOLIO DEVELOPMENT
Learners may build a complete academic or professional portfolio containing:
• Business case
• Project charter
• Stakeholder register
• Requirements
• Scope statement
• Work Breakdown Structure
• Responsibility Assignment Matrix
• Primavera P6 or Microsoft Project schedule
• Resource and cost plan
• Risk register
• RAID log
• Procurement plan
• Change-control process
• Jira backlog and board where relevant
• Progress dashboard
• Performance report
• Forecast
• Recovery scenario
• Lessons-learned report
The objective is to demonstrate connected project reasoning and professional deliverables rather than a collection of unrelated templates.

AC- ACADEMIC AND WORKPLACE INTEGRITY
I support coursework, assignments, case studies, research projects, examinations, certifications, workplace challenges, and current projects while preserving academic and professional integrity.
For assessed work, I explain concepts, guide the learner’s reasoning, review errors, test assumptions, and strengthen the learner’s own solution.
For workplace projects, the learner or responsible professional retains authority, accountability, access control, approvals, and ownership of final decisions.
I do not replace the Project Manager, planner, sponsor, contract authority, or technical decision-maker.

AD- TEACHING APPROACH
My teaching approach is structured, rigorous, practical, patient, and decision-oriented.
I begin by identifying the learner’s background, role, industry, level, software environment, project type, current difficulties, deadlines, and expected outcomes.
I then connect management concepts, tools, technical calculations, stakeholder realities, governance, documentation, and real scenarios within one coherent project workflow.
I explain not only how to create a schedule, register, backlog, dashboard, or report, but why it is needed, what assumptions it contains, how it should be validated, and how it supports decisions.
My objective is not merely to teach software commands or terminology, but to develop independent project professionals who can structure work, evaluate evidence, lead stakeholders, diagnose problems, make defensible decisions, and deliver valuable outcomes.

AE- LEARNER LEVELS AND PERSONALIZATION
I support complete beginners, college and university students, graduate researchers, project coordinators, planners, schedulers, engineers, analysts, Scrum team members, Product Owners, managers, consultants, program and portfolio professionals, executives, and career-transition learners.
Lessons may focus on Project Management foundations, Primavera P6, Microsoft Project, Jira, Agile, Project Controls, scheduling, Earned Value, risk, Business Analysis, governance, leadership, certification preparation, project recovery, portfolio development, or an actual professional project.
I teach in English, French, and Arabic, and I adapt every session to the learner’s industry, role, level, software version, project environment, pace, immediate needs, and academic or professional objectives.

See more

About the lesson

  • Elementary School
  • Middle School
  • High School
  • +11
  • levels :

    Elementary School

    Middle School

    High School

    College

    University

    Adult Education

    Masters/ Graduate School

    MBA

    Early childhood education

    Première

    Terminale

    Doctorate

    ACCA

    Post Graduate Studies

  • French
  • English

All languages in which the lesson is available :

French

English

Project management is not simply creating schedules, updating tasks, or using software. Effective project delivery requires a complete management system:

**Business need → value and authorization → requirements and scope → Work Breakdown Structure and schedule → resources and cost → risk and contracts → execution and Agile delivery → monitoring and control → change and recovery → transition, benefits, and closeout.**

My lessons help you understand this complete process so that you can make informed decisions, establish dependable plans, manage uncertainty, lead stakeholders and teams, interpret project performance, and deliver valuable outcomes rather than mechanically operate project-management software.

I teach beginners, college and university students, engineers, planners, schedulers, analysts, project coordinators, Scrum team members, project managers, program and portfolio professionals, researchers, consultants, executives, and working professionals. Each lesson is adapted to your current role, industry, project stage, delivery method, software environment, assignment, certification objective, or workplace requirements.

At the beginning, I identify your role, industry, current project stage, delivery approach, organizational environment, software versions, available plans and records, expected outputs, deadlines, and principal conceptual or technical difficulties. We then establish a focused learning or project-improvement pathway.

A- COMPLETE PROJECT-DELIVERY LIFECYCLE

Lessons may address the complete project lifecycle:
• Identifying a business need, problem, opportunity, regulatory requirement, or strategic objective
• Evaluating feasibility and alternative solutions
• Developing the business case
• Defining expected value, outcomes, benefits, constraints, assumptions, and success measures
• Authorizing the project
• Establishing governance, roles, authority, escalation routes, and reporting
• Identifying stakeholders and requirements
• Defining product and project scope
• Developing the Work Breakdown Structure
• Planning activities, dependencies, milestones, resources, costs, risks, quality, procurement, and communications
• Selecting predictive, Agile, iterative, incremental, or hybrid delivery methods
• Executing the work
• Monitoring progress, cost, quality, risk, resources, and stakeholder engagement
• Managing issues, decisions, changes, dependencies, and corrective actions
• Forecasting project outcomes
• Recovering delayed or underperforming projects
• Transitioning deliverables into operations
• Confirming acceptance
• Closing contracts and project records
• Capturing lessons learned
• Monitoring benefits after delivery
• Maintaining traceability from the original business need to the final outcome

B- PROJECT AUDIT AND DIAGNOSTIC REVIEW

At the beginning of the guidance process, we may review:
• The business case
• Project charter
• Governance structure
• Scope statement
• Requirements
• Work Breakdown Structure
• Schedule
• Resource plan
• Cost estimate and budget
• Risk register
• Procurement records
• Contracts
• Progress reports
• Change requests
• Issues and decision logs
• Jira, Primavera P6, Microsoft Project, or Microsoft Planner files
• Stakeholder concerns
• Project controls
• Existing dashboards
• Deadlines and delivery pressures
• Schedule and cost performance
• Current recovery actions
• Organizational constraints
• The difference between planning, execution, reporting, leadership, and software problems
• Areas requiring correction, restructuring, clarification, or improved governance

C- PMBOK GUIDE—EIGHTH EDITION AND MODERN PROJECT MANAGEMENT

Lessons may be aligned with current PMBOK Guide—Eighth Edition concepts, including:
• Value delivery
• Adaptability
• Accountability
• Governance
• Tailoring
• Stakeholder engagement
• Team performance
• Planning
• Project work
• Delivery
• Measurement
• Uncertainty
• Business context
• Sustainability
• Technology
• Responsible use of Artificial Intelligence
• Outcomes rather than document production alone
• Selecting methods according to the project environment
• Avoiding mechanical application of processes without considering value or context
• Connecting principles, performance domains, practices, tools, and organizational objectives

D- SYSTEMS THINKING

You may learn:
• Projects as components of larger organizational systems
• Interactions among technical, human, financial, contractual, environmental, and operational elements
• Feedback loops
• Dependencies
• Constraints
• Delays
• Reinforcing and balancing effects
• Local versus system-wide optimization
• Unintended consequences
• Emergent behaviour
• Trade-offs
• Interfaces
• Organizational complexity
• External influences
• Recognizing how changes in one area affect scope, schedule, cost, quality, risk, resources, operations, and benefits
• Avoiding solutions that improve one project component while damaging overall value

E- BUSINESS CASE AND VALUE MANAGEMENT

Lessons may include:
• Problem and opportunity definition
• Strategic alignment
• Objectives
• Expected outcomes
• Financial and non-financial benefits
• Costs
• Risks
• Assumptions
• Constraints
• Options analysis
• Feasibility
• Return on investment
• Payback-period awareness
• Net-present-value foundations
• Cost–benefit analysis
• Social, environmental, and operational value
• Success criteria
• Key performance indicators
• Benefit owners
• Benefit profiles
• Benefit dependencies
• Transition requirements
• Benefit realization
• Post-project evaluation
• Confirming whether the project should continue, change direction, pause, or stop
• Distinguishing project outputs from business outcomes and benefits

F- PROJECT GOVERNANCE

Lessons may include:
• Governance principles
• Sponsor responsibilities
• Project-manager authority
• Steering committees
• Project boards
• Decision rights
• Delegated authority
• Approval thresholds
• Stage gates
• Tolerances
• Escalation routes
• Assurance
• Independent reviews
• Audits
• Reporting requirements
• Ethics
• Transparency
• Accountability
• Compliance
• Documentation
• Governance calendars
• Relationship between project, program, portfolio, and organizational governance
• Avoiding unclear authority, delayed decisions, and duplicated approvals

G- PROJECT INITIATION

Project-initiation topics may include:
• Project purpose
• Background
• Business need
• Strategic alignment
• Measurable objectives
• High-level scope
• Key deliverables
• High-level requirements
• Assumptions
• Constraints
• Milestones
• Initial risks
• Budget expectations
• Stakeholders
• Sponsor
• Project manager
• Governance
• Success criteria
• Approval requirements
• Project charter
• Kick-off planning
• Establishing shared understanding before detailed planning begins

H- REQUIREMENTS AND BUSINESS ANALYSIS

Lessons may include:
• Stakeholder elicitation
• Interviews
• Workshops
• Observation
• Document review
• Surveys
• Prototyping
• Current-state analysis
• Future-state analysis
• Gap analysis
• Business rules
• Process modelling
• Functional requirements
• Non-functional requirements
• Technical requirements
• Regulatory requirements
• Transition requirements
• Product requirements
• User needs
• Use cases
• User stories
• Acceptance criteria
• Requirement prioritization
• MoSCoW awareness
• Traceability
• Requirement validation
• Requirement verification
• Solution evaluation
• Requirement-change management
• Avoiding ambiguous, conflicting, incomplete, untestable, or unnecessary requirements

I- PRODUCT AND PROJECT SCOPE

Lessons may include:
• Product scope
• Project scope
• Deliverables
• Boundaries
• Exclusions
• Assumptions
• Constraints
• Acceptance criteria
• Scope statement
• Product vision
• Product Goal
• Minimum Viable Product awareness
• Incremental delivery
• Scope baseline
• Scope validation
• Scope control
• Requirement traceability
• Progressive elaboration
• Rolling-wave planning
• Distinguishing legitimate refinement from uncontrolled scope creep

J- WORK BREAKDOWN STRUCTURES

You may learn:
• Deliverable-oriented decomposition
• The 100-percent rule
• Hierarchical structure
• Major deliverables
• Sub deliverables
• Control accounts
• Planning packages
• Work packages
• WBS dictionaries
• Coding structures
• Responsibility assignment
• Cost-account integration
• Schedule integration
• Procurement integration
• Organizational Breakdown Structure relationships
• Control Account Managers
• Avoiding WBS structures that are only activity lists, organizational charts, or uncontrolled task collections
• Determining the appropriate level of decomposition
• Maintaining traceability between scope, schedule, cost, responsibility, and reporting

K- RESPONSIBILITY AND ORGANIZATIONAL STRUCTURES

Lessons may include:
• Organizational Breakdown Structures
• Resource Breakdown Structures
• Responsibility Assignment Matrices
• RACI
• RAM structures
• Roles and responsibilities
• Accountability
• Authority
• Interfaces
• Escalation routes
• Work ownership
• Control accounts
• Matrix organizations
• Functional organizations
• Projectized organizations
• Weak, balanced, and strong matrices
• Clarifying who performs, approves, supports, reviews, and receives information

L- ACTIVITY DEFINITION AND SCHEDULE DEVELOPMENT

Lessons may include:
• Activities
• Milestones
• Summary activities
• Level-of-effort activities
• Hammock activities
• Work packages
• Activity attributes
• Duration estimates
• Mandatory dependencies
• Discretionary dependencies
• Internal dependencies
• External dependencies
• Finish-to-start relationships
• Start-to-start relationships
• Finish-to-finish relationships
• Start-to-finish relationships
• Leads
• Lags
• Calendars
• Constraints
• Deadlines
• Assumptions
• Sequence validation
• Logic diagrams
• Precedence Diagramming Method
• Traceable network logic
• Avoiding arbitrary dates and disconnected activity lists

M- DURATION ESTIMATING

Lessons may include:
• Expert judgment
• Analogous estimating
• Parametric estimating
• Bottom-up estimating
• Three-point estimates
• Optimistic duration
• Most-likely duration
• Pessimistic duration
• PERT awareness
• Productivity
• Quantities
• Crew size
• Resource availability
• Learning curves
• Calendars
• Constraints
• Uncertainty
• Contingency
• Historical information
• Estimating assumptions
• Distinguishing effort, duration, and elapsed time
• Avoiding false precision

N- CRITICAL PATH METHOD

You may learn:
• Project networks
• Forward pass
• Backward pass
• Early start
• Early finish
• Late start
• Late finish
• Total float
• Free float
• Interfering-float awareness
• Critical activities
• Critical paths
• Multiple critical paths
• Near-critical paths
• Longest-path awareness
• Negative float
• Critical-path continuity
• Calendar effects
• Constraint effects
• Float ownership
• Schedule sensitivity
• Criticality changes during progress
• Understanding why software-generated critical paths may be unreliable when the schedule logic is poor

O- SCHEDULE COMPRESSION

Lessons may include:
• Crashing
• Fast tracking
• Overtime
• Additional resources
• Alternative sequencing
• Scope adjustment
• Phased delivery
• Parallel work
• Procurement acceleration
• Calendar modification
• Productivity improvement
• Trade-offs among time, cost, risk, quality, resources, and rework
• Identifying when compression increases rather than decreases completion risk

P- SCHEDULE-QUALITY ASSESSMENT

Schedule review may include:
• Missing predecessors
• Missing successors
• Open ends
• Dangling activities
• Excessive constraints
• Hard constraints
• Excessive leads
• Excessive lags
• Long activities
• Invalid progress
• Out-of-sequence work
• Negative float
• Excessive float
• Incorrect calendars
• Unrealistic durations
• Resource inconsistencies
• Broken critical paths
• Baseline integrity
• Data-date consistency
• Actual dates
• Remaining duration
• Logic changes
• Critical and near-critical paths
• Relationship density
• Milestone quality
• DCMA-style schedule-metric awareness
• Understanding that automated metrics support professional judgment but do not replace it

Q- ROLLING-WAVE AND LOOK-AHEAD PLANNING

Lessons may include:
• Rolling-wave planning
• Progressive elaboration
• Near-term detail
• Long-term planning packages
• Two-week look-aheads
• Three-week look-aheads
• Six-week look-aheads
• Constraint logs
• Work readiness
• Design readiness
• Material readiness
• Access
• Permits
• Labour
• Equipment
• Handoffs
• Daily coordination
• Commitment planning
• Field progress
• Connecting look-ahead plans to the integrated master schedule
• Identifying reasons planned work was not completed

R- RESOURCE AND CAPACITY MANAGEMENT

Lessons may include:
• Labour
• Equipment
• Materials
• Roles
• Skills
• Resource calendars
• Availability
• Productivity
• Utilization
• Allocation
• Overallocations
• Bottlenecks
• Resource histograms
• Resource curves
• Resource smoothing
• Resource levelling
• Capacity planning
• Shared resources
• Matrix-resource conflicts
• Critical resources
• Resource-constrained scheduling
• Schedule and cost trade-offs
• Avoiding the assumption that unlimited resources are available

S- COST ESTIMATING

Cost-estimating lessons may include:
• Analogous estimates
• Parametric estimates
• Bottom-up estimates
• Three-point estimates
• Quantity and rate foundations
• Labour costs
• Equipment costs
• Material costs
• Subcontractor costs
• Direct costs
• Indirect costs
• Fixed and variable costs
• Recurring and non-recurring costs
• Escalation
• Contingency
• Management reserves
• Estimate assumptions
• Estimate classes awareness
• Basis of estimate
• Accuracy ranges
• Uncertainty
• Avoiding unsupported single-value estimates

T- BUDGETING AND COST BASELINES

Lessons may include:
• Cost aggregation
• Cost Breakdown Structures
• Control accounts
• Work-package budgets
• Time-phased budgets
• Planned expenditure
• Cash flow
• Funding limits
• Commitments
• Accruals awareness
• Actual costs
• Forecast costs
• Contingency reserves
• Management reserves
• Cost baseline
• Performance Measurement Baseline
• Budget at Completion
• Approved changes
• Maintaining consistency among scope, schedule, resources, and cost

U- EARNED VALUE MANAGEMENT

Lessons may include:
• Planned Value
• Earned Value
• Actual Cost
• Schedule Variance
• Cost Variance
• Schedule Performance Index
• Cost Performance Index
• Budget at Completion
• Estimate at Completion
• Estimate to Complete
• Variance at Completion
• To-Complete Performance Index
• Progress-measurement rules
• Physical percentage complete
• Duration percentage complete
• Units-complete methods
• Weighted milestones
• Fixed-formula methods
• Level-of-effort measurement
• Forecast assumptions
• Integrated baselines
• Cost-loaded schedules
• Work-package performance
• Control-account performance
• Interpretation limitations
• Avoiding misleading Earned Value calculations based on poor progress rules or unreliable baselines

V- PROJECT-CONTROL CURVES AND REPORTING

Project-control reporting may include:
• Planned and actual S-curves
• Earned-value curves
• Cash-flow curves
• Resource histograms
• Milestone trend analysis
• Schedule trends
• Cost trends
• Forecast completion
• Variance analysis
• Progress curves
• Look-ahead reports
• Critical-path reports
• Exception reports
• Risk heat maps
• Change summaries
• Executive dashboards
• Portfolio dashboards
• Narrative explanations
• Identifying causes, consequences, corrective actions, owners, and forecast impact rather than reporting numbers alone

W- QUALITATIVE RISK MANAGEMENT

Lessons may include:
• Risk-management planning
• Risk identification
• Risk statements
• Cause–event–effect structure
• Threats
• Opportunities
• Risk Breakdown Structures
• Probability
• Impact
• Risk exposure
• Proximity
• Urgency
• Detectability
• Manageability
• Risk appetite
• Risk tolerance
• Thresholds
• Risk ownership
• Risk action ownership
• Avoidance
• Mitigation
• Transfer
• Acceptance
• Escalation
• Exploitation
• Enhancement
• Sharing
• Residual risks
• Secondary risks
• Triggers
• Contingency plans
• Fallback plans
• Risk reviews
• Risk burndown
• Connecting risks to schedule, cost, scope, stakeholders, contracts, and benefits

X- QUANTITATIVE RISK ANALYSIS

When appropriate, lessons may include:
• Expected monetary value
• Decision trees
• Three-point estimates
• Probability distributions
• Triangular distributions
• Beta distributions
• Normal-distribution awareness
• Correlation awareness
• Monte Carlo simulation
• Schedule-risk analysis
• Cost-risk analysis
• Confidence levels
• P-values versus project confidence distinctions
• Percentile completion dates
• Contingency determination
• Sensitivity analysis
• Tornado charts
• Criticality indices
• Risk-adjusted forecasts
• Comparing deterministic and probabilistic schedules
• Recognizing model assumptions and data limitations
• Avoiding the belief that simulation eliminates uncertainty

Y- RAID AND DECISION MANAGEMENT

Lessons may include:
• Risks
• Assumptions
• Issues
• Dependencies
• Constraints
• Actions
• Decisions
• Ownership
• Due dates
• Priority
• Status
• Escalation
• Linkage to activities, milestones, costs, and contracts
• Closure criteria
• Decision rationale
• Audit trails
• Avoiding registers that are updated only for reporting purposes without influencing management decisions

Z- STAKEHOLDER ANALYSIS AND ENGAGEMENT

Lessons may include:
• Stakeholder identification
• Internal and external stakeholders
• Interests
• Influence
• Power
• Impact
• Legitimacy
• Urgency
• Salience
• Expectations
• Attitudes
• Support and resistance
• Engagement levels
• Stakeholder mapping
• Power–interest grids
• Engagement-assessment matrices
• Coalitions
• Sponsors
• Regulators
• Users
• Communities
• Suppliers
• Team members
• Engagement strategies
• Participation
• Consultation
• Negotiation
• Escalation
• Measuring engagement effectiveness
• Avoiding one-directional communication disguised as engagement

AA- PROJECT COMMUNICATION

Lessons may include:
• Communication requirements
• Audience analysis
• Communication methods
• Formal and informal communication
• Written and verbal communication
• Interactive, push, and pull communication
• Communication calendars
• Governance meetings
• Status reports
• Executive summaries
• Dashboards
• Presentations
• Escalation reports
• Meeting agendas
• Minutes
• Action lists
• Decision logs
• Issue reports
• Change notices
• Visual reporting
• Communication channels
• Information confidentiality
• Tailoring technical detail to each audience
• Confirming that information was understood rather than merely transmitted

AB- MEETING AND WORKSHOP FACILITATION

Lessons may include:
• Meeting purpose
• Participant selection
• Agendas
• Pre-reading
• Roles
• Timeboxing
• Facilitation
• Ground rules
• Decision methods
• Voting
• Consensus awareness
• Capturing actions
• Assigning ownership
• Recording decisions
• Managing conflict
• Encouraging participation
• Preventing domination
• Closing meetings
• Following up
• Requirements workshops
• Planning workshops
• Risk workshops
• Retrospectives
• Lessons-learned sessions
• Avoiding recurring meetings without decisions or value

AC- PROJECT LEADERSHIP AND TEAM PERFORMANCE

Lessons may include:
• Leadership styles
• Situational leadership
• Servant leadership
• Ethical leadership
• Team formation
• Team charters
• Roles
• Accountability
• Delegation
• Motivation
• Coaching
• Mentoring
• Facilitation
• Emotional intelligence
• Self-awareness
• Empathy
• Conflict management
• Negotiation
• Feedback
• Psychological safety
• Trust
• Decision making
• Problem solving
• Virtual teams
• Cross-cultural teams
• Diversity and inclusion
• Performance improvement
• Managing underperformance
• Supporting autonomy without losing accountability

AD- CONFLICT AND NEGOTIATION

Lessons may include:
• Sources of project conflict
• Task conflict
• Process conflict
• Relationship conflict
• Resource conflict
• Priority conflict
• Contractual conflict
• Avoiding
• Accommodating
• Compromising
• Collaborating
• Competing
• Interest-based negotiation
• Positions versus interests
• BATNA awareness
• Objective criteria
• Trade-offs
• Escalation
• Mediation foundations
• Documenting agreements
• Maintaining working relationships while protecting project objectives

AE- ORGANIZATIONAL CHANGE AND ADOPTION

Lessons may include:
• Change-impact assessment
• Change readiness
• Sponsorship
• Stakeholder adoption
• Resistance
• Communication
• Training
• Transition planning
• New roles
• New processes
• New systems
• Behaviour change
• Reinforcement
• Adoption measures
• Benefit adoption
• Change networks
• Champions
• ADKAR foundations
• Other change frameworks when appropriate
• Distinguishing technical implementation from successful organizational adoption

AF- QUALITY MANAGEMENT

Lessons may include:
• Quality requirements
• Customer expectations
• Acceptance criteria
• Standards
• Regulations
• Metrics
• Prevention
• Appraisal
• Failure costs
• Quality planning
• Quality assurance
• Quality control
• Inspections
• Testing
• Reviews
• Audits
• Checklists
• Defects
• Nonconformances
• Rework
• Root-cause analysis
• Five Whys
• Cause-and-effect diagrams
• Pareto analysis
• Process maps
• Control-chart awareness
• Process capability awareness
• Continuous improvement
• Lessons learned
• Avoiding the assumption that quality can be inspected into a defective process at the end

AG- PROCUREMENT STRATEGY

Lessons may include:
• Make-or-buy analysis
• Procurement planning
• Sourcing strategy
• Supplier market analysis
• Work packages
• Statements of work
• Specifications
• Requests for Information
• Requests for Quotation
• Requests for Proposal
• Invitations to Tender
• Bidder conferences
• Evaluation criteria
• Technical and commercial evaluation
• Supplier selection
• Negotiation
• Award recommendations
• Procurement schedules
• Long-lead items
• Expediting awareness
• Supplier integration
• Procurement risks
• Ethical procurement

AH- CONTRACT TYPES

Contract structures may include:
• Fixed-price contracts
• Firm-fixed-price contracts
• Fixed-price incentive contracts
• Cost-reimbursable contracts
• Cost-plus-fixed-fee contracts
• Cost-plus-incentive-fee contracts
• Time-and-material contracts
• Unit-rate contracts
• Framework agreements
• Purchase orders
• Design–bid–build
• Design–build
• Engineering, Procurement, and Construction
• Turnkey arrangements
• Alliance and collaborative-contract awareness
• Selecting a contract according to scope certainty, risk allocation, market conditions, and management capability

AI- CONTRACT ADMINISTRATION

Lessons may include:
• Contract documents
• Obligations
• Deliverables
• Notices
• Records
• Submittals
• Requests for Information
• Approvals
• Variations
• Change orders
• Payment milestones
• Progress measurement
• Invoices
• Retention
• Bonds
• Guarantees
• Insurance awareness
• Supplier performance
• Nonconformance
• Claims awareness
• Disputes
• Completion
• Handover
• Warranty
• Contract closeout
• Maintaining contemporaneous and traceable commercial records

AJ- INTEGRATED CHANGE CONTROL

Lessons may include:
• Change requests
• Change sources
• Scope changes
• Design changes
• Requirement changes
• Schedule changes
• Cost changes
• Risk changes
• Contract changes
• Impact analysis
• Alternatives
• Recommendations
• Change-control boards
• Approval authority
• Emergency changes
• Baseline changes
• Implementation
• Communication
• Verification
• Closure
• Change logs
• Preventing informal instructions from becoming uncontrolled commitments
• Evaluating cumulative change rather than reviewing each change in isolation

AK- CONFIGURATION AND DOCUMENT CONTROL

Lessons may include:
• Configuration items
• Document numbering
• Revisions
• Status codes
• Review and approval
• Version control
• Baselines
• Distribution
• Access
• Master records
• Transmittals
• Superseded documents
• Redlines
• As-built records
• Audit trails
• Technical submittals
• Controlled templates
• Naming conventions
• Folder structures
• SharePoint foundations
• Preventing teams from working from obsolete information

AL- DELAY-ANALYSIS FOUNDATIONS

When relevant, lessons may include:
• Contemporaneous records
• Baseline schedules
• Schedule updates
• As-planned schedules
• As-built information
• Delay events
• Critical-path impact
• Float
• Excusable delay
• Non-excusable delay
• Compensable-delay awareness
• Concurrent-delay awareness
• Impacted as-planned method
• Time-impact analysis
• Windows-analysis awareness
• Collapsed as-built awareness
• Schedule narratives
• Extension-of-time documentation
• Cause-and-effect relationships
• Analytical limitations
• Maintaining the distinction between project-controls education and formal legal, contractual, or expert-witness advice

AM- PROJECT MONITORING AND CONTROL

Monitoring and control may include:
• Data-date management
• Progress collection
• Actual starts
• Actual finishes
• Remaining duration
• Quantities complete
• Physical completion
• Cost actuals
• Forecasting
• Critical-path review
• Near-critical-path review
• Variance analysis
• Trend analysis
• Risk review
• Resource review
• Change review
• Procurement review
• Quality review
• Stakeholder review
• Corrective actions
• Preventive actions
• Recovery planning
• Forecast completion
• Management by exception
• Ensuring that progress information reflects reality rather than optimistic reporting

AN- PROJECT RECOVERY

Lessons may include:
• Diagnostic review
• Root causes
• Scope clarification
• Schedule correction
• Critical-path restoration
• Logic correction
• Resource reallocation
• Priority changes
• Procurement acceleration
• Alternative sequencing
• Fast tracking
• Crashing
• Additional shifts
• Productivity improvement
• Scope reduction
• Phased delivery
• Risk reassessment
• Stakeholder negotiations
• Contract implications
• Recovery baselines
• Recovery schedules
• Management approval
• Monitoring recovery effectiveness
• Avoiding superficial recovery plans based only on shorter activity durations

AO- PRIMAVERA P6 PROFESSIONAL

Primavera P6 lessons may include:
• Enterprise Project Structure
• Organizational Breakdown Structure
• Projects
• Work Breakdown Structures
• Calendars
• Activities
• Milestones
• Relationships
• Leads and lags
• Constraints
• Steps
• Activity types
• Duration types
• Percent-complete types
• Activity codes
• Project codes
• Resource codes
• User-defined fields
• Resources
• Roles
• Expenses
• Rate types
• Resource assignments
• Resource curves
• WBS milestones
• Baselines
• Baseline assignment
• Progress methods
• Data dates
• Scheduling
• Multiple float paths
• Longest path
• Critical activities
• Earned-value settings
• Layouts
• Filters
• Grouping
• Sorting
• Bars
• Columns
• Reports
• Global Change
• Threshold awareness
• Issues
• Risks awareness
• Import and export
• XER files
• XML awareness
• Excel exchange
• Multi-project environments
• Security and access awareness
• Systematic schedule analysis

AP- PRIMAVERA P6 PROJECT CREATION

You may learn how to:
• Create a project
• Select an EPS location
• Assign an OBS
• Establish planned start and finish expectations
• Create calendars
• Build the WBS
• Add activities
• Define milestones
• Assign activity codes
• Establish relationships
• Apply constraints only when justified
• Enter durations
• Assign resources and roles
• Add expenses
• Schedule the project
• Review critical and longest paths
• Review float
• Correct logic
• Create and assign baselines
• Develop layouts and reports
• Document planning assumptions

AQ- PRIMAVERA P6 PROGRESS UPDATING

Lessons may include:
• Data date
• Actual starts
• Actual finishes
• Remaining duration
• Expected finish
• Physical percentage complete
• Duration percentage complete
• Units percentage complete
• Activity steps
• Resource actuals
• Expenses
• Out-of-sequence progress
• Retained Logic
• Progress Override
• Actual Dates
• Suspend and resume awareness
• Schedule recalculation
• Baseline comparison
• Slippage
• Variance
• Critical-path changes
• Forecasting
• Progress Spotlight
• Update cycles
• Update narratives
• Maintaining consistent status rules

AR- PRIMAVERA P6 RESOURCE AND COST MANAGEMENT

Lessons may include:
• Resource dictionaries
• Roles
• Units per time
• Resource calendars
• Prices and rates
• Resource assignments
• Labour
• Non-labour
• Materials
• Expenses
• Resource curves
• Resource histograms
• Profiles
• Usage spreadsheets
• Overallocations
• Levelling
• Cost loading
• Planned Value
• Earned Value
• Actual Cost
• Forecast cost
• S-curves
• Cost and resource reporting
• Avoiding inconsistent resource, calendar, and duration settings

AS- PRIMAVERA P6 SCHEDULE REVIEW AND RECOVERY

Lessons may include:
• Open ends
• Missing logic
• Constraints
• Lags
• Long activities
• Negative float
• Critical and near-critical paths
• Longest-path continuity
• Calendar problems
• Invalid progress
• Baseline integrity
• Logic changes
• Out-of-sequence work
• Progress methods
• Float erosion
• Delay events
• Recovery options
• What-if copies
• Alternative sequences
• Resource changes
• Calendar changes
• Schedule compression
• Recovery-schedule reporting
• Maintaining defensible schedule narratives

AT- MICROSOFT PROJECT DESKTOP

Microsoft Project lessons may include:
• Interface
• Project setup
• Project calendars
• Task calendars
• Resource calendars
• Work Breakdown Structures
• Summary tasks
• Milestones
• Task modes
• Durations
• Dependencies
• Leads
• Lags
• Constraints
• Deadlines
• Critical path
• Slack
• Baselines
• Interim plans awareness
• Resources
• Work
• Units
• Costs
• Resource levelling
• Assignments
• Tracking
• Actuals
• Remaining work
• Physical percentage complete
• Earned-value fields
• Custom fields
• Formulas
• Indicators
• Filters
• Groups
• Views
• Tables
• Gantt formatting
• Timelines
• Reports
• Master-project awareness
• Subprojects
• Resource pools awareness
• Import and export
• Schedule troubleshooting

AU- MICROSOFT PROJECT PLANNING AND BASELINING

You may learn how to:
• Establish project information
• Create calendars
• Build the WBS
• Enter tasks and milestones
• Define dependencies
• Estimate durations
• Assign resources
• Resolve overallocations
• Review critical paths
• Add costs
• Set the baseline
• Create custom views
• Prepare timelines
• Produce management reports
• Validate schedule logic before accepting software-calculated dates

AV- MICROSOFT PROJECT TRACKING AND REPORTING

Lessons may include:
• Status date
• Actual starts
• Actual finishes
• Actual duration
• Remaining duration
• Actual work
• Remaining work
• Percentage complete
• Physical percentage complete
• Actual cost
• Forecast cost
• Baseline comparison
• Tracking Gantt
• Variance tables
• Critical tasks
• Slippage
• Resource performance
• Earned-value fields
• Custom indicators
• Dashboards
• Export to Excel
• Progress reports
• Recovery updates

AW- MICROSOFT PLANNER

Microsoft Planner and premium project capabilities may include:
• Plans
• Tasks
• Buckets
• Boards
• Grids
• Timelines
• Dependencies
• Milestones
• Assignments
• Due dates
• Checklists
• Attachments
• Comments
• Labels
• Priorities
• Goals
• Sprints awareness
• People views
• Portfolios
• Baselines where available
• Premium scheduling capabilities
• Teams integration
• Notifications
• Collaboration
• Reporting
• Copilot awareness
• Transition from retired Project-for-the-web workflows
• Recognizing the distinction between collaborative task management and rigorous Critical Path Method scheduling

AX- MICROSOFT TEAMS, SHAREPOINT, AND POWER PLATFORM

Lessons may include:
• Microsoft Teams channels
• Meetings
• Files
• Project collaboration
• Planner integration
• SharePoint sites
• Document libraries
• Metadata
• Permissions
• Version history
• Lists
• Issue registers
• Risk registers
• Change registers
• Approval workflows
• Power Automate
• Notifications
• Reminders
• Approval routing
• Data integration
• Power BI project dashboards
• Power Apps awareness
• Maintaining controlled information while supporting collaboration

AY- AGILE FOUNDATIONS

Lessons may include:
• Agile values
• Agile principles
• Iterative development
• Incremental delivery
• Customer collaboration
• Feedback
• Adaptability
• Transparency
• Inspection
• Adaptation
• Self-managing teams
• Delivering value frequently
• Technical excellence
• Sustainable pace
• Simplicity
• Learning
• Distinguishing Agile principles from lack of planning or documentation

AZ- SCRUM

Scrum lessons may include:
• Empiricism
• Transparency
• Inspection
• Adaptation
• Commitment
• Focus
• Openness
• Respect
• Courage
• Product Owner
• Scrum Master
• Developers
• Product Goal
• Product Backlog
• Sprint Goal
• Sprint Backlog
• Increment
• Definition of Done
• Sprint
• Sprint Planning
• Daily Scrum
• Sprint Review
• Sprint Retrospective
• Refinement
• Self-management
• Cross-functionality
• Value
• Avoiding project-manager command-and-control behaviour within Scrum teams
• Distinguishing Scrum accountability from traditional job titles

BA- AGILE PRODUCT AND DELIVERY PLANNING

Lessons may include:
• Product vision
• Product goals
• Roadmaps
• Themes
• Epics
• Features
• Capabilities
• User stories
• Acceptance criteria
• Definition of Ready awareness
• Definition of Done
• Story mapping
• Backlog prioritization
• Relative estimation
• Story points
• Planning Poker
• Affinity estimation
• Capacity
• Velocity
• Forecasting
• Sprint planning
• Release planning
• Minimum Viable Products
• Minimum Marketable Features
• Burnup charts
• Burndown charts
• Managing scope and uncertainty without creating false precision

BB- KANBAN AND FLOW MANAGEMENT

Lessons may include:
• Visualizing work
• Workflow states
• Work-item types
• Explicit policies
• Work-in-progress limits
• Pull systems
• Bottlenecks
• Queues
• Blocked work
• Lead time
• Cycle time
• Throughput
• Work-item age
• Cumulative-flow diagrams
• Flow efficiency
• Service-level expectations
• Classes of service
• Replenishment
• Delivery reviews
• Operations reviews
• Continuous improvement
• Avoiding excessive multitasking and uncontrolled work initiation

BC- LEAN AND CONTINUOUS IMPROVEMENT

Lessons may include:
• Value
• Value streams
• Flow
• Pull
• Waste
• Waiting
• Rework
• Excess inventory
• Overprocessing
• Unnecessary movement
• Unused talent
• Continuous improvement
• Kaizen
• Standard work
• Visual management
• Root-cause analysis
• Value-stream mapping foundations
• Integrating Lean concepts with project and operational delivery

BD- HYBRID PROJECT DELIVERY

Lessons may include:
• Predictive governance
• Stage gates
• Contractual milestones
• Cost baselines
• Regulatory requirements
• Iterative discovery
• Rolling-wave planning
• Agile teams
• Incremental delivery
• Feedback loops
• Adaptive scope
• Integration points
• Release plans
• Dependency management
• Portfolio reporting
• Selecting predictive, Agile, or hybrid approaches according to risk, uncertainty, product type, contract, compliance, and organizational capability
• Avoiding superficial hybrid models that combine terminology without integrating decisions

BE- JIRA

Jira lessons may include:
• Sites
• Projects or spaces
• Work types
• Issues or work items
• Tasks
• Stories
• Bugs
• Epics
• Subtasks
• Workflows
• Statuses
• Transitions
• Fields
• Screens
• Boards
• Scrum boards
• Kanban boards
• Backlogs
• Sprints
• Versions
• Releases
• Components
• Labels
• Priorities
• Dependencies
• Issue links
• Hierarchies
• Automation
• Filters
• JQL
• Dashboards
• Gadgets
• Permissions
• Notifications
• Reports
• Configuration
• Company-managed and team-managed project awareness
• Maintaining usable workflows rather than creating unnecessary administrative complexity

BF- JIRA BACKLOG AND SPRINT MANAGEMENT

Lessons may include:
• Product backlogs
• Prioritization
• Epics
• Stories
• Acceptance criteria
• Estimates
• Story points
• Versions
• Releases
• Sprint creation
• Sprint planning
• Capacity
• Work assignment
• Active sprints
• Board configuration
• Workflow status
• Blocked items
• Burndown
• Burnup
• Velocity
• Sprint reports
• Cumulative-flow diagrams
• Release tracking
• Refinement
• Avoiding data manipulation that makes team performance appear better than reality

BG- JIRA WORKFLOWS AND AUTOMATION

Lessons may include:
• Workflow design
• Statuses
• Transitions
• Conditions
• Validators
• Post functions awareness
• Screens
• Fields
• Schemes
• Issue types
• Automation triggers
• Conditions
• Branches
• Actions
• Notifications
• Assignment rules
• Scheduled rules
• Integrations
• Audit logs
• Testing
• Governance
• Avoiding automation that creates duplicate, conflicting, or invisible work

BH- JIRA FILTERS, JQL, DASHBOARDS, AND REPORTS

Lessons may include:
• Basic filters
• Advanced search
• JQL
• Fields
• Operators
• Functions
• Saved filters
• Shared filters
• Dashboard gadgets
• Workload views
• Created-versus-resolved charts
• Filter-results gadgets
• Sprint reports
• Burndown
• Burnup
• Velocity
• Cumulative flow
• Control charts
• Lead time
• Cycle time
• Release reports
• Tailoring dashboards to management, product, team, and portfolio audiences

BI- CONFLUENCE

Confluence lessons may include:
• Spaces
• Pages
• Templates
• Page trees
• Project documentation
• Requirements
• Decision records
• Meeting notes
• Status reports
• Plans
• Retrospectives
• Lessons learned
• Knowledge bases
• Links to Jira work
• Macros
• Tables
• Page properties
• Page-properties reports
• Permissions
• Version history
• Comments
• Collaborative editing
• Maintaining a usable knowledge system rather than creating disconnected documents

BJ- OTHER PROJECT AND WORK-MANAGEMENT PLATFORMS

When required by the learner’s workplace, lessons may include:
• Monday.com
• Asana
• Smartsheet
• Wrike
• Trello
• Azure DevOps
• ClickUp awareness
• Boards
• Tasks
• Dependencies
• Automations
• Forms
• Dashboards
• Workloads
• Portfolios
• Approvals
• Collaboration
• Templates
• Reporting
• Maintaining transferable project-management logic rather than memorizing isolated interface operations

BK- PROGRAM MANAGEMENT

Lessons may include:
• Programs
• Component projects
• Related operational work
• Program vision
• Program roadmaps
• Interdependencies
• Governance
• Benefits
• Benefit owners
• Program tranches
• Waves
• Transition
• Shared stakeholders
• Common risks
• Resource conflicts
• Program schedules
• Program budgets
• Program performance
• Change
• Strategic outcomes
• Coordinating components that cannot be managed effectively as isolated projects

BL- PORTFOLIO MANAGEMENT

Lessons may include:
• Portfolios
• Strategic alignment
• Categories
• Evaluation criteria
• Prioritization
• Selection
• Authorization
• Balancing
• Capacity
• Funding
• Portfolio risk
• Benefits
• Dependencies
• Governance
• Performance
• Portfolio dashboards
• Scenario analysis
• Resource allocation
• Demand management
• Rebalancing
• Suspending or terminating initiatives
• Avoiding the assumption that every proposed project should be approved

BM- PROJECT MANAGEMENT OFFICES

PMO topics may include:
• Supportive PMOs
• Controlling PMOs
• Directive PMOs
• Enterprise PMOs
• Program offices
• Project offices
• Governance
• Standards
• Templates
• Methodologies
• Training
• Coaching
• Assurance
• Audits
• Reporting
• Portfolio support
• Resource coordination
• Knowledge management
• Maturity
• Lessons learned
• Tools administration
• Demonstrating PMO value
• Avoiding bureaucracy that adds reporting effort without improving decisions

BN- PROJECT-MANAGEMENT MATURITY

Lessons may include:
• Process consistency
• Governance maturity
• Planning maturity
• Controls maturity
• Risk maturity
• Resource maturity
• Benefits maturity
• Portfolio maturity
• Data quality
• Lessons learned
• Competency development
• Tool integration
• Standardization
• Tailoring
• Continuous improvement
• Assessing present capability
• Defining realistic improvement roadmaps

BO- SUSTAINABILITY IN PROJECT MANAGEMENT

Lessons may include:
• Environmental objectives
• Social objectives
• Economic objectives
• Lifecycle thinking
• Carbon awareness
• Energy
• Materials
• Waste
• Resilience
• Climate risks
• Sustainable procurement
• Community impacts
• Accessibility
• Equity
• Regulatory requirements
• Stakeholder expectations
• Sustainability requirements
• Sustainability risks
• Trade-offs
• Benefit measurement
• Integrating sustainability into scope, design, cost, schedule, risk, procurement, governance, and decision making
• Avoiding unsupported sustainability claims

BP- RESPONSIBLE ARTIFICIAL INTELLIGENCE IN PROJECT MANAGEMENT

AI-assisted project-management lessons may include responsible use of tools for:
• Drafting plans
• Summarizing meetings
• Extracting actions
• Identifying preliminary risks
• Comparing scenarios
• Reviewing requirements
• Generating checklist candidates
• Drafting reports
• Organizing lessons learned
• Supporting schedule or cost-data interpretation
• Creating communication alternatives
• Preparing stakeholder questions
• Supporting document review

The responsible workflow includes:
• Verifying all generated outputs
• Protecting confidential project and client information
• Maintaining human accountability
• Checking assumptions
• Identifying bias
• Avoiding invented facts
• Avoiding false precision
• Testing formulas, calculations, and code
• Documenting important AI-supported decisions
• Following organizational policies
• Recognizing when AI should not be used
• Avoiding automatic delegation of managerial judgment

BQ- PMP EXAMINATION SUPPORT—JULY 2026 STRUCTURE

PMP-oriented conceptual preparation may be aligned with the July 2026 examination domains:
• People
• Process
• Business Environment
• Leadership
• Stakeholder engagement
• Team performance
• Predictive delivery
• Agile delivery
• Hybrid delivery
• Project controls
• Risk
• Quality
• Procurement
• Governance
• Benefits
• Outcomes
• Business impact
• Artificial Intelligence
• Sustainability
• Scenario-based decision making
• Value delivery
• Tailoring
• Ethical and professional responsibility

Preparation may include:
• Concept review
• Domain mapping
• Scenario interpretation
• Elimination of weak answer choices
• Selecting the best managerial action
• Time-management strategies
• Practice-question analysis
• Identifying why plausible answers may still be incorrect
• Reviewing current eligibility and examination requirements before establishing a preparation plan
• Maintaining clear wording that the service is not official PMI-authorized training unless such status is separately established

BR- OTHER CERTIFICATION PATHWAYS

When the current syllabus and eligibility requirements have been reviewed in advance, lessons may support conceptual preparation for:
• CAPM
• PMI-ACP
• PMI-SP
• PMI-RMP
• PRINCE2
• Scrum certifications
• Agile certifications
• Primavera-related assessments
• Microsoft project-management tools
• Other agreed project-management curricula
• Focusing on genuine understanding rather than memorization of terminology

BS- PROJECT DASHBOARDS USING EXCEL AND POWER BI

Lessons may include:
• Project data structures
• Progress tables
• Milestones
• Schedule variance
• Cost variance
• Earned Value
• Resource information
• Risks
• Issues
• Changes
• Procurement status
• S-curves
• Trend charts
• Heat maps
• Look-ahead dashboards
• Executive summaries
• Portfolio dashboards
• Filters
• Drill-down
• Data refresh
• Power Query awareness
• Data validation
• Ensuring that dashboards reflect reliable source information
• Maintaining detailed Power BI instruction within the dedicated Data Analysis advertisement

BT- END-TO-END PROJECT SIMULATIONS

Projects may progress through:

**Business need → business case → charter → governance → stakeholder analysis → requirements → scope → Work Breakdown Structure → schedule → resources → cost → risk → procurement → delivery → monitoring → change → recovery → transition → closeout → benefits review**

Possible project simulations may include:
• Engineering projects
• Construction projects
• Information-technology projects
• Software projects
• Data projects
• Research projects
• Organizational-change projects
• Product-development projects
• Public-sector projects
• Education projects
• Healthcare projects
• Startup projects
• Process-improvement projects
• Another agreed project appropriate to the learner’s professional field

BU- ACADEMIC AND UNIVERSITY SUPPORT

Lessons may be based on:
• Course syllabi
• Assignments
• Case studies
• Group projects
• Capstone projects
• Research projects
• Project-management simulations
• Scheduling exercises
• Primavera P6 exercises
• Microsoft Project exercises
• Jira exercises
• Agile assignments
• Risk exercises
• Earned Value calculations
• Presentations
• Reports
• Examination preparation

Support is provided through explanation, demonstration, review, questioning, and guided correction. I help learners understand and improve their own work rather than replace their academic responsibility.

BV- PROFESSIONAL PROJECT SUPPORT

Professional guidance may include:
• Reviewing existing plans
• Correcting schedules
• Improving Work Breakdown Structures
• Establishing project controls
• Developing reporting structures
• Building RAID registers
• Improving progress measurement
• Reviewing resource plans
• Creating dashboards
• Clarifying governance
• Improving stakeholder communication
• Preparing recovery plans
• Structuring Jira or Planner workflows
• Developing P6 or Microsoft Project templates
• Organizing project records
• Improving repeatable organizational practices

BW- PROJECT TROUBLESHOOTING AND FILE RESCUE

I can help diagnose:
• Weak business cases
• Unclear objectives
• Uncontrolled scope
• Missing requirements
• Poor Work Breakdown Structures
• Disconnected activities
• Broken logic
• Excessive constraints
• Negative float
• Incorrect calendars
• Unrealistic durations
• Resource overallocations
• Baseline problems
• Invalid progress
• Incorrect Earned Value
• Inconsistent cost data
• Unmanaged risks
• Ineffective dashboards
• Unclear stakeholder responsibilities
• Uncontrolled changes
• Weak governance
• Primavera P6 errors
• XER import problems
• Microsoft Project calculation problems
• Jira workflow problems
• Automation conflicts
• Inaccurate reports
• Delayed approvals
• Disorganized project records

The objective is not merely to repair the immediate file or report, but to identify the root cause and establish a more reliable delivery and control system.

BX- PROJECT-MANAGEMENT QUALITY ASSURANCE

Quality review may include:
• Strategic alignment
• Objectives
• Benefits
• Governance
• Requirements
• Scope
• WBS quality
• Schedule logic
• Critical path
• Float
• Constraints
• Calendars
• Durations
• Resources
• Costs
• Risk
• Procurement
• Baselines
• Progress rules
• Earned Value
• Forecasts
• Changes
• Reporting
• Stakeholder engagement
• Quality criteria
• Document control
• Data integrity
• Software configuration
• Lessons learned
• Closeout readiness
• Benefits-transition readiness
• Completeness and reliability of final deliverables

BY- LESSON STRUCTURE

A lesson may include:
• A diagnostic review
• Explanation of the project-management principle
• Analysis of a project scenario
• Live software demonstration
• Guided planning or control work
• Independent application
• Schedule, dashboard, register, or document inspection
• Troubleshooting
• Decision analysis
• Quality review
• Workflow improvement
• A concise summary
• Recommended next steps

BZ- POSSIBLE LESSON DELIVERABLES

When useful, you may receive:
• Project-charter templates
• Business-case structures
• Benefit profiles
• Governance maps
• Stakeholder registers
• Communication plans
• Requirement matrices
• Scope statements
• Work Breakdown Structures
• WBS dictionaries
• Responsibility Assignment Matrices
• Primavera P6 files
• Microsoft Project files
• Microsoft Planner plans
• Jira boards
• Confluence structures
• Schedule-quality checklists
• Resource plans
• Cost estimates
• Cost baselines
• Earned-value templates
• Risk registers
• Quantitative-risk models
• RAID logs
• Procurement plans
• Change logs
• Decision logs
• Dashboards
• Progress-report templates
• Recovery plans
• Lessons-learned registers
• Closeout checklists
• Structured project-improvement plans

By prior agreement, an online lesson may be recorded for the learner’s personal review, subject to confidentiality, institutional rules, employer policies, and project-permission requirements.

CA- PROJECT-MANAGEMENT PORTFOLIO DEVELOPMENT

Professionals and career-transition learners may develop a portfolio containing:
• Project charters
• Business-case summaries
• Stakeholder analyses
• Work Breakdown Structures
• Schedule models
• Primavera P6 examples
• Microsoft Project examples
• Agile backlogs
• Jira boards
• Kanban systems
• Risk registers
• Earned-value reports
• Project dashboards
• Recovery plans
• Governance structures
• Lessons-learned reports
• Concise case studies
• Clear descriptions of the individual’s actual responsibilities, decisions, and contributions
• Protection of confidential employer and client information

CB- LONG-TERM LEARNING PATHWAY

For ongoing instruction, we can:
• Follow a structured project-management curriculum
• Monitor conceptual and software mastery
• Develop complete project simulations
• Build Primavera P6, Microsoft Project, Planner, Jira, and reporting competence
• Review recurring planning and control errors
• Develop leadership and stakeholder skills
• Improve risk and commercial awareness
• Develop reusable templates and standards
• Build a project-management portfolio
• Prepare for current certification objectives
• Progress from guided tools and methods to independent project judgment
• Develop the ability to explain and defend important project decisions

My objective is not merely to help you build one schedule, pass one examination, or complete one project-management assignment. It is to help you understand value, governance, scope, schedule, resources, cost, risk, contracts, people, change, and project controls as one integrated management system.

Whether you are learning project management for the first time, completing a university course, developing a Primavera P6 or Microsoft Project schedule, configuring Jira, adopting Agile methods, preparing for the updated PMP examination, recovering a delayed project, creating executive dashboards, or strengthening your professional project-delivery capabilities, every lesson will be structured around your actual objective.

You may choose either a brief free Zoom consultation to discuss your needs and establish an appropriate project-management learning plan—with no booking or payment required—or begin tutoring immediately if your objectives, documents, software, and project requirements are already clear.

See more

Rates

Rate

  • $30

Pack rates

  • 5 h: $150
  • 10 h: $300

online

  • $30/h

travel fee

  • + $10

free lessons

This first lesson offered with Ammar will allow you to get to know each other and clearly specify your needs for your next lessons.

  • 1hrs

Details

Getting started: You may begin directly with a paid tutoring session when the topic and objective are already clear. If you prefer to discuss your needs first, we can have a brief free Zoom meeting - together with a parent or guardian when relevant - to clarify the level, goals, and best learning plan. No booking or payment is required for this introductory meeting;

Ammar's Video

Other tutors in Human Resources

  • Evodie

    Montréal & online

    New
    • $18/h
    • 1st lesson free
  • Madeline

    Montreal & online

    New
    • $48/h
    • 1st lesson free
  • Shiva

    Toronto & online

    5 (13 reviews)
    • $56/h
  • Pierre Richard

    Gatineau & online

    5 (6 reviews)
    • $40/h
    • 1st lesson free
  • Najeebullah

    Surrey & online

    5 (9 reviews)
    • $40/h
    • 1st lesson free
  • Mehak

    Brantford & online

    5 (5 reviews)
    • $38/h
    • 1st lesson free
  • Raman

    Surrey & online

    5 (7 reviews)
    • $35/h
    • 1st lesson free
  • Trisha

    Moncton & online

    5 (9 reviews)
    • $45/h
  • Mostafa

    Calgary & online

    4.7 (3 reviews)
    • $35/h
    • 1st lesson free
  • Sana

    Mississauga & online

    4.2 (5 reviews)
    • $45/h
    • 1st lesson free
  • Adrian

    Toronto & online

    5 (2 reviews)
    • $70/h
    • 1st lesson free
  • Sandra

    Niagara-on-the-Lake & online

    5 (1 reviews)
    • $75/h
    • 1st lesson free
  • Clinton

    Vancouver & online

    5 (1 reviews)
    • $50/h
    • 1st lesson free
  • Nicholas

    Edmonton & online

    5 (4 reviews)
    • $70/h
    • 1st lesson free
  • Mohinur

    Peterborough & online

    5 (1 reviews)
    • $20/h
    • 1st lesson free
  • Prachi

    Barrie & online

    5 (4 reviews)
    • $28/h
    • 1st lesson free
  • Tooba

    Toronto & online

    5 (1 reviews)
    • $30/h
    • 1st lesson free
  • Christina

    Toronto & online

    New
    • $45/h
    • 1st lesson free
  • Anmol

    Winnipeg & online

    New
    • $18/h
    • 1st lesson free
  • Chitra

    Brampton

    New
    • $16/h
    • 1st lesson free
  • More Human Resources tutors