Category: Information Technology, IT

Project Management Mistakes and How to Avoid

Project Management Mistakes and How to Avoid

Is Microsoft MS Project Desktop (offline) app being retired?

No, Microsoft Project desktop is not being retired. It remains the “gold standard” for complex project scheduling and will continue to be supported and available for purchase. 

MS Project Templates can be downloaded in the template bundle, click on link at banner above

To purchase example MSP MPP Microsoft Project plan templates (and many others), click here.

Confusion often arises because Microsoft has announced the retirement of several related cloud-based and web-based services. Here is the current status of the Microsoft Project ecosystem: 

Products Being Retired

  • Project Online: This service will officially retire on September 30, 2026. After this date, Project Online environments and data will no longer be accessible.
  • Project for the Web: Retired as a standalone brand and was fully merged into the new Microsoft Planner in 2024/2025.
  • Project/Roadmap Apps in Teams: These were retired in August 2025 and replaced by the unified Planner experience. 

Products Staying Active

  • Project Desktop (Project Professional/Standard): Not impacted by the cloud service retirements. You can still use it to manage .mpp files locally or connect it to alternative backend systems like Project Server SE.
  • Project Server Subscription Edition (SE): This on-premises/self-hosted version will remain supported through at least 2031. It is the recommended migration path for organizations that want to keep the “Project Web App” (PWA) interface without using the retired Project Online cloud service.
  • Microsoft Planner: Now serves as the primary cloud-based project management tool, absorbing the features of Project for the Web. 
MS Project Templates can be downloaded in the template bundle, click on link at banner above

Looking to modernise your Microsoft project management solutions?

As Microsoft continues to evolve its project management ecosystem, organisations may want to explore how Planner/Planner Premium, Power Platform and Dynamics 365 Project Operations can complement their existing tools and support broader business processes.

Centiun is a specialist Microsoft Business Applications consultancy helping organisations design, implement and optimise solutions across Planner/Planner Premium, Dynamics 365 and Power Platform, including workflow automation, system integration and business process modernisation.

Exploring your options? Get in touch with Centiun⁠ to discuss how Microsoft Business Applications could support your organisation.

Key Dates for Project Online Users:

  • October 1, 2025: End of sale for new Project Online subscriptions.
  • April 2, 2026: SharePoint 2013 workflows (which many Project Online users rely on) will be retired.
  • September 30, 2026: Full shutdown of Project Online.

Home Computer historical development timeline by era

The transition from massive, industrial room-sized mainframes to the “home computer” was driven by the invention of the microprocessor in the early 1970s. 

The Pre-Home Era (1971–1976) 

Before “home computers” existed as off-the-shelf products, they were sold as DIY kits for electronics hobbyists. 

  • 1971: Intel releases the 4004, the first commercial single-chip microprocessor.
  • 1974: The MITS Altair 8800 is featured in Popular Electronics; it is widely considered the spark of the personal computer revolution.
  • 1976: Apple Computer is founded. The Apple I goes on sale as a hand-soldered board for $666.66.
  • 1976: MOS Technology releases the KIM-1, the first single-board computer kit. 

The “1977 Trinity” & Early Adoption

In 1977, three computers were released that targeted ordinary consumers rather than just hobbyists. 

  • Apple II: Features colour graphics and eight expansion slots, becoming a standard for schools and early home users.
  • Commodore PET 2001: The first “all-in-one” home computer with a built-in monitor and tape drive.
  • TRS-80 Model I: Sold through Radio Shack stores, making computers accessible on the high street for $399. 

The 1980s Boom

This decade saw fierce competition between manufacturers and the rise of gaming and office productivity. 

  • 1980: Sinclair ZX80 launches in the UK as a very low-cost entry point into computing.
  • 1981: The IBM PC is released, creating the “PC-compatible” standard that still dominates today.
  • 1981: The Commodore VIC-20 becomes the first computer to sell over one million units.
  • 1982: The Commodore 64 launches and eventually becomes the best-selling single computer model of all time.
  • 1984: Apple launches the Macintosh, the first successful mass-market computer with a Graphical User Interface (GUI) and a mouse.
  • 1985: The Amiga 1000 and Atari ST bring advanced multimedia and multitasking to the home. 

Standardisation & The Modern Age (1990s–Present) 

