4 ms·

I often hear that from smart engineers and like the DIY attitude. However, it's not a no-brainer to build a stable architecture to provide this service. We know

by nerdben 12y ago

I often hear that from smart engineers and like the DIY attitude. However, it's not a no-brainer to build a stable architecture to provide this service. We know, because we build many sw architectures before. One of the ideas behind is, that we want to provide something using a communication channel people use every day rather than introducing a new one like Slack, Hipchat etc. However, StandupMail is a great addition to teams using those tools already. Using StandupMail is not about sending in "dones" for every single task accomplished. It's more about a quick recap of what everyone thinks is important for the team to know to stay productive the next day and overlook the big picture of the project.

deanclatworthy 12y ago
I'd suggest you look closer at the services that teams are already using and try and add value to those by algorithmically generating what you think is useful for people to know. I agree simply acknowledging what to-do's people have ticked off in the day isn't that useful (BC can already do this for example) but there is room for intelligent insight here. You could determine people's productivity rate towards a milestone and provide predictions if things are on track for a particular milestone date etc. I think then you would have a valuable service. Just my 2 cents ;-)