These days many projects have a computer in a shop, a factory, a hospital or a truck. This computer gathers information and makes choices right there. It does not send all the information to the cloud first.
This is called edge computing. If you are in charge of technology projects, you will come across it soon.
You do not need to be an engineer. You just need to understand what changes in your plan. Let us make this easy.
What Is Edge Computing?
Edge computing means the data is processed close to where it is created.
Imagine a security camera.
The old way: the camera sends all the video to the cloud. The cloud looks for something that seems wrong.
The edge way: a small computer near the camera checks the video itself. It only sends the parts that are important.
Why people like it:
- It is faster
- It uses less internet data
- It works even if the internet stops
Why Should a Project Manager Care?
Edge is not just a technology choice. It changes your plan.
You now have hardware. Cloud projects are only software. Edge projects need devices, wires, power and someone to put them in place. You cannot fix hardware with an update.
You now have places. If you set up in 40 shops, you have 40 site contacts and 40 visit dates. That is a lot of people to handle. If those shops sit in different countries, read our guide on cultural intelligence in global projects before you plan the rollout.
Your timeline depends on delivery. Getting and shipping the devices is often the slowest part of the project. This is a good time to use the Critical Path Method. In edge projects, the delivery date sets everything else.
Testing is more complicated. A lab is clean and quiet. A real site has dust, heat, weak signal and busy workers. Things break in ways you did not predict.
Five Things That Change in Your Plan
1. Scope
Write down what happens on the device and what happens in the cloud.
Most projects use both. The device handles quick decisions. The cloud handles reports and storage.
If this is not clear in your scope, you will get change requests later.
2. Schedule
Plan backwards from the day the hardware arrives.
Give time for shipping, customs, site access, electricity and network setup. Always do a test at two or three sites first. It avoids problems later.
Because delivery dates move so often, many teams add buffers instead of padding every task. That idea comes from Critical Chain Project Management, and it fits edge projects well.
3. Cost
Edge projects cost more at the start because you buy hardware. But the monthly cloud bill is lower.
Your sponsor may not know this. Tell them early.
Also buy spare devices. Devices in the field can fail. Include spares in the budget.
To track cost and progress together as sites go live, use Earned Value Management. You can even set it up quickly with our Excel EVM dashboard guide.
4. Risk
Most edge risks are physical, not technical:
- Someone steals or unplugs the device
- No one on site knows who is responsible
- An update fails on a device you cannot reach
- Security issues, because each device is a new way into your network
- Data rules that change between countries
Add these to your risk list early. Give each one a person to handle.
If many devices fail at the same time, you are no longer managing a risk. You are managing an incident. Our guide to crisis management in projects explains how to lead the team through it.
5. Updates and Rollout
Updating 500 devices is not like updating one website.
You need a step-by-step rollout, a way to undo it if it fails, and good automated testing. If your team does not work this way, read our guide to continuous integration for project managers before your first release.
Vendors and Contracts
Edge projects usually involve several companies. One for hardware. One for internet. One for installation. One for software.
That means four companies who can all blame each other when something goes wrong. Keep those meetings calm and useful with the ideas in our post on conflict resolution in projects.
Include this in the contract:
- Who owns the device after it is installed?
- How fast will a broken device be replaced?
- Who pays for site visits?
- How long will they support updates and security fixes?
- What happens to your data if you end the deal?
Sort this out early. Our guide to contract management for project managers shows you how.
A Simple Checklist Before You Start
- Is the edge and cloud split written down?
- Do you have the hardware delivery time in writing?
- Have you visited a real site?
- Who installs the device, and who looks after it?
- How do you update devices from far away?
- Have security and privacy teams checked the design?
- Is there a pilot before the full rollout?
- Do you have spare devices ready?
If you can answer all eight, you are in a good place.
Common Mistakes
Treating it like a software project. You can fix a code delay in a week. You cannot fix a shipping delay.
Skipping the pilot. If you go live everywhere at once, you fail everywhere at once.
Forgetting the people on site. Someone local has to plug it in and call you when the red light comes on. Train them. Give them a phone number or email.
Forgetting about the future. Ask who will support this system in three years. Bring that team into the design talks now.
Frequently Asked Questions
Do I need a technical background? No. You just need to understand enough to ask good questions. Your architect handles the details.
Is edge replacing the cloud? No. Most systems use both. Edge gives speed. Cloud gives storage and reports.
Which industries use edge the most? Factories, shops, hospitals, transport, energy and telecom. They all have real sites and need fast answers.
Which method works best for edge projects? A mix. Use normal planning for hardware and buying. Use agile for the software part. You can compare the options on our PM methodologies page.
Final Thoughts
Edge computing is not just a technology word. It moves your project from pure software into the real world of devices, sites, suppliers and people.
Plan for the physical side. Run a pilot. Write good contracts.
Do that, and an edge project is just another project you can manage well.
For more guides like this one, browse our project management blog.
