Website Author IT Career Timeline Breakdown

Mark Whitfield is a highly experienced IT professional with a career spanning over 30 years, transitioning from a technical programmer to a senior digital engagement and project manager. His expertise is rooted in HPE NonStop (Tandem) systems and has evolved to encompass complex Agile and Cloud delivery across diverse industries. 

Early Technical Era (1990–1995)

Following his graduation in Computing in 1990, Whitfield began his career as a Programmer at The Software Partnership (later Deluxe Data). 

  • Focus: Electronic banking software, specifically sp/ARCHITECT-BANK on Tandem Mainframe Computers.
  • Key Work: Developed code for major banks including TSB, Barclays, and Rabobank. This included early digital innovations like voice-driven phone banking and inter-account transfers before the internet was widespread. 

Growth and Product Management Era (1995–2004) 

Whitfield joined Insider Technologies Limited (ITL) in 1995 as a Senior Programmer

  • Focus: Platform health and diagnostic software for HPE NonStop systems.
  • Key Projects:
    • Co-developed diagnostic plug-ins for the Reflex monitoring suite.
    • Managed the first HP OpenView Operations (OVO) Smart Plug-In certification for the NonStop platform in 2002.
    • Consulted for CRESTCo (Euroclear) in 1997, conducting benchmark testing on new S7000 nodes. 

Strategic Leadership and Project Management Era (2005–2014) 

During this decade, he transitioned into IT Project Management, focusing on high-value financial transaction tracking. 

  • Focus: Waterfall and Agile project delivery for payment systems and banking infrastructure.
  • Key Milestones:
    • 2011: Led a massive transaction tracking project at Al Rajhi Bank (Saudi Arabia), parsing terabytes of tape-archived data into a normalised SQL database.
    • 2013–2014: At Wincor Nixdorf, managed a £5+ million project for Lloyds Banking Group to migrate ATM driving responsibilities from legacy systems to AIX-based Oracle technologies. 

Senior Digital Engagement Era (2014–Present)

Since 2014, Whitfield has focused on senior-level digital transformation and engagement management. 

  • Betfred (2014–2016): Served as Senior Digital Project Manager for online and mobile platforms (iOS/Android), managing fraud detection and payment gateway integrations.
  • Capgemini (2016–Present): Joined as an Engagement Manager (SC cleared).
    • Focus: Managing large-scale Agile and Waterfall digital projects across aerospace, defence, and government sectors.
    • Notable Projects: Leading a £13.5m programme to migrate 130 UK government applications to the cloud (AWS/Azure) and delivering real-time airspace monitoring apps for air traffic organisations. 
Mark Whitfield IT Career Timeline Breakdown

Mark Whitfield Online Resume Overview

Mark Whitfield is a highly experienced Senior IT Project Manager and former developer with over 30 years of expertise in HP NonStop (formerly Tandem) systems, primarily within the electronic banking and payments sectors. He is currently a Senior Project Manager at Capgemini (SC cleared until 2031) and maintains a professional portfolio at mark-whitfield.com

Historical Timeline & Customer Breakdown

  • 1990 – 1995: The Software Partnership / Deluxe Data (now FIS)
    • Customer/Projects: Developed electronic banking software, specifically sp/ARCHITECT-BANK, for major financial institutions including TSBBank of ScotlandRabobank, and Girofon (Denmark).
    • Technical Breakdown: Focused on low-level programming using COBOL85NonStop SQL, and TAL (Transaction Application Language).
    • Role: Programmer.
  • 1995 – 2013: Insider Technologies Ltd (ITL)
    • Customer/Projects: Focused on HP NonStop monitoring, diagnostic, and payment software for high-value banking clients. Key products included Enterprise ManagerXPNETBASE24, and EPS.
    • Technical Breakdown:
      • XPERT24: Produced technical designs for this performance monitoring tool to track XPNET layers and transaction interchange counters (ATM/POS approval rates).
      • RTLX Payments: Served as IT Project Manager for RTLX (Real-Time Long-term eXchange) payment software.
      • Infrastructure: Extensive use of Guardian utilities (PATHWAY, SCF, FUP, INSPECT), TACL, and SCOBOL.
    • Role: Software Design, Team Leading, and Product Management.
  • 2013 – 2016: Freelance / Contract Projects
    • Customer/Projects: Managed software development lifecycle (SDLC) projects for various blue-chip companies.
    • Role: IT Project Manager.
  • 2016 – Present: Capgemini
    • Customer/Projects: Managing large-scale digital and public sector transformations. Notable clients include UK Government (MS Azure Cloud migration), Jaguar Land Rover (JLR)HeathrowRoyal Mail GroupBank of EnglandHSBCBarclays, and Deutsche Bank.
    • Technical Breakdown: Transitioned from legacy Tandem environments to modern Agile Scrum delivery and Microsoft Azure Cloud hosting.
    • Role: Senior Project Manager / Technical Delivery Manager.

