If you ask me what I have learned from all these years of working on experiments as a scientist and what are the takeaways? I will say for certain it's the way of thinking through a problem.
There is no predefined process to follow, at least not a fancy name for us to practice the way of thinking like waterfall or Agile. Some steps can be ignored in some problems but some will be added into the process in some other problems. In general, here are the five steps that are applicable in most of the cases: define the problem, generate a hypothesis, experiment and collect data, analyze the collected data, and make a conclusion.
A scientific project is a story full of quests on the way to the end. It is not enough just knowing the process to solve an issue, but you also need to break down a big issue into smaller ones and map out where they fit in the journey. So that you won't one day wake up and get lost in between the stacks of the experiment results and not sure where you came from or where you are heading to.
To summarize, the process of solving an issue, a tool to break down a big problem to smaller stacks, and a way to map out where the issues along your journey to the goal you set. These three are the takeaways from all these years in sciences and in labs, what I have started to realize in the last few years is that knowing these gives me a tremendous boost in the software industry.