Tag Archive | agile

Zombag, facing a Zombie (software) apocalypse

I think there are many things to solve still in Agile. I am developing a framework (most of it for fun, I have to admit it) that is intended to help in the future with teamwork and other things. You can help me by providing feedback or joining the initiative. It is still in his first stage but I try to gather many ideas of what I have been learning in my life, experience working on software development and PhD.

Many aspects are about to come! Especially the ones of my PhD that are not included.

Hope you enjoy it at least! It is kind of a funny idea.

It is about zoooombiieees. Hohoho.

Zombag – Alpha Version

Help me out with constructive solutions, if possible!

I will update it with the time. I had a lot of fun with it!

Is adaptation a double-edged weapon?

We hear many people saying that adaptation is the key. In agile, adaptation is mandatory, and it seems everyone is comfortable with that. Recently, I wonder if this adaptation premise is harmless or not. I heard many people saying “well… we didn’t do this of Scrum (or other), because it was a necessary adaptation. Our business, A,B, C…”. Even they invented something called ScrumBut, that helps to realize and recall that you are doing some things out of the recommended way of Scrum. Adaptation is necessary, don’t get me wrong, since in this world everything is about that. Of course you need time to implement agile too. Nevertheless, the adaptation premise is an escape for many people who is not willing to fully implement an agile methodology. Many people just don’t have the experience or the, let’s call it vision, for modifying properly an agile methodology at certain point in the development (or even making prior-decisions). They may feel they are implementing agile, but they are implementing a partial agile. Partial agile, usually mixed with other approaches, seems to have way worse results than agile itself. De facto, not de jure. And it would be interesting to compare it with more traditional approaches.

People needs to be well-prepared, no matter how. To have experience in the field and theoretically in a balanced way. They don’t need experience so much as some companies sell or so much university formation as some universities sell too. They need good leaders or teachers wherever they go. I have seen 45 years old people, highly experienced and short headed (nothing against 45 years-old people of course, just an example. Also, the most intereting people are around 45 too hehehe). Same for university.

Whenever you make a change, this change should come as mandatory I would say. Imagine a team decides to avoid to have a customer integrated, since they have difficulties “A,B,C” (I have seen that!). Maybe everything seems easier and results come faster, or other “good” things may arise, but I am sure that it is not possible to measure other more difficult tricky things. What about the abstract-and-difficult-to-measure concept of quality, or implementing the correct thing, or delays due to useless implementations.

I think I read about a guru (I don’t recall who was, damn!) that asked to people -who were working as Scrum Masters or agile “managers” or whatever- “who is implementing agile in their company now?”. They rised their hands, and the guru was asking basic questions related with agile, quite important. He realized almost everyone was not using a real agile approach. I recently realized there is this double-edged effect with the premise of adaptation. If you teach and you explain what adaptation is, make always sure you explain the “psychological” drawbacks of the concept itself. Adaptation is not a blank check. Be careful.

Work to do

Recently, I talked to a friend who is an analyst in a renamed company. I was curious about the way the company works and the view my friend has about the company, the situation, etc. Two things especially captured my attention:

– My friend said that they have a manager figure, planning and so on, but apparently useless for my friend, doing nothing, or nothing significative. A few times he came and ask, “everything alright?”.

– They had to fulfill some sheets to control the productivity of the workers. If they don’t achieve some goals or minimum they are fired. Apparently that thing happened quite often.

I didn’t have much time to talk since we were with other friends that didn’t like much our topics. Nevertheless, with these two bullets you can guess there is still a lot of work to do in the way companies still work.

Results of the agile course

I finished yesterday the agile course I taught. It was a very funny and interesting experience for me. I present here the details of this course and the evaluations the student did:

Total number of hours: 4.5 h.

Number of days: 3 days.

Nationalities: French, Greek, Thailand, Saudi Arabia, Malaysia, Chinese and Japanese students.

Teams: 3

  • 3 french
  • 1 saudi arabia, 1 chinese, 2 japanese, 1 malaysian
  • 1 greek, 1 thailand, 1 chinese, 1 japanese

Participants: 12

Results of the questionnaire




Unfortunately I just had 3 classes to teach the course so some people couldn’t get all the details. A practical example is a good idea, but still, the time limit we had make that impossible. I hope in further courses I can solve this issues.

If you want me to teach the course, just let me know! I want to improve this course as much as possible!