Technical Breakdown by Competency

  • Operating Systems: HP NonStop (Guardian/NSK), Windows, Linux, Unix.
  • Programming Languages: TALTACLCOBOL85SCOBOL, C, C++, Java, and ASP.NET framework.
  • Databases: NonStop SQL/MP, MS SQL.
  • NonStop Middleware: PATHWAYXPNETBASE24EPS, and EMS (Event Management System).
  • Methodologies: Registered PRINCE2 PractitionerAgile SCRUM, ITIL, and ISO9001:2008. 

Web Hyperlinks & Resources

iProPMTemplates on Etsy for Project Management Templates with FREE Upgrades

Mark Whitfield is a Senior Project Manager with over 30 years of experience in delivering PRINCE2 Waterfall and Agile Scrum projects. Operating the Etsy shop ProjectTemplatesSoft (also known as iProPMTemplates), he provides a comprehensive bundle of over 200 professional project management templates. 

Operating the Etsy shop ProjectTemplatesSoft (also known as iProPMTemplates)

Author Overview: Mark Whitfield

  • Professional Background: Graduated in Computing in 1990 and began his career as a programmer in electronic banking software.
  • Expertise: Senior Project Manager and PRINCE2 Practitioner with extensive experience in the Software Development Lifecycle (SDLC).
  • Value Proposition: His templates are designed to be “imitation-proof” professional toolsets used in real-world project delivery.
  • Support Policy: Offers FREE upgrades and additions for life to anyone who purchases his template bundles; users simply contact him via Etsy or his official website

Detailed Project Templates Inventory

The expanded inventory typically included in his master ZIP file covers the entire project lifecycle across various formats (Excel, Word, PowerPoint, and MS Project). 

1. Planning & Scheduling Templates

  • MS Project (MPP) Plans: Detailed SDLC Microsoft Project plans adaptable for Waterfall and Agile Scrum, including PRINCE2 7th Edition specific plans.
  • Excel Project Planners: Robust Waterfall and PRINCE2 planners with automated Gantt views, designed for users without MS Project licenses.
  • Plan on a Page (POaP): High-level PowerPoint and Excel templates for stakeholder presentations, showing project timelines and key milestones.
  • Agile Frameworks: Templates for Sprint planning, Daily Stand-ups, Sprint Reviews, and Retrospectives. 

2. Tracking & Control (RAID & RACI)

  • Comprehensive RAID Log: An Excel-based master tracker for Risks, Assumptions, Issues, Dependencies, and Decisions.
  • RACI Matrix: For defining roles and responsibilities (Responsible, Accountable, Consulted, Informed).
  • Agile Trackers: Includes Burn Down and Burn Up charts for teams not using Jira or similar tools. 

3. Financial & Resource Management

  • Project Financial Tracker: Detailed spreadsheets for tracking forecasts, actuals, margins, and variance.
  • Resource Costing Grid: Tools for estimating resource costs across project phases, useful for bidding and Statements of Work (SoW).
  • Capacity Planning: Templates for managing team availability and on-boarding mobilization kits

4. Documentation & Reporting

  • Status Reports: Weekly and monthly templates in Word and PowerPoint.
  • Standard PRINCE2 Artifacts: Complete set including Business Cases, Project Briefs, Highlight Reports, and End Stage Reports.
  • Governance Tools: Meeting minutes, stakeholder analysis plans, and Benefits Realisation Plans

iProPMTemplates on Etsy for Project Management Templates with FREE Upgrades

