www.agilesherpas.com
Open in
urlscan Pro
2606:2c40::c73c:6702
Public Scan
Submitted URL: https://www.agilesherpas.com/e3t/Btc/GE+113/cTjm204/VWYjc33c1W7PW6-csdK38P6VBW5wYw0_4BRDywN3Z5r9G3lLBGV1-WJV7CgVgYW3dm8488SgD...
Effective URL: https://www.agilesherpas.com/blog/kanban-for-agile-marketing?utm_medium=email&_hsmi=192747766&_hsenc=p2ANqtz-8ferID_7MmT1Brph...
Submission: On December 08 via manual from DE — Scanned from DE
Effective URL: https://www.agilesherpas.com/blog/kanban-for-agile-marketing?utm_medium=email&_hsmi=192747766&_hsenc=p2ANqtz-8ferID_7MmT1Brph...
Submission: On December 08 via manual from DE — Scanned from DE
Form analysis 2 forms found in the DOM
POST https://forms.hsforms.com/submissions/v3/public/submit/formsnext/multipart/7291028/f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7
<form novalidate="" accept-charset="UTF-8" action="https://forms.hsforms.com/submissions/v3/public/submit/formsnext/multipart/7291028/f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7" enctype="multipart/form-data"
id="hsForm_f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_742" method="POST"
class="hs-form stacked hs-custom-form hs-form-private hsForm_f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7 hs-form-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7 hs-form-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_0bb774e2-d455-485c-b6c2-f26af6c8cde0"
data-form-id="f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7" data-portal-id="7291028" target="target_iframe_f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_742" data-reactid=".hbspt-forms-1">
<div class="hs_email hs-email hs-fieldtype-text field hs-form-field" data-reactid=".hbspt-forms-1.1:$0"><label id="label-email-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_742" class="" placeholder="Enter your Email"
for="email-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_742" data-reactid=".hbspt-forms-1.1:$0.0"><span data-reactid=".hbspt-forms-1.1:$0.0.0">Email</span><span class="hs-form-required" data-reactid=".hbspt-forms-1.1:$0.0.1">*</span></label>
<legend class="hs-field-desc" style="display:none;" data-reactid=".hbspt-forms-1.1:$0.1"></legend>
<div class="input" data-reactid=".hbspt-forms-1.1:$0.$email"><input id="email-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_742" class="hs-input" type="email" name="email" required="" placeholder="" value="" autocomplete="email"
data-reactid=".hbspt-forms-1.1:$0.$email.0" inputmode="email"></div>
</div>
<div class="hs_blog_agilesherpas_blog_27827265935_subscription hs-blog_agilesherpas_blog_27827265935_subscription hs-fieldtype-radio field hs-form-field" style="display:none;" data-reactid=".hbspt-forms-1.1:$1"><label
id="label-blog_agilesherpas_blog_27827265935_subscription-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_742" class="" placeholder="Enter your Notification Frequency"
for="blog_agilesherpas_blog_27827265935_subscription-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_742" data-reactid=".hbspt-forms-1.1:$1.0"><span data-reactid=".hbspt-forms-1.1:$1.0.0">Notification Frequency</span></label>
<legend class="hs-field-desc" style="display:none;" data-reactid=".hbspt-forms-1.1:$1.1"></legend>
<div class="input" data-reactid=".hbspt-forms-1.1:$1.$blog_agilesherpas_blog_27827265935_subscription"><input name="blog_agilesherpas_blog_27827265935_subscription" class="hs-input" type="hidden" value=""
data-reactid=".hbspt-forms-1.1:$1.$blog_agilesherpas_blog_27827265935_subscription.0"></div>
</div>
<div class="hs_lifecyclestage hs-lifecyclestage hs-fieldtype-radio field hs-form-field" style="display:none;" data-reactid=".hbspt-forms-1.1:$2"><label id="label-lifecyclestage-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_742" class=""
placeholder="Enter your Lifecycle Stage" for="lifecyclestage-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_742" data-reactid=".hbspt-forms-1.1:$2.0"><span data-reactid=".hbspt-forms-1.1:$2.0.0">Lifecycle Stage</span></label>
<legend class="hs-field-desc" style="display:none;" data-reactid=".hbspt-forms-1.1:$2.1"></legend>
<div class="input" data-reactid=".hbspt-forms-1.1:$2.$lifecyclestage"><input name="lifecyclestage" class="hs-input" type="hidden" value="subscriber" data-reactid=".hbspt-forms-1.1:$2.$lifecyclestage.0"></div>
</div><noscript data-reactid=".hbspt-forms-1.2"></noscript>
<div class="hs_recaptcha hs-recaptcha field hs-form-field" data-reactid=".hbspt-forms-1.3">
<div class="input" data-reactid=".hbspt-forms-1.3.0">
<div class="grecaptcha-badge" data-style="inline" style="width: 256px; height: 60px; box-shadow: gray 0px 0px 5px;">
<div class="grecaptcha-logo"><iframe title="reCAPTCHA"
src="https://www.google.com/recaptcha/enterprise/anchor?ar=1&k=6Ld_ad8ZAAAAAAqr0ePo1dUfAi0m4KPkCMQYwPPm&co=aHR0cHM6Ly93d3cuYWdpbGVzaGVycGFzLmNvbTo0NDM.&hl=de&v=_7Co1fh8iT2hcjvquYJ_3zSP&size=invisible&badge=inline&cb=u46n0dua9pgz"
width="256" height="60" role="presentation" name="a-efpg99ucsoz6" frameborder="0" scrolling="no" sandbox="allow-forms allow-popups allow-same-origin allow-scripts allow-top-navigation allow-modals allow-popups-to-escape-sandbox"></iframe>
</div>
<div class="grecaptcha-error"></div><textarea id="g-recaptcha-response-2" name="g-recaptcha-response" class="g-recaptcha-response"
style="width: 250px; height: 40px; border: 1px solid rgb(193, 193, 193); margin: 10px 25px; padding: 0px; resize: none; display: none;"></textarea>
</div><iframe style="display: none;"></iframe>
</div><input type="hidden" name="g-recaptcha-response" id="hs-recaptcha-response" value="" data-reactid=".hbspt-forms-1.3.1">
</div>
<div class="hs_submit hs-submit" data-reactid=".hbspt-forms-1.5">
<div class="hs-field-desc" style="display:none;" data-reactid=".hbspt-forms-1.5.0"></div>
<div class="actions" data-reactid=".hbspt-forms-1.5.1"><input type="submit" value="Subscribe" class="hs-button primary large" data-reactid=".hbspt-forms-1.5.1.0"></div>
</div><noscript data-reactid=".hbspt-forms-1.6"></noscript><input name="hs_context" type="hidden"
value="{"rumScriptExecuteTime":1547.900001525879,"rumServiceResponseTime":1912.900001525879,"rumFormRenderTime":2.4000015258789062,"rumTotalRenderTime":1951.400001525879,"rumTotalRequestTime":363.7999954223633,"embedAtTimestamp":"1638977882923","formDefinitionUpdatedAt":"1601894174237","pageUrl":"https://www.agilesherpas.com/blog/kanban-for-agile-marketing?utm_medium=email&_hsmi=192747766&_hsenc=p2ANqtz-8ferID_7MmT1BrphFYiPVx_A4PuWAQor8PxW2EncZ8ZK1jndY7sBOhVB6wofOMpPhHEOe9E_cB3DY26lWzuBn3tgK4-w&utm_content=192747766&utm_source=hs_email","pageTitle":"Beginner's Guide to Kanban for Agile Marketing","source":"FormsNext-static-5.417","sourceName":"FormsNext","sourceVersion":"5.417","sourceVersionMajor":"5","sourceVersionMinor":"417","timestamp":1638977882925,"userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36","originalEmbedContext":{"portalId":"7291028","formId":"f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7","formInstanceId":"742","pageId":"33201785940","region":"na1","pageName":"Beginner's Guide to Kanban for Agile Marketing","inlineMessage":true,"rawInlineMessage":"Thanks for submitting the form.","hsFormKey":"481c1ae2578ec6ff33dd7214664f68ae","target":"#hs_form_target_form_873880952","contentType":"blog-post","formsBaseUrl":"/_hcms/forms/","formData":{"cssClass":"hs-form stacked hs-custom-form"}},"canonicalUrl":"https://www.agilesherpas.com/blog/kanban-for-agile-marketing","pageId":"33201785940","pageName":"Beginner's Guide to Kanban for Agile Marketing","formInstanceId":"742","urlParams":{"utm_medium":"email","_hsmi":"192747766","_hsenc":"p2ANqtz-8ferID_7MmT1BrphFYiPVx_A4PuWAQor8PxW2EncZ8ZK1jndY7sBOhVB6wofOMpPhHEOe9E_cB3DY26lWzuBn3tgK4-w","utm_content":"192747766","utm_source":"hs_email"},"renderedFieldsIds":["email"],"rawInlineMessage":"Thanks for submitting the form.","hsFormKey":"481c1ae2578ec6ff33dd7214664f68ae","formTarget":"#hs_form_target_form_873880952","correlationId":"fb967327-75df-41e4-bdfc-fadb3b52e7ab","contentType":"blog-post","hutk":"25460fe03655b1a161975a8b4a9b8ce5","captchaStatus":"LOADED","isHostedOnHubspot":true}"
data-reactid=".hbspt-forms-1.7"><iframe name="target_iframe_f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_742" style="display:none;" data-reactid=".hbspt-forms-1.8"></iframe>
</form>POST https://forms.hsforms.com/submissions/v3/public/submit/formsnext/multipart/7291028/f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7
<form novalidate="" accept-charset="UTF-8" action="https://forms.hsforms.com/submissions/v3/public/submit/formsnext/multipart/7291028/f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7" enctype="multipart/form-data"
id="hsForm_f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_3930" method="POST"
class="hs-form stacked hs-custom-form hs-form-private hsForm_f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7 hs-form-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7 hs-form-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_bd56f1f2-decc-4251-baa4-b7a3a81f0162"
data-form-id="f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7" data-portal-id="7291028" target="target_iframe_f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_3930" data-reactid=".hbspt-forms-0">
<div class="hs_email hs-email hs-fieldtype-text field hs-form-field" data-reactid=".hbspt-forms-0.1:$0"><label id="label-email-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_3930" class="" placeholder="Enter your Email"
for="email-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_3930" data-reactid=".hbspt-forms-0.1:$0.0"><span data-reactid=".hbspt-forms-0.1:$0.0.0">Email</span><span class="hs-form-required" data-reactid=".hbspt-forms-0.1:$0.0.1">*</span></label>
<legend class="hs-field-desc" style="display:none;" data-reactid=".hbspt-forms-0.1:$0.1"></legend>
<div class="input" data-reactid=".hbspt-forms-0.1:$0.$email"><input id="email-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_3930" class="hs-input" type="email" name="email" required="" placeholder="" value="" autocomplete="email"
data-reactid=".hbspt-forms-0.1:$0.$email.0" inputmode="email"></div>
</div>
<div class="hs_blog_agilesherpas_blog_27827265935_subscription hs-blog_agilesherpas_blog_27827265935_subscription hs-fieldtype-radio field hs-form-field" style="display:none;" data-reactid=".hbspt-forms-0.1:$1"><label
id="label-blog_agilesherpas_blog_27827265935_subscription-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_3930" class="" placeholder="Enter your Notification Frequency"
for="blog_agilesherpas_blog_27827265935_subscription-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_3930" data-reactid=".hbspt-forms-0.1:$1.0"><span data-reactid=".hbspt-forms-0.1:$1.0.0">Notification Frequency</span></label>
<legend class="hs-field-desc" style="display:none;" data-reactid=".hbspt-forms-0.1:$1.1"></legend>
<div class="input" data-reactid=".hbspt-forms-0.1:$1.$blog_agilesherpas_blog_27827265935_subscription"><input name="blog_agilesherpas_blog_27827265935_subscription" class="hs-input" type="hidden" value=""
data-reactid=".hbspt-forms-0.1:$1.$blog_agilesherpas_blog_27827265935_subscription.0"></div>
</div>
<div class="hs_lifecyclestage hs-lifecyclestage hs-fieldtype-radio field hs-form-field" style="display:none;" data-reactid=".hbspt-forms-0.1:$2"><label id="label-lifecyclestage-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_3930" class=""
placeholder="Enter your Lifecycle Stage" for="lifecyclestage-f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_3930" data-reactid=".hbspt-forms-0.1:$2.0"><span data-reactid=".hbspt-forms-0.1:$2.0.0">Lifecycle Stage</span></label>
<legend class="hs-field-desc" style="display:none;" data-reactid=".hbspt-forms-0.1:$2.1"></legend>
<div class="input" data-reactid=".hbspt-forms-0.1:$2.$lifecyclestage"><input name="lifecyclestage" class="hs-input" type="hidden" value="subscriber" data-reactid=".hbspt-forms-0.1:$2.$lifecyclestage.0"></div>
</div><noscript data-reactid=".hbspt-forms-0.2"></noscript>
<div class="hs_recaptcha hs-recaptcha field hs-form-field" data-reactid=".hbspt-forms-0.3">
<div class="input" data-reactid=".hbspt-forms-0.3.0">
<div class="grecaptcha-badge" data-style="inline" style="width: 256px; height: 60px; box-shadow: gray 0px 0px 5px;">
<div class="grecaptcha-logo"><iframe title="reCAPTCHA"
src="https://www.google.com/recaptcha/enterprise/anchor?ar=1&k=6Ld_ad8ZAAAAAAqr0ePo1dUfAi0m4KPkCMQYwPPm&co=aHR0cHM6Ly93d3cuYWdpbGVzaGVycGFzLmNvbTo0NDM.&hl=de&v=_7Co1fh8iT2hcjvquYJ_3zSP&size=invisible&badge=inline&cb=2qswuwf7i3e4"
width="256" height="60" role="presentation" name="a-fvxgl5xrcksj" frameborder="0" scrolling="no" sandbox="allow-forms allow-popups allow-same-origin allow-scripts allow-top-navigation allow-modals allow-popups-to-escape-sandbox"></iframe>
</div>
<div class="grecaptcha-error"></div><textarea id="g-recaptcha-response-1" name="g-recaptcha-response" class="g-recaptcha-response"
style="width: 250px; height: 40px; border: 1px solid rgb(193, 193, 193); margin: 10px 25px; padding: 0px; resize: none; display: none;"></textarea>
</div>
</div><input type="hidden" name="g-recaptcha-response" id="hs-recaptcha-response" value="" data-reactid=".hbspt-forms-0.3.1">
</div>
<div class="hs_submit hs-submit" data-reactid=".hbspt-forms-0.5">
<div class="hs-field-desc" style="display:none;" data-reactid=".hbspt-forms-0.5.0"></div>
<div class="actions" data-reactid=".hbspt-forms-0.5.1"><input type="submit" value="Subscribe" class="hs-button primary large" data-reactid=".hbspt-forms-0.5.1.0"></div>
</div><noscript data-reactid=".hbspt-forms-0.6"></noscript><input name="hs_context" type="hidden"
value="{"rumScriptExecuteTime":1547.900001525879,"rumServiceResponseTime":1912.8000030517578,"rumFormRenderTime":2.5,"rumTotalRenderTime":1915.8000030517578,"rumTotalRequestTime":362.6999969482422,"embedAtTimestamp":"1638977882919","formDefinitionUpdatedAt":"1601894174237","pageUrl":"https://www.agilesherpas.com/blog/kanban-for-agile-marketing?utm_medium=email&_hsmi=192747766&_hsenc=p2ANqtz-8ferID_7MmT1BrphFYiPVx_A4PuWAQor8PxW2EncZ8ZK1jndY7sBOhVB6wofOMpPhHEOe9E_cB3DY26lWzuBn3tgK4-w&utm_content=192747766&utm_source=hs_email","pageTitle":"Beginner's Guide to Kanban for Agile Marketing","source":"FormsNext-static-5.417","sourceName":"FormsNext","sourceVersion":"5.417","sourceVersionMajor":"5","sourceVersionMinor":"417","timestamp":1638977882922,"userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36","originalEmbedContext":{"portalId":"7291028","formId":"f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7","formInstanceId":"3930","pageId":"33201785940","region":"na1","pageName":"Beginner's Guide to Kanban for Agile Marketing","inlineMessage":true,"rawInlineMessage":"Thanks for submitting the form.","hsFormKey":"5265580c5ab10843d03e44f6e1460b46","target":"#hs_form_target_form_598257226","contentType":"blog-post","formsBaseUrl":"/_hcms/forms/","formData":{"cssClass":"hs-form stacked hs-custom-form"}},"canonicalUrl":"https://www.agilesherpas.com/blog/kanban-for-agile-marketing","pageId":"33201785940","pageName":"Beginner's Guide to Kanban for Agile Marketing","formInstanceId":"3930","urlParams":{"utm_medium":"email","_hsmi":"192747766","_hsenc":"p2ANqtz-8ferID_7MmT1BrphFYiPVx_A4PuWAQor8PxW2EncZ8ZK1jndY7sBOhVB6wofOMpPhHEOe9E_cB3DY26lWzuBn3tgK4-w","utm_content":"192747766","utm_source":"hs_email"},"renderedFieldsIds":["email"],"rawInlineMessage":"Thanks for submitting the form.","hsFormKey":"5265580c5ab10843d03e44f6e1460b46","formTarget":"#hs_form_target_form_598257226","correlationId":"020670f3-05fa-4882-b45f-e659cf7f6ecb","contentType":"blog-post","hutk":"25460fe03655b1a161975a8b4a9b8ce5","captchaStatus":"LOADED","isHostedOnHubspot":true}"
data-reactid=".hbspt-forms-0.7"><iframe name="target_iframe_f8b6db0e-d23f-44c9-b9b5-01bd2a190aa7_3930" style="display:none;" data-reactid=".hbspt-forms-0.8"></iframe>
</form>Text Content
This website stores cookies on your computer. These cookies are used to improve
your website experience and provide more personalized services to you, both on
this website and through other media. To find out more about the cookies we use,
see our Privacy Policy.
We won't track your information when you visit our site. But in order to comply
with your preferences, we'll have to use just one tiny cookie so that you're not
asked to make this choice again.
Accept Decline
* Your Path
* Successes
* Resources
* Blog
* About
Contact Us
* Your Path
Transform the Marketing Organization Develop an Agile Marketing Team Educate
Individual Agile Marketers
* Successes
Charles River Laboratories M&T Bank
* Resources
* Blog
* About
About AgileSherpas Why Agile Marketing? Become a Sherpa
TRANSFORM THE MARKETING ORGANIZATION
Enterprise-grade solutions and support to achieve the balance of speed, quality,
and strategy that Agile marketing offers.
Learn More
DEVELOP AN AGILE MARKETING TEAM
Achieve team-wide efficiency AND effectiveness with Agile marketing. All built
by marketers, for marketers.
Learn More
EDUCATE INDIVIDUAL AGILE MARKETERS
ICAgile-accredited training, both online and off (post-COVID, of course). Less
waste. Fewer reviews. More work that matters.
Learn More
CHARLES RIVER LABORATORIES
In conversation with Darci Helbling, Executive Director, Global Marketing
Operations, discussing her department's Agile journey, how this way of working
is helping them solve their process challenges and how the pandemic has
influenced their marketing operations.
Learn More
M&T BANK
In conversation with Zach Meixner, Senior Digital Program Manager, discussing
M&T marketing before Agile, the challenges of adoption, his team's favorite
Agile techniques so far and success metrics they're measuring.
Learn More
ABOUT AGILESHERPAS
Learn who we are, and why we're "special" unicorns. (Hint: Marketers + Agilists
+ Trainers & Coaches)
Learn More
WHY AGILE MARKETING?
Agile marketing is a unique discipline. Our custom approach helps individuals,
teams, and organizations navigate the path.
Learn How
BECOME A SHERPA
AgileSherpas is always looking for marketers to join our team of coaches. See
what it takes to become one of us.
Learn More
BEGINNER'S GUIDE TO KANBAN FOR AGILE MARKETING
by Andrea Fryrear
At the core of Kanban lies a paradox: by limiting the amount of work we do, we
become more productive. That’s one of the things that make Kanban one of the
most preferred Agile frameworks.
When you consider how much time we lose to multitasking (or, more accurately,
task switching, since no one can truly multitask), you can see why this
seemingly paradoxical methodology is so useful.
Compared to Scrum, Kanban is a young work-management method. Its main objective
is to visualize a team’s workflow and improve the efficiency of processing
tasks.
David J. Anderson best articulated its application to software development, in
2013, in the foundational book Kanban: Successful Evolutionary Change for Your
Technology Business, and its adoption hasn’t been as universal as Scrum’s during
the early days of Agile software development. But, for teams that chafe under
the strictures of the Scrum process, Kanban can be a freeing alternative.
ORIGINS OF KANBAN
Although it was adapted to knowledge work only a few years ago, the concept of
kanban (lower case k) has been around for decades.
The Japanese term “kanban” translates to “signal card,” and was originally
developed by Toyota in the 1940s. Inspired by grocery stores, which stock only
as much product as people need, Toyota’s manufacturing teams began using cards,
or kanbans, to signal to other parts of the production line that they needed
more parts.
The use of kanban was part of a JIT (Just in Time) approach that enabled plants
to create only as many parts as were needed at the time and to conserve
resources by not making extra. This production system created the foundations of
Lean by setting the goal to create value without wasting resources.
AVOIDING WASTE ON THE ASSEMBLY LINE
Let’s say my job is to put tires on a car. It’s wasteful for me to have hundreds
of tires that I don’t yet need piled up behind me.
It’s efficient for the team that makes tires to produce them just in time for me
to install them on a car. So once my stock reaches an agreed-upon point, say a
dozen tires on hand, I put out a kanban card to spur the tire-making team to
action. Throughout the assembly line, “workers at each step in the process are
not allowed to do work unless they are signaled with a kanban from a downstream
step.”
When applied to software development and marketing, a Kanban implementation
doesn’t typically include physical signal cards that cause another worker to
begin work.
Instead, the signal to pull new work is inferred from the visual quantity of
work-in-progress in any given state.
For example, if I’m responsible for editing content on my marketing team, I
infer from the amount of work in the “Edit ready” column that it is or isn’t
time to pull a new project into my own workload. (This assumes that the number
of items in progress in the “editing” column falls below the set WIP limit,
enabling me to pull in additional work; more on that shortly.)
KANBAN VS. KANBAN
Like Scrum, a Kanban implementation requires a prioritized Backlog of
work-to-be-done, from which the team pull their work.
Business owners and stakeholders are responsible for religiously maintaining and
prioritizing that list, because it is the sole source of work for the marketing
team.
You’ve probably seen kanban tracking boards used on all kinds of teams, but
simply having a Backlog and moving work from one side of a whiteboard to another
doesn’t mean you’re using Kanban. Anderson reminds us that “card walls are not
inherently kanban systems. They are merely visual control systems. They allow
teams to visually observe work-in-progress and self-organize, assign their own
tasks, and move work from a backlog to complete without direction from a project
or line manager.
However, if there is no explicit limit to work-in-progress and no signaling to
pull new work through the system, it is not a kanban system.”
So, putting a bunch of cards on a wall doesn’t mean you’re using Kanban.
In fact, many Scrum teams use this type of visualization to manage their work.
The primary piece that sets Kanban apart is the commitment to limiting
work-in-progress (WIP).
THE COOL POWER OF WIP LIMITS
Instead of using timeboxes to govern their work, as a Scrum team does, a Kanban
team uses WIP limits. Each state of work has an upper limit of productive work
that it can contain.
After the team exceeds that limit, waste enters the system. That upper limit
then becomes a formalized piece of the Kanban process.
Team capacity can be optimized by limiting WIP. It feels counterintuitive at
first, but team members embark on new work only when the previous task is
finished, preventing them from getting overwhelmed by their workload.
This limit is one of the core practices of Kanban. It allows the team to be
efficient, fluid, and focused on the workflow. But WIP limits aren't constant;
they vary from team to team and from one state of work to another.
For example, your team of 5 might have a WIP limit of 10 on their “Doing”
column, enabling each person to work on 2 things at once. The limit on work
being reviewed, however, might be different, depending on how long this piece of
the workflow takes, how many people are assigned to review work, and other
factors.
Routinely experiment with your WIP limits and document the outcomes, to ensure
that your Kanban system functions at its highest possible level.
FIVE CORE PROPERTIES OF KANBAN
WIP limits may be Kanban’s core defining feature, but it’s not all you need.
Anderson defines five core properties that make for a successful implementation:
1. Visualize Workflow
2. Limit Work-in-Progress
3. Measure and Manage Flow
4. Make Process Policies Explicit
5. Use Models to Recognize Improvement Opportunities
Unlike Scrum, Kanban doesn’t prescribe a way of managing work; it doesn’t
dictate regular meetings or create unique roles within the team.
Kanban enables you to boost the flexibility of already established workflows.
With that being said, Kanban assumes that you already have some form of
work-management process in place, and that you want to continuously improve it.
This makes Kanban easier than Scrum for marketing teams to implement, because
you can start Kanban with little educational overhead.
The good thing about Kanban is that you can start with what you do now. The
method easily points out the problematic areas of the workflow, so you can
address them and plan their improvement.
Kanban also adapts readily to changing contexts. No two teams -- even within the
same department -- implement it in exactly the same way. This makes sense: the
bottlenecks in each team’s workflow are distinct, so each team’s improvement
strategy is distinct. For Anderson, this approach is freeing:
> "Kanban is giving permission in the market to create a tailored process
> optimized to a specific context. Kanban is giving people permission to think
> for themselves...You have permission to try Kanban. You have permission to
> modify your process. You have permission to be different. Your situation is
> unique and you deserve to develop a unique process definition tailored and
> optimized to your domain, your value stream, the risks that you manage, the
> skills of your team, and the demands of your customers."
If you’re new to Agility and aren’t yet ready to think for yourself, this may
sound terrifying rather than freeing; you might start with a Scrum
implementation before moving toward Kanban.
VISUALIZING FLOW WITH YOUR KANBAN BOARD
The Kanban board is a core element of the Kanban framework. The board contains
columns, and each one symbolizes a stage of the work process (e.g. To Do, Doing,
Done). The cards in the columns show the progress of each task; the board helps
the team to visualize the workflow and commit to the right amount of work.
The first rule of your first Kanban board is that it reflect reality rather than
the official or ideal process for completing work on your marketing team.
Your first task is to identify the start and end points for your team. Where do
you take over complete control of work, and where do you hand it off to another
team or department? These mark the beginning and end of your workflow
visualization.
Next, fill in what happens on the team between those two points.
One way to visualize how work makes its way through the team.
Think of any significant gates or gatekeepers in your workflow -- such as
approvals, reviews, handoffs from one person to another, or releases out into
the world -- and use those to define the columns of your board. Another approach
is to think of parts of your workflow that have limits as to how many tasks can
be in the same stage at the same time before your effectiveness in getting them
all done begins to degrade.
At its simplest, a marketing Kanban board can start with five columns: To Do,
Create, Review, Test, and Done.
A content team might start with one like this:
CREATING YOUR FIRST KANBAN BOARD
You may find it useful to sketch the flow organically, without trying to fit it
into the vertical column view, before translating it into this format.
The first few weeks are likely to see lots of changes to your board layout, so
don’t stress about getting it perfect the first time. You're free to create as
many columns as you need and experiment with the visualization. Use a format
that can easily be changed, such as dry-erase markers and sticky notes on a
whiteboard.
Once you’re confident that the flow reflects your team’s flow, you can create a
more permanent version with tape or software.
Depending on the type of work that your team typically does, columns just for
work that has left one state and is waiting to be pulled into the next may be
useful. Known as buffers, these columns can help some teams visualize
bottlenecks.
This sample content marketing board, for example, includes columns for content
that is ready to be reviewed and ready to be published.
When first setting up your Kanban board, don’t be too restrictive with the WIP
limits you place on each column; make them a little higher than you need. Your
workflow will be plagued by variability, waste, and bottlenecks early on, and
you don’t want those problems to interfere with the introduction of a pull-based
mentality.
The Kanban board is great for facilitating workflow transparency and for
applying positive reinforcement. As opportunities for improvement become clear,
you can reduce WIP limits and add buffers accordingly.
DAILY STANDUPS AND AFTER MEETINGS
The daily standup meeting is an integral part of Kanban just as it is in Scrum,
but the format deviates slightly.
The Kanban board accurately representation of all work in progress eliminates
the need for team members to give daily status updates. Instead, the meeting
centers on how work is flowing (or not flowing) through the system. A
facilitator of some kind walks the board, usually from right to left, reviewing
the cards and, when need arises, querying team members for a status update or
information that the team does not already have.
A Kanban standup focuses on blocked items (a status that indicated on the card
with a flag) or on cards that haven’t changed status in several days.
This condensed style of standup is one reason that Kanban teams can be
considerably larger than Scrum teams. Teams as large as 50 can complete these
kinds of standups in under 15 minutes, a rate not feasible using the Scrum
standup format.
Many Kanban teams also engage in what’s known as an After Meeting, an informal
gathering of team members who are collaborating on their own projects.
Anderson reports that this ceremony “emerged as spontaneous behavior because
team members wanted to discuss something on their minds: perhaps a blocking
issue, perhaps a technical design or architecture issue, but more often, a
process-related issue.” As a result, After Meetings tend to be fertile ground
for ideas to improve process and generate innovations.
REPLENISHING THE KANBAN QUEUE
In place of Review and Retrospectives, Kanban teams use queue-replenishment
meetings to keep their backlog prioritized and refined. They must happen at
regular intervals, but their cadence doesn’t need to be tied to any other cycle
of Kanban.
So, even if you release new content every week, your queue replenishment might
need to occur only once a month. Whatever timing you choose, make sure that it’s
consistent, because “a steady cadence for queue replenishment reduces the
coordination cost of holding the meeting and provides certainty and reliability
over the relationship between the business” and the marketing team.
Whenever possible, include a wide variety of decision makers from the
most-senior management position available in queue replenishment.
These attendees can often provide more contextual detail and make decisions
where lower-level attendees would have to defer. The goal is to produce a
Backlog from which the marketing team can work with the utmost confidence, so
you need attendees that can make that happen during the meeting.
6 STEPS FOR SUCCEEDING WITH KANBAN
If you choose Kanban as your first Agile marketing methodology, keep in mind
that the “essence of starting with Kanban is to change as little as possible,”
and that you want to map your existing workflow and processes before you begin
the ongoing improvement efforts.
This recipe for success comes from David Anderson, who crafted it based on his
experience as a new manager adopting an existing team. For marketing teams
looking to adopt this methodology, these steps serve you equally well:
1. Focus on Quality: Anderson focused on this step first to cut down on the
amount of time a development team spends on dealing with software defects;
marketers would do well to start here too. Without a commitment to producing
the highest possible quality of marketing work, it doesn’t really matter if
you can enhance your productivity.
2. Reduce Work-in-Progress: There is a direct correlation between a lower WIP
limit and an increase in quality, so this second step must be implemented
along with, or immediately after, Step 1. Reducing the amount of work that
the team and its members do at any given time lowers the time it takes to
complete work and improves its quality. Keep your WIP as low as possible.
Period.
3. Deliver Often: Frequent releases of content, email, social-media posts, and
pretty much any other marketing collateral that you can think of builds
trust with audiences and stakeholders. They also increase the number of
learning opportunities for your Agile team.
4. Balance Demand Against Throughput: In this step you’re focused on finding a
rate for accepting new work into the marketing Backlog that corresponds with
the rate you can deliver high-quality marketing work. This is effectively
limiting the WIP for your Backlog, and it means that discussions about
priorities and commitments to completing new work can happen only after some
work has been released. This balance produces some slack in the team’s
capacity; only those working in the bottleneck areas are constantly busy,
and even they must not be given cause to feel overwhelmed. Slack is
powerful, because it enables team members to focus on doing their jobs with
precision and quality and gives them time to apply themselves to improving
the team and its workflow. This step can be difficult, because we tend to
want to optimize our workflow to use up everyone’s available time; but
Kanban’s continuous improvement demands a system with some slack, which can
only be achieved by balancing demand against throughput.
5. Prioritize: When you have no predictability in your team, prioritization
doesn’t much matter, which is why it’s down here at Step 5. But when
high-quality work is going out steadily and the team has some slack in their
days, management can begin to ensure that the most valuable work is being
done. Additionally, for marketing teams that lack political capital in an
organization, building up confidence by showing an improved workflow may
need to precede any attempt to change strategy or priorities.
6. Attack Sources of Variability to Improve Predictability: Variability is
undesirable because it results in more WIP and longer release cycles. But
understanding its effects and how to reduce it are advanced and difficult
topics. When you’ve reached a high level of Agile maturity, you can tackle
this final step by experimenting with your existing process policies.
DISCOVERING THE AGILE SYSTEM THAT’S RIGHT FOR YOUR TEAM
Teams who don’t take well to the rigidity of Scrum may find freedom in a Kanban
system, while those who need additional insulation from upper management may
need the buffer of a Scrum master and Product Owner.
For teams completely unused to agile methodologies, the ritual and constancy of
Scrum may offer them a sense of security. Kanban is more often adopted when
Scrum begins to break down, and so may be a good second iteration of agile
marketing for some teams.
The important thing is not to try and force your marketing team into a system
that isn’t right for them.
Agile is about constant improvement, and that goes for your processes as well as
your products.
GET FREE ADVICE FROM LEADING EXPERTS IN AGILE MARKETING IN YOUR INBOX EVERY
WEEK.
New subscribers get a free Agile Marketing Quick Start Guide too!
Email*
Notification Frequency
Lifecycle Stage
Share this post:
ANDREA FRYREAR
Andrea Fryrear is a co-founder of AgileSherpas and oversees training, coaching,
and consulting efforts for enterprise Agile marketing transformations. See More
From Andrea Fryrear Find Andrea Fryrear Online
RELATED RESOURCES
View Resource Center
THE RISE OF AGILE MARKETING: HOW TO MOVE FROM THEORY TO PRACTICE WEBINAR
View Recording
4TH ANNUAL STATE OF AGILE MARKETING REPORT
Get It Now
4TH ANNUAL STATE OF AGILE MARKETING WEBINAR
View Recording
RELATED POSTS
View Blog
AGILE MARKETING IS THE ANSWER TO MARKETERS’ WOES: DATA ON WHY
Read Post
AGILE ACCELERATION: 4TH ANNUAL STATE OF AGILE MARKETING REPORT
Read Post
ENTERPRISE MARKETING AGILITY
Read Post
* Your Path
* Transforming the Marketing Organization
* Develop an Agile Team
* Educate Individuals
* Services
* Agile Marketing Fundamentals
* Agile Marketing Leadership
* 90-Day Jumpstart Program
* Coaching
* Why Agile Marketing?
* Resources
* Blog
* About
* Agile Marketing
* Our Team
* Become a Sherpa
* Contact
* Find us Online
*
SIGN UP FOR AGILESHERPAS BLOG NOTIFICATIONS
Email*
Notification Frequency
Lifecycle Stage
©2021 AgileSherpas Privacy Policy