Centiun Microsoft Business Applications and AI Specialists

Website: https://centiun.com

Centiun Microsoft Business Applications and AI Specialists

Centiun Overview

Centiun is a British IT services consulting company and Microsoft Partner, helping enterprise public and private sector organisations achieve digital transformation excellence through the Microsoft cloud.

We specialise in Microsft Dynamics 365, Power Platform, and Micrisoft 365, delivering expert consultancy, solution architecture, implementation, and managed services that enable organisations to modernise operations, improve service delivery, and unlock greater value from their technology investment.

From CRM transformation and business process automation to secure collaboration, data-driven decision making, and AI enabled innovation, Centiun supports customers to build smarter, faster and more resilient ways of working.

Our approach combines deep Microsoft expertise with a practical focus on outcomes – designing and delivering solutions that are scalable, compliant, and tailored to the needs of complex organisations.

Whether you’re starting your digital journey or optimising an existing platform, Centiun is your trusted Microsoft for long-term transformation and support.

Website: https://centiun.com

On LinkedIn: https://www.linkedin.com/company/centiun/

Email: info@centiun.com

Centiun services
Centiun Microsoft Business Applications and AI Specialists
Centiun Microsoft Business Applications and AI Specialists

Mark Whitfield IT Training Career Timeline Overview

Mark Whitfield, an experienced IT Project Manager, has a career and certification history spanning over 30 years. His professional development includes a range of technical, project management, and cloud-based qualifications. 

2020s: Cloud & Modern Platforms

  • 2024 (July): Microsoft Excel Refresher Course – Udemy.
  • 2022 (December/February): C&CA UK’s Communications & Engagement Award and AZ-900 Microsoft Certified Azure Fundamentals. 

2010s: Advanced Management & Development 

  • 2017 (November/April): Advanced Engagement Management (Level 2) and Microsoft Excel 2010 Expert Skills.
  • 2014 (July): Advanced Microsoft Excel 2013.
  • 2011 (May–July): PRINCE2 Practitioner, Agile SCRUM, Java, and Android programming. 

2000s: Web Applications & Database Systems 

  • 2009 (March–November): Thales e-Security, BIRT, Web Design, and SQL Server training.
  • 2006 (Feb–Dec): NetObjects Fusion, Cryptography, and Thales e-SECURITY SafeSign.
  • 2004 (March): MultiBatch NSK Job Scheduling.
  • 2000 (February): Fundamentals of Successful Project Management. 

1990s: Core Programming & System Fundamentals

  • 1990s (1993–1999): TANDEM/HP NonStop systems, C/C++ programming, project management, and HND in Computer Studies (1990).

Mark Whitfield Training IT Career Timeline Overview

Mark Whitfield, a Senior IT Project Manager who has spent over 30 years specialising in HP NonStop (formerly Tandem) computing systems. 

Professional Background

  • Specialisation: Mark Whitfield is a highly experienced technician and project manager for the HP NonStop platform, which is a high-availability, fault-tolerant mainframe environment used primarily for mission-critical financial transactions.
  • Career Timeline:
    • The Software Partnership / Deluxe Data (1990–1995): Began as a programmer working on the sp/ARCHITECT-BANK solution for Tandem computers.
    • Insider Technologies (1995–2013): Spent 18 years focusing on monitoring and diagnostic software for HP NonStop, including products like Reflex 80:20, XPERT24, and Enterprise Manager.
    • Capgemini (2016–Present): Currently serves as an SC-cleared Senior Project Manager, delivering complex IT projects for major banks and government agencies. 

Key Technical Contributions to NonStop

  • Product Development: He co-developed Reflex (a platform health/diagnostic tool) and designed XPERT24 to monitor performance in the XPNET layer of BASE24.
  • Financial Systems: He has managed major projects for global financial entities, including Barclays, HSBC, Bank of England, and Royal Mail Group, often involving ATM and POS monitoring systems.
  • Programming Expertise: His technical skill set includes NonStop-specific languages and tools such as TAL (Tandem Application Language), PATHWAY, XPNET, COBOL85, and C++. 

