New York, NY
There’s a lot to learn before you can successfully grow your own food, but GROW simplifies the process with a smart planter and an app to go with it. Their hardware and software development teams use Clubhouse to build a complete solution.
Merging hardware and software comes with its own unique project management challenges. As Idan Cohen, co-founder and CEO, puts it, "There’s a diversity of roles even in a small team — we have less than ten people in the company. If you had a software company that size, probably everyone would know the codebase. For us, we have a hardware engineer and different front-end and back-end software engineers, plus firmware and electrical engineers. All of these people work together, but they have very little understanding or knowledge about the work that the other person is doing. That brings some new challenges into managing a product."
Compared to teams where there is the looming concern about information siloes, at GROW it’s important that everyone be able to just focus on their own piece. The custom views help them do this. Along with co-founder, Andrew Wanliss-Orebar, Idan can easily keep an eye on the big picture and track progress across the enterprise.
Each of our teams uses the built-in structure to fit their different needs. With the different views and advanced filtering, they build and views their task pipeline the way they see fit. This in-built flexibility means we're a more dynamic and productive team.Idan Cohen, Co-Founder GROW
Rather than working in sprints, they track progress weekly, setting plans for the following week at the end of each week. Every week, before the planning meeting, a team member picks the stories they plan to work on in the following week and sets the status of status of those stories to "Upcoming."
During the planning meeting, the team discusses the upcoming tasks, and if everyone agrees on those stories being the focus for the next week, they’re set to "Current," then moved to "In Development" and "Ready for Sign-off" as progress is made.
Other than that, the individual teams and employees shape their Clubhouse usage depending on what their needs are. The software team often has to deal with multiple, interdependent tasks, and makes heavy usage of dependencies and states.
Meanwhile, the manufacturing team often has to deal with following up with the factory, reviewing product, and so on, without many internal dependencies, which means they use Clubhouse as more of an advanced task-list where everyone can track external project and add notes that the team (and management) can view as needed.
This flexibility and ability to create a more granular (or more streamlined) workflow depending on what individual teams need makes Clubhouse the perfect fit for GROW as it carves its niche in the gardening industry.