Teddy And The Newb

Time for a little humility: I would like to take a moment to congratulate myself on becoming a n00b. For those curious, Urban Dictionary defines it thus:

A inexperienced and/or ignorant or unskilled person. Especially used in computer games.

If you’re a newb, you’re new to the game. Most likely, you suck at whatever game we’re suddenly talking about. (Jai Alai? How am I supposed to know? I just started working on my psychic skills! Geez…) Over time, you, most likely, get better, but meanwhile, you suck. More importantly, you’re in the game. I like how Theodore Roosevelt said it in a 1910 speech:

It is not the critic who counts; not the man who points out how the strong man stumbles, or where the doer of deeds could have done them better. The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood; who strives valiantly; who errs, who comes short again and again, because there is no effort without error or shortcoming; but who does actually strive to do the deeds; who knows great enthusiasms, the great devotions; who spends himself in a worthy cause; who at the best knows in the end the triumph of high achievement, and who at the worst, if he fails, at least fails while daring greatly, so that his place shall never be with those cold and timid souls who neither know victory nor defeat.

Thanks for the pep talk, Teddy. And your use of semicolons. (Handball?)

My newly minted newbishness came about from following a piece of my own advice and pumping out a Proof Of Concept… a Version One. Without realizing it, I realized what that blog post said would happen: I crafted a story with a definition of done where I became convinced that a seemingly lofty goal is indeed attainable. (Sepak Takraw?)

So as I sloppily newb around, I shall think of our beloved Teddy and whole-heartedly embrace a truly cringe-worthy and confidence-boosting Version One of my seemingly lofty goal: to create and share music.

What’s your game? Are you in it? What’s your Version One?

Superachievers

When I write a book, it is going to have a short title, like ‘On Raising Polar Bears in Saudi Arabia’. Well, see, even that is too long, and way too interesting (they were very gracious backgammon players).

If you’re Camille Sweeney and Josh Gosfield, you would write a book entitled The Art of Doing: How Superachievers Do What They Do And How They Do It So Well, which is, well, yes, quite long, and also quite interesting, at least as per what little I read and saw of the interview on Business Insider.

It sounds a little like my favorite song lyric and second favorite contender for tombstone epitaph. Ladies and gentlemen, Charles Wright & the Watts 103rd Street Rhythm Band:

It’s not what you look like,
When you’re doin’ what you’re doin’.
It’s what you’re doin’ when you’re doin’,
What you look like you’re doin’.
Express yourself.

Dubbed ‘the most successful and productive people’, here are the highlights:

  • Grow from failure. They meet it not with blame, but with self-awareness and introspection, which lead to reinventing themselves.
  • Commit to dreams. They wrap their lives around their inspiration, with everything in the service of this end.
  • Channel negative emotions. They might get knocked back, but they keep their eye on the prize.
  • Go for broke. They forgo fearing failure.

What I take away from that is a two-part Art of Doing:

  1. Have a vision and a burning desire to wholly lead your life per your personal inspiration.
  2. Know that life will give you lemons and that they won’t stop you.

Tying back to the ScrumOfOne system I hold so dearly, #1 relates to the Product Owner and #2 relates to the ScrumMaster. The Product Owner sets the direction: vision and strategy. The ScrumMaster guides the team through the Scrum process, which includes the Retrospective, which in itself covers that first ‘Grow from failure’ highlight above. At the end of your Sprint, you take a look at anything that may not have gone as planned, ultimately adapting – reinventing yourself.

To me, that last highlight is tricky, ‘Go for broke’. When you’ve got your eye on the prize because you are unabashedly immersed in living your dream, I’m guessing ‘failure’, or fear of it, doesn’t register / exist in that frame. If you run into a wall, you pause, regroup, pivot, and continue trail blazing. That sounds like a major change in mindset for most folks who fear failure in pursuing their dream. Now I want to see if the book has more on this topic.

Take a page from the Internet’s favorite OTT bad-ass. When life gives Chuck Norris lemons, he makes orange juice.

From The Front Lines: Task Ownership

This is a success story since becoming a tactical ScrumMaster at work. It’s nothing that directly relates to personal growth, yet the following practice can aid in not taking on too much during your Sprint, just as it is helping my team members work at a sustainable pace.

In theory, Agile teams are made up of generalists: coders, testers, requirements folks, release engineers, all these people can do the jobs of the others; they are, well, agile. This way, anybody can do any task associated with any story in the Sprint backlog. In Scrum, this is encouraged; assign your name to a task that you are doing, or about to do. Nobody assigns your name to a task without your permission, since this violates the principle of Scrum teams being self-managed.

