Understanding Project Management Frameworks

Understanding Project Management Frameworks

Theory of Constraints (TOC) Overview and Timeline History

The Theory of Constraints (TOC) is a management philosophy introduced by Dr. Eliyahu M. Goldratt in his 1984 bestselling business novel, The Goal

At its core, TOC operates on a simple premise: A chain is only as strong as its weakest link. In any complex system—be it a manufacturing plant, a hospital, or a software team—there is always one specific constraint (bottleneck) that limits the system from achieving more of its goal. If you improve anything other than that constraint, you are wasting your time. 

The Five Focusing Steps

TOC uses a rigorous five-step process for continuous improvement: 

  1. Identify the constraint.
  2. Exploit the constraint (ensure it doesn’t waste time).
  3. Subordinate everything else (align the whole system to support the constraint).
  4. Elevate the constraint (invest in more capacity if steps 2 and 3 weren’t enough).
  5. Repeat (prevent inertia; find the next bottleneck). 

Annotated Timeline of TOC Evolution

  • 1979 – Optimized Production Technology (OPT): Goldratt introduces OPT, a scheduling software that challenged traditional cost accounting by focusing on throughput.
  • 1984 – The Goal Published: Goldratt pivots from software to education. He uses a fictional story to introduce the Drum-Buffer-Rope (DBR) method and the concept of “Throughput Accounting.”
  • 1990 – The Haystack Syndrome: This marks the shift toward formalising TOC metrics: Throughput (money coming in), Inventory (money stuck inside), and Operating Expense (money going out).
  • 1994 – It’s Not Luck: Goldratt introduces the Thinking Processes (TP)—a set of logical tools (like the Current Reality Tree) used to solve complex problems and overcome resistance to change.
  • 1997 – Critical Chain: TOC is applied to Project Management. This introduced “buffers” at the end of project paths rather than individual tasks, drastically reducing project durations.
  • 2003 – Strategy & Tactic (S&T) Trees: A framework developed to synchronise large-scale organisational change, ensuring every action aligns with the ultimate goal.
  • 2000s–Present – Throughput Economics: Integration of TOC with Lean and Six Sigma (often called TLS) becomes the gold standard for high-performance manufacturing. 

Theory of Constraints (TOC) Overview and Timeline History

Project Management, Pre-Contract vs Post- Contract Phase

Project Management, Pre-Contract vs Post- Contract Phase

Project Management, Servant Leadership

Project Management, Servant Leadership

Critical Chain Project Management (CCPM) Overview and Timeline

Critical Chain Project Management (CCPM) represents a paradigm shift in how timelines are managed, moving away from traditional task-based safety to system-wide buffers. Its history is deeply rooted in the Theory of Constraints (TOC) and evolved through four primary eras of modern project management

The Foundations: Pre-1958 

Before the formal creation of CCPM, the industry relied on “craft-based” approaches and the early Gantt Chart (1910s) to visualize task durations. During this era, projects like the Hoover Dam (1931) and the Manhattan Project proved that large-scale coordination was possible, but they lacked a systematic way to handle resource constraints or project-wide uncertainty. 

The Traditional Era: 1958 – 1979 

This period saw the birth of the “Critical Path,” the ancestor of the “Critical Chain.” 

  • 1957: The Critical Path Method (CPM) was invented by the DuPont Corporation to manage chemical plant maintenance.
  • 1958: The Program Evaluation Review Technique (PERT) was developed for the U.S. Navy’s Polaris Project, introducing probabilistic task durations.
  • The Limitation: While these methods identified the longest sequence of tasks, they often ignored resource availability, leading to frequent delays and “multitasking” inefficiencies. 

The Conceptual Era: 1980 – 1994 

The theoretical seeds for CCPM were planted during the rise of the personal computer and the introduction of a new management philosophy.

  • 1984: Dr Eliyahu M. Goldratt published his seminal business novel, The Goal, introducing the Theory of Constraints (TOC).
  • Core Principle: Goldratt argued that every system has at least one constraint that limits its output. Managing this “bottleneck” is the key to overall performance.
  • Focus Shift: Organizations began looking at “flow” rather than just individual task completion. 

The CCPM Era: 1995 – Present 