Project Management Templates Overview and Author Timeline

Mark Whitfield provides a comprehensive suite of over 200 editable project management templates designed for Agile, Waterfall, and PRINCE2 methodologies. These tools are based on his 30+ years of project delivery experience in high-stakes sectors like banking and aerospace. 

Overview of Project Management Templates

Whitfield’s collection, available on his official website and Etsy, includes specialized tools for various delivery phases: 

  • Planning & Scheduling: Includes Plan on a Page (POaP) (30+ PowerPoint examples for executive summaries), detailed MS Project (MPP) plans, and Excel-based Gantt charts for those without MS Project licenses.
  • Tracking & ControlRAID Logs (Risks, Actions, Issues, Dependencies/Decisions) with built-in charts, and RACI Trackers for defining roles and responsibilities.
  • Methodology-Specific Tools:
    • PRINCE2: Full 7th Edition MS Project plans and standard Word templates.
    • Agile/Scrum: Agile burn-down and burn-up charts, story dependency trackers, and sprint overview templates.
  • Financial Management: Detailed trackers for budgets, forecasts, actuals, margins, and resource costing per project phase.
  • Reporting & Governance: Weekly/monthly status report templates (Word and PowerPoint), project organization charts, stakeholder analysis plans, and meeting minutes.
  • Delivery & Mobilization: Onboarding kits, deployment runbooks, and Statement of Work (SOW) guidance for both Agile and Waterfall. 

Historical Career Timeline

Mark Whitfield’s template development is rooted in a career that evolved from technical programming to senior engagement management. 

  • 1990–1995: The Software Partnership / Deluxe Data: Started as a programmer specializing in electronic banking software for Tandem Computers (HPE NonStop).
  • 1995–2013: Insider Technologies (18 years):
    • 1997: Consultant at CRESTCo (now Euroclear) for volume testing and performance benchmarking.
    • 2002: Managed the first HP OpenView Operations 2-way Smart Plug-In certification for the NonStop platform.
    • Early 2000s: Transitioned to IT Project Manager, managing waterfall projects for real-time log extraction (RTLX) products for clients like HSBC.
    • Late 2000s–2013: Senior roles in product and project management, managing large-scale transaction monitoring for global banks.
  • 2013–2014: Wincor Nixdorf: Served as a Project Manager for the Banking Division, managing a £5m+ project for Lloyds Banking Group (LBG) to replace legacy software across their ATM estate.
  • 2014–2016: Betfred: Senior IT Digital Project Manager in the Online and Mobile Division, delivering projects using the Agile Scrum framework.
  • 2016–Present: Capgemini UK:
    • 2016: Lead Project Manager for a UK Air Traffic organization, delivering iOS apps for airspace visualization.
    • 2023–2024: Technical Delivery Manager for a £1m+ UK Government project involving fish export and health document portals.
    • Current: Serving as an Engagement Manager (Certified PRINCE2 Practitioner and Agile SCRUM) augmented into MuleSoft. 

Project Management Templates Overview and Author Timeline

Agile Development Overview and Detailed Timeline by Era

Agile development is an iterative and incremental approach to project management and software delivery that prioritises flexible planning, frequent delivery of working software, and rapid response to change. At its core, Agile seeks to shorten work cycles to deliver value to customers quickly while using frequent feedback to improve quality. 

Core Overview

The foundation of modern Agile is defined by the Agile Manifesto (2001), which establishes four central values: 

  • Individuals and interactions over processes and tools.
  • Working software over comprehensive documentation.
  • Customer collaboration over contract negotiation.
  • Responding to change over following a plan. 

The Agile life cycle typically moves through six phases: Concept, Inception, Iteration, Release, Maintenance, and Retirement


Comprehensive Timeline of Agile Development

Agile did not emerge in a vacuum; it evolved from early 20th-century industrial concepts and decades of experimentation in software engineering. 

Era 1: The Industrial & Theoretical Roots (1910s – 1960s)

