How we work with you?
Everything we do is based on gaining your trust. How do we do that? By being open and realistic about technologies, scope, risks and budgets right from the start.
Our experience shows that the most successful projects are defined by
- close cooperation between our experts and customer stakeholders
- highly focused resources, and
- the ability to accommodate change.
Whether you’re a creative genius, a technical guru or a business leader, we speak your language. We can turn your idea into reality, or simply implement your technical instructions to the letter. And we’ll communicate your way, whether you prefer e-mail, telephone, Skype or face-to-face meetings
Not only that, all your conversations with us, from pre-sales through execution to completion and ongoing support, will be with people who know, understand and work on your project.
It has been proven time and again that a talented team lead working with two super-efficient and experienced programmers can do the work of a team of 10, 20 or even 30 people in a traditional ‘big name’ software development house.
In fact, those big software houses frequently rely on a couple of our top coders to rescue projects that go wrong. Our recommendation? Start your software development project with our top coders in the first place.
Our team leaders are not only experienced software developers and business analysts, but they are also excellent communicators. Our programmers contribute by actively seeking technical solutions to client problems rather just by writing code, as they are all proficient system architects. That enables our small teams to achieve unrivalled levels of productivity.
If you prefer to define your project with tight specifications, establish strict change management procedures and scope control, we are more than ready to work within such a framework.
However, many organisations realise that building bespoke software for their business is a learning process. New requirements often emerge during the project as a result of changing market conditions, or user feedback. Agile Development Practices help accommodate these kind of unexpected changes. And we know how to use them to your advantage.
Working on your project – some practicalities
As we’ve mentioned, we follow agile development principles that are outlined in the Agile Manifesto. There are many methodologies that prescribe in detail how those projects are run. Maybe you have already adopted one, such as the popular Scrum? Whether you have or not, it’s important to understand that agile development principles inform our entire approach to developing your software. That approach is focused on two objectives:
- release the first functional and usable version of a software as soon as possible.
- hit your deadline and budget targets.
These objectives are met by effectively executing several key aspects of the development project.
A project starts with a discovery phase, although aspects of discovery are likely to recur until completion and beyond. During this stage we will have a look at the plans you’ve got and enhance them to make the path ahead clear enough to start coding. Discovery outputs could include:
- data model
- user stories
- iteration/release plan
- draft visuals
Once we have aligned our ideas about what’s ahead, we will move forward in short iterations, lasting 2-6 weeks each (depending on the project type and your preferences).
At the end of each iteration there will be some tangible deliverables for you to review and provide your feedback on. The project plan and the way we work can be adjusted after each iteration based on lessons learned.
A release is something more substantial, where a project is finalised and loose ends are tied up. The software release stage results in a commercially viable product. This product may not be in what will ultimately be its final form, but it will be fully functional and working.
The time it takes to get to the first release will vary depending on a whole range of project-specific factors. But if significant progress is not made within three months, then we won’t consider it a successful project. We prefer to deliver results sooner than later, shifting less important functionalities into subsequent releases. Software only works when you use it and benefit from it, not when it simply complies with specification and test parameters…
Keeping your options open
We want to keep your options open all the time. After each release or even iteration you will get something useful you can build upon. If it is viable at some stage to switch in-house resources utilizinge a more specialised development team or even stop the project, we will support you in your decision. There is no long-term commitment from your side.
Next to “How to get started“