Author: Mark Whitfield

Welcome to my site! After graduating in Computing in 1990, I accepted a position as a programmer at a Runcorn based software house specialising in electronic banking software, namely sp/ARCHITECT-BANK on Tandem Computers (now HPE NonStop). This was before the internet became more prevalent and so the notion of enabling desktop access to company accounts for inter-account transfers and book keeping was still quite a cutting edge idea (and smartphones only ever hinted at in Space 1999). The company was called The Software Partnership (which was taken over by Deluxe Data in 1994). I spent 5 years in Runcorn developing code for SP/ARCHITECT for various banks like TSB, Bank of Scotland, Rabobank and Girofon (Denmark) to name but a few. I then moved onto a software house in Salford Quays for further bank facing projects. After a further 23 years in the IT industry and now a Senior IT Project Manager (both Agile and Waterfall delivery), I thought I would echo out my Career Profile in this corner of the internet for quick and easy access.

Benefits Realization Process is a structured framework

Benefits Realization Process

The benefits realization process is a structured framework used to ensure that projects and programmes deliver the tangible value and strategic outcomes intended by an organisation. Unlike traditional project management, which focuses on outputs (deliverables like a new software), benefits realization focuses on outcomes (the actual value derived, such as a 10% increase in efficiency). 

Core Stages of the Process

While various frameworks exist, most follow three or four primary stages:

  • 1. Identification: Defining the expected benefits at the start of a project. This involves aligning benefits with the organisation’s strategic goals and identifying “benefit owners” who will be accountable for their delivery.
  • 2. Planning: Developing a Benefits Realization Plan that establishes metrics, Key Performance Indicators (KPIs), and timelines for when benefits will be achieved.
  • 3. Execution & Delivery: Monitoring and managing the project to ensure it stays on track to deliver the planned benefits. This includes managing risks that could negatively impact benefit delivery.
  • 4. Sustainment & Review: Occurring post-project completion, this stage focuses on ensuring benefits are fully realized and sustained over the long term. A final review is conducted to compare actual results against the original business case. 

Key Components and Tools

  • Benefits Register: A central document used to track and manage all identified benefits, their owners, and their current status.
  • Benefit Profiles: Detailed records for individual benefits, describing what they are, how they will be measured, and who is responsible for them.
  • Benefit Dependency Map (BDM): A visual tool showing the links between project outputs, organizational changes, and final strategic objectives.
  • Benefit Owners: Individuals (usually from the business side) who are accountable for ensuring a specific benefit is achieved and sustained after the project team disbands. 

Why It Matters

Organizations that mature in benefits realization management are significantly more likely to meet their original goals and business intent. It bridges the gap between high-level strategy and tactical project execution, ensuring that investments translate into actual business value. 

Benefits Realization Process is a structured framework

Project Quality Plan PQP in QA/QC Overview

Project Quality Plan PQP in QA/QC Overview

The primary purpose of a Project Quality Plan (PQP) is to define the standards, tools, and processes required to ensure a project’s deliverables are “fit for purpose” and meet all stakeholder expectations. It serves as a strategic roadmap for the project team to maintain consistent quality throughout the project lifecycle rather than treating it as an afterthought. 

Core Objectives

A PQP is designed to achieve several critical goals: 

  • Define “Quality”: Translates vague stakeholder needs into measurable criteria and specific benchmarks.
  • Prevent Defects: Establishes Quality Assurance (QA) processes to proactively “build in” quality from the start, reducing the risk of errors.
  • Detect and Correct Issues: Outlines Quality Control (QC) activities, such as testing and inspections, to identify and fix defects before they reach the customer.
  • Clarify Accountability: Assigns specific roles and responsibilities so every team member knows who is responsible for performing, checking, and approving work.
  • Ensure Compliance: Guarantees the project adheres to relevant internal policies, legal regulations, and industry standards like ISO 9001. 

Strategic Benefits

