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.
Retrospective - Summer
Works best for:
Retrospectives, Agile Methodology, Meetings
The Retrospective - Summer template offers a seasonal and themed approach to retrospectives, perfect for capturing the spirit of summer. It provides elements for reflecting on achievements, experiences, and goals amidst the summer backdrop. This template enables teams to relax, recharge, and recalibrate their efforts for the upcoming season. By promoting reflection and rejuvenation, the Retrospective - Summer empowers teams to celebrate successes, learn from setbacks, and embark on new adventures with renewed energy and enthusiasm effectively.
5Gs Retrospective
Works best for:
Agile Methodology, Retrospectives, Meetings
The 5Gs Retrospective template offers a structured approach for teams to reflect on their projects or iterations, focusing on five key aspects: Goals, Gains, Gratitude, Gaps, and Growth. It provides elements for identifying achievements, expressing gratitude, and addressing areas for improvement. This template enables teams to conduct retrospectives systematically, fostering a culture of learning, appreciation, and continuous improvement. By emphasizing the five dimensions of reflection, the 5Gs Retrospective empowers teams to optimize their performance, enhance collaboration, and achieve their goals effectively.
Kanban Framework Template
Works best for:
Kanban Boards, Agile Methodology, Agile Workflows
Optimized processes, improved flow, and increased value for your customers — that’s what the Kanban method can help you achieve. Based on a set of lean principles and practices (and created in the 1950s by a Toyota Automotive employee), Kanban helps your team reduce waste, address numerous other issues, and collaborate on fixing them together. You can use our simple Kanban template to both closely monitor the progress of all work and to display work to yourself and cross-functional partners, so that the behind-the-scenes nature of software is revealed.
Kaizen Report Template
Works best for:
Agile Methodology, Operations, Documentation
What makes a great company great? They know that greatness needs to be fostered and maintained — meaning they never stop working to improve. If you’re one of those companies (or aspire to be), a kaizen report is an ideal tool. It creates a simple visual guide to continuous improvement activities on a team, departmental, and organizational level. Using a kaizen report approach, every employee in an organization audits their own processes and understands what they might have overlooked, making this a powerful tool for increasing accountability at all levels.
SAFe PI Planning
Works best for:
Agile
SAFe PI Planning is a collaborative event for Agile Release Trains to plan and align on program increments. It provides a structured framework for setting objectives, identifying dependencies, and sequencing work. This template facilitates PI Planning sessions, enabling teams to visualize their commitments and coordinate cross-team dependencies effectively. By promoting transparency and alignment, SAFe PI Planning empowers Agile organizations to deliver value at scale with predictability and quality.
Lean Inception
Works best for:
Agile, Meetings
Lean Inception is a collaborative workshop for aligning teams on project goals and scope. It provides a structured framework for defining the product vision, user personas, and feature prioritization. This template enables cross-functional teams to collaborate, validate assumptions, and establish a shared understanding of the project vision and objectives. By promoting early alignment and customer-centric thinking, Lean Inception empowers teams to kickstart projects with clarity and purpose, driving efficiency and innovation from the outset.