About HP NonStop Systems

In the context of Mark Whitfield’s work, NonStop refers to a “shared-nothing” architecture designed by Tandem Computers. These systems are uniquely capable of: 

  • Fault Tolerance: Handling hardware or software failures without system downtime.
  • Scalability: Doubling throughput by adding processors (up to 4,000) without hitches in performance.
  • Core Banking: Processing massive commercial workloads for retail banks and stock exchanges globally.

Project planning timeline is typically structured to five phases

A project planning timeline is typically structured around the five phases of the project management lifecycle: Initiation, Planning, Execution, Monitoring/Control, and Closure. This framework breaks a complex project into manageable stages to ensure systematic progress and stakeholder alignment. 

1. Project Initiation

The foundation phase where the project’s value and feasibility are established. 

  • Primary Objective: Secure formal approval to begin.
  • Key Activities: Identify stakeholders, perform feasibility studies, and create a Project Charter.
  • Output: Project Charter or Business Case. 

2. Project Planning

The most critical stage for the timeline, where the high-level vision is translated into a detailed roadmap. 

  • Primary Objective: Define the “how” of project delivery.
  • Key Activities:
    • Scope Definition: Establish what is and is not included.
    • Work Breakdown Structure (WBS): Break large goals into “bite-sized” tasks.
    • Scheduling: Sequence tasks, estimate durations, and link dependencies.
    • Resource & Risk Planning: Allocate staff/budget and identify potential bottlenecks.
  • Output: Gantt Chart or Project Management Plan. 

3. Project Execution

The “action” phase where the team carries out the planned tasks to produce deliverables. 

  • Primary Objective: Complete the work according to the finalized plan.
  • Key Activities: Assign tasks, hold kickoff meetings, and manage workflows using tools like Asana or Trello.
  • Output: Status reports and tangible deliverable packages. 

4. Project Monitoring and Controlling

This phase runs concurrently with Execution to ensure the project stays on track. 

  • Primary Objective: Track progress against the original timeline and budget.
  • Key Activities: Measure KPIs (e.g., ROI, cost performance), manage scope creep, and adjust schedules as needed.
  • Output: KPI Dashboards and Change Logs. 

5. Project Closure

The final wrap-up where the project is formally ended and evaluated. 

  • Primary Objective: Formal handover and knowledge capture for future projects.
  • Key Activities: Host a Post-Mortem Meeting, archive project documents, and release remaining resources.
  • Output: Final reports and a lessons-learned document. 

Project planning timeline is typically structured to five phases

Project Management evolution timeline by era

The history of project management has evolved from ancient manual coordination to highly sophisticated, digital-first methodologies. 

Pre-20th Century: The Era of Ancient Marvels

During this era, project management was characterized by massive labour forces and basic resource coordination without standardized scheduling tools. 

  • 2570 BC: Completion of the Great Pyramid of Giza. Documentation shows managers were assigned to each of the four faces to oversee progress.
  • 208 BC: Construction of the Great Wall of China. Labour was systematically organized into groups of soldiers, civilians, and criminals.
  • 1850s: Construction of the Pacific Railroad. This is often cited as one of the first large-scale industrial project management undertakings in the U.S.. 

1900–1950: The Birth of Modern Project Management 

This era introduced scientific management principles and the first visual scheduling tools. 

  • 1911: Frederick Taylor publishes The Principles of Scientific Management, focusing on efficiency and unskilled labour training.
  • 1917: Henry Gantt develops the Gantt Chart, a radical tool for visualising schedules that remains a global standard today.
  • 1931–1936: Construction of the Hoover Dam. This project was a major early adopter of Gantt’s scheduling techniques.
  • 1942–1945: The Manhattan Project. This complex R&D effort pioneered the use of large-scale task coordination and resource management. 

1950–1980: The Era of Management Science 

Driven by the Cold War and space race, this period saw the creation of mathematical scheduling techniques. 

  • 1956: AACE International is formed, focusing on cost engineering.
  • 1957–1958: Development of Critical Path Method (CPM) by DuPont and Program Evaluation and Review Technique (PERT) by the U.S. Navy.
  • 1962–1975: Introduction of Work Breakdown Structure (WBS) by the DoD, founding of IPMA and PMI, and development of PROMPT (later PRINCE). 

