Software Development

Our approach to software development projects is based on a flexible working relationship basis where trust and a partnership understanding are critical. Essentially we have three key ways of working, which we use in different circumstances to meet our customer requirements.

Estimate based working
Daily rate contract basis
Fixed price contract basis

During a software project our Project Manager always stays in close contact with our customer, usually face to face on a regular basis. When we are working on an estimate or daily rate basis we never exceed budgets or estimates without permission.
Where InfoSys is taking responsibility for the development, whatever, the commercials basis, we work to the development methodology shown below:

Software Development Methodology (Lotus Notes Projects)

[1] Sales produce either an internal or a customer specification together with an agreed set of information (a pro-forma checklist?) about the project, such as:

[2] Sales provide the customer with a written quote. PM may have input. The Quote will include:

[3] Once order received, PM contacts the customer to:

[4] Following discussions with the customer, if the scope of the project has changed or the complexity of the project has increased PM will provides Sales with a revised cost estimate. Sales may or may not then decide to contact the Customer, discuss the cost implications of the additional work, agree on a new price and a revised number of development days.

[5] Once the development cost, scope of the project and the requirements have been signed off by the customer PM agrees: The actual timescales for the project (based on current team availability)

[6] PM allocates Developers to the project, books the project into InfoDiary and advises the customer of ‘key’ project dates by providing the customer with a basic project plan.

[7] PM briefs the allocated project Developer(s) on:

[8] Developer(s) begin development.

[9] PM meets with the Development Team on at least a weekly basis to:

[10] Software will be released to the customer only after someone other than the Developer has tested it.

[11] Software will only be released to the customer once the agreed test plan has been satisfactorily executed.

[12] During the development process, the Developer will advise the PM in a timely fashion of any deviations from the agreed project scope and requirements that may require the PM to raise a change control for the customer.