This week, we’ll continue with development principles for Biotech Data Teams related to collaboration, with a principle that may seem obvious, but is hard to get right in practice: Development timelines should be deliberately coordinated with experiments to maximize opportunities for feedback.
Speaking of Coding and Data not wanting to "miss the bus", the Wet Lab cannot afford to "Miss the Truck". In the manufacturing world, missing a shipping deadline can bankrupt a firm.
For the Wet Lab, patents, licensing, funding, go-to-market, quarterly earnings, hand-off to engineering, trade shows, are just a few concerns. Many of us have been burned by "New and Improved", so even with "Coordinate Rollouts" there will be a temptation to go instead go with "Tried and True" A double of "Deliberate Empathy" might be in order.
In principle this is a great idea. A could be a bit tricky, tho. Getting the budget is a 'small' issue, since the code shouldn't delay the wet lab.
The easiest rollout would be a strictly performance release, e.g. speed or storage. The most challenging would be one where features which the wet lab have gotten accustomed to, get removed. New features, especially those requested by the wet lab, like any x.x.0 release, might be a bit buggy, so testing and repair time needed.
Getting the lab liaisons involved in testing before full deployment seems prudent.
Speaking of Coding and Data not wanting to "miss the bus", the Wet Lab cannot afford to "Miss the Truck". In the manufacturing world, missing a shipping deadline can bankrupt a firm.
For the Wet Lab, patents, licensing, funding, go-to-market, quarterly earnings, hand-off to engineering, trade shows, are just a few concerns. Many of us have been burned by "New and Improved", so even with "Coordinate Rollouts" there will be a temptation to go instead go with "Tried and True" A double of "Deliberate Empathy" might be in order.
In principle this is a great idea. A could be a bit tricky, tho. Getting the budget is a 'small' issue, since the code shouldn't delay the wet lab.
The easiest rollout would be a strictly performance release, e.g. speed or storage. The most challenging would be one where features which the wet lab have gotten accustomed to, get removed. New features, especially those requested by the wet lab, like any x.x.0 release, might be a bit buggy, so testing and repair time needed.
Getting the lab liaisons involved in testing before full deployment seems prudent.