> Jira, Trello, Asana, the stickies on your wall, or reach out on Slack
In a nutshell, the article claims that these electronic tools render a daily standup pointless and/or disruptive.
First, note how many different tools are mentioned. If your project uses one or more of them, you'll need to monitor them all to understand what's happening around you.
Second, the constant interruptions of Slack can be extremely disruptive to workflow, as has been noted in a few articles posted here.
Third, the article makes an assumption I've seen elsewhere and cannot relate to at all: that project members don't need a high-level snapshot of the project on a day-to-day basis. That it doesn't improve what they do and only sucks time away from the more important job of getting stuff done. As the author puts it:
> I'd argue the loss of your focus more probable than the benefit of knowing what someone else is working on.
This is a recipe for the entire team heading off a waterfall, each in their own hermetically-sealed, technologically sublime barrels. This is not to say that a daily standup can save you if the team is determined to do it. But getting that daily overview can help build consensus for changes in direction that simply can't come about by monitoring Jira.
I always wonder how effective team members showing the tendency to minimize the bigger picture while maximizing the importance of their own contribution will be on a team. The answer usually turns out to be "not very."
In a nutshell, the article claims that these electronic tools render a daily standup pointless and/or disruptive.
First, note how many different tools are mentioned. If your project uses one or more of them, you'll need to monitor them all to understand what's happening around you.
Second, the constant interruptions of Slack can be extremely disruptive to workflow, as has been noted in a few articles posted here.
Third, the article makes an assumption I've seen elsewhere and cannot relate to at all: that project members don't need a high-level snapshot of the project on a day-to-day basis. That it doesn't improve what they do and only sucks time away from the more important job of getting stuff done. As the author puts it:
> I'd argue the loss of your focus more probable than the benefit of knowing what someone else is working on.
This is a recipe for the entire team heading off a waterfall, each in their own hermetically-sealed, technologically sublime barrels. This is not to say that a daily standup can save you if the team is determined to do it. But getting that daily overview can help build consensus for changes in direction that simply can't come about by monitoring Jira.
I always wonder how effective team members showing the tendency to minimize the bigger picture while maximizing the importance of their own contribution will be on a team. The answer usually turns out to be "not very."