This era established the foundational concepts of efficiency, waste reduction, and iterative cycles that would later inform Agile frameworks. 

  • 1911: Frederick Taylor publishes The Principles of Scientific Management, advocating for managers to analyse and adopt worker-led process improvements.
  • 1930s: Walter Shewhart at Bell Labs develops the Plan-Do-Check-Act (PDCA) cycle, a groundbreaking iterative methodology for quality control.
  • 1948: Toyota formalises the Toyota Production System (Lean), introducing concepts like Kaizen (continuous improvement) and Just-in-Time manufacturing.
  • 1957: Gerald Weinberg and others at IBM begin using incremental development on projects.
  • 1958: NASA’s Project Mercury uses half-day iterations and test-first development, marking one of the earliest high-stakes uses of iterative cycles.

Era 2: Evolutionary Alternatives to Waterfall (1970s – 1980s) 

As the rigid Waterfall model became dominant, practitioners began developing “lightweight” alternatives to handle complex, shifting requirements. 

  • 1970s: Barry Boehm proposes Wideband Delphi, an early forerunner to Planning Poker.
  • 1976: Tom Gilb publishes the Evolutionary Delivery Model (Evo), perhaps the first explicitly named incremental alternative to Waterfall.
  • 1980: Toyota introduces Visual Control, the predecessor to Agile “information radiators” like Kanban boards.
  • 1986: Hirotaka Takeuchi and Ikujiro Nonaka publish “The New New Product Development Game” in Harvard Business Review, introducing the “rugby” approach that inspired the Scrum framework.
  • 1988: Barry Boehm formalises the Spiral Model, an iterative model focused on identifying and reducing risks. 

Era 3: The Proliferation of Frameworks (1990 – 2000) 

This decade saw a “crisis” in software development where traditional methods failed to keep up with the personal computing boom, leading to the birth of modern frameworks. 

  • 1991: James Martin publishes Rapid Application Development (RAD), formalising the use of timeboxing and iterations.
  • 1993: Jeff Sutherland and team at Easel Corporation first implement Scrum as a formal process.
  • 1994: The Dynamic Systems Development Method (DSDM) is created as a non-profit consortium to provide a framework for RAD.
  • 1995: Ken Schwaber and Jeff Sutherland co-present the Scrum methodology at the OOPSLA conference.
  • 1996: Kent Beck creates Extreme Programming (XP) while working on the Chrysler Comprehensive Compensation (C3) project.
  • 1997: Jeff De Luca introduces Feature-Driven Development (FDD).
  • 1999: Kent Beck publishes Extreme Programming Explained, popularising many engineering practices like pair programming.

Era 4: The Manifesto & Mainstream Adoption (2001 – 2010)

Agile shifted from a niche experimental approach to a global industry standard. 

  • 2001 (Feb): 17 developers meet at Snowbird, Utah, and author the Manifesto for Agile Software Development.
  • 2001 (Post): The Agile Alliance is formed to promote the manifesto’s values.
  • 2003: Mary and Tom Poppendieck publish Lean Software Development, formally linking Lean manufacturing principles to Agile.
  • 2005: Mike Cohn introduces Planning Poker in Agile Estimating and Planning.
  • 2007: The Scaled Agile Framework (SAFe) is introduced by Dean Leffingwell to apply Agile to large enterprises.
  • 2009: The concept of DevOps emerges, seeking to bridge the gap between Agile development and IT operations. 

Era 5: Scale, Transformation, and Modern Evolution (2011 – Present)

Agile has expanded beyond software into marketing, HR, and education, becoming a “culture” rather than just a tool. 

  • 2011: The Project Management Institute (PMI) introduces the Agile Certified Practitioner (PMI-ACP).
  • 2012–2015: Agile adoption surpasses 50% in the development world as success metrics become undeniably clear.
  • 2017: AXELOS updates PRINCE2 to make agility a core focus of the project management standard.
  • 2020s: Continued evolution toward “Business Agility,” where entire organisations adopt Agile mindsets to survive rapidly changing market conditions. 

Agile Development Overview and Detailed Timeline by Era

Senior Project Manager vs Project Manager vs Program Manager

Senior Project Manager vs Project Manager vs Program Manager

AI Projects and Methodologies for Managing AI Projects

Artificial intelligence (AI) is transforming project management through two distinct but related paths: the use of AI-powered tools to manage general projects and the specialized methodologies required to manage AI development itself

1. Methodologies for Managing AI Projects

