The Rezare Systems team bring a variety of skills to assist with your agricultural software and IT system project. These include business requirements analysis and farm systems analysis, software architectural design and usability patterns in agriculture, software development, testing and support.
Our IT skills are underpinned by a substantial understanding of agricultural systems and supply chains, and our network of contacts and collaborators in New Zealand and internationally.
We categorise our expertise into three broad areas:
Doing Business with Rezare Systems
The Rezare Systems team are focused on delivering quality software that solves real problems for our customers. We value a long-term, synergistic relationship, and we believe that if our customers are successful, then we will be too.
To build these successful relationships we:
Listen to our customers – our first meetings while we flesh out your project are free of charge (apart from travel expenses if we come to you). This is because we want to take time to understand your business and be sure that we are the best fit for your needs.
Make sure we are clear about requirements – specifically we need to know what you need to achieve to be successful. Our experience is that the detailed requirements for software products changes as you understand more of what you are building – and changes again when real people start using the software! While understanding detail is useful, the big picture is more important, and helps us suggest other options to create a win.
Put in place a structured plan for delivery – a project without a schedule and milestones is really just a good intention. While we allow for (and expect) change, we need to understand exactly what each party is responsible for – and when.
Use modern software tools and techniques – for most projects we use Microsoft Visual Studio as the development environment, and we embrace frameworks such as MVC that keep our code clean and make our developers effective. We are strong proponents of incorporating testing early in the process – at the developer level with unit tests, and also with testers and test plans.
- Seek your ongoing engagement – software products don’t just appear a certain number of weeks after you slip the specifications (and pizza) under a developer’s door. Our developers and analysts will need regular engagement with you to clarify details, answer questions, and review our developing product. This is what makes our development lifecycle “agile” and we use regular, short sprints to enforce this close engagement.
If you would like to know more, please contact us.