The market shifted away from proprietary “home computers” toward standardized “PCs” and portable devices. 

  • 1990: Microsoft Windows 3.0 is released, making GUI computing standard on IBM-compatible PCs.
  • 1995: Windows 95 launches, moving the PC away from its MS-DOS roots and integrating internet support.
  • 1998: The Apple iMac revitalizes Apple’s consumer line with an integrated, colourful design and USB ports.
  • 2010: The Apple iPad introduces the “tablet” as a primary home computing device for many users.
  • 2012: The Raspberry Pi launches, bringing home computing back to its DIY and educational roots.

The history of the home computer evolved from large, room-sized mainframes into the diverse, interconnected devices used today. This timeline categorises the evolution by era and key annual milestones. 

The Pre-Home Era: Mainframes & Minicomputers (1940s–1960s) 

Before computers could fit in a home, they were massive machines used by governments and corporations. 

  • 1945: ENIAC (Electronic Numerical Integrator and Computer) is completed as the first general-purpose electronic digital computer.
  • 1951: UNIVAC I is delivered to the US Census Bureau, becoming the first commercial computer produced in the US.
  • 1960: DEC PDP-1 is introduced, representing the first “minicomputer” that was smaller than its predecessors.
  • 1965: The DEC PDP-8 launches, becoming the first commercially successful minicomputer. 

The Hobbyist Era: The First Personal Computers (1970–1976) 

The invention of the microprocessor allowed computers to become small enough for individuals to own, though they often required manual assembly. 

  • 1971: Intel 4004, the first single-chip microprocessor, is released.
  • 1974: The MITS Altair 8800 appears on the cover of Popular Electronics, sparking the hobbyist revolution.
  • 1976: The Apple I, a single-board computer kit designed by Steve Wozniak, is released.

The “1977 Trinity” & The Home Boom (1977–1983) 

This era saw the transition from kits to fully assembled, consumer-ready “home computers”. 

  • 1977: The “1977 Trinity” launches: the Apple II (with colour graphics), the Commodore PET, and the Tandy TRS-80.
  • 1980: Sinclair ZX80 is released as one of the first low-cost home computers in the UK.
  • 1981: The IBM PC is released, setting the industry standard for hardware and software compatibility.
  • 1981: The Osborne 1 is released as the first commercially successful portable computer.
  • 1982: The Commodore 64 launches; it eventually becomes the best-selling single computer model of all time.
  • 1982: The ZX Spectrum is released, becoming a cultural icon in Europe. 

The Graphical User Interface (GUI) Era (1984–1994)

Computers moved away from text-based commands toward visual icons and mice. 

  • 1984: The Apple Macintosh launches, popularising the mouse and Graphical User Interface (GUI).
  • 1985: The Commodore Amiga 1000 and Atari ST launch, bringing advanced multimedia and multitasking capabilities.
  • 1990: Tim Berners-Lee creates the World Wide Web, fundamentally changing how home computers would be used.
  • 1994: PowerPC processors are introduced by Apple, significantly increasing processing speed. 

The Internet & Mobility Era (1995–Present)

Home computing shifted focus toward connectivity, portability, and eventually, the cloud. 

  • 1995: Windows 95 is released, integrating internet support and making PCs user-friendly for the masses.
  • 1998: The Apple iMac launches, ditching the floppy drive and embracing USB.
  • 2000s: Laptops begin to outsell desktops as portable computing gains momentum.
  • 2010: The Apple iPad pioneers the modern tablet market, creating a new “casual computing” category.
  • 2012: The Raspberry Pi is released, re-engaging a new generation in hobbyist computer building.
  • 2020s: The rise of Cloud Computing and AI Integration (like the Apple M1 chip) shifts the focus from local storage to remote applications and machine learning.

Agile Before and After

Agile Before and After

Azure AI vs Google Cloud AI vs AWS AI vs IBM Watson vs Alibaba Qwen

Azure AI vs Google Cloud AI vs AWS AI vs IBM Watson vs Alibaba Qwen

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. 

HPE NonStop Tandem Programming Languages, a development timeline

HPE NonStop (formerly Tandem) has evolved through distinct architectural eras, each introducing specific programming languages and environments to maintain its legendary fault tolerance. 

1. The Tandem Stack Machine Era (1974–1990)