Traditional software development methods (like Waterfall) often fail for AI because these projects are experimental and non-linear. Specialized frameworks have emerged to handle the “data-first” nature of AI: 

  • CPMAI (Cognitive Project Management for AI): A leading methodology that combines Agile principles with data-centric phases: Business Understanding, Data Understanding, Data Preparation, Model Development, Model Evaluation, and Model Operationalization.
  • Agile-AI Hybrid: Adapts standard Agile by using “short-boxed” iterations for model training and allowing for a “flexible scope” because model performance is unpredictable until tested.
  • Data Driven Scrum: A variation of Scrum that prioritizes work based on data availability and experimental results rather than just feature backlogs.
  • MLOps (Machine Learning Operations): An operational framework focused on the continuous integration, deployment, and monitoring of models to prevent “model drift” after a project officially “ends”. 

2. AI-Augmented Project Management (The “AI Copilot”)

For non-AI projects, AI acts as an intelligent assistant to automate administrative tasks and provide predictive insights. 

3. Implementation Strategy

Experts recommend a phased approach to integrating AI into management workflows: 

  1. Assess Inefficiencies: Identify repetitive tasks (e.g., status reporting) that can be automated first.
  2. Data Governance: Ensure project data is clean and centralized; AI is only as good as the data it consumes (“Garbage In, Garbage Out”).
  3. Human-in-the-Loop: Use AI for data-heavy lifting, but retain human judgment for high-stakes leadership, ethics, and stakeholder empathy.

AI Projects and Methodologies for Managing AI Projects

Key Skills for the Project Manager

Key Skills for the Project Manager

Agile Scrum Methodology Summary Breakdown Overview

Scrum is 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

Agile Framework Executive Summary Overview Snapshot

Agile Framework Executive Summary Overview Snapshot

Understanding Project Management Frameworks

Understanding Project Management Frameworks

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

Microsoft Power Platform Development Timeline Overview

Microsoft Power Platform is a suite of low-code tools designed to help organizations analyze data, build custom solutions, automate processes, and create AI-powered agents. It enables both professional developers and “citizen developers” (business users) to rapidly build end-to-end business applications that integrate with the broader Microsoft Cloud ecosystem

Microsoft Power Platform

Core Product Areas

The platform consists of five primary applications: 

  • Power BI: A business analytics tool for data visualization and interactive reporting.
  • Power Apps: A low-code development environment for building custom web and mobile business applications.
  • Power Automate: A service for workflow automation and robotic process automation (RPA).
  • Power Pages: A platform for creating and hosting secure, external-facing business websites.
  • Copilot Studio: A graphical tool for building and customizing AI-powered agents and chatbots. 

Underlying Capabilities

The platform’s strength lies in its shared infrastructure: 

  • Microsoft Dataverse: A secure, cloud-scale data store that provides a common data model for all Power Platform apps.
  • Connectors: Over 1,000 prebuilt integrations that allow apps to communicate with external data sources like SAP, Salesforce, and Google Analytics.
  • AI Builder: A capability that allows users to add AI models (e.g., sentiment analysis or object detection) to their apps and flows without writing code.
  • Power Fx: A low-code, strongly-typed programming language used for expressing logic across the platform.

The Microsoft Power Platform has evolved from individual components like Power BI and Power Apps into a unified suite, now heavily integrated with Copilot and AI

Origins & Early Growth (2013–2018)

  • 2013Power BI is first released as an Excel add-in before becoming a standalone service in 2015.
  • 2015Power Apps enters public preview as a low-code tool for building business applications.
  • 2016Microsoft Flow (now Power Automate) is launched to provide workflow automation across apps and services.
  • 2018: The term “Microsoft Power Platform” is officially introduced to unify Power BI, Power Apps, and Flow. 

Expansion & Rebranding (2019–2022)

  • 2019Power Virtual Agents is added to the suite for creating no-code chatbots. Microsoft Flow is rebranded as Power Automate.
  • 2020: Launch of Power BI Premium per user and the Dataverse (formerly Common Data Service) rebranding.
  • 2021Power Fx, an open-source formula language based on Excel, is introduced as the standard language across the platform.
  • 2022Power Pages is launched as the fifth standalone product for building secure, low-code business websites. 