CCPM was formally introduced as a distinct methodology to address the failures of traditional CPM. 

  • 1997: Goldratt published the book “Critical Chain”, officially launching the method.
  • Key Innovations: Unlike CPM, the Critical Chain accounts for both task dependencies and resource constraints. It replaced individual task “safety margins” with:
    • Project Buffers: A collective time safety net placed at the end of the project.
    • Feeding Buffers: Placed where non-critical tasks feed into the critical chain to prevent delays.
    • Fever Charts: A new visual tool for tracking buffer consumption rather than just task deadlines.
  • Modern Integration: In the 21st century, CCPM has been integrated with Agile and Lean practices to help organizations manage multi-project pipelines and global resource pools. 

Critical Chain Project Management (CCPM) timelines differ from traditional methods by shifting safety margins from individual tasks to strategic buffers at the end of the project or at integration points. This approach accounts for both task dependencies and resource constraints to determine the “Critical Chain”—the true longest path in a project. 

Core Components of a CCPM Timeline

  • The Critical Chain: The longest sequence of dependent tasks, adjusted for resource availability.
  • Aggressive Task Estimates: Tasks are estimated at a 50% confidence level (how long it takes if things go well) rather than the traditional 90% (safe) estimate.
  • Project Buffer: A single aggregate buffer placed at the very end of the project to protect the final delivery date.
  • Feeding Buffers: Placed at points where non-critical task sequences (feeding chains) merge into the critical chain, preventing delays in minor tasks from affecting the main timeline.
  • Resource Buffers: Virtual markers or alerts placed before critical tasks to ensure that key resources (people or equipment) are ready to start exactly when needed.
CCPM versus Traditional Timeline (CPM)

Implementing a CCPM Timeline

  1. Identify the Critical Path: Map the logical sequence of tasks.
  2. Level Resources: Adjust the schedule so no single resource is over-allocated, transforming the path into a Critical Chain.
  3. Strip Task Padding: Reduce task durations by roughly 50% to eliminate “Student Syndrome” (procrastinating until the last minute).
  4. Insert Buffers: Add a Project Buffer (typically 50% of the chain’s length) at the end and Feeding Buffers where non-critical paths merge.
  5. Monitor via Fever Chart: Use a Fever Chart to track if the buffer is being consumed faster than tasks are being completed.

Critical Chain Project Management (CCPM) Overview and Timeline

Critical Path Method CPM Overview and Timeline by year

The Critical Path Method (CPM) is a mathematical algorithm used for scheduling a set of project activities. It identifies the longest sequence of dependent tasks required to complete a project, which in turn determines the shortest possible duration to finish it. 

Timeline of the Critical Path Method

The evolution of CPM is categorised into four primary eras, moving from manual mathematical foundations to modern AI-driven automation. 

1. Pre-Formalisation Era (1940s – Early 1950s) 

  • 1940–1943: DuPont develops precursor techniques for scheduling that are applied to the Manhattan Project.
  • Early 1950s: Growing complexity in industrial plants leads to “scheduling crises,” where traditional Gantt charts are no longer sufficient for managing thousands of interdependent tasks. 

2. The Development & Mainframe Era (1956 – 1969)

  • 1956: Morgan R. Walker of DuPont and James E. Kelley Jr. of Remington Rand begin collaborative research to improve plant maintenance scheduling.
  • 1957–1958: The duo formalises the Critical Path Method (CPM).
  • 1958: The U.S. Navy and Booz Allen Hamilton develop the Program Evaluation and Review Technique (PERT) for the Polaris missile program; it is from this project that the term “critical path” is actually coined.
  • 1959: The first computer-based CPM is implemented on a UNIVAC mainframe, allowing DuPont to reduce plant maintenance downtime from 125 to 78 hours.
  • 1966: CPM is used for the first time in a massive skyscraper project for the construction of the World Trade Center Twin Towers in New York City. 

3. The PC Revolution & Methodology Expansion (1970s – 1999) 

  • 1970s: Dedicated project management software companies like Oracle (then Software Development Laboratories) begin to emerge.
  • 1984: Eliyahu M. Goldratt introduces the Theory of Constraints (TOC), which later influences the development of the Critical Chain.
  • 1980s: The advent of the Personal Computer (PC) makes CPM accessible to smaller companies, moving it away from expensive, bulky mainframes.
  • 1997: Eliyahu M. Goldratt introduces Critical Chain Project Management (CCPM), a more sophisticated evolution of CPM that accounts for resource constraints and buffers. 