Implementing a structured quality plan provides tangible advantages for project management: 

  • Reduced Costs and Rework: By catching errors early, the team avoids expensive last-minute fixes and wasted resources.
  • Improved Efficiency: Standardised workflows and clear metrics allow the team to focus on production rather than constant troubleshooting.
  • Increased Stakeholder Trust: Providing objective evidence through audits and reports gives sponsors and clients confidence in the final outcome.
  • Continuous Improvement: The plan often includes feedback loops and lessons-learned processes to refine and enhance quality for future project phases.

Project Quality Plan PQP in QA/QC Overview

Bangor Garth Pier into Menai Strait toward Anglesey, North Wales, UK

Bangor Garth Pier is a Grade II* listed Victorian landmark in North Wales, recognized as the second-longest pier in Wales and the ninth-longest in the British Isles. Stretching 1,500 feet (460m) into the Menai Strait, it is celebrated for its well-preserved architectural elegance and panoramic views of the Eryri (Snowdonia) mountains and Anglesey. 

Bangor Pier taken 15th March, 2026

Key Highlights

  • Award-Winning Heritage: It was named Pier of the Year 2022 by the National Piers Society for its successful community-led restoration and original Victorian charm.
  • Victorian Kiosks: The deck features a series of distinctive octagonal, onion-domed kiosks that house local independent businesses, including sweet shops, artisan crafts, and a gallery.
  • The Pavilion: At the pier-head stands a large domed pavilion housing a family-friendly café famous for its tea, coffee, and homemade scones.
  • Leisure & Wildlife: The pier is a popular spot for crabbing and fishing. Visitors can also spot local wildlife, including a colony of black guillemots often referred to as “Bangor Penguins”.

Bangor’s Garth Pier is a Grade II* listed structure stretching 1,500 feet (460m) into the Menai Strait toward Anglesey. It is the second-longest pier in Wales and is renowned for its well-preserved Victorian architecture, featuring original kiosks and ornamental ironwork. Unlike many other piers, it was never heavily modified with large theatres, retaining its elegant, traditional character. 

Bangor Pier, March 2026

Comprehensive Historical Timeline

The Early Origins (Pre-1896)

  • 1292: Records mention the Porthesgob ferry operated by the Bishop of Bangor, establishing the area as a key crossing point to Anglesey.
  • 1826: The principal crossing shifted to the new Menai Bridge, though the local Garth ferry continued operating for many years.
  • 1893: A Parliamentary Bill was passed to authorize the construction of a permanent pier. 

The Victorian Boom (1896–1914)

  • 1896 (May 14): Lord Penrhyn officially opened the pier. It was designed by JJ Webster and cost approximately £17,000.
  • 1896–1914: The pier thrived as a landing stage for pleasure steamers from Liverpool, Blackpool, and the Isle of Man. A 3-foot gauge tramway ran its length to transport passenger luggage.
  • 1914: The cargo ship SS Christiana broke free and crashed into the pier, severing a section of the structure. The baggage railway was subsequently removed. 

Transition & Decline (1915–1971)

  • 1921: Permanent repairs for the 1914 ship damage finally resumed following the conclusion of World War I.
  • 1927: Professor Phillip White established a small marine laboratory in one of the pier kiosks, eventually leading to Bangor University’s renowned marine science department.
  • 1939–1945: The pier remained a local landmark through WWII; historical photos show servicemen and locals using the structure.
  • 1960s: Lack of investment led to severe structural deterioration.
  • 1971: The pier was officially closed to the public on safety grounds. 

Threat of Demolition & Rescue (1974–1988) 

  • 1974: Ownership passed to Arfon Borough Council, which proposed demolishing the structure.
  • 1975–1978: Following public outcry, Bangor City Council purchased the pier for a symbolic fee of 1p.
  • 1982: A major six-year restoration project began, funded by the National Heritage Memorial Fund and the Manpower Services Commission.
  • 1983: The ongoing project won the Prince of Wales Award.
  • 1988 (May 7): The Marquess of Anglesey officially reopened the pier after a £3 million restoration. 

