Category: Information Technology, IT

Microsoft Project Timeline, Development History Overview

Microsoft Project has evolved from a DOS-based tool in the 1980s into a cloud-integrated platform. Its “Timeline” feature specifically has transitioned from a simple static view to a multi-layered, interactive reporting tool. 

Template included in package – see website banner

Timeline Feature Development History

  • Early Era (1984–2007): For decades, the “timeline” was synonymous with the Gantt Chart. Users had to rely on complex print-outs or third-party tools to create high-level summaries for executives.
  • The dedicated Timeline View (2010): Microsoft introduced a native Timeline view in Project 2010, allowing users to cherry-pick specific tasks and milestones to display on a single horizontal bar.
  • Multi-Timeline Support (2016): Project 2016 expanded this by allowing multiple timeline bars in a single view. This enabled managers to represent different project phases or workstreams with independent start and end dates.
  • Cloud & Web Integration (2019–Present): With the launch of Project for the web, timelines became more interactive, supporting drag-and-drop adjustments and real-time co-authoring.
  • Task History Tracking (2023): Microsoft added a Task History pane to the web version, allowing users to see a chronological log of changes to specific timeline items. 

Key Components of a Modern MS Project Timeline

Templates included in download bundle – see website banner
  • Gantt-Style Visualization: Displays tasks as horizontal bars against a calendar timescale.
  • Milestones & Callouts: Important dates appear as diamonds or labels that can be dragged above or below the main bar to avoid clutter.
  • Dependencies: Visual links between tasks that illustrate the sequence of work and the Critical Path.
  • Copy for Presentation: A dedicated formatting tool that allows users to export the timeline directly to Microsoft PowerPoint or email at various sizes (Small, Medium, Full Size). 

Future Outlook

Template included in download bundle – see website banner

Microsoft has announced that Project Online will be officially retired on 30 September 2026, with development focus shifting entirely to the new Microsoft Planner and Project for the web ecosystem.

Microsoft Project Timeline, Development History Overview

ITSM IT Service Management Framework Overview

ITSM IT Service Management Framework Overview

Mark Whitfield, Senior IT Project Manager – Training Timeline

Mark Whitfield, a Senior Project Manager currently at Capgemini UK, has documented a detailed IT and Management training timeline spanning over three decades: 

Technical Training Timeline

  • July 2024: Microsoft Excel Refresher 2024 (Udemy)
  • July 2014: Advanced Microsoft Excel 2013
  • July 2011: Google Android programming (Eclipse IDE)
  • June 2011: Java programming (Eclipse IDE)
  • November 2009: HP NonStop Security (SRM) & PayShield 9000
  • July 2009: Business Intelligence Reporting Tools (BIRT)
  • March 2009: Querying MS SQL 2000 with Transact SQL
  • January 2007: Developing Web Apps using Visual Studio .NET
  • March 1997: C / C++ Programming (Comtec)
  • June – Nov 1995: HP NonStop Performance, Analysis, Tuning & TAL Programming

Management & Methodology Training

  • February 2022: AZ-900 Microsoft Certified Azure Fundamentals
  • November 2019: Resilience and Peak Performance (Capgemini)
  • November 2017: Advanced Engagement Management Certification Level 2
  • January 2012: ITIL Foundation Course
  • May 2011: PRINCE2 Practitioner, Foundation, and Agile Scrum Course (RADTAC)
  • January 2006: PRINCE2 Project Management Foundation
  • February 2000: Successful Project Management (SkillPath)
  • October 1999: Managing Multiple Projects, Objectives and Deadlines 

Foundational Education

  • 1988 – 1990: BTEC HND Computing (Distinction) at Bolton Institute of Higher Education.
  • 1985 – 1988: A-Levels in English, Biology, and Computing at Leigh College. 

Mark Whitfield, Senior IT Project Manager – Training Timeline

sp/ARCHITECT-BANK module – development in Runcorn, Cheshire by The Software Partnership

The software known as sp/ARCHITECT (specifically the sp/ARCHITECT-BANK module) has a timeline tied to its development in Runcorn, Cheshire, by a firm originally called The Software Partnership. 

Company & Product Timeline

  • Mid-1980s: The Software Partnership is co-founded by Nigel Walsh.
  • 1989: The company begins significant operations in Runcorn, initially at Wingate Drive (Timperley) and later moving to Norton House in Crowngate.
  • 1990–1994: Development period for sp/ARCHITECT in Runcorn. The software was a banking system used by major institutions including TSB, Bank of Scotland, and Rabobank.
  • 1992: The firm relocates its Runcorn base to Wingate House on Northway.
  • 1994: The Software Partnership is acquired by the American company Deluxe Electronic Payment Systems (a division of Deluxe Corporation).
  • Post-1994: Following the acquisition, the entity operated as Deluxe Data International Operations.
  • Later Transitions: The lineage of the Runcorn operations eventually merged into larger fintech entities, including eFunds, EFD, and ultimately FIS. 
Deluxe Data, Wingate House
The Software Partnership, Norton House

sp/ARCHITECT-BANK module – development in Runcorn, Cheshire by The Software Partnership

TSP / Deluxe Data : 1990 – 1995

Project Management Templates Bundle FREE Upgrades

Mark Whitfield’s project management templates offer a range of timeline and planning views designed for Agile, Waterfall, and PRINCE2 delivery. These templates typically include a high-level Plan on a Page (POaP) and detailed Microsoft Project (MPP) or Excel schedules. 

Example Plan on a Page POaP

