Techniques for Time Management Overview

Techniques for Time Management Overview

World’s Tallest Buildings Timeline by Era Overview

The timeline of the world’s tallest buildings has evolved from ancient stone monuments to modern steel and concrete megastructures. Historically, the title has shifted from religious and funerary structures in Egypt and Europe to the corporate skyscrapers of North America, and most recently, to the massive mixed-use towers of Asia and the Middle East. 

Ancient & Medieval Era (Spiritual & Funerary)

For millennia, the tallest structures were largely pyramids and cathedrals, often holding records for centuries. 

  • c. 2570 BC – 1311 AD: Great Pyramid of Giza (Egypt) – 146.6m. Held the record for over 3,800 years.
  • 1311 – 1548: Lincoln Cathedral (England) – 160m. The first structure to surpass the Great Pyramid.
  • 1548 – 1884: European Cathedrals (Various) – Following the collapse of Lincoln’s spire, several cathedrals held the title, including St. Mary’s Church (151m) and Cologne Cathedral (157m). 

The Rise of Modern Structures (1884–1930) 

The Industrial Revolution introduced steel frames and safety elevators, moving the “race to the sky” to the United States. 

  • 1884 – 1889: Washington Monument (USA) – 169m. The world’s tallest all-stone structure.
  • 1889 – 1930: Eiffel Tower (France) – 312m. Nearly doubled the previous record; it was the first structure to exceed 300 metres.
  • 1894 – 1908: Philadelphia City Hall (USA) – 167m. Often cited as the first modern building to hold the title. 

The “Golden Age” of NYC Skyscrapers (1930–1974)

A fierce competition in New York City led to rapid record-breaking. 

  • 1930: Chrysler Building – 319m. The first building to surpass 1,000 feet.
  • 1931 – 1970: Empire State Building – 381m. Held the record for 40 years and was the first building with over 100 stories.
  • 1970 – 1973: World Trade Center (North Tower) – 417m. Briefly the world’s tallest before being surpassed by Chicago. 

The Contemporary Era (1974–Present)

The record moved from the US to Asia and the Middle East as construction technology advanced. 

  • 1974 – 1998: Sears Tower (Willis Tower) (USA) – 442m. Held the record for 25 years.
  • 1998 – 2004: Petronas Towers (Malaysia) – 452m. The first time the record left the US in a century.
  • 2004 – 2010: Taipei 101 (Taiwan) – 508m. The first building to reach the 500-metre mark.
  • 2010 – Present: Burj Khalifa (UAE) – 828m. Currently the world’s tallest building, shattered previous records by over 300 metres.
  • 2024: Merdeka 118 (Malaysia) – 678.9m. While not the tallest overall, it was completed in 2024 as the second-tallest building in the world.

World’s Tallest Buildings Timeline by Era Overview

Golf Historical Timeline Overview

The history of golf is broadly categorised into five distinct eras that track its evolution from a forbidden Scottish pastime to a multi-billion dollar global industry. 

1. The Foundation Years (Pre-1400s – 1899)

This era established the basic rules, the 18-hole standard, and the first major championships. 

  • 1457: King James II of Scotland bans golf and football because they distract young men from archery and military training.
  • 1502: King James IV lifts the ban and becomes a golfer himself, leading to the sport’s popularity among royalty.
  • 1744: The first official golf club, the Honourable Company of Edinburgh Golfers, is formed and establishes the first 13 rules of golf.
  • 1764: The Old Course at St Andrews reduces its round from 22 holes to 18 holes, setting the global standard for course length.
  • 1848: The “Guttie” ball (made of gutta-percha) is introduced, making the game more affordable and durable than the original feather-filled leather balls.
  • 1860: The first Open Championship (British Open) is held at Prestwick, won by Willie Park Snr.
  • 1894: The United States Golf Association (USGA) is founded to govern the sport in America.
  • 1895: The first U.S. Open and U.S. Women’s Amateur championships are held. 

2. The Golden Era (1900 – 1945)