4. Modern Era: Digital Integration & AI (2000 – Present) 

  • 2000s–2010s: CPM becomes a standard feature in cloud-based tools like AsanaWrike, and Microsoft Project, allowing for real-time schedule updates.
  • 2020: The COVID-19 pandemic accelerates the adoption of virtual project management tools, where CPM is used to manage remote, globally distributed teams.
  • 2025–Present: Artificial Intelligence is increasingly used to predict risks and automatically calculate “crashing” scenarios (reducing task duration to shorten the overall project) based on historical data.
Summary of Key CPM Concepts

Critical Path Method CPM Overview and Timeline by year

Project Scope vs Project Scope Statement in Project Management

Project Scope vs Project Scope Statement in Project Management

Program Evaluation and Review Technique (PERT) Timeline by era and year

The Program Evaluation and Review Technique (PERT) is a statistical project management tool designed to analyse and represent the tasks involved in completing a project. It is particularly effective for large-scale, complex, and non-routine initiatives—such as Research and Development (R&D)—where task durations are uncertain. 

Overview of PERT

  • Purpose: To identify the critical path and the minimum time required to complete a project.
  • Core Mechanism: Uses a three-point estimation method for each task:
    • Optimistic time (O): The shortest possible time.
    • Most likely time (M): The most realistic duration.
    • Pessimistic time (P): The longest time if major setbacks occur.
  • Formula: The Expected Time () is calculated as .
  • Visualisation: Tasks are represented as nodes (circles or rectangles) and dependencies as arrows.

Timeline History by Era

The history of PERT is defined by its transition from a secretive Cold War military tool to a foundational standard in global project management.

1. The Era of Inception (1956–1959)

This era was marked by the urgent need for a massive deterrent during the Cold War. 

  • 1956: The Polaris Project (Fleet Ballistic Missile program) began, facing the immense challenge of building nuclear-powered submarines capable of launching solid-propellant missiles.
  • 1958: PERT was officially developed by the U.S. Navy Special Projects Office, specifically by Charles E. Clark. It was initially called “Program Evaluation Research Task”.
  • 1958: Around the same time, the Critical Path Method (CPM) was independently developed by the DuPont Corporation.
  • 1959: The technique was renamed to “Program Evaluation and Review Technique”. 

2. The Era of Expansion & Mandates (1960–1975)

During this period, PERT moved from military use into government mandates and international visibility. 

  • 1960: The Polaris program, managed via PERT, achieved its first successful underwater launch and was completed 18 months to two years ahead of schedule.
  • 1962: The U.S. Department of Defense mandated the Work Breakdown Structure (WBS) as part of the PERT approach for all future projects of this size.
  • 1965–1968: One of the first large-scale civilian applications of PERT occurred during the planning of the Winter Olympic Games in Grenoble, France.
  • Late 1960s: PERT was adopted by major public programs globally, including the UK’s nuclear power programs and Sweden’s fighter jet development. 

3. The Era of Professionalization (1976–1999)

Project management began to coalesce into a formal academic and professional discipline. 

  • 1987: The Project Management Institute (PMI) published the first PMBOK Guide (Project Management Body of Knowledge), which included and standardised PERT and CPM concepts.
  • 1989Earned Value Management (EVM), which grew out of early PERT/Cost frameworks, became a mandatory part of U.S. government procurement.
  • 1998: The PMBOK Guide was recognised as a standard by the American National Standards Institute (ANSI). 

4. The Modern Era (2000–Present)

PERT has transitioned from hand-drawn charts to being integrated into digital ecosystems. 

  • 2000s: PERT concepts became core features in project management software (like Microsoft Project), where the math is often automated behind the user interface.
  • 2020s: Emerging trends include AI-enhanced estimations, where machine learning algorithms analyse historical project data to generate the optimistic, pessimistic, and most likely time estimates more accurately than human experts.

Program Evaluation and Review Technique (PERT) Timeline by era and year

Gantt Chart Detailed Timeline History by Era and Year

Henry Gantt (1861–1919) was an American mechanical engineer and management consultant who revolutionized project management by introducing visual tools to track work against time. A close associate of Frederick Taylor, he humanized “scientific management” by focusing on employee motivation and social responsibility alongside industrial efficiency. 

Gantt Chart in MS Project, templates can be downloaded at website banner link

