This is a real photograph that has been edited using AI to anonymise sensitive information and protect client confidentiality.

In a nutshell
Good project delivery isn't about following a methodology to the letter. It's about knowing when to adapt. Reflecting on one of her most challenging projects at Alphero, Senior Project Manager Julieanne shares how a few simple changes, including moving desks, introducing a paper timeline, and rethinking how the team worked with the client, helped everyone work together and keep delivery moving against a tight deadline. Sometimes the simplest solutions are the most effective.
It was all going to plan, until it wasn’t
When I think back on the projects I've delivered over my five years at Alphero, one of my favourites is also one of the most challenging.
Don't get me wrong, it was a tough project. But what I really enjoyed was having the freedom to deliver it in the way I thought worked best. One of the things I like about working at Alphero is that I'm trusted to adapt my approach. I'm not expected to follow Scrum to the letter or stick to a strict Waterfall process. I can take what works, leave what doesn't and adjust things as the project evolves.
And on this particular project, that's exactly what I needed to do.
When the pressure came
At the start, everything was going pretty much to plan. We had our roadmap, the team was delivering to it, and we were making good progress. Then, just before Christmas, we were asked to bring the delivery date forward.
We were already moving at pace, so I needed to take another look at how we were working and see where we could squeeze out some efficiencies.
One thing I've noticed is that the Alphero team moves fast. Sometimes our clients find that pace a little hard to keep up with, which is understandable when they're juggling other priorities alongside the project.
But if we were going to meet this new deadline, we needed everyone moving at the same pace, and that's when I noticed a gap.
We were having daily stand-ups, talking through our Jira board and giving regular progress updates. From our side, we had pretty good visibility of what was happening.
But the client-side team was often playing catch-up. We needed information from them to keep moving, and those things weren't always ready when we needed them.
The stand-ups were useful for talking about what was happening, but they weren't giving the client a clear enough picture of what they needed to focus on next. Something had to change.
First, we moved desks
The first thing we did was move the project team so we were all sitting together. It sounds like such a small thing, but it made a big difference.
Instead of sending a Slack message and waiting for someone to respond, we could just turn around and ask a question. If something needed sorting out, we could get the right people together there and then. It made collaboration much quicker and helped us keep the momentum going. But we still needed a better way to see what was coming up and where the dependencies were.
Then I got out pieces of paper
Yes, actual paper! Just like we did in the early days of Agile, before everything moved online and we had a digital tool for just about everything.
On a portable pinboard, I created a physical timeline showing the features we needed to deliver and when they needed to be ready.
Every morning, the team would literally stand around the board and talk through where we were at. We used green, orange and red pins to show the status of each feature. It was incredibly simple, but everyone could see at a glance what was on track, what needed attention and what was at risk.
More importantly, we could see the dependencies. For example, the middleware needed to be ready before our frontend developers could do their work. If that slipped, it would have a knock-on effect. Having everything laid out in front of us made those conversations much easier.
Of course, we could have built another digital board. We already had Jira and a Figjam roadmap. But there was something about physically standing around the timeline, moving pins and talking through what needed to happen that just worked. It made everything feel more tangible.
I'd often catch people standing around the board outside our daily stand-ups, checking what was coming up or talking through priorities. It wasn't just something we looked at once a day. The team was actually using it.
But what about the client?
The physical board was working well for us, but obviously it wasn't going to work for a client and we still had the issue of needing them to keep up with our delivery pace.
So I created a second board, this time specifically for the client-side team. This one was digital, and it showed our progress against the delivery dates, but it also showed them where they needed to focus their attention. Not just what we were working on today, but what they needed to do today so we wouldn't be blocked tomorrow. That was the important bit.
Rather than constantly chasing information or decisions, we were giving the client a clear view of what was coming and what we needed from them. They could see which features were approaching, where the dependencies were and what needed their attention first. And it worked!
We were no longer just reporting progress to the client and waiting for them to catch up. We were now working as one team, with everyone clear on what needed to happen and when.
Sometimes simple is better
Looking back, I think what I enjoyed most about this project was being able to recognise that something wasn't working and just change it.
I didn't need to introduce a complicated new process or another tool. We moved a few desks, put a timeline on the wall and changed how we communicated priorities with the client. That's not to say Jira, Scrum or our other delivery practices weren't useful. They absolutely were, and we continued using them. But they weren't solving every problem we had.
I think sometimes we can get so caught up in following a particular way of working that we forget we're allowed to change it.
For me, that's one of the things I enjoy most about project delivery. Every project is different. Different teams, different clients, different challenges. What worked brilliantly on one project might not work at all on the next.
And sometimes, when you're trying to deliver a complex programme of work against a tight deadline, the thing that makes the biggest difference is a piece of paper and a few coloured pins.

