Eating a Frog or How to Develop a Project the Right Way

October 4th, 2016

Mobile / Product Development // Natalie

How to Develop a Project the Right Way

I believe that every project is like a living organism with its own character traits, various interests, weaknesses, and strengths. While their lifecycle usually follows more or less standard paths and strategies, there are development lifehacks as well, which can bring benefit to the team that works on it and, ultimately, the client.

If we talk about mobile development, every app has its CORE feature, which is the center of its consumer’s needs. The rest of the features are usually built around this main feature, supporting it and depending on it, kind of like our solar system with the Sun in the center and the planets orbiting it. Technical specifications are mostly concentrated on it and every single detail of it should be discussed so that the client and everyone on the development team are on the same page.

Mark Twain said once: “Eat a live frog first thing in the morning and nothing worse will happen to you the rest of the day.” When my mobile development team and I begin working on the project, we prefer to “eat a frog” in the very onset. It’s not about the worst things in the development world, but rather about the hardest ones. In this case, “eating a frog” in a project is developing this CORE feature, the basis of the app, which is most often the hardest part of the project and possibly the most continuous.

What are the benefits of such strategy for the client and the team?

Time and Money

When the entire team is initiative, full of energy, and concentrated on one thing, it usually takes less time to develop the feature. In some cases, the solutions that come to mind are also non-standard and innovative, which is a value-added for many projects. Starting with the “frog” feature right away also gives the mobile team (or any team, actually) more time to concentrate on the app logic, algorithms, etc.

Visible Results

It helps both parties (client and the team) if the core feature is worked on at the very beginning because when the client can see the progress in the first 1-2 sprints and the core feature is drawn in, it helps the team’s reputation and the client can be satisfied.

Psychological Relief

When you have done the hardest part of the project, everything else seems easy and almost primitive to you. Another bonus of this is that often other logic and functionality are done faster than it was originally estimated (this doesn’t happen all the time, but it happens).

Freedom

When the mobile development team works on the main feature, they concentrate on it, moving the “weight center” of knowledge and skills to it. They feel free and without obstacles and resistance in its development because at the very beginning of the project, the team isn’t burdened yet with other functionality.

Such strategy can be described by the bike sports activity. Check out the video below.

Why does his strategy work?

  • Smooth road: i.e. start of the project, full trust credit, full of energy;

  • No obstacles: i.e. no functionality that demands more attention and time;

  • Minimum of resistance: i.e. no rush for deadlines;

  • Shifted center of mass: i.e. the entire team is concentrated on this core feature.

Try such strategy in your projects with our team!

Author: Natalie

Natalie is a Project Manager who is a great team leader for her mobile development team. She is an expert when it comes to iOS and Android development and to building apps that win markets.

Tags Native Management Cross-Platform

See all blog

x

Grossum Startup Guide:
Five Things to Consider Before Web & Mobile Development

Get the Guide