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 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.
Agile Transition Plan Template
Works best for:
Agile Methodology, Agile Workflows
An Agile transformation roadmap can help you, your team, and your organization transition from rigid compliance-heavy methods to the more flexible Agile way of doing things incrementally. From requirements to integrations to security, you can map out your organization's moving parts as “swim lanes” that you can then update regularly. Use your roadmap as a way to tell the story of how you see your product growing over a period of time. Get buy-in without overselling and keep your roadmap simple, viable and measurable. By using an Agile transformation roadmap, you can avoid getting bogged down in details and instead invest in big-picture strategic thinking.
Event Storming
Works best for:
Agile
Event Storming is a collaborative workshop technique for exploring complex business problems and modeling solutions. It fosters communication, uncovers dependencies, and aligns stakeholders by visualizing the flow of events in a system. This template empowers teams to map out processes, identify bottlenecks, and iterate towards more efficient solutions, driving continuous improvement and innovation.
The Agile Manifesto - Pocket Sized Principles
Works best for:
Kanban Boards, Agile Methodology, Agile Wokflows
The Agile Manifesto - Pocket Sized Principles template distills the core principles of agile methodology into a concise and actionable format. By providing a visual reference, this template reinforces agile values and principles, guiding teams towards collaborative, adaptive, and customer-centric practices. This template serves as a reminder of agile principles and encourages teams to embody these principles in their daily work.
DevOps Roadmap Template
Works best for:
Documentation, Product Management, Software Development
DevOps teams are constantly creating code, iterating, and pushing it live. Against this backdrop of continuous development, it can be hard to stay abreast of your projects. Use this DevOps Roadmap template to get a granular view of the product development process and how it fits into your organization's product strategy. The DevOps Roadmap lays out the development and operations initiatives you have planned in the short term, including milestones and dependencies. This easy-to-use format is easily digestible for audiences such as product, development, and IT ops.
Product Discovery Ideation Session
Works best for:
Agile
The Product Discovery Ideation Session template fosters creativity and innovation in product development. By providing a structured framework for brainstorming ideas, exploring user needs, and generating solutions, this template fuels ideation sessions. With sections for user persona development, problem validation, and idea prioritization, it guides teams through the product discovery process, ensuring that solutions are aligned with user needs and market opportunities. This template serves as a catalyst for generating and refining innovative product ideas.
SaaS Implementation Timeline
Works best for:
Agile
The SaaS Implementation Timeline template offers a visual roadmap for planning and tracking the implementation of Software as a Service (SaaS) solutions. It provides a structured framework for defining milestones, allocating resources, and monitoring progress. This template enables organizations to manage SaaS deployments effectively, ensuring successful adoption and realization of business value. By promoting transparency and accountability, the SaaS Implementation Timeline empowers teams to deliver projects on time and within budget, driving organizational agility and competitiveness.