Useful read for software engineers

The article could have had some more depth and details. But from the perspective of a CXO who is looking at a bird’s eye view of what is important, it does give a decent representation.

I especially like the part where scaling has been moved out of the core. Much waste has been generated past few years by everyone pushing some scaled framework training down to all levels, especially junior developers, when it’s not needed.

They would be far better off with a good understanding of Scrum, User Stories and Test-First approaches.

Source: 12 Agile Skills for Software Developers (

Read the full article from Gartner here:

12 Agile Skills for Software Developers (



Photo by Christina @ on Unsplash

Conversations and the right level of elaboration for whatever you are trying to build at that point of time is crucial.

Not to say the concept of user stories and the formats of writing them are not helpful. They definitely are.

However users stories and their formats are still “tools”, the interactions matter much more.



Photo by on Unsplash

1️⃣ #quietquitting is often visible. A good leader would always know when staff is #quietquitting . They may not do anything about it for many factors but they know. If leaders don’t know, then you have a much bigger problem.

2️⃣ #quietquitting isn’t new. The fact that it trends now just indicates probably a lot more people are doing it now than earlier.

3️⃣ While a lot of executives are worried about the #greatresignation and #attrition trends, probably they should be more worried about the employees who are #quietquitting. The path to a resignation often goes through #quietquitting, not to mention the loss in #productivity that most executives are so passionate about.