Development

Nurturing good working relationships into mature partnerships is key to building good software applications, where both parties understand their roles and responsibilities and deliver on their obligations.
Today’s requirements for rapid response and pro-active exploratory development demand new working practices. When a customer requests a change, a choice or trade-off must be made; How this process is handled tests the effectiveness of the relationship and may alter the outcome of the project for better or for worse.
The traditional way of dealing with change management within formal contracts can slow projects to a crawl. We adopt working practices to enable customers/users to cut the chains of bondage of traditional development methodologies, enable technical teams to give their best, give the contractual processes the mechanisms to adjust with change and maintain momentum and fairness. We welcome changing requirements to enhance the customer’s competitive advantage, even late in development.

Time for Agile Engineering

Fortunately new methodologies and tools have sprung up to improve the development process and the way that technical teams can communicate with their target audience. We believe in individuals and interactions over tools and processes, working software over comprehensive documentation, customer collaboration over contract negotiation and responding to challenge over following a plan. We consider tools and processes, comprehensive documentation, contract negotiation and following a plan important too, just not as important as delivering reliable software with adequate documentation on time. Reading the principles behind Agile Engineering it’s not difficult to empathise.

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software