Member-only story
How to Approach Feature Development and Problem-solving
5 steps to develop any feature
There are many ways to develop a new feature. The process starts with a product owner coming to the dev team with an idea. They usually have some user research and some data to sustain the idea, and after a brief discussion, everyone agrees on building the feature.
Then, the product manager asks for estimates on the time required to develop the new feature. The staff/lead/principal engineer provides those estimates and the project starts: it is split into smaller tasks and the individual contributor starts with the implementation.
Designs are made, code is written and, sometimes, it is thrown away. And, on many occasions, we need to write it again. This is one of the worst ways to approach a project: an head-down approach from the idea to the estimates, to the implementation.
A better approach involves properly gathering the requirements and making sure that everyone is on-board. Today, we want to illustrate a 5-step process to develop any feature with the goal of maximizing the probability of being successful, from the perspective of a mobile engineer.
