Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
It's then natural to want to work with people who are just like us, our clones.
So, every once in a while when we come across people who do not value our inputs, crush our ideas, ignore what we have to say, act as a know-it-all, seem to find pleasure in criticism, satisfaction in creating chaos and look for the negative side of things, it upsets us.
I started out this blog post writing about shared accountability for agile program teams. Accountability is an interesting, large topic that gets skipped over quite often in our agile community. In fact, I found in my writing a realization that we don’t have a great track record for defining it. So here’s my take.
You may also like: Creating a Fear-Driven Development Culture
Caution! I am trying to pair down my mindmap of points to discuss in this blog. Apparently, I am not doing a great job and I’ll own that. The way that I’ll own it is by committing to write to conclusion about:
Sorting out who does what on a project would appear to be pretty basic. Clear tasks, with clear responsibilities and deadlines, is Project Management 101. But in too many projects, it remains unclear who is responsible for a deliverable until it’s too late.
The Circle Dot Chart addresses this issue. It’s a tool for getting clear on what deliverables are due, when, and who is responsible for them. The chart consists of lines that represent tasks, and circles at the intersection of tasks and functional responsibilities. It identifies key deliverables on the horizontal axis and key roles or key individuals on the vertical axis. Open circles indicate that an individual function is involved, while solid circles represent the directly responsible individual (DRI) for a given deliverable. It is essential that there be one and only one DRI.
No doubt you have heard that software is eating the world and possibly even that developers are the new kingmakers. If all this is true, then there is a lot of responsibility that now rests with developers (for people practicing DevOps, this is also self-evident). Even before the rise of DevOps, developers were effectively entrusted with a lot of responsibility for the success of the business. Millions of dollars, or in some cases even lives, could be at stake.
Surely you have heard that with great power comes great responsibility? The flip side of this “new kingmaker” capability is that now (a lot) more is expected of developers.