Outcomes Over Being Busy
Outcomes Over Being Busy
The author explores being busy and the importance of backlog.
Join the DZone community and get the full member experience.Join For Free
The Agile Zone is brought to you in partnership with Techtown Training. Learn how DevOps and SAFe® can be used either separately or in unison as a way to make your organization more efficient, more effective, and more successful in our SAFe® vs DevOps eBook.
How often have you asked friends or co-workers how they were doing and they respond that they have way too much on their plate and feel like they are constantly juggling things?
I often feel the same way. When I look at the constant channels of input – email, texts, phone calls – it is no wonder that we’re drowning. It is clear that we have plenty of opportunities to stay busy and plenty to keep us busy.
But is staying busy the goal? I think not. There is nothing wrong with staying busy but what we should be after are clear outcomes.
As I work with software development organizations, I’ve yet to find teams that aren’t super busy. But is busy good enough?
The Importance of a Well-Defined Backlog
A core belief at LeadingAgile is that there must be clarity in the backlog – clarity on what we are asking our teams to deliver. Clarity in the backlog ensures that teams are focused on the right outcomes.
I’ve seen situations where organizations are super-focused on keeping their teams busy but with a lack of clarity in the backlog. Even so, the organization feels they must keep the teams busy regardless of the state of the backlog. Even in the absence of a clear backlog, the teams forge ahead doing work with non-ready requirements. When our teams stay busy in this situation they end up filling in the blanks. They are not necessarily building what is needed to meet the needs of the business. I’ve seen situations where these busy teams end up reworking 50% of what they have completed, if not more! Yes, teams are staying busy…
There are many reasons why this might be the case and often I see that there aren’t sufficient resources involved with backlog refinement, or they are refining requirements well past the last responsible moment. Any investment we can make in providing clarity in the backlog pays huge dividends. We have less rework, we have faster feedback, and reduced waste in delivering working, tested software. It has been said that the number one reason agile teams fail is the lack of a well-defined backlog. I would agree and an early focus with any agile transformation is to invest in providing clarity in the backlog.
Yes, we are busy, but let’s make sure we are focused on clear outcomes.
Published at DZone with permission of Rick Austin . See the original article here.
Opinions expressed by DZone contributors are their own.