dots

Starting a software development project might raise many questions. No matter if it’s a web development or mobile development, you have to know what to expect. Here’s a short summary of steps needed to kick off a project at Sunscrapers.

The process will differ in some aspects, from case to case. That’s because we approach every project individually. Over the years, we’ve learnt that software development is far too complex to tar everyone with the same brush. What’s most important is the execution and decision making in a given business context. Market landscape, leadership, resources – all those factors  have an impact on the ultimate success of an application. We know that this context is inevitably different for everyone. That’s why we must approach those individual circumstances in – you guessed it – the individual way.

How do we start then?

1. An introductory call

We set up a 15-30min Skype (or Hangouts) video call to get to know each other. This is the moment to talk about your vision, goals, requirements, resources and constraints. We will also tell you more about Sunscrapers and our software development services.

The goal of the call is to give us enough input to determine:

We care about your time and needs, that’s why we won’t discuss functional aspects of the application during this call. Without determining the fit first it will probably a little bit too early to do that.

2. Project proposal

Based on your individual circumstances as well as your progress up to date we’ll propose the best way to tackle the software development project. Essentially there are three entry points for collaboration:

  1. Product discovery workshop – aimed for those who just have an initial idea of what should be accomplished, don’t know much else and need our help in clarifying the business concept, it’s assumptions and feasibility. 
  2. Scoping session – most of projects will start with this step. It’s goal is to take all your input (brief, list of functionalities / requirements, mockups – everything or anything you have), analyse it, follow up with Q&A sessions (that’s where we discuss functional requirements in details) and then start our own internal process aimed at putting together a solid strategy for product development in a formal project proposal document. 
  3. Code audit – if we’re taking the project over from a different team, we will want to start with reviewing the existing codebase to get an opinion about it’s current state. Then, if the project backlog is well defined we may jump straight to development, or otherwise revert to the scoping session. 

3. Agreement

Once we’re mutually happy with the project proposal, we will move on to sort out the formalities needed to kick off the project.

4. Onboarding

Alright, all set! Our project manager will now take you through our client onboarding so that you understand how our collaboration will look like in detail. We’ll tell you about the tools, working process, roles and responsibilities to make sure we all make the most of our time together.

The whole process is designed to bring as much value to our prospects as possible. Our existing clients happily admit they’ve learnt a lot during our initial conversations! Even if we’ll not be able to help, we’ll always look for genuine ways to help, guide or recommend other solutions/providers. That’s simply the way we are.

If you’d like to see the process in practise and learn something on the way – do get in touch to check if we’ll be able to help you with your project.