Enter any website URL to analyze its complete technology stack

Executive Summary for theprojectmanagementguide.com

882 Response Time (ms)
200 HTTP Status
60 Scripts
20 Images
35 Links
HTTP/1.1 Protocol

SEO & Content Analysis

Basic Information
Page Title
The Project Management Guide - No nonsense Project Management tips, tricks, strategies and shortcuts
Meta Description
No nonsense Project Management tips, tricks, strategies and shortcuts
HTML Language
en-GB
Robots.txt Present
Sitemap Present
total_urls: 2
SEO Meta Tags
content-type: text/html; charset=UTF-8
Page Content

The Project Management Guide - No nonsense Project Management tips, tricks, strategies and shortcuts

Small projects are easy right?People tend to think that “small” projects equals “simple” projects – but in my experience small projects can be really frustrating to manage and consume a disproportionate amount of time to their size. Project Managers often need to be quite tenacious and really exercise all of their skills and experience to get them finished. They will often be juggling multiple small projects at the same time or together with a larger project. In this article I explore some of the constraints on small projects. I also outline some typical types of small project, how they come about, the associated challenges and some strategies for running them.Note – it should be said, at this point, that size is relative and small in one organization doesn’t necessarily translate directly to small in another organization so you will need to adapt this information to your own organization.Small project constraints are the same as any other projectAll projects operate within a set of constraints in terms of the scope that can be delivered in some timescale to some agreed budget. Small projects will typically have to deliver a limited scope, but they may have constraints on budget which could manifest itself as follows:Project Management time available is small (say 1-2 days per week)Resources or delivery team limitations such as time available or ability to increase team size or capacityLimiting the time available on a small project can actually be beneficial as we will see later. This assumes that there are less constraints on budget and scope.There are also other constraints that impact small projects.Small projects are often “lower priority” projectsSmall projects can often be lower priority projects for the delivery team. This may be fine if the project gradually works its way up the priority list and gets completed as planned. However, this can become problematic if it gets bumped down the priority list repeatedly. The impact of this could be on other dependent activities and extended timelines for your project. The Project Manager needs to address this with whoever manages the delivery team and also seek help to increase the priority via the Project Board. Low priority extends timelines so use time as a project driverA project with a low priority will mean that time constraints have been lowered, removed or become flexible. Whilst having unrealistic timelines in a project can be a bad thing, having a project with flexible or changing time constraints can also be a bad thing too. Having a time driver can be really beneficial as a focus for getting a small project done and out of the way.The Project Manager should do all they can to raise the issue with their Project Board for assistance and also negotiate with whoever prioritises the work in project delivery teams.  Some typical small projectsThere are a number of other types of projects that present challenges for the Project Manager. They are often associated with small projects. The “unloved essential” projectThis type of project may be seen as essential by the Project Sponsor but no-one else involved is bought into it or wants to do it. The Sponsor normally has a good business reason for doing the project but there is a disconnect between the technical delivery team and business viewpoints. Sometimes you also get a disconnect between the people managing the delivery team and the sponsor.What you have here is a disagreement in the priority level. This can be even harder if the disagreement is not explicit ie people are saying one thing and doing another – so they may appear to be supporting the project but in reality, they are not backing it. This rubs off on the delivery team and the result is slow delivery, lack of focus and often lots of moaning from the delivery team as they would rather be doing work that they see as higher priority (and so do their managers).The Project Manager needs to get hold of this and try as many of these as possible:Meet with the Sponsor, Key Stakeholders and Managers of the delivery team to discuss and clarify the priority of the projectQuestion the need to do the project and get it stopped if possibleCut scope to the bare minimumPush to get the project finished and out of the wayCommunicate any agreements to all involved in the projectThe “post-launch phase” projectThis type of small project could be a mopping up phase, final phase or decommissioning phase of a much bigger project that has been running for a long time. Typically, the main launch has been completed but there is still a body of work to complete. Often these types of projects are handed over to more junior project managers to complete.These can often be quite good projects to run but the problem here is that sometimes the urgency element has gone out of the project so getting traction can be difficult. Another challenge with decommissioning type projects is that they can actually be quite complex and involved to unpick from a technical level.Another challenge with these types of project is that they are often handed over mid-flight so this process can be a bit messy.It is really important for the Project Manager to either setup the project properly from scratch or do a project audit to establish the real status of the project and set it up for success. I cover this later in the article.The “must do but tricky” projectThese types of project can be challenging because although the work required may appear to be small in fact it may be tricky, boring, time consuming or just really difficult to do. So, if it is also lower down the priority list too then project teams tend to put it off as long as possible in preference for other more straight forward work.This can obviously delay the project. The Project Manager needs to tackle this head on and urge the team to take on the challenge, support them as much as possible, make tea, offer cake or do whatever it takes to get the project done.The small “nearly finished” projectI’ve been handed a few of these small projects in my time – the ones that I could run in my “spare time” – one of them took nearly 2 years to finish. The Project Manager is taking over an in-flight project, so they need to get a handle on it quickly.The problem here is that someone has perceived the project as small and nearly finished. You need to go in with your eyes open and make your own assessment of what the true position is.One really effective approach is to run a really quick project audit – I have outlined how to do this in a later section.The “important low priority” project These ones are always a challenge to run. Typically the organization really wants to do the project. They may even have to do the project to reduce business risk, comply with some regulations or some other important reason. However – the importance and priority never really quite makes it far enough up the priority list and so gets pushed back and back. Sometimes the project may have been started and some elements finished but has since sat on the shelf to come back to later.The only real way to tackle these types of project is the same as the “unloved essential project” ie by trying as many of these as possible:Meet with the Sponsor, Key Stakeholders and Managers of the delivery team to discuss and clarify the priority of the projectQuestion the need to do the project and get it stopped if possibleCut scope to the bare minimumPush to get the project finished and out of the wayCommunicate any agreements to all involved in the projectHow to tackle small projectsThere are many ways to tackle small projects, but the key is to run them as you would any other project. Light weight Project Management processAll projects benefit from using a repeatable Project Management framework or process. This is no different for small projects – it simply means that some of the processes and governance put in place will need to be simplified and pared back to a minimum, but still effective, level.Starting a small project from scratchUsing a standard planning and startup process will really help the project. This should be documented. The project startup framework should cover the following: Identifying the Project Sponsor and Key StakeholdersUnderstanding the project requirements, scope and deliverablesDefining the project benefits and criteria for successIdentifying and establishing the project delivery teams and any suppliersAgreeing the delivery approach, timelines and delivery scheduleSetting up a simple governance processI covered this in a separate post How To Start Your Project Faster.Once the project is planned and approved to start then the project needs to be managed closely but efficiently.Taking over projects in mid-flightSome of the small projects outlined above had the scenario where the project was handed over to someone else in mid-flight – this can be a bit messy but again the project needs to be established or re-established on a solid footing.If you are taking over the project you need to understand where we are on the project. One method is to run through the Project startup framework and fill out a standard plan to understand the project in its entirety. This may be just for the benefit of the Project Manager’s understanding, but it is really effective for getting to grips on what the project is all about. Project audit Another method effective method is to run a project audit.Asking lots of questions like these can help to understand the true picture:What is the scope of the project?What has been delivered?What is there left to deliver?When is this forecasted to be complete?Do we think we are going to be able to deliver this?Is the team on track to deliver?Are there any issues, blockers or risks to the delivery timeline?What is the project budget, how much has been used so far and is it enough to complete the project?Simple project governanceOn small projects it is essential to run a simple light weight governance process. This will help to tackle the challenges around project prioritization and keep everyone up to date on the challenges of the project.  The minimum governance I would run would be this:Regular Project Report:Weekly or fortnightly (but always done)Issued to Sponsor and key Stakeholders via emailIncludes Progress update against plan and summary of risks and issuesOne-page summary should be the max required hereProject Board:With Sponsor and key StakeholdersProgress update against plan, and budget since last meetingSummary of risks and issues and any help neededA few simple slides should suffice for thisSmall projects are funAs we have seen running small projects has its challenges. However, if they are run in the same manner as any other project, but with a lighter weight set of processes, they can be run quite smoothly and effectively. They can also be quite fun to run as you can run a number of them together and you get the satisfaction of finishing things and moving onto the next project.;

