Design Planning

Welcome to the Jira for Designers series, brought to you by Design at Scale™ Academy. In a previous article, we discussed ReDefine the Relationship(↘︎Link) and how we might approach entering development environments. This article will take a more practical approach to product design delivery in complex development environments.

Despite the basic product development routines like sprint planning(↘︎Link), stand-ups(↘︎Link), daily calls(↘︎Link), and retrospective(↘︎Link) allocation(↘︎Link) show and tell(↘︎Link) empower large organisations. Design, on the other hand, has to align with their design system teams’(↘︎Link) central function(↘︎Link), which is operation design leadership(↘︎Link) and management(↘︎Link). If we get all these routines together, we might soon end up having more meetings than actually producing any qualitative or quantitative work. Therefore, our weekly deliverables tend to combine these meetings into shorter, more productive slots.

Sprint panning

Sprint planning is no different from development spring planning. However, we tend to differ in what we discuss in the context of existing and new components in a design system. Importantly, we often align with our colleagues in…