This morning's chats have got me thinking about an initiative at the Developer Success Lab we've been talking about we're calling Be Your Own Scientist -- publishing guidance and teaching all about helping YOU bring the power of science to answer questions about software teams (and perhaps using it to protect the good stuff you already know you're doing!) 😎
What kinds of topics would you want our team of social scientists to tackle??
Follow
@grimalkina Among other things, Agile tries to find insights about how software teams work.
It's mostly not very scientific (or successful). Are there ways to approach iterative (team-wide) improvement in a scientific way?
It could be the kinds of questions we ask, or how we evaluate outcomes.
