Skip to main content

SDM Insights: Revise your definition of Success

SDM Insights: Revise your definition of Success

In celebration of my fourth anniversary as a Software Development Manager (SDM), I've written a series of reflections on some lessons learned. See the full list here.

Separating the two halves of my IT career is a 9-year hiatus, most of which was spent as an Anglican priest in a small, rural parish. Despite knowing better, I internally defined my success by the attendance and financial health of the parish. So as people aged and died, and weekly attendance and giving slowly shrank, my frustration and sense of failure grew.

The fundamental flaw was that I was using the wrong definitions of Success.

As a developer, my definition of Success was more oriented toward the tasks I was assigned. Was I delivering them on time? Was I increasing the test coverage as I did so? Was I meeting and exceeding my targets for fixes and new features?

Was I out-performing the other developers?

Those definitions were a mix of qualitative and quantitative, of absolute and relative performance. And they were either within my control or ones over which I had significant direct impact.

As a Manager, on the other hand, I am one or several steps removed from the hands-on-keyboard side of Development. I have less opportunity to do what needs to be done myself, to ensure that the feature is completed and solid and tested.

Now, I need to align other factors that clear the way for my team to do their jobs. My definition of Success needed a change.

So what is Success for a SDM?

I define Success along three different overlapping time scales.

Fireworks - celebrating success!

Daily-Scale

The shortest such time scale is Daily. On any given day, have I handled any crisis that arose? They could be a tech issue blocking progress, or a production issue needing immediate attention, or interpersonal conflict. Have I blocked distractions from interfering with my team? have I adequately moved forward the future projects that depend on me? Any given day can have the Urgent interrupt the Important, so have I properly prioritized tasks and challenges? When I can end my work-day satisfied that I did good work and am set up well for tomorrow, then the day-to-day definition of Success has been met.

Sprint-Scale

Next is the Sprint-scale measure of Success. Mid-Sprint 1-on-1 check-ins with each Developer, keeping the pulse of the issues in the Daily Scrums, these and other techniques give me as SDM a chance to forecast and affect as necessary how the Sprint will measure up against its commitments - the definition of a successful Sprint being to complete all tickets to the agreed-upon state by the end of the Sprint.

When I started this role, the team's Sprint board regularly had 70 or more tickets on it, the vast majority of which would be carried over from Sprint to Sprint. In order to create more successful Sprints, we needed changes to several processes, and clearer articulation of expectations. We needed a cultural change, one that is still not complete although we have moved closer to a culture of successful, targeted and realistic Sprints.

Release-Scale

Finally, the Release-scale measure is the ultimate, long-term definition of Success. A Software Development team's purpose is to build and maintain quality software and get it into the hands of our clients. Whether the releases happen monthly, quarterly, or continuously, this scale is a vital factor in SDM Success. Did we deliver what we needed to deliver, on time and on budget? Once in the hands of clients, was the software solid and stable? What bug reports or significant production issues arose as a result of the released code? Whether a single individual or a whole team contributed to the feature and release, these measures across the whole team contribute to the SDM success.

As a Developer, achieving Success felt like something I could directly influence.

As an SDM, Success is more influenced by the rolling together of the individual successes of everyone on the team, plus the goals and objectives for the team as a whole. As someone who is passionate about helping others be their best selves, I have embraced this broader definition, even as the control-freak side of me has lamented being a step removed from the direct hands-on-keyboard influence.




Labels:

Popular posts from this blog

Git Reset in Eclipse

Using Git and the Eclipse IDE, you have a series of commits in your branch history, but need to back up to an earlier version. The Git Reset feature is a powerful tool with just a whiff of danger, and is accessible with just a couple clicks in Eclipse. In Eclipse, switch to the History view. In my example it shows a series of 3 changes, 3 separate committed versions of the Person file. After commit 6d5ef3e, the HEAD (shown), Index, and Working Directory all have the same version, Person 3.0.
Read more

Scala Collections: A Group of groupBy() Examples

Scala provides a rich Collections API. Let's look at the useful groupBy() function. What does groupBy() do? It takes a collection, assesses each item in that collection against a discriminator function, and returns a Map data structure. Each key in the returned map is a distinct result of the discriminator function, and the key's corresponding value is another collection which contains all elements of the original one that evaluate the same way against the discriminator function. So, for example, here is a collection of Strings: val sports = Seq ("baseball", "ice hockey", "football", "basketball", "110m hurdles", "field hockey") Running it through the Scala interpreter produces this output showing our value's definition: sports: Seq[String] = List(baseball, ice hockey, football, basketball, 110m hurdles, field hockey) We can group those sports names by, say, their first letter. To do so, we need a disc
Read more

Java 8: Rewrite For-loops using Stream API

Java 8 Tip: Anytime you write a Java For-loop, ask yourself if you can rewrite it with the Streams API. Now that I have moved to Java 8 in my work and home development, whenever I want to use a For-loop, I write it and then see if I can rewrite it using the Stream API. For example: I have an object called myThing, some Collection-like data structure which contains an arbitrary number of Fields. Something has happened, and I want to set all of the fields to some common state, in my case "Hidden"
Read more

How to do Git Rebase in Eclipse

This is an abbreviated version of a fuller post about Git Rebase in Eclipse. See the longer one here : One side-effect of merging Git branches is that it leaves a Merge commit. This can create a history view something like: The clutter of parallel lines shows the life spans of those local branches, and extra commits (nine in the above screen-shot, marked by the green arrows icon). Check out this extreme-case history:  http://agentdero.cachefly.net/unethicalblogger.com/images/branch_madness.jpeg Merge Commits show all the gory details of how the code base evolved. For some teams, that’s what they want or need, all the time. Others may find it unnecessarily long and cluttered. They prefer the history to tell the bigger story, and not dwell on tiny details like every trivial Merge-commit. Git Rebase offers us 2 benefits over Git Merge: First, Rebase allows us to clean up a set of local commits before pushing them to the shared, central repository. For this
Read more

Code Coverage in C#.NET Unit Tests - Setting up OpenCover

The purpose of this post is to be a brain-dump for how we set up and used OpenCover and ReportGenerator command-line tools for code coverage analysis and reporting in our projects. The documentation made some assumptions that took some digging to fully understand, so to save my (and maybe others') time and effort in the future, here are my notes. Our project, which I will call CEP for short, includes a handful of sub-projects within the same solution. They are a mix of Web APIs, ASP MVC applications and Class libraries. For Unit Tests, we chose to write them using the MSTest framework, along with the Moq mocking framework. As the various sub-projects evolved, we needed to know more about the coverage of our automated tests. What classes, methods and instructions had tests exercising them, and what ones did not? Code Coverage tools are conveniently built-in for Visual Studio 2017 Enterprise Edition, but not for our Professional Edition installations. Much less for any Commun
Read more