Agile

Agility beyond IT: HR, marketing and agile leadership

By Anass JdaaPublished 12 October 2026Updated 15 October 20269 min read

Agile works outside IT, provided you do not copy the rituals of software development wholesale. In HR as in marketing, it means making work visible, delivering in small batches and correcting course through frequent feedback rather than a fixed annual plan. But what actually makes a team more responsive is leadership: managers who set outcomes, delegate decisions and revisit their commitments at short intervals.

What does agile look like outside IT?

Agile was born in software, but its principles are not about code: they are about uncertain work. When you cannot know in advance which job advert will attract the right candidates or which message will land with a customer segment, it is better to move forward in short steps than to plan in fine detail over twelve months. An agile HR or marketing team follows a few simple rules:

• Visible work: everyone can see what is in progress, blocked or done on a shared board, not buried in inboxes.
• Small deliveries: a campaign tested on one segment or one improved step of the onboarding journey, rather than a big project delivered in one go.
• Frequent feedback: a check-in at a fixed interval with internal or external customers, followed by concrete adjustments.
• Continuous improvement: a short retrospective to decide what to change in the way the team works, not just in the work itself.

There is no point forcing Scrum on the payroll department, whose work is paced by the calendar and by regulation. Pick the practices that solve a real problem: lead times that keep growing, priorities that change without warning, work redone because the need was misunderstood.

How do you apply agile to human resources?

Much of HR work is a flow: applications, employee requests, onboarding. That is Kanban's natural territory, because it starts from the existing process instead of replacing it.

A recruitment pipeline on a Kanban board

A Kanban board makes recruitment readable for everyone, including the manager waiting for their new hire. A starting point for the columns:

1. Need approved with the hiring manager
2. Sourcing
3. Shortlisting
4. Interviews
5. Decision and offer
6. Onboarding

The decisive rule is the work-in-progress limit, for example a maximum number of roles in the interview stage at the same time. It forces the team to finish before starting and exposes bottlenecks: if cards pile up in front of "Decision and offer", sourcing is not the problem. The principles of flow are covered in detail in the Kanban course.

One practical choice matters: one card per role, not per candidate. Candidate information is personal data, governed in Morocco by Law 09-08 (loi 09-08, the personal data protection law) and overseen by the CNDP, the national data protection authority. It stays in the recruitment tool with restricted access, and the shared board shows progress only.

Iterative goals rather than a single annual review

A goal set in January can be obsolete by April if the organisation or the market has moved. The agile approach keeps a formal moment but complements it with goals reviewed at a short rhythm, often quarterly, and with regular feedback between manager and employee. The annual appraisal becomes a summary with no surprises rather than a verdict.

That feedback has to be specific and close to the facts: "Tuesday's presentation lost the room at the third slide" is more useful than "you need to work on your communication". It is a skill that can be learned, by managers and employees alike.

How do you apply agile to marketing?

Instead of an annual plan and a few big campaigns judged once the budget has been spent, agile marketing offers a different rhythm:

• Campaign sprints: over a short, fixed period, the team commits to a few deliverables (a landing page, an email sequence, a series of posts), then presents the result and early feedback to stakeholders.
• Test and learn: before rolling everything out, test a message on one segment or one city, compare two variants and keep the better one. The success criterion is set before launch, not picked afterwards from whichever metrics look flattering.
• Small batches: a campaign broken into separately deliverable pieces can be corrected along the way instead of being judged as a whole.

The framework depends on the work. Campaigns that can be planned lend themselves to sprints; a continuous stream of requests from sales or senior management is better served by Kanban, with a written prioritisation policy. Our Scrum vs Kanban comparison will help you decide.

A common trap: running sprint after sprint without ever looking at the results. If the end-of-cycle review is just a matter of ticking off deliverables, the team has gained pace, not learning.

Agile leadership: what leaders need to change

If management steers the way it always has, a board and short stand-ups change nothing fundamental. Agile leadership rests on three shifts.

Outcomes rather than outputs

"Ten posts a month" measures activity. "More qualified applications for technical roles" sets an outcome and leaves the team to choose how to get there. The manager defines the direction and the success criteria; the team decides the route.

Rolling commitments

Instead of a detailed plan for the year, the leader commits precisely over a short horizon and to a broader direction beyond it, which they confirm or adjust at each review. The annual budget does not disappear; it is the detail of how it is allocated that is decided as you go, with up-to-date information.

