A little creative - calendar with antipatterns
Hello!
Fasting increased frivolity, for Friday.
I want to tell you about antipatterns that crystallized in our company. Just For Fun.
Every time the developers / installers / circuitry used a repeating email, it was fixed and listed. When the list grew and almost 12 excuses appeared in it, we had the idea to make our calendar with antipatterns (since excuses illustrate how not to think and do, we equate them to antipatterns). To do this, we had to master the layout of the calendar and for each anti-pattern "give birth" to the corresponding picture. Layout was done in LaTex, and the pictures - in inkscape, in svg-format. In general, it turned out quite open-source'no. But the post is still no longer about the technical implementation, but about the anti-patterns themselves. Who cares, welcome.
At first I will describe our anti-patterns, with pictures. All of them, for the most part, illustrate the misunderstandings between managers and performers. That is why I zapulnul post in the hub of project management. I think many will see something familiar.
')
I just want to say that the anti-patterns themselves and the pictures for them are just a joke, we did not try to offend anyone.
Go!
Number one: "The task had a low priority"
Otmaza arose when they began to actively implement scrum. It seemed that no task should be solved if it has a lower priority than those who took on the work for this sprint. Sometimes it was funny, because the low priority task was actually important and interfered with higher priority tasks. At the same time, the project owner was not informed, but at the end of the sprint it turned out like this:
Number two: "we had no tool!"
This is a favorite otmaza installers. Surprisingly, the presence of a blank check for the purchase of virtually any instrument did not solve the problem. The picture turned out cruel.
Number three: “they will say to do - we will do it!”
Here is a man sitting and waiting to be told that this should be done. Are you sure that this is obvious and you just need to start doing it. A bit intersects with the antipattern "there was no command to do it." But it always sounded in that form.
Number four: "we work . "
Terrible phrase, which had been heard from the head of the questions relating to the optimality and rationality of what is happening on his site. I had to write ...
Number five (my favorite anti-pattern ): "Everything is ready, but you need to remove it . "
Until now, often hear and even sometimes pronounce. When a bunch of brenches are made from a trunk, and from these bricks a working system is established. And it seems that everything is ready and at least immediately - in production, but no - you must first remove it. The comicity of the situation is that putting off is not always such a simple and quick process, followed by testing again, etc.
Number six: "We always did that."
We did it crookedly and we will do it crookedly, because we always did that. How long?
Number seven: "It is exactly what was asked for."
Some people like to turn off the brain at the time of performing some task. He is dedicated to this anti-pattern. And some others think that others think the same way they do. So it turns out ...
Number eight: "There was no command to do this"
We recorded it when we saw that our colleagues were ready to sit and waste time, waiting for the command. It seems to have outlived this. Now, when the tasks end, they themselves come up and talk about it (although I don’t remember something, that the tasks have ended recently). Well, or independently decide that this should be done.
Number nine: "This needs to be planned."
I think many have noticed that there are little things that are easier to do at once than to plan, because they are little things. And when we are told that these little things need to be planned (yeah, write in backlog, put priority, and go) - we write it down as an anti-pattern. We did not invent a picture for this anti-pattern. It turned out this:
Number ten: "It needs to be worked out."
Fresh anti-pattern. We noticed behind ourselves that we often say that “this must be done”. So we must take and do, and not talk. The picture turned out appropriate.
Number eleven: "I know nothing - there was no letter"
It is used when communicating in real life after a long corporate correspondence. It is very convenient - it is quite difficult to prove that the letter really was:
When the pictures were finished, they laid out a calendar in LaTex and released a small edition for distribution within the company and gifts.
The source code of the calendar is laid out in github . For a successful build, you will need the Tikz package, since the calendar itself (dates, numbers, etc.) is done with it. With a little effort from this calendar, you can do any other, you are welcome! In the same place, in the pdfs catalog there are collected versions - see README.
Great weekend to everyone!
PS: And what antipatterns are observed in your companies?
Fasting increased frivolity, for Friday.
I want to tell you about antipatterns that crystallized in our company. Just For Fun.
Every time the developers / installers / circuitry used a repeating email, it was fixed and listed. When the list grew and almost 12 excuses appeared in it, we had the idea to make our calendar with antipatterns (since excuses illustrate how not to think and do, we equate them to antipatterns). To do this, we had to master the layout of the calendar and for each anti-pattern "give birth" to the corresponding picture. Layout was done in LaTex, and the pictures - in inkscape, in svg-format. In general, it turned out quite open-source'no. But the post is still no longer about the technical implementation, but about the anti-patterns themselves. Who cares, welcome.
At first I will describe our anti-patterns, with pictures. All of them, for the most part, illustrate the misunderstandings between managers and performers. That is why I zapulnul post in the hub of project management. I think many will see something familiar.
')
I just want to say that the anti-patterns themselves and the pictures for them are just a joke, we did not try to offend anyone.
Go!
Number one: "The task had a low priority"
Otmaza arose when they began to actively implement scrum. It seemed that no task should be solved if it has a lower priority than those who took on the work for this sprint. Sometimes it was funny, because the low priority task was actually important and interfered with higher priority tasks. At the same time, the project owner was not informed, but at the end of the sprint it turned out like this:
Number two: "we had no tool!"
This is a favorite otmaza installers. Surprisingly, the presence of a blank check for the purchase of virtually any instrument did not solve the problem. The picture turned out cruel.
Number three: “they will say to do - we will do it!”
Here is a man sitting and waiting to be told that this should be done. Are you sure that this is obvious and you just need to start doing it. A bit intersects with the antipattern "there was no command to do it." But it always sounded in that form.
Number four: "we work . "
Terrible phrase, which had been heard from the head of the questions relating to the optimality and rationality of what is happening on his site. I had to write ...
Number five (my favorite anti-pattern ): "Everything is ready, but you need to remove it . "
Until now, often hear and even sometimes pronounce. When a bunch of brenches are made from a trunk, and from these bricks a working system is established. And it seems that everything is ready and at least immediately - in production, but no - you must first remove it. The comicity of the situation is that putting off is not always such a simple and quick process, followed by testing again, etc.
Number six: "We always did that."
We did it crookedly and we will do it crookedly, because we always did that. How long?
Number seven: "It is exactly what was asked for."
Some people like to turn off the brain at the time of performing some task. He is dedicated to this anti-pattern. And some others think that others think the same way they do. So it turns out ...
Number eight: "There was no command to do this"
We recorded it when we saw that our colleagues were ready to sit and waste time, waiting for the command. It seems to have outlived this. Now, when the tasks end, they themselves come up and talk about it (although I don’t remember something, that the tasks have ended recently). Well, or independently decide that this should be done.
Number nine: "This needs to be planned."
I think many have noticed that there are little things that are easier to do at once than to plan, because they are little things. And when we are told that these little things need to be planned (yeah, write in backlog, put priority, and go) - we write it down as an anti-pattern. We did not invent a picture for this anti-pattern. It turned out this:
Number ten: "It needs to be worked out."
Fresh anti-pattern. We noticed behind ourselves that we often say that “this must be done”. So we must take and do, and not talk. The picture turned out appropriate.
Number eleven: "I know nothing - there was no letter"
It is used when communicating in real life after a long corporate correspondence. It is very convenient - it is quite difficult to prove that the letter really was:
When the pictures were finished, they laid out a calendar in LaTex and released a small edition for distribution within the company and gifts.
The source code of the calendar is laid out in github . For a successful build, you will need the Tikz package, since the calendar itself (dates, numbers, etc.) is done with it. With a little effort from this calendar, you can do any other, you are welcome! In the same place, in the pdfs catalog there are collected versions - see README.
Great weekend to everyone!
PS: And what antipatterns are observed in your companies?
Source: https://habr.com/ru/post/234987/
All Articles