Difference between revisions of "User:Shawndouglas/sandbox/sublevel4"

From LIMSWiki
Jump to navigationJump to search
Line 1: Line 1:
[[File:Project, program managers get lesson in risk communication (11437247733).jpg|right|300px]]A dedicated project manager (PM) is crucial to a successful implementation. The PM should be able to competently demonstrate critical aspects of project management, including paying attention to detail, managing multiple tasks simultaneously, and managing team members and their activities. By extension, this means the PM must take the time to become thoroughly familiar with your laboratory and its processes. They must also be experts on the LIMS itself in order to ensure your lab’s needs and the LIMS’ capabilities match.
Comprehensive and accurate requirements gathering is also critical to a successful implementation. This process ensures everyone understands what the lab’s actual needs are and how the proposed LIMS is able to assist with those needs. This responsibility rests on both the lab’s and vendor’s shoulders, not only in the development of requirements documentation but also in reviewing and refining the requirements. If this process isn’t given the attention required, significant time and money may be wasted.


In order to accomplish this, effective communication between the lab’s and vendor’s project team is vital, with the PMs for both teams needing to be great communicators. Real-time information flow and discussion means team members of both the lab and the vendor are working together optimally. Beyond effective requirements gathering and scope definition, this is probably the single most important factor that determines successful implementation. The project managers from both teams should agree upon appropriate communication methods (e.g., online or onsite meetings, phone calls, emails, project management application documentation, etc.) and frequencies that will best facilitate effective communication.
The vendor should be able to demonstrate industry knowledge throughout this process. A vendor who is not well acquainted with the workflows, regulations and standards affecting a particular industry will lead to problems in communication and understanding. Similarly, the vendor who is not well-acquainted with how their own solution meets the requirements of an industry results in poor or even inaccurate implementations. The inexperienced vendor may cause delays in implementation times or, even worse, attempt to gloss over the details, leaving the lab to deal with the fallout later on. The experienced vendor will be attentive to your lab’s requirements and may be able to offer solutions to problems you didn’t know you had.

Revision as of 21:22, 9 March 2022

Comprehensive and accurate requirements gathering is also critical to a successful implementation. This process ensures everyone understands what the lab’s actual needs are and how the proposed LIMS is able to assist with those needs. This responsibility rests on both the lab’s and vendor’s shoulders, not only in the development of requirements documentation but also in reviewing and refining the requirements. If this process isn’t given the attention required, significant time and money may be wasted.

The vendor should be able to demonstrate industry knowledge throughout this process. A vendor who is not well acquainted with the workflows, regulations and standards affecting a particular industry will lead to problems in communication and understanding. Similarly, the vendor who is not well-acquainted with how their own solution meets the requirements of an industry results in poor or even inaccurate implementations. The inexperienced vendor may cause delays in implementation times or, even worse, attempt to gloss over the details, leaving the lab to deal with the fallout later on. The experienced vendor will be attentive to your lab’s requirements and may be able to offer solutions to problems you didn’t know you had.

Retrieved from "https://www.limswiki.org/index.php?title=User:Shawndouglas/sandbox/sublevel4&oldid=46950"