Managing the Upgrading of Lims Software - Example

MANAGING THE UPGRADING OF LIMS SOFTWARE. DOCUMENT 1: USER REQUIREMENTS {1 PAGE} Type of project Laboratory Information Management System (LIMS) for a hospital Trust and its surrounding primary care practices. Summary of what is needed Install an upgraded/replacement LIMS to be used for the information system management of pathology tests. The system will need to merge its functionalities across a range of different environments, including the laboratory, the hospital, the wards, the clinics, and the GP surgeries and practices. The project is expected to:- Deliver a great user experience—user acceptance is the measure of success Function without interfering with LIMS systems Provide a central repository of consistent data Answer complex queries quickly Provide a variety of powerful analytical tools, such as LIMS and data mining The system will serve the following users of this Hospital Trust’s Clinical Laboratory for their pathology services. 15 wards 20 departments 30 GP practices The modules are required to handle tests in the following areas: Biochemistry Haematology Immunology Blood Transfusion Microbiology Cellular Pathology Statistics and reporting Billing Customer This refers to the person or group that is the direct beneficiary of a project or service is the client / customer. These are the people for whom the project is being undertaken (indirect beneficiaries are stakeholders). The customer for this project is a hospital trust’s clinical laboratory including its surrounding primary care practices. The care practices include: 15 wards, 20 departments, 30 GP practices. Rough Cost Traditional license delivery model cost of LIMS. Small Scale - £65,000 – Large Scale - £500,000 (1) Annual Maintenance cost - £15,000 (2) Given that our customer has a fairly large network of wards, clinics and general practitioners, we can assume the cost will scale higher than the small scale minimum, but would not be applicable for a large scale distributed enterprise client. Therefore I would suggest a rough cost of around £250,000 (+ £15,000 PA). Approximate duration 6 months Obvious risks Immediate installation not possible, infrastructure rework required. System requirements scope necessitates revisions during development. (4) Installation of LIMS may interfere with the high priority deployment of the OCS Future maintenance of LIMS (minimum 10 years) may necessitate new or reworked interfaces which may require possible hardware/network upgrades after the project has been completed. DOCUMENT 2 - BREAKDOWN STRUCTURE {1 PAGE} Work breakdown structure The work breakdown structure (WBS) is a list of major deliverables that the project team will complete during the project. The WBS is organized in a hierarchy and is typically decomposed into several sub-levels. Work Breakown Structure (WBS) is used for breaking down a project into easily manageable components, or bites. Here we'll break down the process for you, making it easy to use these structures in your project planning. Work breakdown approach The WBS is designed to help break down a project into manageable chunks that can be effectively estimated and supervised. Some widely used reasons for creating a WBS include: Assists with accurate project organization Helps with assigning responsibilities Shows the control points and project milestones Allows for more accurate estimation of cost, risk and time Helps explain the project scope to stakeholders Major activities covered in the proposed project WBS has major activities which include :- DOCUMENT 3: ESTIMAION SUMMERY {1 PAGE} Estimation methods Estimation methods used is Bottom-up estimation This method is usable when the architecture of the system is known and components identified. This can be an accurate method if the system has been designed in detail. Assumptions Made It may underestimate the costs of system level activities such as integration and documentation References to sources that helped make estimations is also sited Algorithmic cost modeling Cost is estimated as a mathematical function of product, project and process attributes whose values are estimated by project managers The function is derived from a study of historical costing data Most commonly used product attribute for cost estimation is LOC (code size) Most models are basically similar but with different attribute values DOCUMENT 4 THE NETWORK DIAGRAM {1 PAGE} Network Diagram Developed in the 1950’s A graphical representation of the tasks necessary to complete a project Visualizes the flow of tasks & relationships How the processes identified in document 2 relate to one another and that provides an estimate of the total time needed to complete the project (the project’s duration). DOCUMENT 5: TIMELINE OR RESOURCE PROFILE {1 PAGE} Required resources Gantt chart Gantt chart is used for tracking the progression of the tasks derived by WBS. A Gantt chart is a bar chart that depicts activities as blocks over time. The beginning and end of the block correspond to the beginning and end-date of the activity. Key milestones in the project A milestone is a scheduling event that signifies the completion of a major deliverable or a set of related deliverables. Given that the hospital network/admin infrastructure is already set in place, installing a LIMS with a focused team will take around 4-6 months, with the inclusion of installing any required hardware and server distributions necessary for running and maintaining the system in the future. Calculating start and finish dates. DOCUMENT 6: CHARGE-OUT COST {1 PAGE} Internal table of charge-out costs Identifies at least four different categories of staff that you will need on the project Making clear: (i) which activities or products they will be working on (from document 1); and (ii) (ii) the rates at which they would be charged to the project . With a justification of why these rates were chosen (referencing any sources that helped you decide the rates). The table of charge-out costs should account for overheads as well as the salaries of the staff. From here on, it should be relatively straightforward to make the main costing, pricing and duration calculations. Demonstrate a familiarity with relevant theory, including that related to estimation, resourcing, risk, and pricing methods, and to be able to assemble a credible bid from an outline specification DOCUMENT 7: MAIN RISK AND MITIGATION Risk There may be potential internal or external events that will have a negative impact on the project if they occur. Risk refers to the combination of the probability the event will occur and the impact on the project if the event occurs. Risks and their associated mitigation strategies have been identified and addressed; references sources used to quantify risks are also provided. The risks presented are realistic and relevant to the project. Each risk quantifies the impact it will have on the bid price. DOCUMENT 8: BID SUMMERY This presents the final price offer; it includes the cost and duration of the project, the terms of the maintenance contract. Cost also address contingency and profit. Duration Labor cost Non-labour costs Contingency Warranty and maintenance Profit Final cost Other terms and conditions References Adams, John R. "Principles of Project Management". (c)1997 by the Project Management Institute. Crawford, J Kent; Pennypacker, James S. "Put an End to Project Management". Optimize. Oct. 2002. Pages 73-78. DefiningSystemRequriements.pdf [Internet]. [cited 2015 Oct 11]. Available from: http://www.atlab.com/docs/DefiningSystemRequriements.pdf Friedlein, Ashley. "Web Project Management". (c)2001 by the Presentation Company Limited. Morgan Kaufmann Publishers. Hartman, Francis; Ashrafi, Rafi A. "Project Management in the Information Systems and Information Technologies Industries." Project Management Journal. Sep 2002. Vol. 33. Issue 3. Pages 5-15. Hoffer, Jeffrey A; George, Joey F; Valacich, Joseph S. "Modern Systems Analysis & Design". (c)2002 by Pearson Education, Inc. Prentice Hall. Kim Shah. Making LIMS affordable [Internet]. Laboratory News. [cited 2015 Oct 11]. Available from: http://www.labnews.co.uk/features/making-lims-affordable-20-05-2010/ Kioppenborg, Timothy J; Opfer, Warren A. "The Current State of Project Management Research: Trends, Interpretations, and Predictions." Project Management Journal. June 2002. Vol. 33. Issue 2. Pages 5-18. Mountain States Consulting, LLC. MSC-LIMS Laboratory Information Management System [Internet]. 2014 [cited 2015 Oct 11]. Available from: http://www.msc-lims.com/lims/prices.html Payne, John & Shirley. "Management Basics". (c)1998 by the Adams Media Corporation. Quick, James Aaron; New, Cheryl Carter. "Grant Winner's Toolkit: Project Management and Evaluation". (c)2000 by Cheryl Carter New and James Aaron Quick. Published by John Wiley & Sons, Inc. Rasmussen L, Maddox CB, Harten B, White EL. A Successful LIMS Implementation: Case Study at Southern Research Institute. J Assoc Lab Autom. 2007 Dec 1;12(6):384–90. Schimmoller, Brian K. "The Changing Face of Project Management." Power Engineering. May 2001. Vol. 105. Issue 5. Pages 28-30. Read More