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.
Learning Loop Retro Template
Works best for:
Retros, Agile
The Learning Loop Retro template is a powerful tool designed to help teams reflect on their projects by recognizing successes and identifying areas for improvement. This template is part of Miro's Intelligent templates, which streamline workflows and keep teams engaged by integrating AI, interactive tools, and seamless integrations. One key benefit of the Learning Loop Retro template is its ability to drive continuous improvement. By regularly reflecting on their work and identifying areas for enhancement, teams can consistently elevate their performance and achieve better outcomes.
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.
Sprint Review Template
Works best for:
Sprint Review, Agile
The Sprint Review Template is a vital tool in Agile project management that enhances communication between team members and stakeholders by providing a clear format for presenting the sprint's accomplishments and challenges. It encourages active participation and feedback from all attendees, leading to more informed decision-making and continuous improvement. In essence, it's a catalyst for meaningful dialogue and collaborative growth.
121 Kanban
Works best for:
Kanban Boards, Agile Methodology, Agile Workflows
121 Kanban template streamlines task management by providing a structured framework for prioritization and execution. It encourages a focused approach to task completion by limiting work in progress (WIP) and promoting collaboration between team members. With clear visualization of tasks and progress, teams can maintain workflow balance and deliver high-quality results efficiently.
What? So What? Now What? Template
Works best for:
Agile Workflows, Retrospectives, Brainstorming
The What? So What? Now What? Framework empowers you to uncover gaps in your understanding and learn from others’ perspectives. You can use the What? So What? Now What? Template to guide yourself or a group through a reflection exercise. Begin by thinking of a specific event or situation. During each phase, ask guiding questions to help participants reflect on their thoughts and experience. Working with your team, you can then utilize the template to record your ideas and to guide the experience.
Kanban Successful Evolutionary Change
Works best for:
Kanban Boards, Agile Methodology, Agile Workflows
Kanban Successful Evolutionary Change template guides organizations through the process of implementing Kanban methodology for gradual and sustainable workflow improvement. By emphasizing incremental changes and continuous feedback, this template fosters a culture of continuous improvement and adaptability. Teams can visualize their workflow, identify bottlenecks, and implement changes iteratively, leading to improved efficiency and productivity.