The Modern Era (2011–Present)

  • 2011: Surveys revealed new structural issues, specifically with the sub-structure.
  • 2017: A new £1 million restoration programme commenced to strengthen the structure and replace handrails.
  • 2021: The pier celebrated its 125th anniversary, and the Friends of Bangor Garth Pier volunteer group took over a kiosk to support further fundraising.
  • 2022: The National Piers Society named it Pier of the Year.
  • 2024: The pier head shelter, absent since 2018, began reconstruction in-situ.
  • 2026: The city plans to hold major celebrations for the pier’s 130th anniversary. 

Bangor Garth Pier into Menai Strait toward Anglesey, North Wales, UK

Llandudno Town Map, North Wales, UK, 15th March 2026

Llandudno Town Map, North Wales, UK

Technical Program Manager Roadmap

Technical Program Manager Roadmap

Agile Scrum Methodology Summary Breakdown Overview

Scrum is a lightweight framework within the broader Agile methodology used to manage complex work through iterative, incremental delivery. It organizes work into fixed-length cycles called sprints, typically lasting two to four weeks, to deliver a usable “increment” of value at the end of each cycle. 

Core Components (The 3-5-3 Structure)

The framework is built around three accountabilities, five events, and three artifacts. 

1. Three Accountabilities (Roles)

  • Product Owner: Represents the customer and stakeholders. They manage the Product Backlog and prioritize work to maximize the value delivered by the team.
  • Scrum Master: A servant leader who coaches the team on Scrum theory and removes impediments that block progress.
  • Developers: A cross-functional, self-managing team that does the actual work to create the product increment. 

2. Five Events (Ceremonies)

  • The Sprint: The container for all other events; a time-boxed period where work is performed.
  • Sprint Planning: The team defines what will be delivered in the sprint and how the work will be achieved.
  • Daily Scrum: A 15-minute daily check-in for developers to synchronize progress and plan the next 24 hours.
  • Sprint Review: Held at the end of the sprint to inspect the outcome with stakeholders and adapt the Product Backlog.
  • Sprint Retrospective: An internal team meeting to reflect on the process and identify improvements for the next sprint. 

3. Three Artifacts

  • Product Backlog: An ordered, evolving list of everything needed for the product.
  • Sprint Backlog: The subset of product backlog items selected for the current sprint, plus a plan for delivering them.
  • Increment: The concrete sum of all completed backlog items that meet the Definition of Done. 

The Three Pillars of Empiricism

Scrum is founded on empirical process control, which relies on: 

  1. Transparency: The process and work must be visible to everyone involved.
  2. Inspection: Frequent checks of artifacts and progress to detect variances.
  3. Adaptation: Adjusting the process or product if an inspection reveals unacceptable deviations. 

Key Values

Success with Scrum depends on the team’s commitment to five core values: Commitment, Courage, Focus, Openness, and Respect. 

Agile Scrum Methodology Summary Breakdown Overview

PRINCE2 Management Stages Overview

In PRINCE2, a project is managed through a series of management stages, which are discrete sections of a project that the Project Board authorises at specific decision points. Every PRINCE2 project must have at least two stages: an initiation stage and at least one further delivery stage. 

PRINCE2 Management Stages Overview

A detailed breakdown of these stages, aligned with the seven core PRINCE2 processes, is provided below. 

1. Starting Up a Project (SU)

This is a pre-project process designed to determine if the project is viable and worthwhile before committing significant resources. 

  • Key Activities:
    • Appointing the Executive and Project Manager.
    • Developing an Outline Business Case.
    • Creating a Project Brief which defines objectives and scope.
    • Planning the initiation stage itself. 

2. Initiating a Project (IP)