This period saw the rise of legendary players, the formalisation of the professional tour, and the transition to steel equipment. 

  • 1916: The PGA of America is founded, and the PGA Championship is inaugurated.
  • 1920s: Steel shafts are patented and eventually legalised by the USGA (1924) and R&A (1929), replacing hickory.
  • 1927: The first Ryder Cup match is played between teams from the United States and Great Britain.
  • 1930Bobby Jones achieves the “Grand Slam” by winning the U.S. Open, U.S. Amateur, British Open, and British Amateur in a single year.
  • 1934: The first Masters Tournament is held at Augusta National, founded by Bobby Jones.
  • 1945Byron Nelson sets a record by winning 11 consecutive tournaments (18 total in the year).

3. The Television Boom (1946 – 1980s)

Broadcast sports turned golf into a global phenomenon, fueled by the rivalry between Jack Nicklaus and Arnold Palmer

  • 1950: The LPGA Tour is officially formed.
  • 1968: The PGA Tour is formally established as a separate entity from the PGA of America.
  • 1971: Astronaut Alan Shepard hits a golf ball on the moon during the Apollo 14 mission.
  • 1970s: Graphite shafts and metal-headed woods (drivers) begin to replace traditional wooden clubs. 

4. The Tiger Era (1990s – 2010) 

The arrival of Tiger Woods sparked a massive surge in popularity, prize money, and athletic training. 

  • 1991: Callaway introduces the Big Bertha driver, popularising oversized metalwood heads.
  • 1997Tiger Woods wins the Masters at age 21 by 12 strokes, becoming the youngest champion and sparking a global “Tiger Boom”.
  • 2009Tiger Woods becomes the first athlete to surpass $1 billion in career earnings. 

5. The Modern Game (2011 – Present)

This era is defined by extreme data analysis (Launch Monitors), advanced technology, and shifting tours. 

  • 2016: Golf returns to the Olympic Games after a 112-year absence.
  • 2022: The launch of LIV Golf introduces a significant competitive landscape shift in professional golf.
  • 2026: A planned “golf ball rollback” is scheduled to manage the increasing distances professional players are hitting the ball.

Golf Historical Timeline Overview

Agile Scrum Evolution Timeline Overview

Agile and Scrum have evolved from specific product development theories into a global standard for project management. While Scrum predates the Agile Manifesto by several years, it has become the most widely adopted framework within the Agile umbrella. 

Agile Scrum Burn down and Burn up charts – can be downloaded from website banner

Evolution Timeline

  • 1986: The Inspiration. Hirotaka Takeuchi and Ikujiro Nonaka publish “The New New Product Development Game” in Harvard Business Review, introducing the “rugby” approach to product development.
  • 1993: The First Scrum. Jeff Sutherland and his team at Easel Corporation implement the first official Scrum.
  • 1995: Public Presentation. Ken Schwaber and Jeff Sutherland formally present Scrum at the OOPSLA ’95 conference, introducing the concept of Sprints.
  • 2001: The Agile Manifesto. 17 software developers meet in Utah to sign the Manifesto for Agile Software Development, codifying the 4 values and 12 principles that define Agile.
  • 2002: Scrum Alliance Founded. The Scrum Alliance is established by Ken Schwaber, Mike Cohn, and Esther Derby to provide training and certifications like the Certified ScrumMaster (CSM).
  • 2009: Founding of Scrum.org. Ken Schwaber founds Scrum.org to provide a more consistent approach to Scrum training and assessments.
  • 2010: The First Scrum Guide. Sutherland and Schwaber publish the first Official Scrum Guide, providing a definitive, minimal definition of the framework.
  • 2011–2017: Iterative Refinements. Updates to the Scrum Guide clarify the Daily Scrum purpose (2013) and emphasize Scrum Values (2016).
  • 2020: The “Simplified” Guide. The latest 2020 Scrum Guide is released, focusing on making the framework less prescriptive and more applicable to non-software industries by removing technical jargon. 

