Planning and roadmaps
Turning goals into a clear plan: scope, priorities, milestones, and realistic timelines everyone agrees on.
RoadmapsBacklogEstimation
Project
management
I oversee software projects from planning to delivery: tracking progress, coordinating the team, and keeping work on course using Agile methods like Scrum and Kanban.
Projects succeed
when people align.
Most late or over-budget software projects do not fail because of the code. They fail because of unclear goals, hidden problems, and a team that is not working from the same plan.
With my technical background, I plan realistically, keep everyone informed, and help the team deliver working software step by step.
What I manage
The planning, tracking, and coordination that keep a software project moving in the right direction.
Scrum and sprint management
Running sprints from planning to review, keeping the team focused on delivering working software regularly.
SprintsStand-upsRetrospectives
Kanban workflows
Visual boards with work-in-progress limits that show where work is stuck and keep delivery flowing smoothly.
BoardsWIP limitsFlow
Progress tracking and reporting
Honest, easy-to-read updates on what is done, what is next, and whether the project is on track.
Status reportsBurndownMetrics
Team coordination
Connecting developers, designers, and stakeholders so everyone knows their part and blockers get removed quickly.
CommunicationHandoversStakeholders
Risk and scope management
Spotting risks early and handling changing requirements without losing control of time or budget.
Risk logChange controlPriorities
Agile ways
of working
I work with the method that fits your team. Switch between the two to see how each one runs.
Scrum
Work is organised into short sprints. Each sprint ends with a working piece of software and a chance to look back and improve.
Best for: Products with evolving requirements, where regular demos and feedback shape what gets built next.
- Sprint planning to agree what will be delivered
- Short daily stand-ups to surface blockers
- Sprint review to demo working software
- Retrospective to improve how the team works
JiraLinearGitHub Projects
A typical 1 to 2 week sprint
Planning
Day 1
Stand-ups
Every day
Review
Last day
Retrospective
Last day
Then the next sprint begins, with what was learned.
How you stay
informed
A steady rhythm of updates, so you never have to wonder where the project stands.
Daily
Quick progress update
A short note on what was done, what is next, and anything blocking the work.
Weekly
Status and priorities
A clear summary of progress against the plan, and a check that priorities still make sense.
Every sprint
Demo and review
A live look at working software, so you can give feedback while changes are still cheap.
Monthly
Roadmap check-in
A step back to review timelines, budget, risks, and the direction of the product.
What guides
my work
Full transparency
Progress, problems, and delays are visible to everyone, early enough to act on them.
Realistic planning
Estimates based on how work actually gets done, not on wishful thinking.
Clear communication
Everyone knows what is expected of them, and questions get answered quickly.
Continuous improvement
Each sprint or cycle teaches something, and the next one runs a little better.
The project
lifecycle
- 01
Initiate
Define the goals, scope, stakeholders, and what success looks like.
- 02
Plan
Build the backlog, roadmap, estimates, and choose the way of working.
- 03
Execute
Coordinate the team, remove blockers, and deliver in regular increments.
- 04
Monitor
Track progress, manage risks, and adjust the plan as things change.
- 05
Deliver
Release, hand over, and make sure the result meets the goals.
- 06
Review
Look back at what worked, and carry the lessons into the next project.
What you
receive
Clear documents and working tools, so the project stays organised even when people change.
- A prioritised backlog and project roadmap
- Sprint plans or a set-up Kanban board
- Regular, plain-language status reports
- A maintained risk and issue log
- Meeting notes with clear action items
- Retrospective findings and improvements
Common
questions
Something else on your mind? Send me a message and I will reply personally.
Scrum works well for building a product in stages with regular feedback. Kanban suits ongoing work where tasks arrive continuously. We can also combine ideas from both. I will recommend what fits your team and explain why.
Yes. On smaller projects I can plan, coordinate, and build. On larger ones I focus on coordination, so the team can concentrate on delivery.
I adapt to what your team already uses, such as Jira, Trello, Linear, GitHub Projects, or Notion. If you do not have a tool yet, I will help you choose a simple one.
You get regular, honest updates and access to the board, so you can see progress at any time. If something slips, you hear about it early, along with a plan to deal with it.
Change is normal. New requests are added to the backlog, weighed against the existing priorities, and scheduled with a clear view of the effect on time and cost.
Let's keep your project on track.
Starting a new project, or one that has lost its direction? Tell me where you are, and we will plan the way forward.