We Should Be Held Accountable
We Should Be Held Accountable
Join the DZone community and get the full member experience.Join For Free
Discover how you can take agile development to the next level with low-code.
This article was originally written by Derek Huether.
Why We Should Be Held Accountable
When I speak to people (including Agile coaches) from other companies, I tend to see and hear a lot of interesting perspectives. Many buy into the idea of Agile being this cultural shift with everyone sitting around a campfire singing Kumbaya and feeling all happy. Personally, I think these people are getting the 10 principles of the Agile Manifesto confused with the 10 principles of Burning Man. In reality, we’re all under a lot of pressure to deliver something. People don’t pay LeadingAgile to just show up and do a magic trick. We dig in and get companies unstuck. We have to work hard to keep teams and organizations moving in the right direction. In order to help ensure delivery commitments are being met, I believe we should be held accountable. Empowerment without accountability becomes chaos…or at least a transformation that doesn’t really go anywhere.
Everyone is Organizationally Accountable
Employers hire people to do work. Employees (including contractors, consultants, and coaches) have skills that contribute to something valuable that employers can sell at a profit. When employers ask if we can get something done in a certain period of time, we can’t refuse to answer the question. We can either say yes unconditionally, say yes but with an alternative timeline with justifications, or just say no. Say yes, and we do everything in our power to make it a reality. In our hearts, we want to keep our commitments. We’re not doing ourselves any favors by making commitments we know we can’t keep. I believe employers respect you more if you say you can’t meet a deadline and explain why, rather than keep saying yes. If you are one of 10 or even 100 employees, and nobody can keep a commitment, I don’t see the business (or at least that employer) lasting for long. We may not feel comfortable with the deadline. We may have to push ourselves. But that’s ok! People are going to be happy, if they are forced to make commitments and then they actually get it done. Why not leverage Agile practices to help keep commitments? Don’t get confused. The goal is not to be Agile. The goal is to get stuff done by focusing attention on the right stuff at the right time, always keeping your eyes and ears focused on what is most important to the business (not you).
I am Personally Accountable
As an Agile Coach, I hold myself personally accountable to a client. We write a statement of work. I commit to do certain things on a certain timeline. I should not accept an assignment if I are unwilling to commit to the deliverables or timelines. Sound familiar? As an Agile Coach, would I ever ask a Scrum team to do less? Sometimes, as coaches, we become myopic. Coaches should understand the engagement from a high level (epic), what timelines or deliverables are valuable to the client (features), and chunk those down into manageable and measurable pieces (stories) that can be demonstrated to the customer on a regular basis. As an Agile Coach, I should be able to use the same metrics I use with client teams. What’s my completion ratio (am I meeting the commitments I recently made)? How long is it taking me to deliver something of value? If the engagement is for a few months, I should know the high level goals. If for just a few weeks, I should have a known list of deliverables with articulated acceptance criteria. Every day, I should be prepared to tell the customer what value I will deliver today and what value I delivered yesterday. Empowerment without accountability becomes chaos. Do you agree? Should we all be more accountable?
Published at DZone with permission of Mike Cottmeyer , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.