The HPE NonStop Data Definition Language (DDL) dictionary is a specialized subsystem used to define and manage data objects for Enscribe files and translate those definitions into source code for various programming languages. It serves as a central repository for metadata, ensuring consistent data structures across applications written in C, COBOL, TAL, or TACL.
Program Summary
The DDL dictionary program functions as a metadata management tool. Key capabilities include:
Centralised Definition: Defines records, fields, and file attributes in a hierarchical structure.
Code Generation: Translates DDL definitions into language-specific source code (e.g., COBOL copybooks or C headers).
Dictionary Maintenance: Allows users to create, examine, and update dictionaries to reflect changes in data structures.
Interoperability: Modern tools like Ddl2Bean convert dictionary files into Java Beans or XML, enabling cross-language and cross-platform use.
Future Outlook
The future of HPE NonStop DDL focuses on modernisation and integration rather than replacement.
Data Virtualization: Integration with AI factories and object storage platforms to expose legacy metadata in open-table formats like Apache Iceberg.
API Centricity: Enhancements to the NonStop API Gateway will likely use DDL metadata to automate REST/JSON service orchestration.
Real-time Analytics: Native streaming of NonStop data into platforms like Kafka, using DDL definitions to map real-time changes into analytics-ready formats.
HPE NonStop PATHCOM is the interactive management interface for the Pathway transaction processing environment. It allows administrators to configure, monitor, and control PATHMON-governed objects such as serverclasses, TCPs (Terminal Control Processes), and links.
Historical Timeline: The Evolution of Pathway & PATHCOM
The history of PATHCOM is inseparable from the Tandem NonStop platform, which pioneered fault-tolerant Online Transaction Processing (OLTP).
The Tandem Era (1974 – 1997)
1974 – 1976: Tandem Computers is founded. The first NonStop I system ships in 1976.
1983: Tandem introduces Pathway software alongside the Transaction Monitoring Facility (TMF). This milestone removes the requirement for developers to manually code fault tolerance into applications, as the Pathway infrastructure (managed via PATHCOM) handles it automatically.
Early 1990s: The platform migrates from proprietary stack machines to MIPS RISC processors (TNS/R architecture). PATHCOM evolves to manage more complex distributed environments.
1994: Open System Services (OSS) is introduced, allowing NonStop to support a Unix-like POSIX environment.
2005: Migration from MIPS to Intel Itanium (Integrity NonStop) begins.
2010s: Pathway evolves into HPE NonStop Pathway with TS/MP (Transaction Services/Massive Parallelism), enabling near-linear scalability for massive OLTP workloads.
The Modern HPE Era (2014 – Present)
2014: NonStop X is introduced, migrating the architecture to Intel x86-64 processors.
2015: Hewlett-Packard splits; the platform continues under Hewlett Packard Enterprise (HPE).
2020 – 2024: Focus shifts toward virtualisation and hybrid cloud. Modern Pathway/TS environments now support massive scaling up to 24,480 cores in a single system image.
Summary of PATHCOM Functionality
Future of NonStop Pathway
HPE’s roadmap for NonStop focuses on integrating mission-critical reliability with modern data centre technologies:
Modernisation: Support for Kubernetes Helm deployments and cloud-native frameworks.
Hardware Advancements: New NS9 X5 and NS5 X5 platforms offer double the memory capacity and 2x faster system interconnects.
Open Integration: Continued emphasis on open application development environments and open-source frameworks.
Hybrid Cloud: Positioning NonStop as a key component of HPE GreenLake for mission-critical workloads in the cloud.
The HPE NonStop Spoolcom (Spooler Command Language) program is the administrative interface for managing the Spooler subsystem on HPE NonStop systems. It allows operators to configure, monitor, and control print jobs, collectors, and print processes.
Program Summary
Purpose: Used to define and manage spooler objects such as collectors, devices, and jobs.
Key Functions: Starting/stopping the spooler, modifying device attributes, and controlling job states (e.g., hold, release, delete).
Architecture: Operates within the Guardian environment, communicating with the Spooler supervisor process to maintain 24/7 fault-tolerant printing operations.
Historical Timeline by Era
1. The Tandem Era (1974–1997)
1976: Introduction of the Tandem NonStop system; basic spooling capabilities were essential for early OLTP (Online Transaction Processing).
1980s: The Spooler evolved to handle complex routing and multiple collectors to support growing enterprise needs.
1997: Spooler D41 released, providing stable management for the MIPS-based architecture.
2. The Compaq & Early HP Era (1997–2014)
1999–2000: Release of Spooler D46, enhancing device ownership and virtual device support.
2001–2002: Spooler D48 released during the transition to the HP Integrity NonStop (Itanium) platform.
2012: Major updates to Spooler D48 to support H01 and H02 RVUs, improving scalability for high-end systems.
3. The Modern HPE Era (2014–Present)
2014: NonStop X (x86-64) introduced. Spoolcom adapted to support the new architecture and virtualised environments.
2018–2020: Focus shifted toward modernised interfaces. While Spoolcom remains the CLI standard, graphical alternatives like MultiBatch began gaining traction for batch management.
2023–2024: Continued integration with HPE GreenLake and hybrid cloud models, ensuring spooling services are available in private cloud deployments.
Futures and Roadmap
Modernisation: HPE is pushing toward “modernisation through tradition,” which includes better integration of legacy tools like Spoolcom with modern DevSecOps and cloud-native frameworks.
Kernel-Level Threading (KLT): Future updates aim to leverage KLT to improve the performance and scale-up capabilities of management processes.
Data-Centric Security: Integration with security platforms like TAMUNIO for field-level tokenization ensures that printed data remains compliant with PCI DSS 4.0 and GDPR.
HPE NonStop Inspect is the primary symbolic, source-level debugger for applications running on the HPE NonStop (formerly Tandem) operating system. It allows developers to interactively control program execution, examine and change data variables, and debug complex multi-process applications in both the Guardian and Open System Services (OSS) environments.
Program Summary
The Inspect debugger family facilitates high-availability software development through several specialized versions:
Inspect (Legacy): A command-line tool for TNS, TNS/R, and TNS/E systems.
Native Inspect (eInspect/xInspect): Adapted from GDB for Itanium and x86 architectures; it provides a command-line interface with scripting capabilities.
Visual Inspect: A Windows-hosted GUI debugger that provides “point-and-click” efficiency for setting breakpoints and displaying variables.
NSDEE (Eclipse): Modern debugging integrated into the Eclipse-based development environment, supporting NonStop Application, Attach Process, and Snapshot debug configurations.
Historic Timeline by Era
The evolution of the NonStop debugger mirrors the platform’s hardware transitions over five decades.
The Tandem Era (1974 – 1997)
1974: Tandem Computers is founded; the platform begins with T/16 (NonStop I).
1980s:Inspect is introduced as the standard interactive debugger for the TNS (Tandem Network Strategy) CISC architecture.
Early 1990s: Migration to MIPS-based TNS/R systems; Inspect is updated to support RISC instruction sets and optimized compilers.
The Compaq & Early HP Era (1997 – 2014)
1997: Compaq acquires Tandem.
2002: HP acquires Compaq; migration to TNS/E (Intel Itanium) architecture begins.
2005 – 2010:Visual Inspect becomes a staple for developers seeking a GUI experience on Windows.
2013: Release of the Inspect H01 Manual, documenting full support for TNS/R and TNS/E concurrent debugging.
The Modern HPE Era (2014 – Present)
2014: Introduction of NonStop X (x86-64 architecture). Native Inspect (xInspect) is launched, based on GDB, to support the move away from Itanium.
2015: HPE is formed; focus shifts to the NonStop Development Environment for Eclipse (NSDEE).
2020 – 2024: Enhancements in NSDEE include improved OSS process handling and support for large-scale application debugging.
HPE’s roadmap for NonStop focuses on modernisation through tradition, ensuring that legacy tools like Inspect remain compatible while transitioning to cloud-native and virtualized environments.
Virtualized NonStop (vNS): Debugging tools are being adapted to work seamlessly within enterprise private clouds and HPE GreenLake consumption models.
Jackson Structured Programming (JSP) is a program design methodology developed by British software consultant Michael A. Jackson in the 1970s. It focuses on mapping the structure of a problem—specifically its data structures—directly onto the structure of the program used to solve it.
Overview of Jackson Structured Programming
JSP is designed to create programs that are easy to maintain and modify because the program’s control structure naturally handles the input and output data structures.
Core Principle: Requirement changes are typically minor tweaks to existing data structures. By aligning program structure with data structure, small changes to inputs or outputs translate into small, manageable changes in the code.
Methodology: The technique involves analyzing the structure of input files and output files, constructing diagrammatic representations of these, and then creating a program structure that handles both.
Key Constructs: JSP utilizes three basic structures for both data and programs, which can be visualized as a form of regular expression:
Sequence: A series of operations performed in order.
Iteration: The repetition of operations until a specific condition is met.
Selection: Choosing between different operations based on a condition.
Diagrams: JSP uses structure diagrams rather than flowcharts to represent the design, breaking down complex tasks into smaller, simpler parts.
Excerpts from my HND project which made use of Jackson Structured Programming (JSP) as part of the program design phase
Detailed Historical Timeline
Early Years (1960s–1974): Conceptualization and Founding
1960s: Michael A. Jackson works in data processing, encountering limitations in program reliability and seeking more systematic approaches to software design.
1968: Jackson contributes to the early modular programming movement, collaborating with other pioneers.
1970: Jackson leaves John Hoskyns & Company to found Michael Jackson Systems Limited, aimed at fully developing a new design methodology.
1971: JSP becomes the core product of Michael Jackson Systems Limited, offering consultancy and training services.
1974: The name “Jackson Structured Programming” is coined by a Swedish licensee of the company.
Established Method (1975–1979): Documentation and Adoption
1975: Jackson publishes “Principles of Program Design,” the definitive text documenting JSP.
1975: Michael Jackson Systems Ltd. begins offering software tools to support JSP design for COBOL programs.
1977: JSP is widely recognized and adopted in Europe, the US, and Asia.
Late 1970s: The UK government adopts JSP (under the name “SDM” – System Development Methodology) as its standard program design method.
Late 1970s: The World Health Organization adopts JSP as a standard for program specification.
Evolution into System Design (1980s): JSD
Early 1980s: Building on the principles of JSP, Jackson develops Jackson System Development (JSD) to address the design of entire information systems, not just individual programs.
1983: Jackson publishes “System Development,” formally introducing JSD.
1983-1989: JSD continues to evolve, with new features introduced in subsequent publications and manuals.
Maturity and Retrospective (1990s–Present)
1990s: Jackson develops the Problem Frames Approach, his third major methodology focusing on requirements analysis.
1997: Jackson receives the Stevens Award for Software Development Methods.
1998: Jackson receives the British Computer Society Lovelace Medal.
2001: At a conference, Jackson provides a retrospective analysis of JSP’s driving forces and its relevance to modern software engineering.
Present: While overshadowed by object-oriented and agile methods, JSP principles remain useful for programming “in the small” and handling specific batch processing or embedded software tasks.
Jackson Structured Programming JSP is a program design methodology, overview and timeline
Mark Whitfield is a highly experienced SC-cleared Senior IT Project Manager and Engagement Manager with over 30 years of experience in the software development lifecycle (SDLC), specializing in Agile and Waterfall delivery for financial, automotive, and public sector clients. He has a strong background in HP NonStop (Tandem) systems and currently works for Capgemini.
Mark Whitfield, Senior IT PM and Project templates author
1990–1994: The Software Partnership (Runcorn): Programmer specializing in electronic banking software (sp/ARCHITECT-BANK) on Tandem Computers.
1994–1995: Deluxe Data (formerly TSP): Lead Analyst/Programmer, focusing on software investigation, design, coding, and on-site installation for clients like TSB, Bank of Scotland, and Rabobank.
Development & Technical Specialization (1995–2013)
1995–2013: Insider Technologies Limited: Spent 18 years progressing from Senior Development Engineer to Project Manager for Strategic Technical Initiatives.
Key Roles: Managed Reflex 80:20 and Reflex ONE24 product development, technical pre-sales, and consultancy. Developed diagnostic software for monitoring payment systems (BASE24).
Notable Project: Managed a bid to replace legacy ATM tools at LloydsTSB (5000 ATMs) with Reflex ONE24.
Banking & Digital Project Management (2013–2016)
2013–2014: Wincor Nixdorf: Project Manager in the Professional Services Banking Division, managing a £5m+ work stream for Lloyds Banking Group’s Self-Service Software Replacement (SSSR) programme.
2014–2016: Betfred: Senior Digital Project Manager for the Online and Mobile Division, delivering payment gateways and sportsbooks for iOS, Android, and Windows.
Senior Engagement Management (2016–Present)
2016–Present: Capgemini UK: Engagement Project Manager responsible for delivering both Waterfall and Agile digital projects.
2016 (Approx.): Assigned to a UK-wide Air Traffic organization (NATS) for Apple iOS app delivery.
2018–2019: MuleSoft (Secondment): Served as a Delivery Manager for the Anypoint Platform.
Current Focus: Cloud Migration (Hybrid) of 130 apps for UK Government.
Agile Management: “Mark provided an excellent barrier between us (developers) and a difficult client…ensuring that we followed the agile principles” — Callum Marriage (Developer).
MuleSoft/Capgemini Engagement: “Customers loved him. His was extremely detailed oriented and understood the often-complex needs…never became flustered in high pressure situations” — Delivery Manager, MuleSoft.
Betfred (2015): “I would highly recommend Mark for his ability to successfully multi-task under significant pressure… [he] produced a very comprehensive handover document” — IT Compliance Analyst, Betfred.
Capgemini/JLR Project: “Mark was able to do a good planning, with the correct resources, on time delivery and with good relationship between stakeholders” — Head of Integration Development.
Mark Whitfield’s website (mark-whitfield.com) serves as a professional portfolio and resource hub for his 30+ year career as a SC-cleared Senior IT Project Manager. It offers over 200 editable project management templates for Agile, Waterfall, and PRINCE2 methodologies, alongside career insights and project experience.
Website & Content Overview
Project Management Resources: The site, often known as PROject Templates, provides downloadable templates for planning, scheduling (Gantt charts), project initiation (PID), and project control.
Methodology Focus: Resources are tailored for PRINCE2 (including Agile Scrum), and Agile/Waterfall delivery methods.
Career Portfolio: Features his work history as a Senior IT Project Manager, including roles at Capgemini, Betfred, and various financial institutions.
Technical Specialization: Highlights expertise in HP NonStop systems, digital projects, and payment/transaction systems.
Professional Background: Mentions his experience with major clients such as Jaguar Landrover, Heathrow, Royal Mail, and various banks.
The site is designed for project managers looking for templates to speed up project documentation and for clients looking to review his career accomplishments.
Senior IT Project Manager & Project Templates author – Mark Whitfield
Templates sold on this website are designed for Microsoft Office (Excel, Word, PowerPoint) and MS Project (MPP) and are used for tracking and planning software development lifecycle (SDLC) projects.
Template Breakdown
The templates, often sold in a bundle, include over 200+ editable items aimed at project delivery. Key components include:
Project Planning (MS Project & Excel): Detailed Waterfall project planners with Gantt views, Agile Sprint plans, and Plan on a Page (POaP) examples.
RAID Logs (Risk, Action, Issue, Dependency): Comprehensive Excel trackers for managing risks, issues, assumptions, and dependencies.
Financial & Resource Management: Project finance trackers (forecasts, actuals, variance) and resource trackers for tracking team members and costs.
This is a detailed, comprehensive historical timeline of project management methodologies, tracing the evolution from ancient practices to modern adaptive frameworks.
I. Pre-Modern Era (Before 1900): Foundation of Task Coordination
2570 BC (Great Pyramid of Giza): Completion of the pyramids, demonstrating early project organization with managers for each of the four faces, planning, and logistics.
208 BC (Great Wall of China): Construction of the Great Wall, involving massive workforce organization divided into soldiers, citizens, and criminals.
1850s (Transcontinental Railroad): US railroad projects requiring large-scale resource and schedule management.
1896 (Harmonogram): Karol Adamiecki developed the harmonogram, a predecessor to the Gantt chart (published in 1931).
II. Early Modern Era (1910s–1950s): The Scientific Management Era
This era brought “scientific management” to project control, focusing on efficiency and visualization.
1910s (Gantt Chart): Henry Gantt developed the Gantt chart, a visual tool for scheduling tasks over time.
1911 (Scientific Management): Frederick Taylor published The Principles of Scientific Management, focusing on efficiency and time-saving.
1931–1936 (Hoover Dam): One of the first large-scale applications of Gantt charts for complex scheduling.
1942–1945 (Manhattan Project): Development of the atomic bomb, creating a need for rapid, complex planning and large-scale team coordination.
III. The “Golden Age” of Project Management (1950s–1960s): Formal Methodologies
This era introduced mathematical models for managing complex, interdependent tasks.
1956 (AACE Formed): The American Association of Cost Engineers (now AACE International) was formed, specializing in cost control and scheduling.
1957 (Critical Path Method – CPM): Developed by Dupont Corporation to manage chemical plant maintenance shutdowns.
1958 (Program Evaluation and Review Technique – PERT): Created by the US Navy Special Projects Office for the Polaris missile submarine project to manage task time and risk.
1962 (Work Breakdown Structure – WBS): The US Department of Defense mandated the use of WBS for large, complex projects.
1965 (IPMA Founded): The International Project Management Association (IPMA) was launched, the world’s first project management association.
1969 (PMI Founded): The Project Management Institute (PMI) was launched to promote the profession, later developing the PMP certification.
IV. The “Silver Age” (1970s–1980s): Systems and Controls
1970s (Waterfall Introduction): While used informally earlier, the Waterfall methodology was formalized for software development in the 1970s, emphasizing sequential phases.
1975 (PROMPTII): Simpact Systems Ltd created PROMPTII, a methodology to handle cost overruns in computer projects, which later formed the basis of PRINCE.
1975 (Mythical Man-Month): Fred Brooks published his seminal work on software engineering project management.
1978 (Toyota Production System): Lean production and Kanban techniques, used in manufacturing, began to influence project workflow.
1984 (Theory of Constraints – TOC): Dr. Eliyahu Goldratt published The Goal, introducing the Theory of Constraints for managing constraints (bottlenecks).
1986 (Scrum): Takeuchi and Nonaka defined Scrum as a project management style for fast-paced development.
1987 (PMBOK Guide): The Project Management Institute published the first Project Management Body of Knowledge (PMBOK) white paper.
1989 (PRINCE): The UK government launched PRojects IN Controlled Environments (PRINCE), the standard for information systems projects.
V. Rebirth and Modern Era (1990s–2000s): Agile and Adaptive Methods
1994 (CHAOS Report): The Standish Group published the first report documenting high IT project failure rates.
1995 (Scrum Formalization): Jeff Sutherland and Ken Schwaber formally defined the Scrum framework.
1996 (PRINCE2): PRINCE was updated to PRINCE2 to become a generic, more flexible methodology applicable to all project types.
1997 (Critical Chain Project Management – CCPM): Eliyahu Goldratt invented CCPM, based on the Theory of Constraints.
1998 (PMBOK Standard): The American National Standards Institute (ANSI) recognized PMBOK as a standard.
2001 (Agile Manifesto): 17 software developers met to publish the Manifesto for Agile Software Development, prioritizing collaboration and adaptability over rigid plans.
2007 (Kanban for Software): David Anderson adopted Kanban for software development, focusing on visualizing work and limiting work-in-progress.
VI. The Contemporary Era (2010s–Present): Hybrid, AI, and Speed
2012 (ISO 21500): The International Organization for Standardization published ISO 21500:2012, “Guidance on Project Management”.
2017 (PMBOK 6th Ed & PRINCE2 Update): PMI introduced Agile/adaptive practices into PMBOK, while AXELOS released a more flexible PRINCE2.
2018 (PRINCE2 Agile): PRINCE2 Agile was launched to combine the governance of PRINCE2 with the flexibility of Agile.
2021 (PMBOK 7th Ed): A major shift in PMI standards, moving from process-based to principle-based, focusing on project outcomes.
2020s–Present (AI/Hybrid): Rise of AI-driven project management, automated reporting, and hybrid methodologies combining Waterfall stability with Agile speed.
Project Management Methodologies, historical timeline by era and year
Mark Whitfield is a highly experienced IT Senior Project Manager and Engagement Manager based in Manchester, UK, specializing in Agile Scrum, PRINCE2, and Waterfall methodologies. He holds a degree in Computing (1990) and has extensive experience in IT hardware solutions, financial services, and Aerospace & Defence.
Here is a comprehensive summary of his profile, with links based on the provided search data:
Professional Profile
Name: Mark Whitfield
Role: IT Senior Project Manager / Engagement Manager (SC Cleared)
Mark Whitfield is a highly experienced IT Project Manager, Senior Developer, and SC-cleared consultant with over 30 years of experience, specializing in HP NonStop (Tandem) systems, banking software, and digital transformation projects. He is currently an Engagement Project Manager at Capgemini.
Career Overview
Specialism: HP NonStop (Tandem) mainframes, BASE24, transaction monitoring, Agile/Waterfall methodologies.
1990: Graduated in Computing and started as a Programmer for The Software Partnership in Runcorn, specializing in sp/ARCHITECT-BANK on Tandem Computers.
1990-1994: Developed banking code for TSB, Bank of Scotland, Rabobank, and Girofon (Denmark).
1992: Worked on the Barclays Business Master II (BBM II) project in Knutsford.
1994: Company taken over by Deluxe Data (later FIS).
2. Insider Technologies & Monitoring Era (1995–2013)
1995–2013: Joined Insider Technologies Ltd as a Senior Development Engineer and Project Manager.
1995-2004: Developed monitoring/diagnostic software (Reflex 80:20, Reflex ONE24) for HP NonStop payment systems.
1997: Worked on projects for CRESTCo.
Early 2000s: Focused on HP NonStop transaction/payment monitoring for ATM/POS devices using ACI’s XPNET.
2005-2013: Managed first HP OpenView Operations Smart Plug-In certification for NonStop; designed XPERT24.
2011: Certified as a PRINCE2 Practitioner.
3. Banking Transformation & Consultancy Era (2013–2016)
2013–2014: Wincor Nixdorf UK – Worked as a Project Manager in Professional Services for the Banking Division.
2013-2014: Assigned to Lloyds Banking Group (LBG) for the Self-Service Software Replacement (SSSR) program (ATM estate upgrade).
2014–2016: Joined Betfred as an IT Project Manager in the gambling/casinos industry, delivering mobile/online payment gateways (iOS, Android).
4. Digital Transformation & Capgemini Era (2016–Present)
2016: Joined Capgemini UK as a client-facing Engagement Manager.
2016-2017: Led digital projects for automotive, local government, and aerospace sectors.
2017: Obtained Microsoft Excel Expert skills and Advanced Engagement Management certifications.
2018–2019: Augmented into MuleSoft as a Delivery Manager for the Anypoint Platform.
2022: Completed Microsoft Azure Fundamentals (AZ-900) certification.
2023–2024: Assigned to a UK Government account for a cloud migration of 130+ applications and the Fish Export Service (FES) project.
Key Qualifications
PRINCE2 Practitioner & Agile Scrum
ITIL Certified
SC Cleared (UK Government)
Technical Skills: C, C++, MS SQL, COBOL, TAL, Java, ASP.NET, HP NonStop
Extreme Programming (XP) is a prominent, disciplined Agile software development framework designed to improve software quality and responsiveness to changing customer requirements. Developed by Kent Beck in the mid-1990s, it focuses on taking beneficial engineering practices—such as pair programming, testing, and continuous integration—to “extreme” levels.
Project Management Summary: Core XP Components
XP differs from other Agile methods by focusing intensely on technical engineering practices alongside project management techniques.
Core Values: Communication, Simplicity, Feedback, Courage, and Respect.
Key Practices: Pair Programming, Test-Driven Development (TDD), Collective Ownership, Continuous Integration, Refactoring, and Small Releases.
Project Management Focus:
The Planning Game: Combines business priorities with technical estimates to determine what to build next.
Small Releases: Frequent, working software releases (often 1–2 weeks) to gather rapid customer feedback.
On-site Customer: A customer representative works with the team to provide instant feedback and clarify requirements.
Sustainable Pace: Limiting work weeks to 40 hours to avoid burnout and maintain quality.
Detailed Historical Timeline of XP
Era 1: Origins and The Chrysler C3 Project (1993–1996)
1993: Chrysler launches the Comprehensive Compensation System (C3) project to upgrade payroll software, which struggles for years.
March 1996:Kent Beck is brought in to lead the C3 project. To salvage the project, Beck starts encouraging team members to adopt a set of technical practices he developed based on his experiences.
1996:Ward Cunningham heavily influences the development of early XP concepts, particularly the “metaphor”.
1996: The project begins adopting daily meetings, pair programming, and TDD.
Era 2: Formalization and “Embracing Change” (1997–2000)
1997: Ron Jeffries is brought in to coach the C3 team, helping solidify the practices.
1998: The term “Extreme Programming” becomes widely discussed within the Smalltalk and Object-Oriented programming communities.
October 1999: Kent Beck publishes Extreme Programming Explained: Embrace Change, formally defining the framework.
February 2000: Daimler-Benz acquires Chrysler and cancels the C3 project after 7 years of work. Despite cancellation, the methodology proved that it could produce working, high-quality software, just not fast enough to overcome the legacy backlog.
Era 3: Rise of Agile and Expansion (2001–2005)
February 2001: Kent Beck and Ron Jeffries are among the 17 developers who draft the Manifesto for Agile Software Development at Snowbird, Utah. XP is recognized as one of the foundational “Agile” methods.
2001: The first Agile Alliance conference is held. XP is considered the dominant agile methodology during this period.
2002–2003: XP gains global popularity; numerous books are published expanding on the core 12 practices.
2004: The second edition of Extreme Programming Explained is released, shifting focus from 12 rigid practices to more adaptive principles.
Era 4: Integration with DevOps and Continuous Delivery (2006–Present)
2006-2010: As Scrum gains popularity for general project management, XP practices like TDD and Pair Programming become the “standard” technical practices for high-performing teams, often blended with Scrum (ScrumXP).
2010s: The rise of DevOps and continuous delivery, which inherently requires XP practices like CI/CD (Continuous Integration/Continuous Delivery).
2020-2026: While fewer companies identify strictly as doing “XP,” its technical practices are considered essential to modern software development and are integrated into almost all Agile methodologies to ensure quality and speed.
Extreme Programming XP project management summary and detailed historical timeline by era and year
PROject Templates 