This little experiment of mine called agile monocle gathered about 40 subscribers along the way: to all of you, especially those of you who subscribed after “Season 1” was over…thank you! Season 2 is in the working and I will probably publish it between February and March.
In the meantime, I’m translating some of the previous episodes in Italian on my website, for the moment you can find:
S01E01 - Have you ever seen a small, autonomous, stable, cross-functional team? → Hai mai visto un team piccolo, autonomo, stabile e cross-funzionale?
S01E02 - Have you ever seen just about enough meetings? → Hai mai fatto il giusto numero di riunioni?
S01E04 - Is data science not agile enough? → La data science non è abbastanza agile?
If there are some topics in particular you’d like me to cover in Season 2, just reply to this email or comment here below.
Since I gave myself a strict time-box and cadence in order to produce a seven episodes season in seven weeks, there is a lot that I didn’t cover during season 1 and a lot of articles that I kept reading after the season was over.
From 1 to 7, these are a few additional perspectives on the topics of Season 1.
Episode 1 was about teams. Some thoughts about calling a “team” something that it’s not a team. To put it bluntly: if the people in your team are not dedicated, you are not managing a team of 10 people, you are managing 10 projects (at least).
At some point you have to decide if not-dedicated teams are a bug or feature in your organization, and act accordingly.
Episode 2 was about meetings. Ah, the daily stand-up, the crown jewel of agile meeting…or not? Some ideas about the most common dysfunctions of the daily standup meeting, and how to defuse them. And since I tend not to speak about tools, let’s speak about tools and think deeply why Zoom is not the problem, but our meeting-centric workflow is.
Episode 3 was about metrics. I talked about metrics at a high level, so I might add some interesting perspective about two of the most common agile metrics you are probably struggling with. So, let’s think about how to tell your boss that story points are a terrible metric if you are a Scrum person, but also, if you are using a Lean/Kanban approach, what if Little’s law could only be a guideline and not a real law?
4. Data science
Episode 4 was about data science. 2021 will be partly devote to continue my research in the area of data-related topics in the realm of “agile”, whether they might be at team level or organizational level. In the meantime I need to catch-up on the technological advancement of the field and this article has been quite helpful.
Episode 5 was about requirements. Well, I didn’t read anything exciting nor interesting regarding requirements, user stories or documentation in the past two months, so I don’t have further readings about to share.
Episode 6 was about planning. Sometimes going back to the basics even further it’s what is needed. I love articles like this one, where the difference between sequencing and prioritizing is so clearly explained. Also, look out for the difference between efficacy, efficiency and effectiveness. From better wording comes better understanding, and from better understanding comes a better planning.
Episode 7 was about experiments. Inspiring workflow on how to write a data-driven story. It sort of falls in between both the topic of experiments and data, a valuable lesson even if your job is not writing data-driven articles. Continue, pivot or put it down?