/
Insight
Logo
Insight

Transparency in software development

In this first blog post, I would like to go into why we built Insight and why we think it will change the field of software development.

The problem

To better explain the problem, I like to use the car analogy.

Imagine yourself driving with no dashboard, you would have no idea of how fast you are going, how much fuel you have left or if your engine is in any troubles. You could only guess if you'll reach your destination safely, on time and without a ticket.
car dashboard image

I wouldn't feel very safe as a passenger and pretty stressed out as a driver.

Well, that's exactly how most software development teams are run today. In those conditions, it's not really surprising that most development teams have trouble delivering software on time...

If you have ever dealt with a development team, you know how hard it is to have some indicators of how the team is progressing towards specific goals without disturbing them.

Agile helps

Agile helps teams with a bit of structure and partialy solves this by making the team collaborate and discuss progress and roadblocks. It also helps discuss what goes well and what could be improved.

Agile also introduces some sort of empowerment of the whole team. The bottom-up approach is really great to solve issues before they become too expensive.

All this is wonderful, but we are still driving without a dashboard. We need to know those things at a glance without having to bother anyone or building an excel report.

Idealy we would have a simple way of sharing relevant information with the whole team, management and our end-users.

The dashboard

So the dashboard was created to solve the unpredictability and answer very common questions:

  • Where are we now?
  • Where are we going?
  • Are we improving?
  • What can we do better?

The dashboard

Flexibility

Every team has it's own specific needs, so the dashboard needs to reflect that reality.

You can filter by people, by labels, report on multiple projects at the same time and you can distribute all this information on one or multiple boards.

The widgets are also customizable in size and colors.

Integrations

We chose to integrate with Pivotal Tracker first because it's a mainstream Scrum platform. However, we plan on integrating with many more project management tools in the coming months.

In the mean time we are still making widgets for your favorite tools such as Github, Jenkins, Teamcity, Code Climate and many more...

The future

We will go deeper into this in a coming post, but we plan on enabling development teams with the equivalent of what is comonly known in baseball as Sabermetrics.

moneyball

So we want to enable development teams with the ability to search for objective knowledge about sofware development.

Insight should be a team's best friend to find and solve bottlenecks and to experiment with their development process.