Earlier quoted context omitted.
> 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.
Launch HN: Spinach.io (YC W22) – Better daily standups
51–60 of 188 posts
Re: Launch HN: Spinach.io (YC W22) – Better daily standups
#52(Curious if the OP has an comments on this.)
Re: Launch HN: Spinach.io (YC W22) – Better daily standups
#53Re: Launch HN: Spinach.io (YC W22) – Better daily standups
#54Tried similar tools and ad-hoc processes during the pandemic. None worked as effectively as turning your camera's on and walking the board for 15 minutes. In fact, the chance of miscommunication increased when we introduced tooling like this. Though agile has been bastardized and gotten a bad rep, it's core values of "Individuals and interactions over processes and tools" and principles like "The most efficient and e…
Re: Launch HN: Spinach.io (YC W22) – Better daily standups
#55Appears you’re using the standard format of “yesterday, today, blockers” — which on my part is maybe me trying to over optimize, but never understood the format since I assume if someone said the were going to do something that it got done unless there was a blocker; meaning to me saying what you did yesterday feels like it’s repetitive. Mentioned this to number of notable scrum thought leaders and normally get to re…
Re: Launch HN: Spinach.io (YC W22) – Better daily standups
#56We used Spinach since early beta days and it was pretty helpful with running concise & effective morning standups.
Re: Launch HN: Spinach.io (YC W22) – Better daily standups
#57Is this what agile/scrum is now? I feel burned out just reading it. IMHO the 'standup' (keep them on their toes!) was always suspect if it was just a PM 'what have you done lately' meeting. Progress can be reported asynchronously. IMHO the point of having the team together daily is to raise exceptions/problems/blockers/whatever to the rest of the team, and perhaps co-ordinate the rest of the day.
I don't mind status meetings but call them what they are: a status meeting. It is not a standup.
Standups were about alignment and movement so you didn't get blocked trying to communicate through a broker like your manager.
They are completely abused and probably always will be.
Re: Launch HN: Spinach.io (YC W22) – Better daily standups
#58Re: Launch HN: Spinach.io (YC W22) – Better daily standups
#59Earlier quoted context omitted.
I've had better success with face-to-face standups. In my experience, "progress should be obvious from the board" and async "standups" have been far less effective than actual standups. Lots of engineers are introverted and hate writing; a good product manager can extract context and blockers via voice (without making it feel like a pop quiz or a blame game) that a shy engineer might be hesitant to broadcast in writi…
"manager can extract context and blockers via voice" lol. Which agile principle is this?
Re: Launch HN: Spinach.io (YC W22) – Better daily standups
#60Earlier quoted context omitted.
'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.
If "extract" is too triggering, you can replace it with "glean." Probably a bad word choice on my part.