Are agile scrums an outdated idea?
Here’s a video on YouTube making the case for why agile was an innovative methodology when it was first introduced 20 years ago.
However, he argues these days, daily scrums are a waste of time, and many organisations would be better off automating their reporting processes, giving teams more autonomy, and letting people get on with their work:
https://youtu.be/KJ5u_Kui1sU?si=M_VLET7v0wCP4gHq
A few of my thoughts.
First, it’s worth noting that many organisations that claim to be “agile” aren’t, and many that claim to use agile processes don’t.
Just as a refresher, here’s the key values and principles from the agile manifesto: http://agilemanifesto.org/
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
* Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
* Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
* Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
* Business people and developers must work together daily throughout the project.
* Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
* The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
* Working software is the primary measure of progress.
* Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
* Continuous attention to technical excellence and good design enhances agility.
* Simplicity–the art of maximizing the amount of work not done–is essential.
* The best architectures, requirements, and designs emerge from self-organizing teams.
* At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Your workplace isn’t agile if your team is micromanaged from above; if you have a kanban board filled with planning, documentation, and reporting tasks; if your organisation is driven by processes and procedures; if you don’t have autonomous cross-functional teams.
Yet in many “agile” organisations, I’ve noticed that the basic principles of agile are ignored, and what you have is micromanagement through scrums and kanban boards.
And especially outside software development teams, agile tends to just be a hollow buzzword. (I once met a manager at a conference who talked up how agile his business was, and didn’t believe me when I said agile was originally a software development methodology — one he revealed he wasn’t following the principles of.)
@Zaktor @bluGill No. A lot of meeting could better have been e-mails or a chat message, but they are still slower than direct communication. Usually people have switch off notifications so they are not distracted by all the emails coming in over the day.
Meetings also synchronize the team which important to give everyone an overview. All are concentrated on the subject (if the meeting is short). Furthermore, it is a ritual. And ritual are important for human beings to structure their day.
The problem isn’t the speed of communication, it’s requiring everyone else to witness communication that doesn’t apply to them. I’ve never been on a team where 8+ people are all potentially involved in the same issue. If it takes someone 5 minutes to write an email or 1 minute to talk it out, it’s still a bad idea to have 8 people listen so their communication will be faster. And generally a back and forth, which is where direct communication really shines over email, shouldn’t be a full-team situation.
And yeah, email can be a distraction, but that means you need to handle email better (filter your team’s email to priority and churn through the bullshit flooding your inbox later). It’s just as much a flow killer to get people up and out for a meeting that may be short, but is largely worthless. I know when a meeting isn’t worth my time. Short is better than long, but it’s still a disruption beyond skimming an email and recognizing “not my thing”.
In the end, what really strikes me as a problem is the frequency of these meetings. You shouldn’t need to be synchronizing your team every day. Leading up to a release, sure, every day matters and things can change in an instant, but for a regular way to manage a software team? You shouldn’t have daily pivots needing realignment. The ritual isn’t to make the devs comfortable by structuring their day, they’re not children and they can make their own structure, it’s instilling a feeling of perpetual crunch.