This represents the first management stage of the project. It establishes the firm foundation for the project’s execution. 

  • Key Activities:
    • Creating the Project Initiation Documentation (PID), which includes the full Business Case, Project Plan, and management strategies for risk, quality, and communication.
    • Setting up project controls and refining the project approach.
    • Securing formal approval from the Project Board to proceed. 

3. Directing a Project (DP)

This is an ongoing process that spans the entire project lifecycle, focusing on high-level decision-making by the Project Board. 

  • Key Activities:
    • Authorising the project to start and approving each subsequent stage.
    • Giving ad hoc direction and advice to the Project Manager.
    • Making the final “stop/proceed” decisions at stage boundaries.

4. Controlling a Stage (CS)

This covers the day-to-day management of each delivery stage by the Project Manager. 

  • Key Activities:
    • Assigning work to teams via Work Packages.
    • Monitoring progress and managing risks and issues.
    • Reporting status to the Project Board through Highlight Reports. 

5. Managing Product Delivery (MP)

This process manages the link between the Project Manager and the Team Managers who are actually building the products. 

  • Key Activities:
    • Teams accepting and executing Work Packages.
    • Ensuring work meets the specified quality standards.
    • Delivering completed and tested products back to the Project Manager. 

6. Managing a Stage Boundary (SB)

This occurs at the end of each stage (except the final one) to help the Project Board decide whether to continue. 

  • Key Activities:
    • Reporting on the performance of the current stage.
    • Creating a detailed Stage Plan for the next stage.
    • Updating the overall Project Plan and Business Case with the latest information. 

7. Closing a Project (CP)

This is the final part of the last management stage, ensuring the project is shut down in a controlled manner. 

  • Key Activities:
    • Confirming all products have been accepted by the customer.
    • Capturing Lessons Learned for future projects.
    • Preparing an End Project Report to evaluate performance against the original plan.

PRINCE2 Management Stages Overview

Essential Requirements Practices for a Business Analyst

Essential Requirements Practices for a Business Analyst

PRINCE2 7 Themes / Practices of PRINCE2

In the PRINCE2 project management methodology, Themes (renamed to Practices in the 7th edition released in 2023) are the seven functional areas of project management that must be addressed continuously throughout the project lifecycle. They provide a structured framework for managing key aspects like cost, risk, and quality to ensure the project remains on track. 

7 Themes / Practices of PRINCE2

Overview of the Seven Themes (Practices)

  • Business Case: Focuses on the “Why” of the project. It establishes the justification for the investment and ensures the project remains desirable, viable, and achievable.
  • Organisation: Addresses the “Who” by defining the project’s structure of accountability and responsibilities. It identifies key stakeholders and establishes the project management team.
  • Quality: Focuses on the “What” by defining the user’s requirements and quality standards. It ensures that deliverables are fit for purpose and meet stakeholder expectations.
  • Plans: Describes the “How,” “How Much,” and “When”. This theme provides techniques for creating project, stage, and team plans to facilitate communication and control.
  • Risk: Manages the “What If” by identifying, assessing, and controlling uncertainties that could impact the project’s objectives, whether they are threats or opportunities.
  • Change (Issues): Deals with the impact of changes and unexpected events. It provides a formal process for capturing, assessing, and controlling requests for change to project baselines.
  • Progress: Evaluates “Where are we now?” versus “Where are we going?”. It establishes mechanisms to monitor actual achievements against planned outcomes and manage deviations through tolerances. 

Key Concepts and Terminology

  • Continuous Application: Unlike processes, which follow a sequence, themes are applied simultaneously throughout the project.
  • Tolerances: Each theme uses tolerances (allowable deviations for time, cost, quality, etc.) to support the principle of Manage by Exception.
  • PRINCE2 7 Updates: The latest edition introduces Sustainability as a 7th performance target and emphasizes People as a core element alongside Principles, Practices, and Processes.

PRINCE2 Process Model Overview

PRINCE2 Process Model

