Measure without putting burden on your team

Imagine a software engineering world in which you measure the value your teams deliver with almost ZERO burden on your teams in terms of spending time to enter information correctly !

If the teams are worried and constantly thinking about being measured, then we are not doing it properly.

It is very possible to measure without putting a burden on your team.

This is where I stand for the first item in the agile manifesto that states: “Individuals and interactions OVER processes and tools”.

For me the number #1 thing is to have the team reach that point at which you look at each other and you know you have the momentum, quality and product value and it’s fun doing it. Then the number #1 thing is to ride this momentum wave as long as you can with fine-tuning adjustments from sprint to sprint and stop any influences where the first item of the agile manifesto would be jeopardized.

Yes, I know that a lot of companies are regulated and you need the processes for auditing purposes, separation of responsibilities, repeatability; however, you still need to watch out for that first item in the manifesto.

Thank you for reading this short article.

Almir Mustafic.

Comments

Teaching kids the importance of information security — A simple fun example with encoding/decoding

Teaching kids about information security is very important today because the social network websites and applications are blurring the line between what should be shared securely and what not. Everybody is busy over-sharing the good, bad and ugly over the internet and in the process of doing that forgetting the basics of information security or never taking the time to learn it. Or is it that nobody is introducing these concepts in school? It is something that needs to be introduced in our education systems from early days. Do you remember the days when we used to send those short messages on a piece of paper in our classrooms? Some encoded those messages because you did not want another person in the middle to open it and understand what it says. How were those messages encoded? The simplest example is: You create a simple mapping for each letter and number in the alphabet. Then you encode your message and write it on a piece of paper. Then the person on the other end decodes...

Daylight saving time and A Software Engineering state of mind ?

You may be wondering what the Daylight saving time has to do with a software engineering state of mind. When thinking about writing this article, at first I thought to start with the following joke and I am: “ Did you know that the Daylight saving time was started because a software developer coded a function that does smart timezone and configurable calculations and then this developer created a problem to solve to use the algorithm; hence, the Daylight saving time was born. ” This is a joke, but on a more serious note , this brings me to a state of mind in software engineering that make this joke a reality to some degree. How many times did we find ourselves in situations where we learned something new in programming and we looked for ways to apply it at any cost? How many times did we see a cool new feature from a creator of a framework and we decided to use it even though that was not the right solution for the problem or maybe there was no problem to solve in the ...

Authenticity (some quick thoughts)

Authenticity - Step back and think about what makes projects successful; it is not all metrics looking good; it is about intangibles that you can't measure. It is the authenticity of certain individuals, their approaches, and how they let their energy radiate within the team. Recognizing their authenticity is the key to success. Almir Mustafic

Software Engineering Blogger

Search This Blog