The AI & Copilot Era (2023–Present)

  • 2023: Integration of Copilot across all Power Platform products, allowing users to build apps, flows, and reports using natural language.
  • 2024: Introduction of Timeline Highlights in Power Apps to provide AI-generated summaries of record activities.
  • 2025: Microsoft announces the retirement of the Power Apps per app plan (January) and ends support for contact tracking in the Dynamics 365 App for Outlook (October).
  • 2026: The 2026 Release Wave 1 begins (April–September), focusing on deeper Role-based Copilot offerings and enhanced security agents.
Microsoft Power Platform Milestone Summary

The Microsoft Power Platform originated from Microsoft’s effort to democratise data and app development by evolving its existing business tools into a unified low-code ecosystem

Origins and Evolution (2003–2015)

The platform’s roots trace back to early business solutions that were eventually merged into the modern suite: 

  • Dynamics CRM 1.0 (2003): The foundation for what became the Microsoft Dataverse (formerly Common Data Service), providing a secure relational database.
  • Project Siena (2013): A “garage project” at Microsoft aimed at building web apps without professional coding tools. This project eventually became Power Apps.
  • Power BI Launch (2015): Originally “Project Crescent” for SQL Server, Power BI was the first of the modern “Power” services to be delivered, entering preview in January 2015. 

Expansion and Formalisation (2016–2019) 

Microsoft transitioned from individual tools to an integrated platform: 

  • Power Apps and Flow (2016): Power Apps and Microsoft Flow (later renamed Power Automate) became generally available in November 2016.
  • Common Data Service (2016): Introduced to provide a shared data platform across Dynamics 365 and the new “Power” tools.
  • Official Branding (2018–2019): The term “Microsoft Power Platform” was officially established as an umbrella brand for the suite of tools. In 2019, Microsoft Flow was rebranded to Power Automate to align with the platform’s naming convention. 

Modern Era and AI Integration (2020–Present) 

The platform has shifted toward “AI-first” development and expanded its core pillars: 

  • New Components: Power Virtual Agents (now Copilot Studio) and Power Pages (for external websites) were added to the core lineup.
  • Acquisitions: Microsoft acquired Softomotive (2020) and Minit (2022) to bolster Power Automate with Robotic Process Automation (RPA) and process mining capabilities.
  • Generative AI: Recent updates have focused on integrating Copilots across all products, allowing users to build apps and automations using natural language. 

Microsoft Power Platform Development Timeline Overview

Microsoft Dynamics 365 Timeline

Agile Scrum Master Skills for Success

Agile Scrum Master Skills for Success

Centiun Microsoft Business Applications and AI Specialists

Websitehttps://centiun.com

Centiun Microsoft Business Applications and AI Specialists

Centiun Overview

Centiun is a British IT services consulting company and Microsoft Partner, helping enterprise public and private sector organisations achieve digital transformation excellence through the Microsoft cloud.

We specialise in Microsft Dynamics 365, Power Platform, and Micrisoft 365, delivering expert consultancy, solution architecture, implementation, and managed services that enable organisations to modernise operations, improve service delivery, and unlock greater value from their technology investment.

From CRM transformation and business process automation to secure collaboration, data-driven decision making, and AI enabled innovation, Centiun supports customers to build smarter, faster and more resilient ways of working.

Our approach combines deep Microsoft expertise with a practical focus on outcomes – designing and delivering solutions that are scalable, compliant, and tailored to the needs of complex organisations.

Whether you’re starting your digital journey or optimising an existing platform, Centiun is your trusted Microsoft for long-term transformation and support.

Website: https://centiun.com

On LinkedIn: https://www.linkedin.com/company/centiun/

Email: info@centiun.com

Centiun services
Centiun Microsoft Business Applications and AI Specialists
Centiun Microsoft Business Applications and AI Specialists

Mark Whitfield IT Training Career Timeline Overview

Mark Whitfield, an experienced IT Project Manager, has a career and certification history spanning over 30 years. His professional development includes a range of technical, project management, and cloud-based qualifications. 

2020s: Cloud & Modern Platforms

  • 2024 (July): Microsoft Excel Refresher Course – Udemy.
  • 2022 (December/February): C&CA UK’s Communications & Engagement Award and AZ-900 Microsoft Certified Azure Fundamentals. 

