Does it ever really feel like your SEO suggestions and initiatives get misplaced within the shuffle or deprioritized by different groups?
When you work in-house, you’ve probably skilled the “worry of lacking out” (FOMO) in terms of getting your optimization work correctly resourced and carried out.
The excellent news is {that a} undertaking administration methodology referred to as “Agile” may help cross-functional groups self-organize and collaborate extra successfully.
By understanding the agile ceremonies (conferences) and processes, you possibly can higher combine with and affect the event cycles to make sure your Search engine optimization necessities don’t get ignored.
On this article, we’ll cowl the important thing facets of the agile methodology, map out the assorted agile conferences it is best to goal to take part in and supply tips about the right way to write efficient tickets and acceptance standards so your Search engine optimization adjustments get prioritized and launched.
Say goodbye to FOMO and begin getting your Search engine optimization work performed by way of the ability of agile processes.

How agile undertaking administration stops FOMO
An agile strategy makes you a part of the method with the groups that get issues performed.
AI could also be trending, however I imagine the agile framework is enduring. In contrast to AI, which will depend on synthetic or software program intelligence, agile depends on how groups naturally set up to perform duties.
It prioritizes tangible options and enhancements. More and more, main know-how groups are embracing agile for its capability to boost enterprise worth and effectivity in managing complicated initiatives.
A fast overview of the agile methodology
Agile undertaking administration is a technique of managing your undertaking work in small, incremental segments that may be simply assigned, simply managed and accomplished inside a brief time frame referred to as an iteration or dash.


Historically, undertaking administration adopted a waterfall-style strategy. On this technique, all of the work is accomplished upfront and buyer suggestions is gathered afterward.
The method can take months to finish, which isn’t all the time excellent, particularly whenever you need to launch a product MVP to the market forward of your competitor. (Sound familiar?)
The agile model is extra iterative as a result of work is designed to be accomplished in brief cycles (sprints), the place suggestions and enhancements (to each the product itself and the groups concerned) are constructed into the method.
Agile has its roots within the software program improvement world. The important thing components are:
For context, that is the manifesto for agile software development:


Agile is based on 12 principles:


My favourite ones are:
- Enterprise individuals and builders should work collectively day by day all through the undertaking.
- Steady consideration to technical excellence and good design enhances agility.
- At common intervals, the group displays on the right way to turn out to be simpler, then tunes and adjusts its conduct accordingly.
- See that? When groups use agile, everybody alongside the way in which turns into a part of the group that works on the precise work. Collectively, everybody accomplishes large issues.
Agile rules are inherently about collaboration and steady enchancment. Any group can use this strategy to lean considering and working to ship worth to their clients.
In previous articles, I’ve referenced the agile methodology and the way it’s executed utilizing a scrum framework.
A scrum-based course of is nice for dealing with large or intricate options as a result of it’s iterative and permits fast market entry. It permits groups to be taught from buyer suggestions and incorporate on-the-go enhancements.
However, Kanban and waterfall methodologies normally take a extra step-by-step, linear strategy.
A core agile group usually consists of:
- A product manager.
- A undertaking/program supervisor.
- Leads from supporting groups like engineering, consumer expertise, QA and SMEs like Search engine optimization.
Inside this construction, day by day and weekly ceremonies (or conferences) assist everybody align on the work and transfer issues ahead.
The work is designed to be accomplished in a time-boxed dash, normally 1-2 weeks. All tickets in a given dash needs to be completed in that point for the group to realize their desired velocity.
Dig deeper: SEO product management: Key framework and fundamentals


