It’s understandable to have the notion that a bigger team could get a project done faster. More hands means more work and more work means more gets done, right? Well, that’s not the case when it comes to product development. Efficiency in product development comes from small, independent teams.
When you have developers working on multiple projects, it’s actually more likely that less will get done. When you try to do everything, you ultimately end up doing nothing. It’s why we apply agile development principles when approaching a build.
Each team has one goal. Having too many goals can lead to confusion, and confusion will certainly lead to failure. Each team has a clear customer, a clear target user. They have to know the audience they are solving the problem for. With smaller groups the most important aspects of product development is made that much easier. Interaction is fast, communication is open, and customer feedback can be constantly incorporated.
These autonomous teams are often made up of a product owner, a front-end developer, more back-end developers, a designer, and a QA engineer. Not every project will call for all of these members. The purpose is to have a team that can work independently, one that can take a project from idea to completion completely on their own. Whatever team members are necessary to make this happen will be there, and these members must be in place before moving forward. The last thing you want is to be scrambling to fill gaps in the middle of production.
From a company standpoint, coordinating all of these teams would appear to be the tricky part. Truth is, when you these groups are truly independent, coordination isn’t an issue. That’s not to say that there aren’t some projects that require multiple teams to be working in tandem. So how do you approach coordination here?
Communication. That’s the key. Team members meet on a near daily basis for progress updates. Product owners are encouraged to attend these meetings as well. As a product owner, you should not only want to be in the loop every step of the way… it’s essential to your product’s success. It’s at these meetings that the team can reveal progress and present demos.
When team members take initiative to share work and communicate the process becomes simple and light weight. They are working out the details on their own and talking directly to the people they need to talk to.
Of course, all of this is getting ahead of itself. Before you’re project is ready to build, you need to figure out if it’s worth building at all. That’s why Rootstrap exists: to vet your idea and make sure it can find success in the marketplace. After that, you can building or team or better yet, use our world-class Los Angeles development shop.