Skip to main content



Some Digital agencies have a project process where waterfalls still plays a big part of it, and as far as I can tell, the tech team is usually the one suffering as they are at the last part of the chain left with limited budget and time for execution.

I do believe that adopting an Agile approach could make a Digital Agency better and faster.
In this article I’m presenting you just another point of view of why it make sense looking at Agile Methodology. 

Why Agile for a Digital Agency?

The Agile movement started in the software development industry, but it has being proven to be useful in others as well. It becomes handy for the type of business that has changing priorities, changing requirements and flexible deliverables.

In the Digital Agency of today you need a different mindset. Creative will always play a huge role (“the bread and butter”). But the “big guys” need to understand that without technology there is no Digital Agency. Technical resources are just as important as creative resources for the modern Agencies. If we talk about multi-touch campaigns, multi-platform solutions, CRM, APIs and so on; you would see how everything is supported by technology.

“In this industry the Techy needs to be creative and creative need to become techier.”

From the Creative/Design perspective perfection is the desire. Agile is more around iterations, as perfection might never come and, if you think about it, it may never be necessary. You need something done, functional, scalable in order to get to where you want to. At that collision of thoughts comes frustration from both parties. The solution comes with compromise and collaboration.

I like to think that creative is the dreamer side (crazy and amazing ideas drives innovation. But things like budget are just stones in the way) were the technical side are the ones making the reality check (inspired to make something amazing real and tangible. But the reality check sometimes looks like pessimism under some eyes). But when synergy happens then this middle ground gives you a different chemistry that provides flexibility.

I believe that Agile goes well with Digital agencies were scope changes, the budget is always a challenge, client change their minds, the talent (resources) switches. In the Agile methodology true collaboration comes into play. For those Digital Agencies that claims collaboration as one of their key elements then it should be a good fit.

By just reading the 1st principal from where the Agile Manifesto is based on, you can tell how beneficial is the Agile approach: “Customer satisfaction by rapid delivery of useful software”

The 2nd nails it for UX cases, were clients keep adding or changing requirements: “Welcome changing requirements, even late in development”

In addition if you look at the 3rd item of the Agile Manifesto you will see how important is engaging the stakeholders: “Customer collaboration over Contract negotiation”

If you are a manager moving forward with this concept then here are some tips around your POC when bringing Agile inside the walls of your Digital shop:
  1. Proof of Concept (POC) by picking 2 projects (small and medium size for example)
  2. Engage the client. Without them this process will fail. Their feedback is key in order to provide the product/service they are expecting. This means your account team is also key maintaining a healthy and transparent communication. The account team should not be a blocker between the client technical team and the digital agency tech team, but they should be aware of everything that is happening. If you heard about extreme programming, where developers work in pair over the same code using the same computer (taking turns), well that type of collaboration has to happen between the account and the PM, at such point that you could not tell which one is what. This will bring the PM closer to the client and the account closer to the tech team (you need your account team to become techier, after all they are the front-line of your army).
  3. Select a PM, a Creative and a Tech (your leads for your POC) that will lead your teams through the Agile process implementation. The PM should be different from the PM of the actual project selected for the POC, as it should be focus on the Agile implementation. (Note: if the budget allows it the PM lead can be a consultant, preferably with experience on Agile Methodology)
  4. Have daily meetings with your leads until the time when the POC start. Mentor/guide them, your support as a manager is key. When the POC start then switch to weekly meeting with your leads. Also one-on-one with members of the team (informal coffee breaks perhaps) will provide valuable feedback.
  5. “Lessons learned” sessions after each iteration and at the end of the POC are crucial as it will help you find:
  • The pros and cons of the implementation
  • Tweaks/adaptations that needs to be made to the process
  • A better understanding that will help to make the proper selection around the tools (software) for supporting your new process.

Some ideas on how to measure the Agile POC

  1. Client feedback. Around execution and product/service delivered (expectations/quality). Make them part of the process by asking them questions about the experience, for example: “what are your thoughts about the project and the process? What can be improved? Do you find this better than our previous process? Was the change in the execution noticeable?”
  2. Get feedback (survey) from all the members of the internal team that participated in the POC. After all is the team that will have to deal with the process on a daily basis. “It is not a process by force, it should flow naturally”. Remember there is always room for improvement.
  3. Budget. Make a comparison between the POC and other projects of the same size.
  4. Quality. Engage your QA team to evaluate and compare the POC with other projects deployment cycles.
  5. Present the results to others in the organization by organizing a Q&A session. Receive more feedback…


As you make mistakes, adjust the process to your needs, gather feedback and finally established a process that works for the Agency (for the client and your team) then you’ll need to arm your army with the required tools.

