Agile Marketing Kanban
This is an Agile marketing KanBan board that is used by the marketing team from the first talk with the client on a daily basis until the finish of the project.
Trusted by 65M+ users and leading companies
This KanBan is meant for one client/one project operation like setting up a web page, digital campaign, organising an event etc.
Step 1: Planning
1.1. Client Brief: Plans, goals & wishes (45 minutes)
This exercise is used for the first briefing with the client about the specific project. It is meant as a support for the briefing interview that the marketing team has at the beginning of the project. You ask the client questions about their goals, expectations, target market, the most important goals and/or wishes and write it down in the sections. We advise that the whole team is present at the first client briefing.
1.2. Client Brief: Decider(s) & budget (15 minutes)
In the briefing interview you also need to get critical information about the decider(s), what is important to them and of course what is the budget for the project. In the Other notes write down anything that the team finds important for the project.
1.3. Task force (15 minutes)*:
Based on the first client briefing, now comes the time that the whole marketing team figures out all the roles that are needed in order to successfully deliver the project on time and with high quality. Based on roles, the team writes down all the tasks that have to be done in order to finish the project successfully. If the relationship with the client is on good grounds, the team defines the Definition of Done with the client. Otherwise, the team defines it alone. The Definition of Done is an agreed-upon set of items that must be completed before a project or user story can be considered complete. It is applied consistently and serves as an official gate separating things from being “in progress” to “done.”When all tasks are written down, make sure to check if some of the tasks are too big to be done in one day and break it down into one-day tasks.
1.4. Priority (15 minutes)*:
After all the tasks are written down, the team decides on the priority of the tasks together with the client or the decision is made by the person that has the most contact with the client. You decide on which tasks are the most important right now and have to be done in the next 14 days? The most important or critical tasks are put on the top of the pyramid, the least at the bottom. The most important tasks can be added also under the pyramid.
Step 2: KanBan (10 minutes):
Team members meet every day for a short Daily stand up, where they answer three questions:Which tasks did I do yesterday?Which tasks will I do today?Am I expecting any problems and where?Discuss about the WIP limit - how many tasks can be waiting for the clients approval. This is to protect the autonomy of the team. Tasks that are Done are put in the Done sections. After 14 days you do a Review: the whole team presents the client what was done, gets feedback and tries to move tasks from Validation into Done. Here you also discuss the Priority pyramid.
Step 3: Retro (12 minutes)*
After the Review and before the next Planning the whole team does a retrospective.
Switch on: What do we have to start doing better? (4 minutes)
Switch off: What do we need to stop doing? (4 minutes)
Status quo: What is ok, we are satisfied with it and we can leave it as it is? (4 minutes)
*Task force, Priority and Retros are done every 14 days.
Get started with this template right now.
Kanban Planner 2024 Week & Month
Works best for:
Kanban Boards, Agile Methodology, Agile Workflows
KANBAN Planner 2024 Week & Month template provides a flexible framework for planning and managing tasks on a weekly and monthly basis. By organizing tasks by priority and deadlines, teams can optimize their workflow and ensure timely delivery of projects. This template fosters transparency and accountability, enabling teams to collaborate effectively and achieve their goals efficiently.
Quick Retrospective Template
Works best for:
Education, Retrospectives, Meetings
A retrospective template empowers you to run insightful meetings, take stock of your work, and iterate effectively. The term “retrospective” has gained popularity over the more common “debriefing” and “post-mortem,” since it’s more value-neutral than the other terms. Some teams refer to these meetings as “sprint retrospectives” or “iteration retrospectives,” “agile retrospectives” or “iteration retrospectives.” Whether you are a scrum team, using the agile methodology, or doing a specific type of retrospective (e.g. a mad, sad, glad retrospective), the goals are generally the same: discovering what went well, identifying the root cause of problems you had, and finding ways to do better in the next iteration.
The Hot Air Balloon Retrospective
The Hot Air Balloon is a simple activity for helping the team identify things that makes them move faster, and things that slow them down.
Hiring Process Template
Works best for:
Operations, Org Charts, Kanban Boards
Having a hiring process in place simplifies that process each step of the way, from recruiting for the position to making finalizing offers. This simple, effective template will give you a straightforward, high-level view of where employees are as they move from applicant to new hire.
4Ps Retrospective
The 4Ps Retrospective template offers a structured framework for teams to reflect on past iterations or projects using the 4Ps model (Praise, Problems, Possibilities, and Plans). It provides elements for sharing positive feedback, identifying challenges, exploring opportunities, and setting action plans. This template enables teams to conduct retrospectives systematically, generate actionable insights, and drive continuous improvement. By promoting a balanced and comprehensive approach, the 4Ps Retrospective empowers teams to enhance collaboration, boost morale, and achieve their objectives effectively.
All-in-one PI Planning
Works best for:
Agile
The All-in-one PI Planning template streamlines the SAFe Program Increment (PI) Planning process by providing a comprehensive framework for teams to collaboratively plan and align on objectives and dependencies. It integrates essential elements such as PI Objectives, Team Breakouts, and Program Board, enabling teams to visualize, prioritize, and coordinate work effectively. This template empowers Agile Release Trains to deliver value predictably and efficiently, driving alignment and synchronization across the organization.