A4IT
Services / Project management
06 / 08
Project management · Business and functional analysis

Momentum every week. Not a status deck about it.

End-to-end project management with measurable outcomes, from planning to delivery. We own scope, budget and quality so your stakeholders see momentum every week, not status decks. Proven frameworks, no overhead theatre. A4IT fills the role your project is missing, for the length of a project or as an interim assignment.

Discuss your project → Roles we fill How an assignment runs

What you get, what stays yours, where it stops

Said before the first meeting
You get
  • One person who owns scope, budget and quality, and says so when one of them slips
  • A plan with dates and owners that is updated every week, not once at kick-off
  • Requirements and designs written so that business and developers read the same thing
  • A handover at the end: open points, decisions taken and where everything is stored
Stays yours
  • The decisions on priority, budget and go-live: we prepare them, you take them
  • All documents, backlogs, models and reports, kept in your own tools
  • The relationship with your suppliers and the contracts behind it
  • The team: we lead and coach your people, we do not replace them
Boundaries
  • No guaranteed delivery date before scope and team capacity are known
  • No certification claims: we work from experience with the methods, not from a badge
  • No hiring, firing or appraisal of your staff; that stays with their manager
  • No legal or financial sign-off on contracts; we read them for scope and risk only

Roles we fill

Six roles · project or interim
01 · Lead

Project manager

From planning to delivery, with one person accountable for scope, budget and quality. Progress is shown in working results, not in slides.

Scope and planning
What is in, what is out and what comes first. A plan in steps small enough to check, with an owner and a date on each one.
Budget tracking
Spent, committed and still to go, compared with the plan every week. A deviation is reported when it appears, with options to correct it.
Risks and issues
A short list that is actually used: what can go wrong, who watches it and what we do if it happens. Blockers are chased until they are gone.
Stakeholders and suppliers
One contact for management, users and external parties. Agreements are written down and followed up, including the uncomfortable ones.
02 · Lead

Agile coach, scrum master and product owner support

Agile methodology: working software over ceremony. Customer collaboration and responding to change, applied and not preached.

Scrum master
Planning, daily stand-up, review and retrospective kept short and useful. Obstacles are removed between meetings, not noted in them.
Product owner support
A backlog that is ordered, sized and understood. We help your product owner write stories, set priorities and say no with reasons.
Coaching the team
For teams that start with agile or are stuck in it. We work alongside the team for a few sprints and leave habits behind, not a handbook.
Regular demos
At the end of every iteration the team shows what works. Stakeholders react to something real and the next iteration is adjusted.
03 · Analyse

Business analyst

The bridge between business and tech: requirements, process modelling and stakeholder alignment, before anyone writes code or signs a licence.

Requirements
Interviews and workshops with the people who do the work. The result is a list of needs with a reason and a priority, not a wish list.
Process modelling
The current process and the intended one, drawn in BPMN so that everyone can follow who does what, when and with which information.
Stakeholder alignment
Departments often want different things from one system. We put the conflicts on the table early and get a decision on each.
Business case and options
Build, buy or adapt what exists. The options are set side by side with effort, impact and risk, as input for your decision.
04 · Analyse

Functional analyst

From agreed requirements to a description a developer can build and a tester can check.

Functional designs
Screens, rules, statuses and exceptions described per function, in language the business can approve and the developer can use.
Use cases and user stories
Each with acceptance criteria that can be tested. A story is done when the criteria pass, not when someone feels it is finished.
Data and interface specifications
Which fields, which formats, which system is the source and what is exchanged with other applications, including the error cases.
Test scenarios and acceptance
Scenarios derived from the design, and support for your users during acceptance testing: preparing cases, logging findings, retesting.
05 · Change

Change management and process simplification

A system that is delivered but not used has cost money and changed nothing. This is the work that gets it used.

Impact per role
What changes for whom, from which day. Written per function in the company, so nobody finds out at go-live.
Process simplification
Before a process is automated we remove the steps nobody needs: double entry, approvals without a purpose, reports nobody reads.
Communication and training
Short messages at the right moment and hands-on sessions with real cases, planned together with the people who lead the teams.
Follow-up after go-live
The first weeks decide whether old habits return. We stay close, collect the questions and adjust the process or the tool.
06 · Govern

PMO, reporting and governance

For companies with several projects at once and no clear view on which one is in trouble.

Portfolio overview
All running and planned projects on one page: goal, owner, status, budget and next milestone. Kept current, not rebuilt for each meeting.
One reporting format
A single short report per project with the same fields everywhere, so management compares projects instead of layouts.
Decision rhythm
A fixed steering meeting with a clear agenda: what needs a decision, what are the options, who decides. Decisions are logged.
Light templates
A project charter, a risk list and a change request form that each fit on one page. Governance sized for an SME.

How an assignment runs

Small steps · a decision after each
  1. Intake
    A call of thirty minutes: your project, the role you miss, your constraints.
    30 minutes
  2. Assessment
    We read what exists and talk to the key people. You get our view in writing.
    Findings + proposal
  3. Start-up
    Scope, plan, roles and reporting agreed with the sponsor and the team.
    Agreed plan
  4. Delivery
    Short iterations, regular demos and a weekly status you can read in two minutes.
    Visible progress
  5. Handover
    Documents, open points and decisions transferred to the people who continue.
    You run it

Methods and tools

Chosen per project · nothing is mandatory
AgileScrum and kanban, with short iterations, regular demos and a backlog the business owns
WaterfallPhased delivery where the contract, a fixed scope or a supplier demands it
ModellingBPMN for processes, use cases and user stories with acceptance criteria for functions
ToolsJIRA for backlog and tracking, Confluence for documentation, or the tools you already use
ChangeChange management: impact per role, communication, training and follow-up after go-live
ProcessProcess simplification before automation, so that waste is removed and not built in

Good fit, and not a fit

Saves both of us a meeting
A good fit when
  • A project has started but nobody owns the whole of it
  • Business and IT use the same words and mean different things
  • You need an experienced role for some months, not a permanent hire
  • You want to hear bad news in the week it happens
Not a fit when
  • The role is expected to report green whatever the facts are
  • No sponsor in the business can take decisions on scope and budget
  • You need a full project office of many people on site every day
  • A certificate on paper matters more to you than the track record

Questions about project management

All questions →
01Who do we actually work with?

With Tim De Smedt, who founded and leads A4IT and has more than ten years of experience in enterprise software development and project management. You work with him directly, with no middlemen. More on the about page.

02Can you step into a project that is already running?

Yes. That is the usual situation. We start with a short assessment of plan, budget, backlog and team, tell you what we found, and agree what changes first.

03Agile or waterfall?

Agile where requirements will move and feedback is cheap, which is most software work. Waterfall where a contract or a fixed scope demands phases and sign-offs. Often it is a mix, and we say which part is which.

04Do you work on site or remotely?

A4IT is based in Belgium and works remotely for clients anywhere. Workshops and key meetings can take place on site in Belgium when that works better. The rhythm is agreed per assignment.

05Can you also build what you analyse?

Yes, if you want that. Analysis and build can stay with A4IT, or the analysis can be handed to your own developers or supplier. See software development and automation & data.

06How do we know the project is on track?

By what is shown, not by what is reported. Every iteration ends with a demo of working results, and the weekly status states scope, budget, risks and decisions needed in plain terms. See how we work.

Bring one project that is stuck. We will tell you what we would do first.

Reply within three business days.Discuss your project →How we work