In Scrum, the “timeline” is typically structured as a repeatable, time-boxed cycle known as a Sprint, which usually lasts between one and four weeks. Each sprint follows a strict sequence of “ceremonies” designed to ensure constant delivery and feedback.
The Standard Sprint Timeline (2-Week Example)
The following is a common chronological breakdown of a typical 10-day (two-week) sprint:
Day 1: Sprint Planning
Goal: Define what will be delivered and how.
Activity: The Product Owner presents prioritized items from the Product Backlog. The team selects items to move into the Sprint Backlog.
Days 2–9: Development & Daily Scrum
Development: The team works in parallel on design, coding, and testing.
Daily Scrum: A 15-minute “stand-up” held every morning. Team members sync on progress and identify blockers.
Ongoing: Backlog Refinement
Goal: Prepare for future sprints.
Activity: The team reviews upcoming backlog items to ensure they are “ready” for the next planning session.
Day 10: Sprint Review & Retrospective
Sprint Review: A demo for stakeholders to show the Product Increment (completed work) and gather feedback.
Sprint Retrospective: An internal meeting where the team reflects on their process to improve for the next cycle.
Strategic Project Phases
While the sprint is the heart of execution, a broader Agile project often follows these foundational stages:
Concept/Ideation: Defining project vision, high-level requirements, and initial scope.
Inception: Building the team, setting up architecture, and creating a mock-up.
Construction (Iterative Sprints): The primary execution phase consisting of multiple back-to-back sprints.
Release/Deployment: Final testing, security checks, and launching the product increment to production.
Maintenance & Operations: Ongoing support, bug fixes, and incorporating user feedback into new sprints.
Time Allocation (The 15/10/5 Rule)
For a standard sprint, many teams use a percentage-based guide to manage ceremony time:
15% for Sprint Planning.
10% for Sprint Review.
5% for Sprint Retrospective.
For more hands-on planning, tools like the Wrike Sprint Template or Jira Timelines can help visualize these cycles across a long-term roadmap.
PRINCE2 (PRojects IN Controlled Environments) has evolved from a rigid, IT-specific framework into a globally recognised, flexible project management standard.
Historical Evolution Timeline
1975: PROMPT Origins – Simpact Systems Ltd developed PROMPT (Project Resource Organisation Management and Planning Techniques) to address IT project overruns.
1996: PRINCE2 Launch – Developed with input from 150 European organisations, PRINCE2 was released as a generic, scalable framework suitable for any industry.
2009: Major “Refresh” – Introduced the seven core principles and made the method more customisable.
2017: 6th Edition Update – Formerly known as the “2017 Update,” this version focused heavily on scalability and tailoring to specific project needs.
2021–Present: PeopleCert Era – PeopleCert acquired AXELOS in 2021. In 2023, PRINCE2 7 was launched, introducing a greater emphasis on people management and sustainability.
Comprehensive Project Timeline Breakdown
A standard PRINCE2 project follows a lifecycle defined by seven processes:
The technical timeline for BASE24 and its core networking component, XPNET, reflects the evolution of high-availability payment switching on HP NonStop (Tandem) systems.
Technical Evolution Timeline
1980s: The Foundation
BASE24 Release: Originally developed by Applied Communications Inc. (now ACI Worldwide), BASE24 was built for the Tandem Guardian operating system.
XPNET Introduction: Developed as the Message-Oriented Middleware (MOM) to handle all transaction routing and communications. It introduced a multi-node architecture allowing different “satellite” processes (ATM, POS, Host) to communicate.
1990s: Scale and Maturity
Classic Era: BASE24 “Classic” became the industry standard for ATM and POS switching.
XPNET 3.x: Enhanced to support larger networks and more complex auditing through NCPCOM.
Language & DB: The system relied on TAL (Tandem Application Language), COBOL, and the Enscribe database.
2000s: The Shift to BASE24-eps
2003–2005: ACI introduced BASE24-eps (Electronic Payment Systems). This was a re-architecture using C++ and Java to provide platform independence.
XPNET 4.1: Released to support the transition, adding features like Common Transport Subsystem (CTS) for better Pathway integration and support for external processes.
z/OS Support: By 2009, BASE24-eps was fully ported to IBM z/OS using CICS and VSAM.
2010s – Present: Modernisation & Cloud
2014–2017: Continued updates to BASE24 Classic R6.0, maintaining its relevance for legacy users.
Cloud Enablement: Recent versions of BASE24-eps focus on REST API integration via tools like LightWave, allowing legacy XPNET paths to be exposed as web services.
Active/Active Environments: Modern implementations focus on “continuous availability” using GoldenGate for data replication between sites.
Key Technical Components
NMM (Network Management Module): The core process of XPNET that manages the configuration of lines, stations, and links.
LCONF: The Logical Network Configuration File used by XPNET to define how messages route between processes.
Auditing: XPNET provides the primary transaction auditing mechanism, which is still utilized by both Classic and eps versions.
The timeline of HPE NonStop ViewPoint (and its modern successor, Web ViewPoint) reflects the evolution of NonStop systems from Tandem’s fault-tolerant beginnings to Hewlett Packard Enterprise’s modern cloud-integrated management.
Detailed History Timeline
Pre-2000: Legacy ViewPoint
Originally developed for the Tandem NonStop platform to provide a graphical operations interface for monitoring system status and events.
Featured early support for DSM/PM (Distributed Systems Management/Performance Monitor) and event management through primary and alternate event logs.
2003–2005: Transition to Web ViewPoint
September 2003: Version 4 AAD released as an early iteration of the web-based management tool.
May–October 2004: Progressive upgrades (Versions 5.0 and 5 AAF) introduced refined management capabilities for S-Series servers.
March 2005: Version 5 AAG released, consolidating features for the S-Series.
November 2005:Web ViewPoint for Itanium (Version H01AAI) launched, marking the shift to the Intel Itanium-based Integrity NonStop architecture.
2013–2015: The x86 Revolution & Virtualization
2014: Support for Intel x86 architecture was officially announced, leading to the launch of NonStop X.
Evolution to Web ViewPoint Enterprise (WVP E): The platform evolved into an automated management product, eventually adding integration with cloud-based analytics like HPE Remote Analyst.
2018–Present: Modern Hybrid Cloud Era
L-Series Support: Continued updates provided support for L-Series operating environments and enhanced security monitoring.
2023–2024: Recent developments focus on Web ViewPoint Enterprise, featuring a global configuration platform and enhanced historical data capture through integrations like Sentinel for HPE NonStop.
For more specific documentation, you can browse the HPE NonStop Manuals on the HPE Support Center.
MultiBatch is a high-performance, mainframe-class workload automation and batch scheduling solution specifically designed for the HPE NonStop parallel architecture (formerly Tandem). It is developed by ETI-NET (formerly by Insider Technologies) to manage complex batch schedules across both NonStop Guardian and OSS environments.
Key Milestones and Timeline
1976 – Tandem NonStop Origins: The foundation for these systems was established with the introduction of the first NonStop servers by Tandem Computers.
2017 – MultiBatch Release: Insider Technologies announced an updated release of MultiBatch to enhance off-line processing flows for the HPE NonStop arena.
2019 – GUI and Monitoring Enhancements: Real-time status monitoring through a GUI interface was highlighted as a major differentiator, allowing users to visually track complex batch schedules like RTGS and securities settlements.
2020 – Business Benefits Proven: Case studies demonstrated that MultiBatch could reduce online-dealing batch times by up to 6 hours per day.
2022 – MultiBatch 10 for TBC:MultiBatch 10 was presented at the NonStop Technical Boot Camp (TBC), positioning it as the only workload manager for NonStop built on continuous innovation principles.
2024 – Modernization and Security: Recent updates focused on securing and modernizing the platform for high-performance multitasking.
Core Functionality
Parallel Execution: Supports batch schedules that run concurrently across multiple nodes, leveraging the NonStop architecture for high availability.
Hybrid Support: Seamlessly integrates both Guardian and OSS jobs within a single schedule.
Batch Prediction: Uses historical metrics in a status database to predict schedule completion times based on average and maximum elapsed run times.
Simplified Migration: Unlike NetBatch, it allows for extracting and inserting schedules between environments (e.g., test to production) without TACL changes.
MultiBatch is a high-performance, mainframe-class workload automation and batch scheduling solution
Mark Whitfield, an SC cleared, Senior IT Project Manager and Engagement Manager, spans over 30 years and transitions from specialized banking software development to high-level project leadership and cloud migrations.
Professional Career Timeline
1990 – 1994:Programmer at The Software Partnership (later Deluxe Data). Developed electronic banking software (sp/ARCHITECT-BANK) on Tandem Computers (now HPE NonStop) for major banks like TSB and Bank of Scotland.
1994 – 1995:Lead Analyst at Deluxe Data International, continuing support and development for banking customer systems.
1995 – 2013: Project Manager of Strategic Technical Initiatives at Insider Technologies Limited. Oversaw projects involving Reflex 80:20, Sentra development, and corporate website authoring.
2013 – 2014: Project Manager (Banking Division) at Wincor Nixdorf Limited, focusing on professional services for the banking sector.
2014 – 2016: Senior Digital Project Manager at Betfred Limited, managing the Online and Mobile Division.
Betfred’s journey from a single shop in Salford to a global betting powerhouse is marked by bold innovations and high-profile acquisitions.
Historical Timeline
1967: Brothers Fred and Peter Done open their first betting shop in Salford, Greater Manchester, using winnings from a bet on England to win the 1966 World Cup.
1984: Launch of the Lucky 15 bet, a major industry innovation that remains popular today.
1997: The company expands to over 100 shops.
1998: Fred Done becomes the first bookmaker to pay out early, paying on Manchester United to win the Premier League (only for Arsenal to win the title instead).
1999: First major acquisition, purchasing 40 shops from the Demmy Racing Group.
2004: The business is officially rebranded to Betfred. The company also launches its online betting site this year.
2006: Betfred launches one of the industry’s first mobile betting platforms.
2011: Wins the auction to buy The Tote from the UK government for £265 million.
2016: Acquires 322 shops from Ladbrokes and Coral following their merger.
2021: Fred Done steps down as CEO to become Chairman, with Joanne Whittaker taking over the CEO role.
2024–2026: Significant global expansion, establishing a presence in South Africa and the United States, though later scaling back some US online operations in late 2025.
Operational Timelines (Payment & Payouts)
If you are looking for current service timelines for transactions, here are the standard processing windows as of February 2026:
Withdrawal Processing: Betfred aims to approve requests within 48 hours.
Fastest Methods: Visa Direct and certain E-wallets (PayPal, Skrill) often arrive within 4 to 6 hours.
Standard Methods: Bank transfers typically take 2 to 5 working days.
Free Bet Credit: Usually credited within 10 hours of a qualifying bet being settled.
Wincor Nixdorf’s journey spans from a mid-century German startup to its 2016 merger with Diebold, forming a global leader in banking and retail technology.
Capgemini’s evolution from a small French startup to a global IT leader is marked by strategic mergers and a shift toward high-growth technologies like AI.
Corporate History Timeline
1967: Serge Kampf founded Sogeti in Grenoble, France, focusing on enterprise management and data processing.
1973–1975: Through hostile takeovers and mergers with CAP and Gemini Computer Systems, the group became CAP Gemini Sogeti.
1985–1988: The company was listed on the Paris Stock Exchange (1985) and entered the CAC 40 index (1988).
1996: The name was simplified to Cap Gemini, and a new logo was launched.
2000: Acquired Ernst & Young Consulting for $11 billion, expanding its global reach, especially in North America.
2004: The brand officially became Capgemini to reflect a unified global identity.
2015: Acquired iGate for $4 billion, making North America its largest market.
2019–2021: Acquired Altran (2019), later rebranded as Capgemini Engineering (2021), to dominate the engineering and R&D services sector.
2024–2025: The strategic focus shifted to AI. In July 2025, Capgemini announced a €3.3 billion deal to acquire WNS Global Services to bolster its agentic AI and intelligent operations.
Recruitment & Career Timelines
The hiring process typically follows this path:
Hiring Process: Usually takes a few weeks, involving application screening, multiple interview rounds (technical and HR), and background verification.
Graduate/Mass Hiring: Often conducted via the Superset platform, where status updates like “offered” appear roughly a week after interviews.
Graduate Programme: The Accelerate Programme (UK) spans approximately 21 months, starting with a 3-month business overview followed by 18 months in a specific pathway academy.
The Software Partnership (TSP) was a Runcorn-based software house co-founded by Nigel Walsh in the mid-1980s. Specialising in on-line banking systems for Tandem and UNIX platforms, the company underwent several acquisitions that integrated its technology into global financial services.
Corporate Timeline
Mid-1980s: Founded as The Software Partnership.
1990: Initial operations were based at Wingate Drive in Timperley before moving to Norton House in Crowngate, Runcorn.
1992: Relocated to Wingate House on Northway, Runcorn.
1994: Acquired by the American firm Deluxe Electronic Payment Systems (a subsidiary of Deluxe Corporation).
2000: The company transitioned to EFD eFunds.
2007: Became part of Fidelity National Information Services (FIS), eventually moving operations to Daresbury Park in Warrington.
Key Products
The company’s primary legacy is the development of sp/ARCHITECT-BANK, a software suite designed for secure card management and electronic transaction processing. This technology became a foundational component for the secure payment systems later managed by Deluxe Data and FIS.
The Software Partnership, Norton House, Crowngate, Runcorn, CheshireThe Software Partnership (TSP) was a Runcorn-based software houseDeluxe Data International Operations, Wingate House, Northway
Insider Technologies Limited is a UK-based software and services company founded in 1989 that specialises in 24×7 mission-critical systems, primarily for the financial, government, and defence sectors.
Key Historical Timeline
1989: Foundation. The company was incorporated on 27 February 1989. It was established in Manchester, England, by IT industry veterans.
1995–2013: Growth & Partnerships.
Became a significant HP Partner, developing solutions for the HP NonStop platform (formerly Tandem Computers).
Expanded its client base to include major institutions such as the Bank of England, Royal Bank of Scotland, and Euroclear.
2002: Training Platform Launch. Founded its interactive systems training platform, which eventually utilised its patented Cloning Technology.
2015: Leadership Transition. In October 2015, there was a major change in the board with the termination of appointments for directors Paul Cashmore, Richard Launder, and Anthony Mowatt, and the appointment of Andrew Donald Hall as a director.
2016–2017: Relocation. The company moved its registered office to 4th Floor, 2 City Approach in Eccles, Manchester, where it remains today.
2019: 30th Anniversary. Celebrated 30 years of operations, highlighting its long-term stability in the NonStop business technology community.
2020–2021: Recent Restructuring. Transitioned its ownership structure under Insider Technologies (Holdings) Limited.
2025: Current Status.
Now operates as part of the PartnerOne group, a global family of mission-critical software companies.
Continues as a Microsoft Gold Partner for Application Development.
Recent board changes include the appointment of Andrew Donald Hall and Jonathan Dionne as directors in late 2025.
Core Product Evolution
Reflex & MultiBatch: Software for business-critical 24×7 systems.
Sentra & RTLX Reactor: Monitoring and tracking products for Windows, Linux, and Unix platforms.
Mission-Critical Support: Provides 24×7 technical support for high-stakes payment and messaging systems.
The institution now known as the University of Greater Manchester (formerly the University of Bolton) has a history spanning over 200 years. Below is the timeline of its evolution from a local mechanics’ institute to a modern university.
1892: The new Bolton Technical School opens to accommodate growing student numbers.
1926: The Technical School is expanded and renamed Bolton Technical College.
1952: A major new building for the Technical College opens on Manchester Road.
The “Bolton Institute” Era (1964–2003)
1964: The technical college separates to establish the Bolton Institute of Technology (BIT).
1970: New facilities on Deane Road are inaugurated by Princess Margaret.
1982: A merger with the Bolton College of Education (Technical) creates the Bolton Institute of Higher Education (BIHE).
1991–1995: The institute expands its capabilities, gaining the authority to confer both taught and research degrees.
Bolton Institute of Higher Education (BIHE) before the rebuild to the university building below.
University Status and Recent History (2004–Present)
2004: BIHE achieves university status, becoming the University of Bolton.
2005–2010: Significant leadership changes occur, including the appointment of Professor George E. Holmes as Vice-Chancellor and Baroness Morris of Bolton as the first Chancellor.
My final year project consisted of an ORACLE SQL-forms designed GUI interface running under an MS-DOS operating system. The GUI interface provided insert, update, delete and transaction rollback facilities for recording information about students attending courses at BIHE, along with their module assignment and exam result details. The student data was held in an ORACLE SQL database set-up on a PC local to the application.
HPE NonStop (formerly Tandem) represents a line of fault-tolerant, high-availability servers designed for 24/7, zero-downtime operations. Originally created by Tandem Computers in 1974, the architecture is now owned by Hewlett Packard Enterprise (HPE) and supports mission-critical workloads like banking and finance.
Key Aspects of HPE NonStop (Tandem):
Continuous Availability: Designed to eliminate single points of failure with 100% fault tolerance.
Architecture: Initially used a proprietary Tandem T/16 design; modern systems are based on HPE Integrity/x86 architectures.
Operating System: Traditionally runs the Guardian OS, which handles the system’s specialized, continuous processing capabilities.
Evolution: Founded by James Treybig in 1974, Tandem was acquired by Compaq in 1997, which then merged with HP in 2002.
Applications: Ideal for transactional applications requiring strict data integrity and real-time processing.
Modern Platforms: Current systems include HPE NonStop Compute NS9 X5 and NS5 X5.
The systems are still widely used today for mission-critical applications that cannot afford to be offline.
HPE NonStop (formerly Tandem) represents a line of fault-tolerant, high-availability servers.