Network & Infrastructure

DNS & Hosting
IP Address
192.0.78.158
Reverse DNS
Not detected
SSL/TLS Certificate
Issuer
CN=E7, O=Let's Encrypt, C=US
Protocol Tls13
Expires In 66 days
HSTS Enabled

Technology Stack

Content Management Systems
WordPress
JavaScript Frameworks
jQuery
Server Technologies
PHP (inferred from WordPress)

Services & Integrations

Analytics & Tracking
Google Analytics GA4 Google Analytics UA
E-commerce Platforms
Magento PrestaShop

CDN & Media Providers

Media Providers
YouTube
Web Fonts
Google Fonts

Dynamic Analysis & Security

Dynamic JavaScript Analysis
Angular (Data Attributes) Bootstrap (CSS Classes) ES6+ JavaScript Features jQuery (CDN Detection) jQuery (Script Analysis) jQuery (script Resource) Single Page Application (SPA) - Suspected Web Server: nginx
Security Headers
HSTS
Server Headers
nginx

Resource Analysis

External Resource Hosts
0.gravatar.com
1.gravatar.com
2.gravatar.com
c0.wp.com
gmpg.org
i0.wp.com
i2.wp.com
jetpack.wordpress.com
public-api.wordpress.com
s0.wp.com
secure.gravatar.com
stats.wp.com
theprojectmanagementguide.com
widgets.wp.com
wp.me
Cookies Observed
UI Frameworks & Libraries
Angular Material (Class Names) Bootstrap (Class Names) D3.js Ionic (Class Names) Slate Swiper Vuetify (Class Names)

Social Media Integrations

Analysis Errors

Analysis Warnings & Errors
The following issues occurred during analysis:
  • Reverse DNS failed: No such host is known.
Analysis Complete

Analyzed theprojectmanagementguide.com with 4 technologies detected across 8 categories

Analysis completed in 882 ms • 2026-03-23 09:24:26 UTC