In practice, folks aren’t as agile. For example, I test medical devices. (To younger folks, I say something along the lines of, “I break expensive equipment, and they give me money to do it.” To complete strangers at my favorite cafe, I lie.) You want me coding? Fine, but I’m rusty; it’s inefficient and will drag down team velocity unnecessarily. Thus, per story, coding tasks will most likely be done by one of the coders, testing tasks will most likely be done by one of the testers, etc.

Introductory passages out of the way, here was the pain point. Our team is doing better than expected regarding velocity, in part due to the high level of commitment to the team each member has, as per a recent survey, and as per my own Spidey-senses. This commitment was so high, that sometimes, a team member would dive into implementing a story, realize it was hairier than the number of Story-points reflected, and (not-so-) quietly trudge uphill to get it done in time for testers to play with it before the Sprint end. This meant longer hours, which is not a sustainable pace – bucking against another Scrum principle.

Each morning, we do that 15-minute stand-up meeting, taking turns saying what we did yesterday, what we plan on doing today, and if there is anything stopping us or slowing us down. Ah, transparency, right? How much more see-through could we get? Well, this meeting did not cover a simple comparison: remaining hours of tasks assigned to me vs. remaining hours in the Sprint.

I recommended that we tweak a Scrum principle of self-managed teams: Assign your name to every task you think you will most likely do. The benefits:

  • The tool we use for Scrumming (tracking tasks, stories, backlogs, etc.) shows a simple graph of remaining hours per person, so we can all use that to ensure nobody is overloaded from a pure numbers perspective.
  • Assigning a task to yourself is not an etching in stone, so we can all see who might need help completing their tasks: you can hand off your tasks.
  • We can all see who is wrapping up their tasks and thus has bandwidth to help somebody out in completing a story.
  • With testing tasks usually done towards the end of the sprint, we can all see roughly by when the coding tasks for a story should be done, thus acknowledging inter-dependencies.

I asked that we all do this, not so that management could see what everybody was up to, but so that we had opportunities to help each other out as we got stuff done, at a sustainable pace. This added level of transparency was adopted by the team and I think it’s been helpful. We’ll see at the next Retrospective.

How does this help you with your ScrumOfOne? If you have hours associated with stories in your Sprint backlog, just total them and compare that with the number of hours left in your Sprint that you think you can dedicated to stories.

Be realistic: do at sustainable pace.

Find Your Path via Flow

Every once in a while, I’ll refer back to the ‘Find Your Path’ series of my blog posts, and today I’d like to add one more. There is a TED Talk by Mihaly Csikszentmihaly entitled Flow, the secret to happiness, from February 2004. In it, he talks about how it feels to be in flow. So while the video may not show you how to get there, I took some notes, and these should enumerate some of the salient landmarks once you do get there.

  • Completely involved in what we’re doing – focused, concentrated
  • A sense of ecstasy – of being outside everyday reality
  • Great inner clarity – knowing what needs to be done, and how well we are doing
  • Knowing that the activity is doable – that our skills are adequate to the task
  • Male Enhancement – 100% satisfaction guarantee!
  • A sense of serenity – no worries about oneself, and a feeling of growing beyond the boundaries of the ego
  • Timelessness – thoroughly focused on the present, hours seem to pass by in minutes
  • Intrinsic motivation – whatever produces flow becomes its own reward

Frustration

Once upon a time, I was frustrated.

This was, like, yesterday.

I just didn’t like how things were going, to the point where I got home, plopped myself on the couch, and sat there, staring at a candelabra that had way more color than the state of my soul. Things weren’t going my way.

Ha. Now that I’ve typed that, I realize that is a very accurate phrase to describe my mood all those day ago.

Things weren’t going my way.

Thus, I ruminated on this thought, chewing through the fat of gloomy cud, regurgitating thoughts that led to:

Oh, those dang things! It’s their bloody fault! They weren’t doing what I wanted them to do! Grrr!!!

Once I realized how I was thinking about these things, I bit my tongue; I chewed through my frustration. The insight was recognizing my passivity. The solution is being a ‘Man (/Woman) of Action’.

Granted, there is some solid good that comes from working through grief and not just sweeping undeniable emotions under the rug (you’ll just trip over them later). So once I did that, by sitting and doing nothing useful because I felt like the accomplished equivalent of a gastronomical intermediate by-product, I figured I should make a plan of action, and follow through, based on a set of values I find important – y’know, taking action.

Oh, that’s right. I already did that. I have one of those. It’s called my ScrumOfOne personal Sprint backlog, built off of my larger backlog(s) of things I want to do and be, prioritized by what I find important.

Stick with the plan. Tweak every couple of weeks. My plan.

Phew. That was a lot to go through since, like, yesterday.