31–40 of 112 posts
Standups are awesome when done right... but unfortunately, given that my team works fairly independently, standups end up getting stretched because some member of the team prolongs his/her update to get a team opinion on either a design issue or a technical problem (or a product issue). The simple way we time-box our stand ups is by planking [1] while giving standup updates. This ensures each person speaks for [1] ht…
Hi HN! I'm JP, founder of Standups.io. Last March, I resigned from my full-time iOS job with the idea of making a web/mobile app for async video standups. I did some traveling (China/Vietnam) while I started to work on the app, but eventually ended up back in Germany, escaping South Asia's rainy season :) The idea of async video standups started to grow on me since last December when I was in the north of Brazil. I w…
Hi HN! I'm JP, founder of Standups.io. Last March, I resigned from my full-time iOS job with the idea of making a web/mobile app for async video standups. I did some traveling (China/Vietnam) while I started to work on the app, but eventually ended up back in Germany, escaping South Asia's rainy season :) The idea of async video standups started to grow on me since last December when I was in the north of Brazil. I w…
Standups are awesome when done right... but unfortunately, given that my team works fairly independently, standups end up getting stretched because some member of the team prolongs his/her update to get a team opinion on either a design issue or a technical problem (or a product issue). The simple way we time-box our stand ups is by planking [1] while giving standup updates. This ensures each person speaks for [1] ht…
Standups are awesome when done right... but unfortunately, given that my team works fairly independently, standups end up getting stretched because some member of the team prolongs his/her update to get a team opinion on either a design issue or a technical problem (or a product issue). The simple way we time-box our stand ups is by planking [1] while giving standup updates. This ensures each person speaks for [1] ht…
Standups are awesome when done right... but unfortunately, given that my team works fairly independently, standups end up getting stretched because some member of the team prolongs his/her update to get a team opinion on either a design issue or a technical problem (or a product issue). The simple way we time-box our stand ups is by planking [1] while giving standup updates. This ensures each person speaks for [1] ht…
You'd probably want team buy-in before doing that, of course. If most people agree that standups are too long, you could get pre-emptive permission by asking the team if they're cool with you becoming the standup police like that. In my experience, most people are willing to admit that long standups are a problem, but only in retrospect - never when they're the one actively talking. :)
Standups are awesome when done right... but unfortunately, given that my team works fairly independently, standups end up getting stretched because some member of the team prolongs his/her update to get a team opinion on either a design issue or a technical problem (or a product issue). The simple way we time-box our stand ups is by planking [1] while giving standup updates. This ensures each person speaks for [1] ht…
I see how this can be used for status reporting, but who really cares about that?
Note, I'm not trying to HN-diss this tool. I really want this tool - assuming it helps us actually use the standup for setting priorities and helping each other out.