Growing our team with retrospectives ↦
From Kira Booth writing on the Plaid blog.
…we take an agile-like approach to how we think about process. If our team’s process isn’t working, we talk about it in a retrospective (aka “retro”) and figure out how to change it. Many companies don’t begin retros until they are large and have many processes in place, but we feel that retros are especially valuable at our size and rate of growth.
Plaid’s engineering organization is rapidly growing. In the Salt Lake City office where I work, we have plans to grow from 20 to 60 engineers this year. Processes that worked just a few months ago may not work now. A culture of continuous process improvement helps us to stay ahead of growing pains like inefficient collaboration, error-prone coding practices, and interpersonal conflict.
Sign in or Join to comment or subscribe