3 ms·
I think the biggest challenge to your statement is "listen to what they want." Much of our modern psychology suggests people don't always know what they want, o
by secstate 10y ago
I think the biggest challenge to your statement is "listen to what they want." Much of our modern psychology suggests people don't always know what they want, or don't want what they think they want. This is not meant as an insult, as it applies to all humans, whether they're a developer or not.
That means that listening is a huge part, but it's not enough to simply implement exactly what you hear they want.
All that said, I still totally agree with your examples.
- SatvikBeri 10y agoYeah, you're totally right. Just literally listening is not enough–you have to ask questions, trace symptoms down to a root cause, and then come up with a good solution for that problem. For example, one person requested that we make standups earlier, because they wanted to get them out of the way before getting into the zone. Another suggested making standups later, because they preferred to start work later in the day. Obviously these solutions as suggested were incompatible. So I tried to figure out what value we were getting from standups, and figured that it was worth experimenting with making them asynchronous using Slack. That worked really well, and is what we do now most of the time. (Occasionally, the team likes having in-person standups when in the middle of a tough series of bugfixes.)
- secstate 10y agoExactly! And kudos on figuring out a system that accomplishes the goal (what's everyone up to), but works well for the most people.
- Drdrdrq 10y ago> So I tried to figure out what value we were getting from standups, and figured that it was worth experimenting with making them asynchronous using Slack. Could you please elaborate on what you are doing? We are facing similar problems so I would love to know more...
- SatvikBeri 10y agoI found that I was getting two things from standups: knowing what people were working on, and having a natural time to ask for/offer help. So (for now) we use Geekbot, and configured it to ask everyone on the team four questions each day: –What did you accomplish yesterday? –What is your top priority today? –Where can you use help/what's blocking you? –Which of these best describes your current level of challenge: bored, relaxed, excited, frustrated? Everyone on the team is expected to read each other's standup reports (we have 7 people.)
- user5994461 10y agoIsn't it too much to have this every day? I've found that asking people every day incentivized them to write about anything and invent stuff just to fill up the question.
- SatvikBeri 10y agoAll the questions are optional. It's a little more than my team would like, and a little less than I would like to ask each day, so I think it's a fair compromise.
- AznHisoka 10y agoWhen i did something like this in my prior company I did not care at all what others wrote. i would lie to my manager that i read it but i still did not care.
- Drdrdrq 10y agoThanks for explaining! I am not sure I would want to it this way because in my experience people tend to avoid "needless" tasks (such as reading on other people's progress :)), but it's good to know nevertheless.
- gregshap 10y agoAgreed! We had the same great experience with turning standup into an async chat room. We're bicoastal so it's even harder to find a workable time, but I still got flack from outside the team. The improvement in outcomes was so huge that it was very easy to defend.
- user5994461 10y agoMy experience was to remove the daily standup. Best decision ever.