Key Shifts in Scrum Maturity

  • Prescriptive to Descriptive: Early Scrum was highly prescriptive about meetings and roles; modern Scrum focuses on Empiricism (Transparency, Inspection, Adaptation).
  • Team Autonomy: The 2013 update pivoted from “selecting tasks” to focusing on the Sprint Goal, empowering teams to decide how to achieve the objective.
  • Scaling Frameworks: As organizations grew, frameworks like SAFe (2011) and LeSS (2013) emerged to apply Scrum across hundreds of teams.
Plan On a Page POaP for an Agile Scrum project, available for download above

Agile Development History Timeline Overview

Agile’s history is a transition from rigid, manufacturing-based “Waterfall” models to flexible, people-centric frameworks. While the term was coined in 2001, its roots trace back to early 20th-century industrial practices and the “software crisis” of the 1960s. 

Early Foundations (Pre-1990s)

Before Agile became a formal software methodology, its core principles of efficiency and iteration emerged from manufacturing and early computing.

  • 1896: Sakichi Toyota introduced the “Stop and Notify” concept (Jidoka), a foundational Lean/Agile practice for immediate problem-solving.
  • 1948: The Toyota Production System (TPS) established Lean manufacturing and the Kanban system to manage workflow.
  • 1957: IBM began using incremental development on large software projects.
  • 1970: Winston Royce published “Managing the Development of Large Software Systems,” which formalized the Waterfall Model but actually cautioned against its rigidity.
  • 1986: Takeuchi and Nonaka published The New New Product Development Game, introducing the “rugby” metaphor for team-based development that inspired Scrum

The Rise of “Lightweight” Methods (1990–2000) 

Frustrated by Waterfall’s slow delivery, practitioners developed several “lightweight” frameworks. 

  • 1991: Rapid Application Development (RAD) popularized timeboxing and iterations.
  • 1993: Jeff Sutherland and his team first implemented Scrum at Easel Corporation.
  • 1994: The Dynamic Systems Development Method (DSDM) was created as a vendor-independent RAD framework.
  • 1995: Ken Schwaber and Jeff Sutherland formally co-presented Scrum at the OOPSLA conference.
  • 1996: Kent Beck introduced Extreme Programming (XP), emphasizing practices like pair programming and continuous testing.
  • 1997: Feature-Driven Development (FDD) and Crystal Clear emerged as alternative iterative models. 

Formalisation & Modern Evolution (2001–Present)

The movement unified under a single name and eventually scaled to entire enterprises. 

  • 2001: 17 software leaders met at Snowbird, Utah, to draft the Agile Manifesto, establishing four core values and 12 principles.
  • 2003: The book Lean Software Development by Mary and Tom Poppendieck officially bridged Lean manufacturing and software agility.
  • 2009: The concept of DevOps emerged, extending Agile principles into IT operations and deployment.
  • 2011: The Scaled Agile Framework (SAFe) was introduced to help large organizations manage multiple Agile teams.
  • 2012–2015: Agile surpassed the 50% mark in global adoption, becoming the industry standard for development.
  • 2020s: Agile principles are now widely applied outside of tech, in fields like marketing, education, and HR

Agile’s evolution is not just a 21st-century phenomenon but a response to decades of “software crises” and rigid industrial processes. Below is a comprehensive historical breakdown of Agile’s journey. 

1. Pre-Digital Foundations (1910s – 1940s)

Long before software, the concepts of efficiency and waste reduction were born in manufacturing. 

  • 1911: Scientific Management. Frederick Taylor encouraged managers to adopt worker suggestions for efficiency, opposing rigid habits.
  • 1940s: Lean Manufacturing (Toyota). Toyota pioneered the “Just-in-Time” method and Kaizen (continuous improvement) after observing American supermarkets.
  • 1948: Toyota Production System. Introduction of Kanban for visual workflow management. 

2. Early Iterative Development (1950s – 1970s)

The 1950s saw the first departures from strictly sequential “waterfall” planning. 

  • 1957: Incremental Development. IBM and Motorola teams, including Gerald Weinberg, used iterative methods indistinguishable from modern Extreme Programming (XP) for Project Mercury.
  • 1968: NATO Software Engineering Conference. Formally identified the “Software Crisis” (projects being late and over budget), sparking a search for better methodologies.
  • 1970: Waterfall Formalised (and Critiqued). Winston Royce described the Waterfall model but notably advocated for iterative releases to reduce risk. 