Timeline & Planning Views

  • Plan on a Page (POaP): A high-level summary view (often in PowerPoint or Excel) used to communicate key phases and milestones to stakeholders without the clutter of a full Gantt chart.
  • Detailed Gantt Charts: Provided in both Microsoft Project (MPP) and Excel, these timelines include task dependencies, resource allocations, and critical path tracking.
  • Agile Sprint Timelines: Specialized views for tracking 2–4 week sprints, daily stand-ups, and sprint retrospectives within a broader project framework.
  • SDLC Progression: The templates are often structured around a typical Software Development Life-cycle (SDLC), moving from Inception to Transition and Early Live Support (ELS). 

Key Timeline Components

The templates are pre-configured with several essential timeline elements: 

  1. Project Start & End Dates: Easily adjustable fields that automatically update durations and downstream tasks.
  2. Milestones & Gateways: Visual markers for critical sign-off points and delivery stages.
  3. Task Dependencies: Pre-built links that show how delays in one area (e.g., hardware delivery) impact the overall project finish date.
  4. Resource View: Timelines integrated with resource calendars to account for holidays and leave. 

You can find the full package of over 200 editable templates, which include these timeline views and RAID logs, on Mark Whitfield’s official website or via his Etsy store. 

Buy Premium Programme & Project Management Delivery Templates – plus all Upgrades and Additions are FREE

Project Management Templates Bundle FREE Upgrades

HPE NonStop Tandem Timeline History

HPE NonStop (originally Tandem) has a nearly 50-year history as the gold standard for fault-tolerant, “always-on” computing. Originally developed by Tandem Computers to eliminate single points of failure, the platform has survived through several major corporate acquisitions while evolving its underlying processor architecture. 

Founding and The Tandem Era (1974–1997)

The “NonStop” architecture was born from the idea that a single hardware failure should never crash a system.

  • 1974: Tandem Computers is founded by Jimmy Treybig and three former HP engineers.
  • 1976: The first Tandem/16 (later NonStop I) is shipped to Citibank. It featured a “shared-nothing” architecture where each CPU had its own memory and copy of the Guardian OS.
  • 1981: NonStop II is released, introducing 32-bit addressing to support larger applications.
  • 1983: The NonStop TXP and Pathway software are introduced. Pathway revolutionized the platform by allowing programmers to write fault-tolerant apps without manually coding “checkpoints”.
  • 1986: NonStop SQL is launched, the first fault-tolerant relational database.
  • 1989: NonStop Cyclone arrives, a high-end mainframe-class system.
  • 1991–1993: Transition to MIPS RISC processors begins with the Cyclone/R and the Himalaya K-series. 

Corporate Acquisitions and Transition (1997–2014)

The platform changed hands twice in five years, but the mission-critical nature of the technology kept it alive.

  • 1997: Compaq acquires Tandem for $3 billion to bolster its enterprise server offerings.
  • 1997: The Himalaya S-Series introduces ServerNet, a high-speed interconnect that later evolved into the industry-standard InfiniBand.
  • 2002: HP merges with Compaq, bringing the NonStop line under Hewlett-Packard.
  • 2005: NonStop i (Integrity) is launched, transitioning from MIPS to Intel Itanium processors. 

The Modern HPE Era (2015–Present)

Today, the platform focuses on integrating with modern data centre standards like x86 and cloud-native virtualisation. 

  • 2014–2015: NonStop X (TNS/X) is introduced, moving the architecture to industry-standard Intel x86-64 processors.
  • 2015: HP splits; the server line becomes part of Hewlett Packard Enterprise (HPE).
  • 2017: Virtualised NonStop (vNS) is released, allowing the software stack to run in virtual machines (KVM/OpenStack).
  • 2020: HPE officially ends sales of Itanium-based systems, completing the transition to x86.
  • 2024: The platform celebrates its 50th anniversary, continuing to power the majority of the world’s ATM and credit card transactions. 

HPE NonStop Tandem Timeline History

Insider Tech : 1995 – 2013
My Career in HPE NonStop Tandem, 1995 thru 2013
TSP / Deluxe Data : 1990 – 1995
My Career in HPE NonStop Tandem, 1990 thru 1995

Agile Scrum Timeline and Overview

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:

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Agile Scrum Timeline and Overview

PRINCE2 – PRojects IN Controlled Environments – Timeline

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.
  • 1989: The Birth of PRINCE – The UK’s Central Computer and Telecommunications Agency (CCTA) licensed PROMPT, renaming it PRINCE (originally “PROMPT II IN the CCTA Environment”).
  • 1996: PRINCE2 Launch – Developed with input from 150 European organisations, PRINCE2 was released as a generic, scalable framework suitable for any industry.
  • 2000–2013: Ownership Shifts – Ownership moved from the CCTA to the Office of Government Commerce (OGC) in 2000, then to AXELOS Ltd (a joint venture) in 2013.
  • 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: 

  1. Pre-Project: Starting up a Project (SU)
    • Ensures the project is viable and worthwhile.
    • Key Output: Project Brief.
  2. Initiation: Initiating a Project (IP)
  3. High-Level Oversight: Directing a Project (DP)
    • An ongoing process where the Project Board provides guidance and makes key decisions without managing day-to-day tasks.
  4. Day-to-Day Management: Controlling a Stage (CS)
    • The Project Manager monitors work, manages risks, and reports progress for each individual stage.
  5. Technical Delivery: Managing Product Delivery (MP)
    • The Team Manager ensures products (deliverables) are created, tested, and handed over according to specifications.
  6. Transition: Managing a Stage Boundary (SB)
  7. Finalisation: Closing a Project (CP)
    • The formal decommissioning of the project, ensuring all products are accepted and lessons are documented. 

PRINCE2 – PRojects IN Controlled Environments