2010s: Advanced Management & Development 

  • 2017 (November/April): Advanced Engagement Management (Level 2) and Microsoft Excel 2010 Expert Skills.
  • 2014 (July): Advanced Microsoft Excel 2013.
  • 2011 (May–July): PRINCE2 Practitioner, Agile SCRUM, Java, and Android programming. 

2000s: Web Applications & Database Systems 

  • 2009 (March–November): Thales e-Security, BIRT, Web Design, and SQL Server training.
  • 2006 (Feb–Dec): NetObjects Fusion, Cryptography, and Thales e-SECURITY SafeSign.
  • 2004 (March): MultiBatch NSK Job Scheduling.
  • 2000 (February): Fundamentals of Successful Project Management. 

1990s: Core Programming & System Fundamentals

  • 1990s (1993–1999): TANDEM/HP NonStop systems, C/C++ programming, project management, and HND in Computer Studies (1990).

Mark Whitfield Training IT Career Timeline Overview

Mark Whitfield, a Senior IT Project Manager who has spent over 30 years specialising in HP NonStop (formerly Tandem) computing systems

Professional Background

  • Specialisation: Mark Whitfield is a highly experienced technician and project manager for the HP NonStop platform, which is a high-availability, fault-tolerant mainframe environment used primarily for mission-critical financial transactions.
  • Career Timeline:
    • The Software Partnership / Deluxe Data (1990–1995): Began as a programmer working on the sp/ARCHITECT-BANK solution for Tandem computers.
    • Insider Technologies (1995–2013): Spent 18 years focusing on monitoring and diagnostic software for HP NonStop, including products like Reflex 80:20XPERT24, and Enterprise Manager.
    • Capgemini (2016–Present): Currently serves as an SC-cleared Senior Project Manager, delivering complex IT projects for major banks and government agencies. 

Key Technical Contributions to NonStop

  • Product Development: He co-developed Reflex (a platform health/diagnostic tool) and designed XPERT24 to monitor performance in the XPNET layer of BASE24.
  • Financial Systems: He has managed major projects for global financial entities, including BarclaysHSBCBank of England, and Royal Mail Group, often involving ATM and POS monitoring systems.
  • Programming Expertise: His technical skill set includes NonStop-specific languages and tools such as TAL (Tandem Application Language)PATHWAYXPNETCOBOL85, and C++

About HP NonStop Systems

In the context of Mark Whitfield’s work, NonStop refers to a “shared-nothing” architecture designed by Tandem Computers. These systems are uniquely capable of: 

  • Fault Tolerance: Handling hardware or software failures without system downtime.
  • Scalability: Doubling throughput by adding processors (up to 4,000) without hitches in performance.
  • Core Banking: Processing massive commercial workloads for retail banks and stock exchanges globally.

Project Management evolution timeline by era

The history of project management has evolved from ancient manual coordination to highly sophisticated, digital-first methodologies

Pre-20th Century: The Era of Ancient Marvels

During this era, project management was characterized by massive labour forces and basic resource coordination without standardized scheduling tools. 

  • 2570 BC: Completion of the Great Pyramid of Giza. Documentation shows managers were assigned to each of the four faces to oversee progress.
  • 208 BC: Construction of the Great Wall of China. Labour was systematically organized into groups of soldiers, civilians, and criminals.
  • 1850s: Construction of the Pacific Railroad. This is often cited as one of the first large-scale industrial project management undertakings in the U.S.. 

1900–1950: The Birth of Modern Project Management 

This era introduced scientific management principles and the first visual scheduling tools. 

  • 1911Frederick Taylor publishes The Principles of Scientific Management, focusing on efficiency and unskilled labour training.
  • 1917Henry Gantt develops the Gantt Chart, a radical tool for visualising schedules that remains a global standard today.
  • 1931–1936: Construction of the Hoover Dam. This project was a major early adopter of Gantt’s scheduling techniques.
  • 1942–1945The Manhattan Project. This complex R&D effort pioneered the use of large-scale task coordination and resource management. 

1950–1980: The Era of Management Science 