Overview of Henry Gantt’s Contributions

  • The Gantt Chart: His most famous invention, a horizontal bar chart that illustrates a project schedule, including task durations and progress.
  • Task and Bonus System: A wage system that guaranteed a base rate but offered bonuses to workers who exceeded daily production goals.
  • Social Responsibility: He argued that businesses have a moral obligation to the welfare of the society in which they operate, not just to their owners.
  • Industrial Efficiency: He advocated for using scientific analysis to eliminate “chance and accidents” in manufacturing. 

Comprehensive Gantt Timeline History

Era 1: Pre-Gantt & Early Origins (1765–1896)

  • 1765: Joseph Priestley creates early timeline charts, which some consider the conceptual distant ancestors of the Gantt chart.
  • 1896: Polish engineer Karol Adamiecki develops the “Harmonogram,” a precursor that displayed interdependent processes. However, he published it only in Polish and Russian, limiting its global recognition. 

Era 2: The Henry Gantt Era (1903–1919)

  • 1903: Henry Gantt develops his first version of a production chart for the American Locomotive Company.
  • 1910–1915: Gantt refines and popularizes his chart through articles and his book Work, Wages and Profits (1910).
  • 1917–1918: At the request of General William Crozier, Gantt charts are used to manage massive military production for the U.S. during World War I.
  • 1919: Henry Gantt passes away. 

Era 3: Global Adoption & Infrastructure (1920s–1970s) 

  • 1922: Wallace Clark, a colleague of Gantt, publishes The Gantt Chart: A Working Tool of Management, leading to international adoption.
  • 1929: Walter Polakov introduces Gantt charts to the Soviet Union for their First Five Year Plan.
  • 1931–1936: Gantt charts are used on massive infrastructure projects like the Hoover Dam and later the U.S. Interstate highway system.
  • 1940s: Extensively used for logistics and military project management during World War II.
  • 1950s: Become a staple in the construction and engineering industries; the first digital predecessors like PERT and Critical Path Method (CPM) emerge. 

Era 4: The Digital Revolution (1980s–Present) 

  • 1980s: The advent of personal computers allows project managers to create and update charts without redrawing them by hand.
  • 1990s: Software like Microsoft Project adds “link lines” to display complex dependencies between tasks.
  • 2000s–2010s: Web-based and cloud-based applications (like Jira or Asana) integrate Gantt charts for real-time team collaboration.
  • Present: Modern tools use AI to automate chart maintenance and predict risks based on historical data.

Gantt Chart Detailed Timeline History by Era and Year

Budgeting vs Forecasting, Financial Concepts overview

Budgeting vs Forecasting, Financial Concepts overview

Project Management and Cost Control

Project Management and Cost Control

Rational Unified Process RUP Overview and Timeline History

The Rational Unified Process (RUP) timeline is a two-dimensional framework where the horizontal axis represents time (divided into phases and iterations) and the vertical axis represents work/activities (divided into disciplines)

Rational Unified Process, RUP

The process is structured into four sequential phases, each culminating in a major milestone where the project’s progress is assessed before moving forward. 

RUP Phases, Iterations and Workflows

RUP Project Phases and Milestones

Each phase of the RUP lifecycle has a specific objective and a corresponding milestone. 

  • Inception Phase
    • Goal: Define project scope, identify business risks, and establish the Business Case.
    • MilestoneLifecycle Objective Milestone – Stakeholders agree on scope and cost/schedule estimates.
  • Elaboration Phase
    • Goal: Analyze requirements in detail and design a stable Software Architecture.
    • MilestoneLifecycle Architecture Milestone – The architecture is validated and major risks are mitigated.
  • Construction Phase
    • Goal: Build the software system by developing and testing all components and features.
    • MilestoneInitial Operational Capability Milestone – A product is ready for beta testing by users.
  • Transition Phase
    • Goal: Deploy the software to the end users and perform final Beta Testing and training.
    • MilestoneProduct Release Milestone – The development cycle is finished and the product is formally accepted. 

Detailed Iteration Timeline

Within each phase, work is performed in iterations (typically lasting 2 to 6 weeks). Each iteration is a mini-lifecycle that includes: 

  1. Requirements Analysis: Refining what needs to be built.
  2. Design: Modeling the system architecture and components.
  3. Implementation: Writing the code for specific features.
  4. Testing: Verifying the quality of the iteration’s output.
  5. Assessment: Evaluating the iteration against its planned goals. 

