You don’t need standup

  1. No stand-ups
  2. No planning at regular intervals
  3. No retros
  4. All meetings are optional
  1. Trello (or whatever you use) has to be kept in sync with what’s discussed in these meetings. It often isn’t. As the team grows this becomes even more complicated.
  2. Stand-ups ENCOURAGE plans to change daily. Lack of consistency is a great way to ruin developer flow.
  3. Standup forces every team member to be productive at a set place and a set time
  4. Extroverts thrive at stand-ups, planning, and retros. It’s no wonder that tech debt is such a common problem. Developers shouldn’t have to PUSH for tech debt to be addressed. Teams should operate at a sustainable pace.
  5. Why do we encourage problems to be discussed once a week? We should address them immediately, not just at retros.
  6. Sprints encourage iterative development. This sounds really good to people like me who strongly advocate small, concise, pull requests over long-living feature branches. But it’s not the same thing. Sprints encourage features over tech debt. How often have you had to advocate spending an entire sprint tackling tech debt?
  1. Developers communicate more
  2. Your team becomes more remote-friendly
  3. Tech debt gets addressed
  4. Developers feel more in control and less stressed
  5. Developers know you trust them and that you have their back
  1. Developers are trusted to be working on the correct things
  2. Developers aren’t interrupted nearly as much so things get done
  3. Backlog is used as a priority queue of work to be done
  4. Tasks are added to the backlog as needed, continuously
  5. Blockers are communicated right away
  6. Planning happens when plans change. Meeting fatigue is reduced and the team knows this was a last resort and is important
  1. Developers aren’t interrupted and get shit done
  2. Problems are addressed sooner
  3. Stickies and sharpies are returned and we buy lunch instead

--

--

--

Engineering lead at Spotify

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Two-phase commit: The start of our journey to a fault-tolerant replicated state machine

Journey to a million models

Go client library best practices

75X Growth: Scaling Postman Enterprise Across PayPal

Future of World is in the hands of better APIs and not better Products

Embrace the Mono-repo!

Local, offline serverless app development with Architect

Einstein Evaluation Store — Beyond Metrics for ML / AI Quality

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
palmerj3

palmerj3

Engineering lead at Spotify

More from Medium

No Agile or Do Agile or Be Agile

Chickens & Pigs in Team O’clock

The Explanation of Agile You Probably Never Heard

Agile does not fix…