3. The Proliferation of “Lightweight” Methods (1980s – 1990s) 

Frustration with heavyweight, document-heavy processes led to several “Agile” precursors. 

  • 1986: “The New New Product Development Game.” Takeuchi and Nonaka published this HBR article, introducing the “Rugby” approach (teamwork over relay-race handoffs), which directly inspired Scrum.
  • 1991: Rapid Application Development (RAD). James Martin introduced RAD, emphasising fast prototyping and client feedback.
  • 1993–1995: The Birth of Scrum. Jeff Sutherland and Ken Schwaber formalised Scrum, presenting it at the OOPSLA ’95 conference.
  • 1996: Extreme Programming (XP). Kent Beck introduced XP at Chrysler, focusing on technical excellence through practices like Pair Programming and Test-Driven Development

4. The Agile Manifesto & Formalisation (2001 – 2010)

Agile moved from a collection of “lightweight” methods to a global standard. 

  • 2001: The Agile Manifesto. 17 developers met in Snowbird, Utah, to draft the Manifesto for Agile Software Development, establishing four core values and 12 principles.
  • 2003: Lean Software Development. Mary and Tom Poppendieck adapted Toyota’s Lean principles specifically for software engineering.
  • 2009: Software Craftsmanship. The Software Craftsmanship Manifesto emerged to refocus the community on the quality of the “craft” rather than just project management.
  • 2010: The First Scrum Guide. Published as the definitive resource on Scrum framework rules. 

5. Scaling and Modern Business Agility (2011 – Present) 

Agile expanded beyond coding into enterprise-wide strategy. 

  • 2011: Scaled Agile Framework (SAFe). Dean Leffingwell launched SAFe to help large corporations apply Agile at scale.
  • 2015–2017: Project Management Integration. Major bodies like AXELOS released PRINCE2 Agile, and the PMI introduced the Agile Certified Practitioner (ACP).
  • 2020s: Beyond Software. Agile principles are now standard in marketing, HR, and hardware development through concepts like Business Agility

Putting Together a Project Plan Overview

Putting Together a Project Plan Overview

Agile Team Techniques Overview

Agile Team Techniques Overview

COBOL Development Detailed Timeline Overview

COBOL (Common Business-Oriented Language) has evolved from a 1959 “stopgap” experiment into a cornerstone of global finance, currently powering approximately 95% of ATM swipes and 80% of in-person credit card transactions

The Early Years (1959–1965)

  • 1959 (Origins): Following a meeting at the Pentagon in May, the Conference on Data Systems Languages (CODASYL) was formed to create a machine-independent language for business. It was heavily influenced by Grace Hopper’s FLOW-MATIC.
  • 1960 (First Release): The COBOL-60 specifications were published. In December, the same program was successfully run on two different manufacturers’ computers (RCA and Univac), proving portability.
  • 1961–1965 (Rapid Revisions): Successive updates included COBOL-61 and COBOL-65, which introduced critical features like the SORT and REPORT WRITER facilities. 

Standardisation & Dominance (1968–1985) 

  • 1968 (COBOL-68): The American National Standards Institute (ANSI) published the first official standard, making COBOL the industry benchmark.
  • 1974 (COBOL-74): This update added file organisation methods and the DELETE statement, further refining data management capabilities.
  • 1985 (COBOL-85): A major milestone that introduced structured programming (e.g., END-IFEVALUATE) to improve code readability and maintainability. 

Modernisation & Object-Orientation (2002–Present) 

  • 2000 (The Y2K Crisis): COBOL regained global attention as programmers rushed to fix the “Millennium Bug” in legacy systems.
  • 2002 (COBOL-2002): The first major update in 17 years introduced Object-Oriented (OO) features, Unicode support, and XML processing.
  • 2014 (COBOL-2014): Simplified the language by making several niche features (like the SCREEN SECTION) optional and adopting IEEE 754 floating-point math.
  • 2023 (COBOL-2023): The current ISO/IEC 1989:2023 standard added modern programming comforts like asynchronous messaging (SEND/RECEIVE), transaction processing (COMMIT/ROLLBACK), and bitwise operators. 