From the development perspective your development team already most be using tools for their cycle. If they don’t then you need to quickly fix that:

  • Version Control System (VCS) for your files (creative documents, code, assets, etc). You have several flavors:
  • TFS
  • SVN
  • Git
  • Mercurial

  • Continuous Integration (CI): several tools out there. It will depend on your budget, your team. Also consider the “flexible aspect”, meaning how well integrates with your other tools (for example your VCS):
  • Microsoft Visual Studio TFS
  • Teamcity
  • Jenkins
  • Bamboo
  • CruiseControl
  • To have a full picture you want a tool that helps you with your Application Lifecycle Management (ALM), that goes well with Agile, works not only to handle your tech side, but also your creative side of your company (you are a Digital Agency) and, if possible, integrates well with your other tools (CIs and VCSs that are part of this cycle). Essentially something that glues everything together, reducing the use of a few things that can slow down a team or misplace “stuff” like:

  1. Multiple Emails with different versions of the requirements list
  2. Emails with out-of-date spreadsheets and other files
  3. Client feedback
  4. Bug lists
  5. Members of the team not knowing the due date of the project
  6. And others
           Here are a list of software that can get you started and move away from the previous list of issues:

Final thought:
Do not be afraid of mixing things up. It is not an exact science and there is no need to enforce every little detail of the “Agile”. Tweak, adapt and find the formula that works for your client relationship, the productivity, the team collaboration and product quality.

If you are still with me then I would like to invite you on taking the time to see this TED video:
-    Agile Programming for your family:


Trending posts

Headless CMS - yet another CMS comparison

If you have used, or are familiar with the term headless CMS (content management system), then you will know the reason behind it. In summary a CMS is called headless because there is no Front end (FE), or output coupled with the CMS. Instead the CMS supports APIs which expose the content that can be consumed by external applications.                                                                 Photo by fotografierende from Pexels We could say that a decoupling from the CMS is provided, allowing, for those that have chosen this alternative, a certain sense of “freedom” in selecting the FE of the solution. There are many reasons for selecting the most popular, and so called “traditional” CMSs in the market. Even though, not sure if it is proper to call them “traditional” anymore as they keep evolving, becoming stronger and versatile and offering new services including SaaS. Even some are providing a flavor of headless. I have my fair share of experience using some of the greatest

Essence of email deliverability - SPF, DKIM, DMARC and segmentation

Recently I attended a lively discussion on email deliverability hosted by Litmus, one of the leading providers of email marketing tools. As email marketers one of the core metrics we often rely on is email deliverability and the discussion was around how to improve the email deliverability in today’s world where our audiences are ever inundated with emails. In addition we often find ourselves operating in a very competitive landscape vying for these audiences' precious attention. Photo by Ivan Samkov from Pexels   Hence it’s becoming increasingly important to ensure our emails are reaching our audiences’ inbox and driving engagement. This is why email clicks and engagement are strong indicators of the performance of our email campaigns instead of just the delivery rate of our campaigns partly thanks to Apple’s Mail Privacy Protection . So let’s start with the distinction between email delivery and email deliverability . This is very well articulated by Dimiter Batmaziam in the Li

Blue Ocean Strategy in the new reality

Photo by Kammeran Gonzalez-Keola from Pexels Since the COVID lockdown started over a year ago I have seen many restaurants in my neighborhood go through transformations - many became available in the top three delivery service: Ubereats, Doordash and Skipthedishes while the rest transformed to support pick up service and patio dining. However, among all of them, one of my favorite Indian restaurants impressed me the most.  The restaurant initially became available via the delivery services just after the lockdown in early 2020. I first ordered from the restaurant via Ubereats. In the delivery the restaurant included a pamphlet encouraging me to order from them directly on their website with an initial enticing offer. I ordered immediately after a few days from their website. I was guided to create an account and subscribe to their newsletter in the process.  The delivery for the order was on time and the food as always was delicious and of high quality. In a few days I received a

Goal setting frameworks for Product Management - OKR and HOSKR

As a business analyst and product manager we often use various frameworks to synthesize and organize our product ideas and goals. I think of frameworks as tools in our product management tool kit which we use depending on the task at hand.  And speaking of goals, OKR is a very popular framework that I often use to set the goals for the products I am managing. However recently I participated the #ProductCon conference hosted by Product School  and I stumbled upon one of the talks in which Rapha Cohen, the CPO at Google Waze introduced a more effective framework for setting product goals. The framework is called HOSKR.  In this post I'll describe both the OKR and HOSKR frameworks in more details using examples. I hope this will provide you, our readers, more practical insights on how to effectively use these frameworks to set your product goals.  OKR OKR stands for O bjectives and K ey R esults. If you are reading this post then you are on our Beolle blog and I am going to use one o

This blog uses cookies to improve your browsing experience. Simple analytics might be in place for pageviews purposes. They are harmless and never personally identify you.