Historical Development Timeline

  • 1988Objectory AB defines the core process.
  • 1995: Rational Software Corporation acquires Objectory.
  • 1998: RUP 5.0 is released, introducing UML integration.
  • 2003: IBM acquires Rational Software.
  • 2012: RUP is largely succeeded by Disciplined Agile Delivery (DAD) and SAFe.

Rational Unified Process RUP Overview and Timeline History

A Practical Guide to the Rational Unified Process RUP

Setting up effective meetings

Setting up effective meetings

ISO 9001 Quality Assurance Detailed Timeline History by year

ISO 9001 is founded on seven core Quality Management Principles (QMPs) designed to guide organisations toward improved performance and consistent quality. Its history is a progression from rigid, procedure-heavy military-style standards to flexible, risk-based management systems. 

Core Principles of ISO 9001:2015

These seven principles form the foundation of the current standard: 

  • Customer Focus: Meeting and exceeding customer expectations is the primary focus to drive loyalty and revenue.
  • Leadership: Leaders at all levels establish unity of purpose and direction, creating an environment where people are engaged.
  • Engagement of People: Competent, empowered, and engaged people across all levels are essential to enhance the organisation’s value.
  • Process Approach: Understanding activities as interrelated processes that function as a coherent system leads to more predictable results.
  • Improvement: A permanent objective of every successful organisation is the continual improvement of its performance.
  • Evidence-based Decision Making: Decisions based on the analysis and evaluation of data are more likely to produce desired results.
  • Relationship Management: Managing relationships with interested parties, such as suppliers and partners, optimizes their impact on performance. 

Detailed Timeline History

The evolution of ISO 9001 can be categorised into four distinct eras: 

1. The Pre-ISO Foundations (1950s – 1986)

  • 1959: US and UK military departments establish MIL-SPECS for procurement.
  • 1969NATO AQAP standards are introduced for defense industry mutual recognition.
  • 1971: The British Standards Institution (BSI) releases BS 9000 for the electronics industry.
  • 1979BS 5750 is published in the UK, becoming the first general-purpose quality management standard for industry. 

2. The Procedural & Quality Assurance Era (1987 – 1999)

  • 1987 (ISO 9001:1987): First international publication. Focused on quality assurance through procedural controls and final product inspections. Three models existed: 9001 (Design/Production), 9002 (Production), and 9003 (Inspection).
  • 1994 (ISO 9001:1994): First revision. Shifted focus toward preventative actions rather than just checking finished products. However, it remained “document-heavy,” often leading to excessive bureaucracy. 

3. The Process Management Era (2000 – 2014)

  • 2000 (ISO 9001:2000): A major overhaul. Consolidated ISO 9001, 9002, and 9003 into a single standard. Introduced the Process Approach and the original eight Quality Management Principles.
  • 2008 (ISO 9001:2008): A minor update focusing on clarification and consistency with other standards like ISO 14001 (Environment). No new requirements were added. 

4. The Risk-Based & Strategy Era (2015 – Present)

  • 2015 (ISO 9001:2015): Introduced Risk-Based Thinking and the High-Level Structure (HLS) to ease integration with other management systems. It reduced prescriptive documentation requirements, focusing instead on organisational context and leadership accountability.
  • 2026 (Upcoming): The next major revision is currently under development (target: September 2026), expected to address digitalisation, sustainability (ESG), and climate change.

ISO 9001 Quality Assurance Detailed Timeline History by year

GDPR General Data Protection Regulation timeline history by year

The history of the General Data Protection Regulation (GDPR) spans several decades, evolving from early privacy concepts to a globally adopted gold standard for data protection. 

The Early Era: Foundations of Privacy (1890–1990) 

  • 1890: The “Right to Privacy” concept is first articulated in the USA by Warren and Brandeis.
  • 1950: The European Convention on Human Rights is established, protecting the right to respect for private and family life.
  • 1970: The German state of Hesse passes the world’s first data protection law.
  • 1973: Sweden enacts the first national Data Protection Act.
  • 1980: The OECD issues privacy principles to harmonise international data flows.
  • 1981Convention 108 is signed, becoming the first legally binding international treaty for data protection. 

The Directive Era: Pre-Internet Regulation (1995–2011) 

  • 1995: The EU adopts the Data Protection Directive (95/46/EC), setting minimum standards for member states.
  • 1998: The UK implements the directive through the Data Protection Act 1998.
  • 2000Safe Harbour Principles are developed to facilitate EU-US data transfers.
  • 2009: The European Commission launches a public consultation on data protection reform. 

