About Petri Kainulainen

Petri is passionate about software development and continuous improvement. He is specialized in software development with the Spring Framework and is the author of Spring Data book.

How to Start a Software Project as Fast as Possible

We started a new project last week, and I started to wonder what are the most important things to do if we want to get a project started as fast as possible (without messing it up).

I figured out three things which have helped me to concentrate on the right things during the early phases of a software project.

These things are:
 
 
 
 

1. Don’t Aim for Perfection

When a software project is started, the first thing that we have to do is to agree on the practices used in the project.

I have noticed that the most efficient way of doing this is to follow these steps:

  1. Create a To-Do list which contains the things which must be taken into account. Typically this list contains things like version control system, project model, technologies, documentation, and so on.
  2. Invite the project team to a meeting and go through your to-do list one by one. Try to decide as many things as you can on this meeting.
  3. If you cannot decide something or a decision creates a need to do something, create a task, assign it to a team member (shared responsibility is nobody’s responsibility), and set a deadline.
  4. Don’t forget to follow up!

The idea is to get everything done as fast as possible, and use retrospective meetings to drive continuous improvement.

2. Use a Project Template

Most projects which use the same technology stack have a common foundation. This foundation includes the build process, dependencies, configuration, and some common functions (registration, login, and so on).

Creating this foundation from scratch every time when it is required makes no sense. It is a waste of time and money.

We can solve this problem by creating a project template or using an existing one. A good project template has one goal:

It ensures that we don’t have to spend any time for doing boring grunt work!

This means that we can concentrate doing work that matters.

You can find many project templates from the internet. If you are working with Spring web applications, you might want to take a look at the following projects:

  • JHipster is a Yeoman generator which is used to create Maven + Spring + AngularJS projects.
  • SpringFuse is an online service which generates code for data-oriented Java applications.

3. Don’t Worry About Features (Yet)

When we start a new project, we should not care about features of the application. We should care only about these two goals:

  1. Decide the common practices used in the project.
  2. Create a solid foundation which is easy to extend.

If we worry about the features of the application when we are starting a project, we spend a lot of energy on worrying about things which aren’t essential right now. This will decrease our chances to meet our goals.

Don’t get me wrong. Solving the right problem is crucial to our success but right now the most important thing that we have to worry about is to get our project started.

There Is a Time and Place for Everything

I think that the easiest (and often the best) way to increase our efficiency is to concentrate on the right thing at the right time. This seems obvious but the next question is a lot harder to answer:

What is the right thing?

I provided one answer to that question. Is my answer the right one?

I have no idea. Ask me again after a few years and I will let you know.

P.S. If you think that I am wrong or I missed something, share your opinion on the comment section.
 

Reference: How to Start a Software Project as Fast as Possible from our JCG partner Petri Kainulainen at the Petri Kainulainen blog.
Related Whitepaper:

Software Architecture

This guide will introduce you to the world of Software Architecture!

This 162 page guide will cover topics within the field of software architecture including: software architecture as a solution balancing the concerns of different stakeholders, quality assurance, methods to describe and evaluate architectures, the influence of architecture on reuse, and the life cycle of a system and its architecture. This guide concludes with a comparison between the professions of software architect and software engineer.

Get it Now!  

Leave a Reply


+ eight = 13



Java Code Geeks and all content copyright © 2010-2014, Exelixis Media Ltd | Terms of Use
All trademarks and registered trademarks appearing on Java Code Geeks are the property of their respective owners.
Java is a trademark or registered trademark of Oracle Corporation in the United States and other countries.
Java Code Geeks is not connected to Oracle Corporation and is not sponsored by Oracle Corporation.

Sign up for our Newsletter

15,153 insiders are already enjoying weekly updates and complimentary whitepapers! Join them now to gain exclusive access to the latest news in the Java world, as well as insights about Android, Scala, Groovy and other related technologies.

As an extra bonus, by joining you will get our brand new e-books, published by Java Code Geeks and their JCG partners for your reading pleasure! Enter your info and stay on top of things,

  • Fresh trends
  • Cases and examples
  • Research and insights
  • Two complimentary e-books
Get tutored by the Geeks! JCG Academy is a fact... Join Now
Hello. Add your message here.