The PRINCE2 process model provides a structured, process-driven roadmap for managing a project from its initial conception to formal closure. It consists of seven core processes that define specific activities, responsibilities, and decision points across the project lifecycle. 

The 7 PRINCE2 Processes

The processes are designed to ensure control and align with the project’s management levels: 

  • Starting Up a Project (SU): A pre-project process that filters out unviable ideas. It focuses on confirming if there is a “viable and worthwhile” business case and appoints the Project Manager and Executive.
  • Directing a Project (DP): Spans the entire project from start to finish. It is the responsibility of the Project Board, which provides strategic oversight, makes key decisions (e.g., authorising stages), and manages by exception.
  • Initiating a Project (IP): Occurs during the first management stage. It involves detailed planning to establish solid foundations, resulting in the Project Initiation Documentation (PID), which includes the project plan, risk management approach, and full business case.
  • Controlling a Stage (CS): Focuses on the Project Manager’s day-to-day management of a stage. This includes assigning work to teams, monitoring progress, and dealing with issues or risks within agreed tolerances.
  • Managing Product Delivery (MP): Governs the link between the Project Manager and Team Managers. It is where the “specialist products” (actual deliverables) are created, quality-checked, and delivered.
  • Managing a Stage Boundary (SB): Occurs at the end of each management stage (except the final one). The Project Manager reviews the current stage, updates the project plan and business case, and plans the next stage for Board approval.
  • Closing a Project (CP): Ensures an orderly end to the project. It confirms that objectives have been met, products have been accepted by the user, and lessons are captured before the project is formally disbanded. 

Hierarchy of Management Levels

The process model operates across four distinct levels of authority: 

  1. Corporate or Programme Management: Sets the initial project mandate.
  2. Directing (Project Board): Responsible for overall governance and major decisions (Directing a Project).
  3. Managing (Project Manager): Handles daily management and stage control (Controlling a Stage, Initiating a Project).
  4. Delivering (Team Members/Managers): Focuses on creating the physical products (Managing Product Delivery). 

Key Characteristics

  • Management Stages: Projects are broken into at least two stages (Initiation and at least one Delivery stage) to provide “stop/go” decision points.
  • Triggers: Each process is activated by a specific trigger, such as a “Project Mandate” from corporate management to start the SU process.
  • Management Products: These are documents like the Business Case, Project Brief, and Highlight Reports used to facilitate control and communication.

PRINCE2 (PRojects IN Controlled Environments) framework is built on seven core principles

PRINCE2 framework is built on seven core principles

The PRINCE2 (PRojects IN Controlled Environments) framework is built on seven core principles that serve as guiding obligations for any project using this methodology. For a project to be considered a “PRINCE2 project,” all seven must be applied. 

  • Continued Business Justification: A project must have a valid reason to start and must remain justified throughout its lifecycle. This is documented in a Business Case, which is regularly reviewed to ensure the project remains viable, desirable, and achievable.
  • Learn from Experience: Project teams are required to seek out lessons from previous projects and record new lessons as the current project progresses. A Lessons Log is typically used to capture these insights.
  • Defined Roles and Responsibilities: Every person involved must understand what is expected of them and who is responsible for specific tasks. PRINCE2 defines a clear management hierarchy: Project Board (Direction), Project Manager (Management), and Team Manager (Delivery).
  • Manage by Stages: Projects are broken down into manageable chunks called management stages. Each stage acts as a “stop/continue” decision point for the Project Board to assess progress before committing more resources.
  • Manage by Exception: Senior management (Project Board) only intervenes when the project deviates beyond agreed tolerances for time, cost, quality, scope, risk, or benefits. This empowers the Project Manager while ensuring efficient use of executive time.
  • Focus on Products: The methodology prioritizes the definition and delivery of high-quality products (outputs) rather than just completing activities. Product descriptions specify the quality criteria and requirements for each deliverable.
  • Tailor to Suit the Project: PRINCE2 is not a rigid “one-size-fits-all” approach; it must be adapted to the project’s specific scale, complexity, and environment. Tailoring ensures that the controls are appropriate for the level of risk involved. 