The Development Era: Crafting the GDPR (2012–2015) 

  • 2012: The European Commission releases the first proposal for the GDPR.
  • 2014: The European Parliament votes overwhelmingly in favour of the draft regulation (621 to 10).
  • 2015: Formal “Trilogue” negotiations between the Parliament, Council, and Commission reach a final agreement.
  • 2015 (Oct): The European Court of Justice invalidates the Safe Harbour agreement in the Schrems I case. 

The Enforcement Era: Implementation and Fines (2016–2020)

  • 2016 (Apr): The GDPR is officially adopted by the European Parliament and Council.
  • 2016 (May): The regulation enters into force, beginning a two-year grace period for compliance.
  • 2018 (May 25): The GDPR becomes fully enforceable across the EU.
  • 2019: Regulators begin issuing major fines, including a €50 million penalty against Google by France’s CNIL.
  • 2020: The Schrems II ruling invalidates the EU-US Privacy Shield, causing uncertainty for international transfers. 

The Modern Era: Brexit and AI Evolution (2021–Present) 

  • 2021 (Jan): Post-Brexit, the UK GDPR and Data Protection Act 2018 take full effect as domestic law in the UK.
  • 2022: The EU Data Governance Act enters into force.
  • 2023: Italy’s regulator temporarily bans ChatGPT over GDPR concerns, highlighting the regulation’s role in governing AI.
  • 2024–2026: Expansion of GDPR-style laws globally and the introduction of the EU AI Act to complement data protection rules. 

GDPR General Data Protection Regulation timeline history by year

IT Career snapshot of Mark Whitfield, Senior IT Project Manager (SC cleared)

This resume summarizes the career of Mark Whitfield, a Senior IT Project Manager with over 30 years of experience specializing in digital and software development lifecycles, cloud migrations, and HP NonStop systems

Personal Details

  • Name: Mark A. Whitfield
  • Location: Manchester, UK
  • Nationality: British
  • Security Clearance: SC Cleared to 2031
  • Professional Profiles: Official Website | LinkedIn Profile 

Executive Summary

  • Experience: 30+ years in IT.
  • Core Focus: Senior Project Management for Digital/ Software Development Lifecycles (SDLC).
  • Expertise: Transitioning from a technical background in programming (pre-2000) to senior leadership in large-scale projects for global blue-chip companies. 

Key Skills & Competencies

  • Methodologies: PRINCE2 Practitioner, Agile (Scrum/ Kanban), Waterfall, ITIL, ISO QA.
  • Project Controls: MS Project, Budget & Burn Tracking, GDPR compliance, Supplier & Stakeholder Management, Statement of Work (SoW).
  • Technical Proficiencies:
    • Platforms: HP NonStop (Tandem), Cloud Migration (Hybrid).
    • Languages (Historical): C/C++, Java, COBOL85, TAL, TACL, SCOBOL, SQL, MS SQL.
    • Utilities: PATHWAY, SCF, FUP, INSPECT, XPNET. 

Professional Experience

  • Senior IT Project Manager (Various Projects):
    • Managed large-scale solutions for clients including Jaguar Land Rover (JLR)HeathrowRoyal Mail Group (RMG)NATS, and Euroclear.
    • Extensive work within the financial sector for Bank of EnglandBarclaysHSBCSantanderStandard CharteredDeutsche Bank, and Global Payments.
    • Government and public sector projects for DefraUKEFWelsh Water, and Scottish Water.
  • Early Career (Programmer / Technical Lead):
    • 1990 – 1995: Programmer at The Software Partnership (later Deluxe Data) in Runcorn, specializing in electronic banking software (sp/ARCHITECT-BANK) on Tandem Mainframe Computers. 

Education & Certifications

  • Degree: Higher National Diploma (HND) in Computing (Distinction, Graduated 1990).
  • Certifications:
    • Microsoft Azure Fundamentals (Certified).
    • PRINCE2 Practitioner.
    • Agile/ Radtac Course Completion. 

Agile Methodology Iceberg Overview

Agile Methodology Iceberg Overview

Stakeholders are key to Project Success

Stakeholders are key to Project Success

Essential Project Management Skills

Essential Project Management Skills

Evolution of Leadership – Culture, Team and Individual Focused

Evolution of Leadership – Culture, Team and Individual Focused