This era focused on the proprietary 16-bit stack-based architecture (TNS), where software was designed to “fail-fast” and operate in process pairs. 

  • Nov 1974: Tandem Computers founded by Jimmy Treybig.
  • May 1976: TAL (Transaction Application Language) launched with the first Tandem/16 (NonStop I) system. It was the only language available at launch, derived from HP 3000’s SPL.
  • Late 1970s: COBOL74, FORTRAN, and MUMPS were added to support business and scientific applications.
  • 1981: NonStop II introduced support for 32-bit addressing, enabling larger application memory.
  • 1983: SCOBOL (Screen COBOL) emerged alongside the Pathway transaction manager to handle terminal-based user interfaces and fault-tolerant logic.
  • 1986: NonStop SQL released as the first fault-tolerant relational database language.
  • 1987: C was introduced to the platform.
  • 1989: Integrity S2 line launched using MIPS processors, introducing a variant of Unix called NonStop UX. 

2. The MIPS RISC / Himalaya Era (1991–2004)

As Tandem migrated to MIPS processors (TNS/R), it introduced a Unix-like personality to attract modern developers while maintaining its legacy Guardian environment. 

  • 1991: Cyclone/R launched. Most software still ran in TNS stack mode using an “Accelerator” tool to translate code to MIPS instructions.
  • 1993: Himalaya K-Series released with native-mode compilers for C and COBOL to leverage MIPS performance.
  • 1994/1995: Open System Services (OSS) introduced a POSIX-compliant environment, enabling C++ and standard Unix utilities.
  • 1995: Java was first supported on the platform.
  • 1997: Compaq acquired Tandem; ServerNet became the standard interconnect.
  • Late 1990s: Support for scripting languages like Perl, Python, and PHP began appearing in the OSS environment.

3. The HP Integrity Itanium Era (2005–2013)

Following the HP merger, the architecture moved to Intel Itanium (TNS/E), branded as HP Integrity NonStop. 

  • 2005: NonStop i introduced. Compilers for C, C++, and Java were updated for the Itanium architecture.
  • 2000s: pTAL (Portable TAL) became the standard for system-level programming to bridge legacy TAL code to modern RISC/Itanium architectures.
  • 2011: Enhanced support for modern web languages and frameworks within the OSS environment. 

4. The Modern x86 / NonStop X Era (2014–Present)

HPE migrated the entire stack to standard Intel x86-64 processors (TNS/X) while retaining binary compatibility for legacy applications. 

  • 2014: NonStop X launched. All languages (COBOL, C, C++, Java) were migrated to target x86-64.
  • 2015: Transition to Hewlett Packard Enterprise (HPE) branding.
  • Recent Years: Integration of modern open-source dev-ops tools and languages, including JavaScript (Node.js), Python 3, Go, and Samba via the HPE NonStop OSS environment. 

HPE NonStop (formerly Tandem) programming has evolved from proprietary languages designed for fault-tolerant, transaction-oriented processing (TAL, COBOL85) to supporting open-source languages (Java, C++, Python, PHP) on modern x86-64 hardware. The ecosystem spans from the initial Guardian OS to modern J-series and L-series OS, supporting TNS, TNS/R, TNS/E, and TNS/X architectures. 

Key Programming Languages & OS Timeline

  • 1970s–1980s (Tandem Guardian): Core development centered on TAL (Transaction Application Language) (system programming), COBOL85 (business logic), and TACL (Tandem Advanced Command Language) (command shell scripting).
  • 1990s (Guardian 90 / NonStop UX): Introduction of C and C++ for more flexible application development, alongside Pascal and FORTRAN.
  • 2000s (H-Series / J-Series – Itanium): Shift towards Java and enhanced support for C/C++ in the Pathway server environment.
  • 2010s–Present (J-Series / L-Series – x86-64): Modern NonStop systems, particularly on x86-64, expanded to include scripting languages like Perl, PHP, and Python within the Open System Services (OSS) environment.
  • pTAL (Portable TAL): Introduced to bridge native TAL to newer, more portable processor architectures. 

Operating System & Architecture Evolution

  • Guardian (TNS): The foundational OS, relying on Tandem’s native stack, with TAL as the primary low-level language.
  • OSS (Open System Services): Introduced to bring POSIX-compliant, Unix-like functionality to NonStop, enabling easier porting of C/C++ and open-source applications.
  • Modern OS (J-series/L-series): Supports both Guardian (native) and OSS environments, allowing for a hybrid approach where traditional transaction processing (COBOL/TAL) mixes with modern web services (Java/Python).