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.
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.
User Story Map Template
Works best for:
Marketing, Desk Research, Mapping
Popularized by Jeff Patton in 2005, the user story mapping technique is an agile way to manage product backlogs. Whether you’re working alone or with a product team, you can leverage user story mapping to plan product releases. User story maps help teams stay focused on the business value and release features that customers care about. The framework helps to get a shared understanding for the cross-functional team of what needs to be done to satisfy customers' needs.
Lean Inception Workshop
Works best for:
Agile, Lean Methodology
The Lean Inception Workshop streamlines project kickoff by aligning teams on goals, scope, and priorities. It leverages Lean principles to eliminate waste and maximize value, guiding exercises to define user personas, map user journeys, and prioritize features. By fostering cross-functional collaboration and customer-centric thinking, this template accelerates project initiation and ensures alignment between stakeholders, empowering teams to deliver customer value faster.
Design Sprint Retrogram
Works best for:
Agile, Retrospective
The Design Sprint Retrogram template facilitates retrospective sessions for Design Sprint teams to reflect on their experiences and identify improvement opportunities. It provides a structured framework for reviewing sprint outcomes, discussing what worked well, what didn't, and generating actionable insights. This template fosters a culture of continuous learning and refinement, empowering teams to enhance their sprint process and deliver better outcomes in subsequent sprints.
Change Control Process Template
Works best for:
Agile Methodology, Documentation, Product Management
You can predict, research, and plan for every detail of a project to go a certain way—then along comes the unforeseen and modifications are needed. That’s when a change control process comes into play. It helps define the right steps to take, gives stakeholders full visibility, and reduces the chances of errors and disruption. And this template is easy to use and highly effective—for ensuring that proposed changes are reviewed before they’re implemented, and empowering teams to veto changes that might prove unnecessary or disruptive.
Backlog Refinement with Jira Template
Works best for:
Agile, Backlog Refinement
The Backlog Refinement with Jira template in Miro improves collaboration among team members. It provides a visual and interactive space for teams to review, prioritize, and clarify upcoming work items together in real time. This collaborative approach ensures alignment on priorities and details, leading to a more organized and efficient workflow. The seamless integration with Jira automatically syncs all changes, reducing the need for manual updates and keeping both platforms up-to-date.
Scrum Puzzle
Works best for:
Agile
The Scrum Puzzle is a collaborative activity that reinforces Scrum roles, artifacts, and ceremonies. By assembling a puzzle representing the Scrum framework, teams gain a deeper understanding of its components and how they interrelate. This template offers a fun and interactive way to reinforce Scrum knowledge and promote team alignment, empowering practitioners to apply Scrum principles effectively and deliver value with agility.