1980–2000: The Computing Revolution 

Personal computers allowed project management software to proliferate into the private sector. Key milestones included the early Scrum framework and the initial PMBOK Guide release. 

  • 1989–1997: Widespread adoption of Earned Value Management (EVM), release of PRINCE2, and development of Critical Chain Project Management (CCPM). 

2000–Present: The Agile and Digital Era 

Modern project management emphasizes flexibility, speed, and digital tools. 

  • 2001: The Agile Manifesto is published.
  • 2012–2021: Release of ISO 21500, major updates to PRINCE2 and PMBOK to integrate Agile, and the shift to performance-based standards in PMBOK 7th Ed.

Project Management evolution timeline by era

Project management has evolved from ancient engineering feats to a highly structured, data-driven discipline. Below is a comprehensive timeline of its historical development and the evolution of its core methodologies. 

Ancient & Early Eras

  • 2570 BC: The Great Pyramid of Giza – Completed with record-keeping and oversight for each of the four faces, demonstrating early forms of planning and control.
  • 208 BC: The Great Wall of China – Built with a massive labour force organised into specific groups: soldiers, ordinary people, and criminals.
  • 1917: Gantt Chart – Developed by Henry Gantt, this scheduling diagram became a radical innovation for tracking project tasks chronologically. 

The Mid-20th Century: Formalization

  • 1956: AACE International Formed – Early practitioners of cost engineering and scheduling founded what is now the leading society for project control specialists.
  • 1957: Critical Path Method (CPM) – Invented by DuPont to address chemical plant maintenance; it saved the company $1 million in its first year.
  • 1958: PERT (Program Evaluation Review Technique) – Developed for the U.S. Navy’s Polaris project to analyse the minimum time needed for task completion.
  • 1962: Work Breakdown Structure (WBS) – Mandated by the U.S. Department of Defense as a hierarchical tree structure for project deliverables.
  • 1965: IPMA Founded – The world’s first project management association was started in Vienna as a global forum for networking.
  • 1969: Project Management Institute (PMI) Launched – Founded to advance the profession, PMI has since become the primary publisher of global standards. 

Late 20th Century: Methodology Proliferation 

  • 1975: PROMPTII & “The Mythical Man-Month” – Guidelines were created for computer projects, while Fred Brooks’s Brooks’s law observed that adding manpower to late software projects makes them later.
  • 1984: Theory of Constraints (TOC) – Introduced by Dr. Eliyahu M. Goldratt, focusing on identifying system bottlenecks.
  • 1986: Scrum – First named as a project management style for software development in a Harvard Business Review paper.
  • 1987: PMBOK Guide First Published – PMI published the first “A Guide to the Project Management Body of Knowledge” as a white paper to standardise practices.
  • 1989: PRINCE & Earned Value Management – The PRINCE method was developed for UK government IT projects; meanwhile, Earned Value Management (EVM) became an essential part of procurement.
  • 1996: PRINCE2 – A more generic revision of PRINCE was published, applicable to any project type.
  • 1997: Critical Chain Project Management (CCPM) – Invented to keep resources levelly loaded and flexible. 

21st Century: Agile & Global Standards

  • 2001: The Agile Manifesto – Written by 17 developers in Utah, codifying the principles of lightweight, iterative software development.
  • 2006: Total Cost Management Framework – Released by AACE International as the first integrated process for portfolio and project management.
  • 2012: ISO 21500:2012 – The International Organisation for Standardisation released its global guidance on project management.
  • 2017: PMBOK 6th Edition & PRINCE2 Update – Updates reflected the integration of Agile practices into traditional project settings.
  • 2021: PMBOK 7th Edition – Shifted toward a principle-based approach to help practitioners be more proactive and innovative.

Project Management Framework – Core Foundations

Project Management Framework – Core Foundations

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.

Agile Before and After

Agile Before and After

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