Continuous experimentation, when software engineers are invested in product and business
Talk
Is it virtuous for a company to let its software engineer invest in the product and the business? In contrast to a hands-on approach, we have chosen to take a central role, self-managing, to cover the phases from gathering requirements to following up with users after deployment.
Empirically, we drew on practices such as extreme programming, DDD, and continuous discovery to gradually break down the boundaries of our jobs and rethink them. Meetings accelerated our thinking, pushing us toward an approach based on experimentation at all levels: our organization, our methods, and our deployed code.
Our developments have taken on more meaning, prioritization has become simpler, and this has enriched the value that we bring to users and, as an extension, to our company.
I invite you to delve into our feedback experience. An opportunity to share what we tested, what we abandoned, and what we loved—in short, our daily routine with several caps. Whether your company is tech-centric or not, daring to take an approach that combines diverse profiles and skills becomes a new source of wealth and a business opportunity.