It’s a steady cycle. Incremental enhancements are thus achieved utilizing what’s referred to as an Agile Release Train.
For ecommerce websites, these groups enhance facets like product element pages, the on-site search performance or the checkout course of.
Get the day by day publication search entrepreneurs depend on.
The best way to combine with an agile group
Conceptually, that is about understanding the workflow of cross-functional groups utilizing agile. Now, fellow Search engine optimization skilled Aleyda Solis wrote:
“Aligning Search engine optimization with the goals and targets of your internet improvement, design and product groups helps hold everybody on the identical web page. This can allow you to determine one of the simplest ways to prioritize Search engine optimization wants and create a plan of motion together with your counterparts from different groups that retains everybody on monitor and transferring in the identical course.
For instance, if the net improvement group works in sprints, understanding how lengthy every dash is may help you coordinate cheap targets for every one.”
Along with understanding the dash length, understanding when and the place to hitch key conferences is essential. Enterprise stakeholders take part at completely different factors within the dash. As such, greedy the broader agile scrum course of will present much more context.
Not taking the time to be taught and familiarize your self with the assembly rituals of groups utilizing agile scrum can perpetuate the sensation of chaos. You don’t know the place to be, what to do or the right way to get different groups that will help you get work performed.
The secret’s to identify the sample.
I’ll information you in recognizing this sample so you possibly can determine who to collaborate with, when conferences occur and what you might want to put together.
Let’s start with the people concerned within the agile course of.
Discover the conductors
First, discover the product supervisor.
When you’re a enterprise stakeholder, you might be largely exterior of this day by day course of. This particular person is your touchpoint to serving to you navigate the agile group’s assembly cadence and might advise you on the place and the right way to submit a ticket.
Enterprise homeowners are primarily introduced in originally (to outline “the ask” to the group) and on the finish (to validate the output).
The second particular person to search out is the discharge prepare engineer (mainly the lead engineer).
This particular person facilitates the agile launch prepare execution, managing dangers and dependencies alongside the way in which. This particular person will largely be capable of information the technical nuances of how your request will get carried out in order that it may be efficiently launched.
Tangentially, you’d do effectively additionally to determine the undertaking supervisor. (This position can have completely different names from scrum grasp to supply supervisor.)
Functionally, they assist the product supervisor when it comes to organizing the group’s present dash and backlog (the lineup of tickets to be labored on) they usually usually report back to the broader group as to the continued standing of the work.
When you determine these roles in your group, they may help direct you to the assorted conferences to attend.
Agile undertaking administration ceremonies (conferences)
The second step is understanding what conferences to attend and the way you assist transfer the group ahead.
On this part, I’ll map out the place you as a enterprise stakeholder must plan to be, the assembly varieties, after they happen and who might be there. As an SEO product manager, I function as each a companion when it comes to being a topic skilled and a enterprise stakeholder.
Taking part in these conferences that assist the agile undertaking administration methodology helps me be within the know whereas partnering with cross-functional groups to get work performed.
Since agile permits for groups to self-organize, beneath is an summary of normal assembly phrases and kinds one would see as a part of this course of.
Stand-up
That is typically day by day or each different day in a given week. These are usually 15-minute conferences the place the agenda is a roundtable of group updates and/or any areas the place they’re blocked with their work.
Enterprise stakeholders don’t usually attend stand-ups however it may be useful to attend a couple of, particularly if it’s been dropped at your consideration that the group has questions on a ticket they’re engaged on in your group.
As a enterprise stakeholder, the day by day stand-ups are what you need to get invited to. It’s a discussion board to listen to what everyone seems to be engaged on, the place they’re blocked, or if they’ve questions associated to your ticket(s) you possibly can assist reply.
Observe that standups aren’t the place to introduce new work. An applicable time for that’s dash planning.
Grooming
That is usually an hour-long, bi-weekly or weekly assembly, relying upon the dash cadence. That is the place the product supervisor and undertaking supervisor speak with the groups (engineering, design/consumer expertise, and many others.) in regards to the work and the extent of effort concerned with every ticket earlier than including it right into a dash.
As soon as there’s a way of the scale and scope of every ticket, it will get added to the dash.
It is a key assembly for enterprise stakeholders to attend as a result of they pitch their ticket to the group engaged on it, reply questions and supply any extra context like precedence or severity. It’s vital to come back ready, be temporary, useful and thorough.
In preparation for grooming, create your ticket by figuring out the kind of ticket you’re bringing to the group. Usually, it’s both a difficulty or an enhancement and might be categorised as the next:
- A bug (i.e., one thing that labored as soon as however doesn’t work now).
- A brand new function or performance.
- A regression (i.e., a earlier performance is now not working as anticipated).
I cowl this in additional element when it comes to how SEO teams can write an effective ticket, which you should use as a information to adapt to combine your personal group’s specs.
Tip: Use quantitative metrics in your acceptance standards and supply the supply for the place the work is to be seen and permitted as full. (For Search engine optimization, it’s typically the supply code. For different groups, it may be “buyer expertise might be X”)
As a enterprise proprietor, when your request and pitch are crystal clear in your ticket, you’re extra prone to get work performed.
Refinement
These might be hour-long conferences and occur as wanted as a result of they’ll apply to the set of present tickets for a dash or the tickets within the backlog.
Ongoing refinement conferences goal to convey the group collectively to align on necessities, modify ticket degree of effort (LOE), QA enter, and many others.
Everyone knows know-how adjustments shortly. This a part of the agile course of helps groups plan necessities and adapt based mostly on present market circumstances.
Dash planning
That is the place the group plans the work that might be included within the upcoming dash. Every dash is normally time-boxed for 1-2 weeks, throughout which all tickets (slated work) are accomplished.
Efficient dash planning leads to your complete group scoping the extent of effort of every ticket and finishing it within the dash. Ideally, their KPI output of velocity tendencies up and to the appropriate.
Being current through the dash planning assembly will assist you to get a view of what the group might be engaged on and delivering within the brief time period.
Having that predictability issue of deliberate work permits the group to concentrate on chipping away at both tech debt or growth-related initiatives. Providing a pleasant stability of an offensive and defensive technique in direction of holistic enchancment.
Backlog refinement
This assembly can happen as wanted when the group wants to arrange and/or prioritize the backlog of tickets they’ve queued up. Usually, this assembly entails the product supervisor, undertaking supervisor and an engineering lead.
A giant a part of the agile scrum methodology is all the time having a “wholesome, groomed” backlog of labor for teammates to choose up as capability permits.
Whereas enterprise stakeholders don’t normally attend this assembly, it may be useful to ask the undertaking supervisor in regards to the group backlog to higher perceive the place there are wants or alternatives for the group to tackle extra work or massive initiatives that may be damaged down.
The operative phrases listed here are “damaged down.” In agile, large initiatives are all the time damaged down into particular person tickets.
Demo/showcase
Happens when the function is purposeful and able to show to stakeholders earlier than going into manufacturing or a stay atmosphere.
The undertaking supervisor schedules it when the engineering group is able to share and showcase their progress to a wider viewers. Stakeholder attendance is essential right here as this can be a touchpoint the place the group validates what’s constructed meets expectations.
As talked about above, if you happen to did an intensive job of together with quantifiable Acceptance Standards in your ticket, by this level within the improvement course of, it’ll be simple to substantiate the ticket is finished.
Retrospective (retro)
This assembly is organized by the undertaking supervisor and happens after the dash is accomplished. Right here, your complete group comes collectively to speak about what went effectively/what didn’t within the current dash and the way they’ll enhance for the longer term.
Exterior stakeholders must take part on this assembly, particularly when their work was a part of the dash, as a result of it’s a time to construct camaraderie and assist everybody enhance.
An effective way to do that is to come back ready with 1-2 tickets as examples and the tangible good or dangerous issues that occurred. Stick with the information and spotlight how issues might be improved. Your suggestions ought to come from a spot of collective development and enchancment working as a group.
The large takeaways listed here are: whenever you’re coming to an agile group with an ask for his or her effort and time, stakeholders ought to present clear, concise info within the ticket relating to “what” is required (not “how,” that’s for the agile group to find out). Be succinct in your replies to assist the group determine to allow them to transfer ahead in architecting an answer.
The FOMO is subsiding, sure? Since you’re turning into a part of the answer.
No. Extra. Worry.
How can I get requested to work with the agile group once more?
It’s sort of addictive, you recognize? Getting issues performed.
When you get one thing carried out, you need extra. The FOMO begins truly to subside since you’re collaborating.
You could have all of the calendar invitations of the group’s assembly cadence. You understand your POCs that facilitate interlocks and communication and when your ticket is able to be reviewed and signed off on.
When you play your playing cards proper, you may even get invited to their inner Slack channel!
The easiest way to make sure you get to work with these groups once more is to assist the group full the work they’ve collectively dedicated to finishing within the time-boxed dash (alliteration is enjoyable). You do that by being engaged and ready.
The best way to not let your necessities get missed
Write this down: Make them quantifiable!
On the outset, outline the ask in easy phrases: listed here are some examples of effective (and ineffective) tickets and the consumer story immediate that will help you crystalize the problem and the ask.
Once more, to quote Solis:
“Verifying that Search engine optimization-related dev requests or tickets have been appropriately carried out is an important step in direction of the specified final result throughout Search engine optimization execution.”
Sure! And also you do that by defining clear and quantifiable acceptance standards (AC) in your ticket.
As a enterprise proprietor, you possibly can present the AC to stipulate your expectation of how one thing features and/or the specified buyer expertise.
The extra quantifiable you may make it, the simpler it’s to validate and provides the group the thumbs up that the work is finished.
A quantifiable output is preferable to a qualitative one as a result of the latter is subjective, and it’s possible you’ll not get precisely what you’re on the lookout for.
For instance, as an Search engine optimization product supervisor, one in all my frequent Search engine optimization-related ACs for hyperlinks is that they’re formatted as:
- The <a href> should be in view:supply.
- The <a href> should be with out parameters.
That criterion is a straightforward sure/no response whenever you see that within the code. It’s both there, in that format, or it’s not. Cross/fail QA.
So, the takeaway is to incorporate quantifiable AC within the ticket. This can permit you to align with the group on the DoD (definition of performed) and simply spot-check and confirm its completion.
How do I do know if my group is utilizing agile?
Actually, ask. Discover somebody with the title of product supervisor and ask them, “Hey, fast query: Are we utilizing the agile technique for undertaking administration? In that case, can I get invited to the day by day stand-up conferences to rise up to hurry with what the group has deliberate within the present dash?”
Whenever you get that invite. Present up on time (actually, as a result of these conferences are brief). Hear. Take notes. The extra you attend the group’s ceremonial conferences, the extra it should sink in.
That’s the way you get issues performed
You now have the best-kept secret of the right way to get issues performed. I do know this can be a lot. It is likely to be new or international to you. And it’s all along with your day-to-day goings on. However discovering these groups is value it. Plugging into the agile course of is the way you get issues performed with broader groups.
When you don’t imagine me that this works, simply proceed working as you’ve gotten. Don’t interact; simply watch as all of your tickets get relegated to some group’s backlog. Nonetheless, if you wish to get large initiatives launched and create change, attempt it. Implement what I’ve outlined right here, take possession and function this manner. I promise you’ll get outcomes. Agile is designed for output.
As an in-house Search engine optimization product supervisor, I can say firsthand that studying about and working throughout the agile framework (and doing so at completely different firms) has taken a couple of years to acclimate to. And if I’m being trustworthy, I’m nonetheless studying. However, like something, the extra you do it and interact and talk together with your teammates, the simpler it will get.
Opinions expressed on this article are these of the visitor creator and never essentially Search Engine Land. Workers authors are listed here.