Towyn overview and detailed annotated timeline history by era and year to 2026

Towyn is a prominent seaside resort in Conwy, North Wales, traditionally known as a tourism hub with a high concentration of holiday parks and a history defined by its relationship with the Irish Sea. Historically, the town is most noted for the catastrophic 1990 floods, which reshaped local coastal defence policy across Britain. Today, it continues to evolve as a key destination for family holidays, with multi-million-pound investments in leisure facilities planned through 2026. 

Historical Timeline of Towyn

Early Origins & Parish Formation (1800s)

  • 1800s: Towyn begins developing as a tourism destination, largely due to its proximity to the established hub of Rhyl.
  • 17 June 1873: St Mary’s Church, designed by renowned architect George Edmund Street, is consecrated. It is famous for its distinctive roof tiling.
  • 22 September 1873: The Parish of Towyn is officially created, comprising the township of Towyn and parts of Cegidog Isaf, Bodoryn, and Bodtegwal. 

Tourism Growth & Mid-Century Development (1900–1980s)

  • Early 1900s: The town’s reputation as a “sunny coastline” (from the Welsh word Tywyn for sand dunes) solidifies it as a popular holiday spot.
  • 29 July 1960: Towyn Development Co. Limited is incorporated, marking a period of formalized commercial development in the area.
  • 1960s–1980s: Continued expansion of caravan and holiday parks, making tourism the town’s primary economic engine. 

The 1990 Flood Disaster & Recovery

  • 26 February 1990 (11:00 AM): A 400-metre breach of the sea wall occurs due to a 1.5m storm surge, gale-force winds, and high tides.
  • February – March 1990: Approximately 2,800 properties are flooded across 10 square km; up to 6,000 residents are evacuated.
  • 1 March 1990: Prince Charles and Princess Diana visit the disaster site.
  • Post-1990: Massive reconstruction of coastal defences begins, utilizing massive rock revetments to absorb wave impact. 

Modern Era & Future Outlook (2010–2026)

  • 2011 Census: Towyn’s population is recorded at 2,380.
  • November 2022: Tir Prince Raceway Ltd purchases the freehold of its 50-acre fairground and race track site, securing long-term investment for the town’s tourism.
  • August 2023: The Towyn and Kinmel Bay Place Plan is published, focusing on collaborative action for “placemaking” and sustainable transport.
  • April 2024: Multi-million-pound expansion plans are revealed for major holiday parks, including new leisure complexes.
  • February 2025: The town marks the 35th anniversary of the 1990 floods with reflections on coastal resilience.
  • March 2026: Target date for completion of several holiday park upgrades, including new high ropes courses and state-of-the-art leisure facilities.

Towyn overview and detailed annotated timeline history by era and year to 2026

Agile Framework Executive Summary Overview Snapshot

Agile Framework Executive Summary Overview Snapshot

Llandudno overview and detailed annotated timeline history by era and year to 2026

Llandudno, often called the “Queen of the Welsh Watering Places,” is a prominent seaside resort on the Creuddyn Peninsula in North Wales. Planned specifically as a mid-Victorian holiday destination, the town is renowned for its well-preserved 19th-century architecture, sweeping promenade, and the towering limestone headland of the Great Orme. 

Town Centre, photo taken March 2026

Historical Timeline by Era

Ancient & Medieval (Prehistory – 1800s)

  • Bronze Age (c. 2000 BCE): Extensive copper mining begins on the Great Orme; these are now recognized as the world’s oldest known copper mines.
  • 6th Century: St Tudno establishes a church on the Great Orme, giving the town its name (“Church of Saint Tudno”).
  • 1284: King Edward I conveys the Manor of Gogarth to the Bishop of Bangor.
  • Early 1800s: Kashmiri goats are introduced to the Great Orme, later becoming an iconic symbol of the town. 

