To gain a better understanding of how we collaborate with our clients on a typical development project, please examine the process overview flow chart presented below. To find out more detail, hold the mouse pointer over specific sections of the diagram. We are flexible in our approach; we often tailor our standard procedures and practices to fit the way things are done in our client's business. On top of that, we always fine tune the process to align it with the client's software product as well as their project implementation strategy. Last but not least, we can get involved or withdraw on your request at any stage of the process, be it the initial scoping, technical specification preparation, GUI design or application development. And do not forget that - as a nearshore service provider - we can visit you regularly to deliver services on-site or collaborate with your people at our premises. It works!
determine the business context of the software system to be developed, i.e. the business model and strategy of the venture to be supported by the platform and/or the business process to be served by the software tool
identify business needs to be satisfied and business objectives to be achieved
establish the Initial Scope of the project
develop a Guesstimate, i.e. a rough estimation of workload, expected cost and timeframe necessary to implement the project
sign a Non-Disclosure Agreement
clarify the terms of collaboration, including approach & methodology, process, team architecture - roles & responsibilities involved, business and technical environment, acceptance criteria, project change, charges & payment terms, intellectual propoerty rights and the like
clarify / adopt a Project Implementation Strategy, i.e. guidelines which help to resolve the inevitable trade-offs between Functionality/Performance, Budget, Schedule, and Support & Maintenance Costs
develop the Preliminary Project Plan; in particular, divide the Initial Scope into Milestones and agree on a milestone implementation sequence taking into account both market and technological constraints involved
the milestone technical specification is provided by the client or developed jointly with the client
it contains at least: (1) a set of unambiguous user story titles - grouped into functional modules and (2) a complete set of wireframes / mock-ups
on small and well defined projects, tech specs can be developed for more than one milestone
based on the technical specification, agree on the cost and verify the deadlines for milestone implementation
in principle, specific work orders, deliverables and their costs as well as implementation schedules are agreed upon a periodic basis for each successive project milestone
a milestone is structured so that it may be implemented in no more than one month
when the project has been completed, we can maintain the application as well as provide technical support for it, i.e. remove defects and correct deficiencies
if needed, sign a contract for providing services to develop the technical specification,including user stories, wireframes/mock-ups, navigation maps and the like
sign a contract for system implementation
specific work orders, deliverables and their costs as well as implementation schedules for successive milestones are listed in Appendices attached to the contract
sign an SLA, which specifies the terms and conditions for managing the application after the project has been completed
the SLA specifies (1) the scope of service (e.g. server administration, data back-ups, etc) and (2) when and how fast we have to respond to issues as they arise