Or we could just do our work and not deal with a daily standup. Can we get an App for that please? or maybe a JIRA replacement? or AI that can go instead of ME?
Launch HN: Spinach.io (YC W22) – Better daily standups
41–50 of 188 posts
Re: Launch HN: Spinach.io (YC W22) – Better daily standups
#42As I see it, this doesn't reduce the the overhead at all but just increases it by introducing a third party tool to the mix and requiring everyone to engage with it. Sure, it might help if your daily standup is already a mess, but overall just by fixing the process by having a single person running the daily and making sure no-one starts to ramble too much solves the problem of excess time spent in dailies. Assuming…
Agree a single person running it can help. In many cases that doesn't happen or folks just don't like playing that role so the app takes care of it
But it does not since when things get off track no one is paying attention or too afraid to interject. You need a person anyways.
Re: Launch HN: Spinach.io (YC W22) – Better daily standups
#43Or we could just do our work and not deal with a daily standup. Can we get an App for that please? or maybe a JIRA replacement? or AI that can go instead of ME?
That's exactly what we're optimizing for - reduce the coordination overhead and allow builders to focus on building
Re: Launch HN: Spinach.io (YC W22) – Better daily standups
#44> We’re starting by taking on the daily status meeting, a.k.a. standups.
Are you able to share other ways you're setting out to reduce the overhead dev projects, beyond daily-status updates? It sounds like you've got the integration part nailed, which is really cool, but the problem space you're tackling first (daily standups) sounds like it could be resolved with automated Slack bots / a Google Doc (albeit more clumsily). As the tip of the iceberg in a much larger meeting-optimization system though, this might make perfect sense.
Re: Launch HN: Spinach.io (YC W22) – Better daily standups
#45Firstly, congrats on launching. Hard work is hard. I don't want to be negative on your launch day, but at the same time feedback is important. 1. I couldn't see myself or the many agile/lean teams I've been part of using this. I don't feel enough of a burden when walking the board for this to be worth the money. 2. A user in spinach.io costs effectively the same amount as a user in Slack, the difference is that I'm g…
Everyone take note, this is how you post constructive criticism on HN.
Re: Launch HN: Spinach.io (YC W22) – Better daily standups
#46> We’re starting by taking on the daily status meeting, a.k.a. standups. Are you able to share other ways you're setting out to reduce the overhead dev projects, beyond daily-status updates? It sounds like you've got the integration part nailed, which is really cool, but the problem space you're tackling first (daily standups) sounds like it could be resolved with automated Slack bots / a Google Doc (albeit more clum…
We want to facilitate and reduce the coordination overhead across project/cycle. After the daily standup we're planning to help teams with planning/prioritization at the start of a cycle
Re: Launch HN: Spinach.io (YC W22) – Better daily standups
#47Hm, from a purely agile standpoint: This seems to reduce daily stand-ups to status report meetings (and then, why have a stand-up at all?). Does a stand-up that is over in 5 minutes (and has 10-15 minutes of prep time) really bring value to anyone but a team lead?
I can't speak for everybody. But for me: yes, a 5 minute standup is valuable. It's much, much better than a 30 minute standup IMO.
Most people can pay attention for 5 minutes. So if the meeting's only 5 minutes, most people will actually listen and engage. Followups can happen afterwards.
If the standup is 30 minutes though, most people are probably going to tune out and start doing other stuff. It becomes an "ignore the meeting while I wait for my turn" kind of thing. A waste of everybody's time.
I don't want to watch the team-lead click a Jira board for 30 minutes, and I'm guaranteed to get bored and tune out. And once that attention's been lost, the standup loses a lot of utility.
Re: Launch HN: Spinach.io (YC W22) – Better daily standups
#48Hm, from a purely agile standpoint: This seems to reduce daily stand-ups to status report meetings (and then, why have a stand-up at all?). Does a stand-up that is over in 5 minutes (and has 10-15 minutes of prep time) really bring value to anyone but a team lead?
Yesterday, today, blockers… already feels like a relic from the past.
I wish more standups would bring back that format, honestly. It's a lot more interesting than the "watch somebody use Jira" format that seems to be more common today.
Re: Launch HN: Spinach.io (YC W22) – Better daily standups
#49Earlier quoted context omitted.
"manager can extract context and blockers via voice" lol. Which agile principle is this?
> The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
'convey', not 'extract'.
It's a quite different stance. The PM does not 'run' this meeting. That's just a traditional project manager daily status meeting, the inverse of a 'scrum' where the team themselves huddle together and discuss their problems, and what they're going to do next, etc.