The Victorian Transformation (1840 – 1901)

  • 1840: St George’s Church is built to serve the growing village.
  • 1848: Architect Owen Williams presents development plans to Lord Mostyn to turn the marshlands into a resort.
  • 1858: The railway branch line from Llandudno Junction opens, making the resort accessible to wealthy tourists from Liverpool and Manchester.
  • 1862: The Great Orme Lighthouse is built by the Mersey Docks and Harbour Board.
  • 1877/1878: The Llandudno Pier opens (700 metres long) and the Marine Drive carriage road around the Great Orme is completed.
  • 1887: Happy Valley is gifted to the town by Lord Mostyn for Queen Victoria’s Golden Jubilee.
  • 1890s: A large Jewish community settles in Llandudno, escaping persecution in Eastern Europe. 

Modern & Contemporary (1902 – 2026)

  • 1902: The Great Orme Tramway—the UK’s only cable-operated street tramway—opens.
  • 1914–1918 (WWI): Hotels are converted into hospitals; the 1st (North Wales) Brigade is headquartered here.
  • 1940–1945 (WWII): The town hosts the Coast Artillery School and becomes a haven for those escaping the London Blitz.
  • 1956: The electric tramway service to Colwyn Bay closes.
  • 1963: The Beatles perform in Llandudno; the Welsh National Eisteddfod is held in Happy Valley.
  • 1986: The first Llandudno Victorian Extravaganza is held to celebrate the town’s heritage.
  • 1994/2006: The North Wales Theatre opens, later expanded and renamed Venue Cymru.
  • 2017: A new lifeboat station is completed on the North Shore.
  • 2022: Llandudno officially twins with Champéry, Switzerland.
  • 2023–2026: Venue Cymru becomes the permanent home for the Welsh Open snooker tournament (February).
  • 2026 (Scheduled):
    • February: Nick Beer 10K (Feb 15) and Welsh Open Snooker (Feb 23–Mar 1).
    • May: Victorian Extravaganza and Transport Festival (May 2–4).
    • June: Llandudno Triathlon & Duathlon (Jun 28).
Wetherspoon pub reopens on 22nd August 2001 – photo as of March 2026

The Palladium in Llandudno, a Grade II listed building, was transformed into a JD Wetherspoon pub in 2001. The following timeline outlines its history from its origins as a grand theatre to its current use. 

The Palladium Timeline

  • 1920: The Palladium Theatre opens on the site of the former 1894 Market Hall. Designed by Arthur Hewitt, it originally featured 1,500 seats across three levels: stalls, dress circle, and balcony.
  • 1972: The building is subdivided for multi-purpose use. Bingo is introduced in the former stalls area, while a 600-seat cinema occupies the circle area.
  • 1999: The venue, then owned by Apollo Leisure, officially closes on 8th September.
  • 2000: The building is purchased by JD Wetherspoon for conversion into a pub.
  • 2001: Following a restoration project that returns the auditorium to a single open space, the Wetherspoon pub reopens on 22nd August – see picture above taken March 2026.
  • 2012–2013: A significant restoration of the exterior is completed to maintain the building’s historic facade.
  • 2024–2025: Wetherspoon invests approximately £1 million in a major refurbishment, focusing on the preservation and restoration of the heritage ceiling and the proscenium arch. 

Visiting The Palladium

  • Location: Gloddaeth St, Llandudno LL30 2DD
  • Type: Wetherspoon Pub in a converted Grade II listed theatre.
  • Features: Retains original theatrical character including painted ceilings, balcony details, and original seating.
  • Hours: Generally open from 8:00 am daily, closing at midnight or 1:00 am on weekends. 

In Llandudno for an amble…

In Llandudno for an amble…

#Llandudno

RACI Matrix to Eliminate Role Confusion in Projects

RACI Matrix to Eliminate Role Confusion in Projects

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