Line-of-Business Applications - developed for that special process

Aurelian Group offers Architecture, Design, and Development services for custom Line-of-Business applications - niche applications that are so specific to a specific need, that there is no alternative on the market - or at least, not one with a realistic budget in relation to the scope of use. 

We help you with ideation and brainstorming, if required. Our Architects have decades of experience in a wide range of industries. As such we are able to provide you with practical advice, implementable solutions, and actionable direction. 

If you already have the idea, you know what gaps the application needs to bridge, Aurelian Group can step in formalise a backlog of features for your application. 

The backlog of features is prioritised and added to development sprints. For prioritisation, we apply the MoSCoW (Must have, Should have, Could have, Won't have yet)classification - and you are in the driver's seat.

As a rule of thumb: 20% of the features drive 80% of the value.

What about the budget? In many occasions, the traditional models of app development have resulted in either significant budget-overrun, massive disappointment in delivery, or both. Whether you contract with your vendor on Fixed Fee model, or Time and Material, ultimately it is YOU, the customer, that draws the shortest straw. And why would you believe Aurelian Group to be any different?

You shouldn't - that is why we fix the iterations, and load them with a risk profile to what you, the customer, find acceptable. How does that work?

Must have requirements in each iteration determine if you have a usable application. Your acceptable risk profile will determine how much of the budget in the iteration is associated with these requirements. For example, 60% budget allocated to must have requirements means there is 40% budget slack for a workable solution. If you then allocate 30% to the Should have requirements - the things that make the application render a higher return on investment - then there is an additional 10% left for the Could have features (they may not have immediate benefit, but helps with additional user satisfaction). To help with risk classification, we offer three models to choose from: M60 (lowest risk), M70 (medium risk), and M80 (upper band of acceptable risk). 

The second variable in the budget is the duration and loading of each sprint (a sprint is a delivery component with a usable delivery at the end). Sprints vary from two to six weeks. The shorter the sprint, the lower the committed budget. Sprint loading means the number of people allocated to the sprint - we will work with you on the optimal loading of a sprint - so that resources are utilised to their capacity during the spring, minimising idle time while waiting for others to complete dependency work. 

Does your organisation have a requirement for an application that solves a business problem, but nothing on the market is available within the budget constraints? Click the button below to contact us, and share the high level requirements - we will be more than happy to discuss and see how we can best serve your needs.