Explicit decision rights

Teams slow down mostly because every decision gets escalated. Writing down what the team decides alone, what it decides after consultation and what stays with senior management removes much of the back and forth. A single page is enough, provided management honours it when it dislikes a delegated decision.

These three changes concern managers first, not teams. That is why the Agile Leadership course is aimed at management and non-IT functions: HR, marketing, support.

Why is agile harder in a hierarchical culture?

In a strongly hierarchical organisation, in Morocco as elsewhere, some habits are perfectly rational: you wait for the boss's approval, you avoid contradicting them in meetings, you break bad news as late as possible. They clash head-on with agile practices:

• a retrospective is pointless if nobody dares say what is wrong in front of their manager;
• a visible board loses its meaning if the real blockers are hidden;
• a "self-organising" team that has every trade-off signed off is self-organising only on paper.

The answer is not to abolish hierarchy but to change its role. A few concrete habits make the difference:

• The manager speaks last in retrospectives and decision meetings, so as not to close the debate from the outset.
• Problems are collected in writing before being discussed, anonymously if need be, while trust builds.
• A problem raised early is welcomed as good news, publicly, the first time it happens.
• Delegated decisions are respected, even when the leader would have chosen differently.

That signal from the top carries more weight than any tool. Conversely, a single public overruling of a delegated decision is enough to send the team back to the old way of working.

How do you start agile with a single team?

A transformation decreed by internal memo produces vocabulary; a pilot produces evidence.

1. Choose a volunteer team with a visible problem: slow recruitment, late campaigns, requests piling up.
2. Appoint a sponsor on the executive committee who protects the experiment and removes obstacles.
3. Set a scope of decision-making for the duration of the pilot, in writing.
4. Start light: a board, a short stand-up, a review with stakeholders, a retrospective. The accountabilities and events of Scrum provide a good framework if the work can be planned in cycles.
5. Measure before and after using indicators you already track, such as time to hire or the lead time for handling a request.
6. Share the results, including what did not work, before extending to a second team.

When several teams need to coordinate, see SAFe and agile at scale; to embed agile in a broader modernisation effort, read our article on digital transformation for SMEs in Morocco.

Agile leadership training in Morocco

Codevista Innovations supports agile transformation beyond IT, notably in HR and marketing, with Scrum, Kanban and Agile Leadership training delivered on site anywhere in Morocco, in hybrid format or remotely. Corporate programmes are tailor-made on the basis of a prior skills audit. Our qualification application with the OFPPT, Morocco's national vocational training office, is in progress, so our programmes cannot yet be funded through its Contrats Spéciaux de Formation (CSF, special training contracts).

Want to try agile with a first HR or marketing team? Let's talk about your context and the pilot that will be most useful to get started.

Frequently asked questions

Is agile suitable for an HR department?

Yes, especially for flow-based work: recruitment, onboarding, employee requests. A Kanban board with work-in-progress limits makes lead times visible and reveals blockages. For performance management, goals reviewed at a short rhythm and regular feedback complement the annual review. Candidate and employee data fall under Law 09-08, Morocco's personal data protection law: they have no place on a shared board.

Should a marketing team use Scrum or Kanban?

It depends on the requests. If the team produces campaigns that can be planned a few weeks ahead, Scrum-style sprints give it a clear rhythm and a clear review point. If it constantly receives unplanned requests, a Kanban flow with explicit priorities is more realistic. Kanban is often simpler to introduce because it starts from the way the team already works; regular reviews can be added later.

What does an agile leader do differently from a traditional manager?

They set outcomes to achieve rather than a list of tasks, make commitments over a short horizon that they revisit regularly, and spell out what the team decides on its own. They control activity less and remove more obstacles. Their authority remains real, but it is exercised through the framework they set, not by signing off every decision.

Where should a Moroccan company start an agile transformation?

With a pilot: a volunteer team, a visible problem, a sponsor on the executive committee and a clear scope of decision-making. Run a few cycles, measure indicators you already track, then share the results before extending. Training the managers involved first avoids a clash with the old way of steering. For funding, the OFPPT's Contrats Spéciaux de Formation (CSF) let a company recover part of its training costs; eligibility conditions should be checked with the OFPPT.