Driven by the Cold War and space race, this period saw the creation of mathematical scheduling techniques. 

  • 1956: AACE International is formed, focusing on cost engineering.
  • 1957–1958: Development of Critical Path Method (CPM) by DuPont and Program Evaluation and Review Technique (PERT) by the U.S. Navy.
  • 1962–1975: Introduction of Work Breakdown Structure (WBS) by the DoD, founding of IPMA and PMI, and development of PROMPT (later PRINCE). 

1980–2000: The Computing Revolution 

Personal computers allowed project management software to proliferate into the private sector. Key milestones included the early Scrum framework and the initial PMBOK Guide release. 

  • 1989–1997: Widespread adoption of Earned Value Management (EVM), release of PRINCE2, and development of Critical Chain Project Management (CCPM)

2000–Present: The Agile and Digital Era 

Modern project management emphasizes flexibility, speed, and digital tools. 

  • 2001: The Agile Manifesto is published.
  • 2012–2021: Release of ISO 21500, major updates to PRINCE2 and PMBOK to integrate Agile, and the shift to performance-based standards in PMBOK 7th Ed.

Project Management evolution timeline by era

Project management has evolved from ancient engineering feats to a highly structured, data-driven discipline. Below is a comprehensive timeline of its historical development and the evolution of its core methodologies. 

Ancient & Early Eras

  • 2570 BC: The Great Pyramid of Giza – Completed with record-keeping and oversight for each of the four faces, demonstrating early forms of planning and control.
  • 208 BC: The Great Wall of China – Built with a massive labour force organised into specific groups: soldiers, ordinary people, and criminals.
  • 1917: Gantt Chart – Developed by Henry Gantt, this scheduling diagram became a radical innovation for tracking project tasks chronologically. 

The Mid-20th Century: Formalization

  • 1956: AACE International Formed – Early practitioners of cost engineering and scheduling founded what is now the leading society for project control specialists.
  • 1957: Critical Path Method (CPM) – Invented by DuPont to address chemical plant maintenance; it saved the company $1 million in its first year.
  • 1958: PERT (Program Evaluation Review Technique) – Developed for the U.S. Navy’s Polaris project to analyse the minimum time needed for task completion.
  • 1962: Work Breakdown Structure (WBS) – Mandated by the U.S. Department of Defense as a hierarchical tree structure for project deliverables.
  • 1965: IPMA Founded – The world’s first project management association was started in Vienna as a global forum for networking.
  • 1969: Project Management Institute (PMI) Launched – Founded to advance the profession, PMI has since become the primary publisher of global standards. 

Late 20th Century: Methodology Proliferation 

  • 1975: PROMPTII & “The Mythical Man-Month” – Guidelines were created for computer projects, while Fred Brooks’s Brooks’s law observed that adding manpower to late software projects makes them later.
  • 1984: Theory of Constraints (TOC) – Introduced by Dr. Eliyahu M. Goldratt, focusing on identifying system bottlenecks.
  • 1986: Scrum – First named as a project management style for software development in a Harvard Business Review paper.
  • 1987: PMBOK Guide First Published – PMI published the first “A Guide to the Project Management Body of Knowledge” as a white paper to standardise practices.
  • 1989: PRINCE & Earned Value Management – The PRINCE method was developed for UK government IT projects; meanwhile, Earned Value Management (EVM) became an essential part of procurement.
  • 1996: PRINCE2 – A more generic revision of PRINCE was published, applicable to any project type.
  • 1997: Critical Chain Project Management (CCPM) – Invented to keep resources levelly loaded and flexible. 

21st Century: Agile & Global Standards

  • 2001: The Agile Manifesto – Written by 17 developers in Utah, codifying the principles of lightweight, iterative software development.
  • 2006: Total Cost Management Framework – Released by AACE International as the first integrated process for portfolio and project management.
  • 2012: ISO 21500:2012 – The International Organisation for Standardisation released its global guidance on project management.
  • 2017: PMBOK 6th Edition & PRINCE2 Update – Updates reflected the integration of Agile practices into traditional project settings.
  • 2021: PMBOK 7th Edition – Shifted toward a principle-based approach to help practitioners be more proactive and innovative.

Project Management Mistakes and How to Avoid

Project Management Mistakes and How to Avoid

Agile Before and After

Agile Before and After