How Marketing Can Achieve a Faster, More Collaborative Workflow w/
summary
Describes converting a waterfall marketing team into a Scrum marketing workflow inside GitLab: issues, boards, labels, templates, milestones and epics hold a single backlog; copy lives in repositories and is treated as copy as code with branches and merge requests; marketing commits small front-end changes into staging of developers’ repos and uses burndown charts to match a six‑week shipping cadence (development moved from six months to six weeks). Service Desk captures customer feedback into the backlog. The change takes months to onboard but yields faster, traceable releases and fewer cross-team handoffs.
AI-written summary · about
chapters (13)
- 0:00Introduction and background
- 3:13Marketing challenges in tech
- 5:19Uniting divided marketing teams
- 7:06Adopting GitLab for collaboration
- 9:55Transitioning to agile marketing
- 12:48Coffee as code and sprints
- 15:15Breaking team silos with DevOps
- 17:04Marketing contributing to code
- 19:53Marketing’s own code and stack
- 21:17Customer-centric workflows
- 25:10Integrating customer feedback
- 26:38Key takeaways and conclusion
- 27:46Q&A session
related talks
27mFrom Waterfall to Agile to DevOps with GitLab
42mElevate Your Expertise: the power tools and smart processes of a modern...
49mBaking Boards: Tweak the Recipe for Agile Development
21mFighting Git Workflows
19mCrossing the Divide: How GitOps Brought AppDev & Platform Teams Together!
35mKanban, our way
21mGitLab: The Asynchronous Enterprise
28mBuilding Better Communication for Kubernetes Contributors with Marketing