Buyer's Guide Overview

---

Do you have a need for some expert Notes/Domino help, but are wondering how to go about getting the correct arrangement in place? We share a few thoughts with you as vendors, with the perspective of having seen multiple customers who have similar needs.

The Process:

• You communicate with Maarga on a requirement you have
• Maarga gets back with initial queries to understand both the context and the specific requirement. In quick iterations Maarga would seek to understand the scope of the work involved, the technology environment, the stakeholders and the nature of relationship sought.
• Maarga would present a proposal outlining a technical approach, a project management approach along with effort, schedule and cost estimates
• Maarga presents draft copies of the legal Master Professional Services Agreement and Statement of Work for review by customer
• Maarga would discuss the aspects of the proposal with you iteratively till all the aspects of proposal are in alignment with your requirements.
• Customer and Maarga would sign the Master Professional Services Agreement and the Statement of Work
• Maarga mobilizes delivery team and commences work

Best Practices:

Application Development/Maintenance:

• Establish the business case for your application and communicate it to the vendor. What specific benefits/business results do you visualize from the application? Can they be stated in quantitative terms? Do this right upfront, so the vendor can think along with you in visualizing the application.
• Give the vendor some leeway in terms of handling technology. Being specialists, we see a lot of situations in which Lotus Notes applications are developed and used, and we would definitely have some ideas that would be of help. Unless you feel strongly about your technology preferences, just communicate your situation and let your vendor suggest a technical approach.
• Choose the correct engagement model (fixed bid vs. time and material). If you have the application detailed out to the last detail by your internal business analysts, consider going in for Fixed Bid. If you are planning to iteratively develop the vision and features of the application, do not seek fixed bid - even if the vendor accepts it, such a situation will result in inflexibility in the process of application development and ultimately could lead to project failure.
• Crawl before you walk and walk before you run. Nothing new about this .. give time for your relationship with the vendor to stabilize. Do not get started with a super-high critical application to be turned around in a short time. Start with a low risk, well defined application, where you can communicate effectively and assess the vendor's performance clearly. Move the relationship gradually to closer engagement .. the operative word being "gradually"
• Resist the temptation to have all bells and whistles thrown in. Your application needs to do all it should to achieve the business objectives - ideally nothing more. Try to keep the application spartan and add embellishments later.
• Watch out with a hawk's eye for changes to requirements. Your vendor would naturally watch for this .. but uncontrolled change is among the biggest reasons for project failure.