Today, despite its age, an estimated 800 billion lines of COBOL remain in active use, with modernization efforts focusing on cloud integration and interoperability with Java and .NET.

COBOL Development Detailed Timeline Overview

WordPress Content Management System (CMS) Timeline Overview

WordPress has evolved from a basic blogging tool in 2003 into a dominant Content Management System (CMS) that powers over 43% of the internet including this https://mark-whitfield.com website. Its history is defined by major version releases, often named after jazz musicians, and shifts toward “Full Site Editing”. 

This WordPress website started around 2021

The Early Years (2001–2005)

  • 2001: French developer Michel Valdrighi launches b2/cafelog, the PHP/MySQL-based blogging software that served as the foundation for WordPress.
  • 2003 (May 27): Matt Mullenweg and Mike Little release WordPress Version 0.7, a fork of b2/cafelog.
  • 2004: Version 1.0 (“Miles Davis”) introduces SEO-friendly permalinks and comment moderation. Version 1.2 (“Mingus”) debuts the plugin architecture, allowing for external extensibility.
  • 2005: Version 1.5 (“Strayhorn”) introduces the Themes system and static Pages, moving WordPress beyond just chronological blog posts. Automattic is founded by Matt Mullenweg in August. 

Expansion and Ecosystem Growth (2006–2010)

  • 2006: The first WordCamp is held in San Francisco. Automattic registers the WordPress trademark.
  • 2007: Version 2.1 (“Ella”) adds autosave and spell-check. Version 2.2 (“Getz”) introduces Widgets.
  • 2008: Version 2.7 (“Coltrane”) revamps the dashboard, moving the menu to the sidebar where it remains today.
  • 2010: Version 3.0 (“Thelonious”) is a major milestone, introducing Custom Post Types and Multisite capabilities. The WordPress trademark is transferred to the non-profit WordPress Foundation

The “Modern” Dashboard & Visual Improvements (2011–2017)

  • 2011: WooCommerce is released (later acquired by Automattic in 2015), revolutionising WordPress e-commerce.
  • 2013: Version 3.7 (“Basie”) introduces automatic background updates for security patches. Version 3.8 (“Parker”) gives the admin dashboard the modern, flat design used today.
  • 2014: Version 4.0 (“Benny”) focuses on media management with a new grid view.
  • 2016: The REST API is integrated into core (v4.4), allowing WordPress to interact with other web applications. 

The Gutenberg & Site Editing Era (2018–Present)

  • 2018 (Dec 6): Version 5.0 (“Bebo”) launches the Gutenberg block-based editor, fundamentally changing content creation from text-heavy to visual blocks.
  • 2022: Version 6.0 introduces Full Site Editing (FSE), enabling users to edit headers, footers, and templates visually without code.
  • 2024: WordPress continues to refine the site editing experience with Version 6.7 (“Rollins”). In late 2024, a public legal conflict began between Automattic and WP Engine over trademark usage and contributions.
  • 2025–2026: Version 6.8 (April 2025) and future Version 7.0 roadmap focus on real-time collaboration (Phase 3 of Gutenberg) and AI integration.

WordPress Content Management System (CMS) Timeline Overview

This WordPress website selling Project Management templates – see banner above

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

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

Project Management Terms Explained Overview

Project Management Terms Explained Overview

Project Management Soft Skills Overview

Project Management Soft Skills Overview

Agile Scrum Pillars Overview – Transparency, Inspection and Adaption

Agile Scrum Pillars Overview – Transparency, Inspection and Adaption

Project Management Types Summarised, Overview

Project Management Types Summarised, Overview

Agile Scrum Terms Summary Overview

Agile Scrum Terms Summary Overview

Accounting Key Performance Indicators KPIs Overview

Accounting Key Performance Indicators KPIs Overview

Common IT Protocol Ports Summary Overview

Common IT Protocol Ports Summary Overview

Overview – Agile Scrum Kanban SAFe LeSS XP

Overview – Agile Scrum Kanban SAFe LeSS XP