Rumors of Death Once Again Exaggerated…and Misplaced

I freely admit that I often run out of things worth saying. Lately, I have been rooting through my old LinkedIn posts for reusable gold and dug up this gem today (if Google stuck an add right below this, keep scrolling to the LinkedIn post):

To save you scrolling through the glitchy LinkedIn iFrame, it is:

Scrum is dead: Breaking down the new open development method

It is one of those that I posted with no context, which is a habit I think I will break starting today. Anyway, I went to re-read before re-posting, especially given the show-and-awe headline. Well…turns out Scrum really isn’t dead (gasp!). Other than a theme based on a very narrow view of how software is built, the article does have some valid points about good habits in open source.

What hit me was the irony. The conclusion has a link to a GitHub repo that has not been updated in many years. The main link on the page points to a site dedicated to the articles’ key concept. Well, I assume it used to. Currently it goes to one of those cheesy, spammy Buy this domain pages.

I’ve certainly written my own poor predictions over the years. And, come to think of it, my domain changed since then, so any links to those errors publicly posted will have a similar result. And so will the correct ones.

This morning ramble brought to you by PTO and writing before coffee.

Facebooktwitterredditlinkedinmail
© Scott S. Nelson

Be Prepared for Meetings

The concept seems like a no-brainer, and maybe it is just my personal experience, but anytime a poll of the meeting attendees is run asking if they reviewed the material sent prior to the meeting, the overwhelming majority response is “no”.

I was reminded of the importance of being prepared while listening to an episode of one my favorite podcasts, “Think Fast, Talk Smart” (please see my YouTube channel for a link to the podcast playlist and subscribe to my channel while you are there so I can finally get a vanity URL). The episode was titled Communicating Our Mistakes: How to Avoid Common Flaws and Make Better Decisions, which I admit was not one of my favorite episodes, but it did spend some time on this topic of preparation, which triggered a confirmation bias response from me. It started with a learning approach where the teacher asked students to complete the lessons before the lecture so that lecture time was spent building on top of that, then moved on to how meetings are more effective if people review the material in advance and discuss in the meeting…

[sounds of wood scraping across the floor as the author pulls his soap box out]

There are corporate cultures where materials are not provided in advance, probably because of the tendency for people not to review them. This makes the problem worse. These same cultures also frequently have meetings schedule with no agenda. I had someone on one of my teams who refused to attend meetings without an agenda. It was difficult for me to fault him, as I agreed with his reasoning.

People hate meetings because they are often inefficient and inclusive. My approach is to go the opposite direction of those who stop sending the material in advance and including agendas: I avoid reviewing the material in the meeting and instead advise those who didn’t to take notes and review it after the meeting. Depending on the purpose of the meeting, I may just reschedule it and advise everyone to come to the next meeting prepared. This may seem anti-[your pet sentiment here], but my experience has been that people become much more productive when they come prepared as a result of the meeting being more productive and few meetings because things were accomplished  the first time.

[author returns his soap box to easily-accessible storage location]

Facebooktwitterredditlinkedinmail
© Scott S. Nelson

Things to Determine before Projects Begin

This post is a perpetual Work-in-Progress. As of now, it is only starting (stalling would be more accurate, I’ve been playing with it in various forms for over a year now).

Here’s what we have so far (please add your additions in the comments):

Project Type Artifact
All Release schedule
All Release process
All Coding standards
All Other StakeHolders that may be impacted
All Where and how architecture decisions are logged
Facebooktwitterredditlinkedinmail
© Scott S. Nelson