It’s rare that we speak about getting the right resources for a project. Even more seldom is that we discuss how LIMS project behavior affects projects. Even beyond that, both personal and organizational behavior affect our LIMS projects.
Whenever someone talks about building a custom LIMS, I insist they not take that route. However, there might be situations where that’s feasible. In any case, there are a number of issues to consider.
LIMS communications go on, every day. Sales people, business analysts and system administrators all make presentations, and team members are sharing ideas.
No, it’s not the end of Agile for LIMS but the reasons why aren’t necessarily positive ones.
With Autumn so close at hand and people returning from vacation, many projects are already planning their ramp-up. If you’re planning to have your LIMS, ELN or LES work done, remotely, you need to consider the tools that will help you with this and how best to use them. This post is focused on LIMS remote work tool tips.
Maximizing a LIMS typically involves creating a LIMS interface with other systems. SAP is a common interface but there are many others, as well.
Lately, the topic of which projects are using remote LIMS resources and which aren’t seems to be the big topic of discussion. Actually, it’s not just with regard to LIMS, ELN and LES, but all aspects of the IT community projects. Whether that’s because we’re coming so close to the beginning of Autumnal work or other factors isn’t clear. Regardless, today’s post gives five of the tips I’ve been handing out, lately.
Crafters seem to have “stashes” – a pile of material collected that they intend to use “some day” but that continues to grow to the point where they have too much money and space invested in materials that they haven’t used. Occasionally, crafters come up with “stashbusting” projects that “bust” the “stash.” If you think of your project that way, where you have too many things on the list of tasks (i.e., where you’ve run into “critical path” issues and/or resource blockages), it’s a little bit like that – it’s a pile of something that needs to be conquered.
In my last post, I talked about how companies sometimes keep non-performing people on their projects. They also keep non-performing vendors and under-performing vendors.
When I first started my business, I knew there were quite a number of projects that had resources who couldn’t finish their work. I don’t mean that they couldn’t finish in a reasonable time, but that they literally couldn’t finish anything, at all. I knew this partly from working with these projects but also from running into customers who told me about their projects at user group meetings or on the phone. I thought this was the best source of revenue I could find. I was wrong on that account.