Getting Stuff Done on a Software Team
It’s a Friday in the office. The end of another Sprint iteration.
And everything is a bit chaotic.
Multiple devs still have outstanding work awaiting approvals so they can merge them into main. Many of them have merge conflicts. We've also got a high-priority bug fix that we still need to start on, which is supposed to be done by the end of the day (the PM promised it would be).
On top of that, no one seems to remember if we hit our Spring Goals — or even what they were! Everyone had focused on working on our individual stories instead of completing our goals.
For far too many devs, this situation is painfully relatable.
For all the promises of Agile software development and tools to facilitate better work streams, many dev teams find it difficult to actually get stuff done. Teams are pulled in various directions internally, find themselves working alone more than intended, and constantly being asked to report on items they never committed to.
But getting stuff done on your software team doesn’t have to be so frustrating and chaotic. And it starts with a simple shift:
Focus on getting things done rather than starting new things.
