Re: [extremeprogramming] Origin of term "standup"?

Just because a practice is being misused does not necessarily mean the
practice itself is the problem.  If a team writes useless tests, does that
make TDD or automated testing a bad practice?

In your example, JIRA (or the approach/culture that makes JIRA seemingly
necessary) is the likely root cause - the misuse of the standup is just the
symptom.  Do you really think getting rid of the standup will motivate the
team to use story names instead of ticket numbers or to swarm instead of
working independently or to interact more outside of the standup?

On Mon, Nov 25, 2019 at 8:25 AM Tim Ottinger via Groups.Io <linux_tim=
[email protected]> wrote:

>
> I said I would let it go, but I don’t see how using 3 questions in a
> standup meeting in the morning focused on updating Jira is “many ways of
> working” but not doing that leaves only exactly 1.
>
> I find that uniformly, when people ARE doing it this way, it’s a sign of
> some dysfunction(s). That’s my experience. There are many ways of working
> that do NOT do that, just as there are many ways of working even if one
> does use Jira update meetings.
>
> But the Jira update meetings are almost always a sign that teamwork is
> lacking, people aren’t talking, and that the 15 minutes is mostly (usually
> about 13 minutes) wasted on everyone there.
>
> Classic “I worked on 2356 yesterday, today I hope to get started on 3440.
> No blockers” typically gives no information that anyone the team has any
> investment in hearing. Nobody knows your ticket numbers, and they all have
> their own. It’s a waste. Who really knows what 2330 means? Remember 2330?
> You worked on that last month. No? Me either.
>
>
>
> Sent from Yahoo Mail for iPad <https://overview.mail.yahoo.com/?.src=iOS>
>
> On Sunday, November 24, 2019, 11:52 AM, Steve Gordon <[email protected]>
> wrote:
>
> "When I see the 3 questions Jira-update meeting, it is a fairly sure sign
> of dysfunction."
>
> Saying that implies there is only one way for a team to work effectively.
> I do not believe that.
>
> Furthermore, when this meeting is a sign of dysfunction, it is quite
> likely the meeting itself is not the most dysfunctional thing the team is
> or is not doing.  I would suspect JIRA is a often a much greater source of
> dysfunction than the meeting is.
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#160348): https://groups.io/g/extremeprogramming/message/160348
Mute This Topic: https://groups.io/mt/56090734/2417047
Group Owner: [email protected]
Unsubscribe: https://groups.io/g/extremeprogramming/leave/4902963/619838065/xyzzy  [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-