A strange case in the management of a project. Which position to take? [closed]

Navigation
-2

The question is relative to project management, where was this the best (perhaps only) way of exposing my doubt to the situation. I agree that it was a bit extensive, but I did not find another way to focus it.

Come on:

The company is seeing a new project (it is a medium-sized system), and in meetings the following happened:

For this project two programmers and one analyst were assigned, where in this case the analyst has less experience than the two programmers (which would be me and another). In a given agenda, the technologies to be used and what would be the layers, architectures, etc ... of this system were being discussed. The analyst made some suggestions. The other programmer (this one with more experience than I) soon interfered with technical arguments showing that it would not be a good choice and in that the analyst did not accept, the meeting passed around the 40 min more than anticipated.

In new meetings the programmer brought documentation and explanations suggesting an architecture model and other points as well, such as GIT flow, etc ... that would be good and planned for the whole project (in this part I realized that they really were good suggestions ) and the analyst again reluctantly, where strangely without any technical argument got approval from the project manager who presented the new project. A week later this programmer received an oral warning (not formal, but in front of the team) about him being obstructing the project with his positions, etc ...

Today, after about four months, the system has an architecture proposed by the analyst with business rules somewhat on a designated layer in PHP, another little in AngularJS. The system was made using AngularJS. The angular itself has a part for routing, but even so there are some pages in PHP as the analyst found it "easier" to do.

In production a DBMS is being used and in the development another different DBMS (another choice of analyst). Each developer has a different version of the database modeling, where a .sql file is sent for the task, and none of them has full system access, much less database modeling, since everything is independent and focused only on the analyst. / p>

All technical decision-making today is focused only by this analyst and although errors have already appeared up to R $ 1,000.00 in commissions (parts of the system is already in use, because it is an internal system), and the focus of management continues to give all technical relevance to this. Just like all the more complex implementations, the kind that would be interesting reviews, team-building decisions, debates, etc. this does it all by itself. The other day, when he saw this programmer again correcting a mistake on a screen, the analyst simply kind of "threw in the face" saying that he was the analyst and that he made all the decisions that would be that way and that's it.

Given the context described above, and taking into consideration that the company pays financially (R $) in a reasonable way, I get the following points:

  • I need opinions, feedback, criticism, praise, suggestions, ways of thinking, etc ... in general on this context.

  • Is it worth investing in a career in a company that has such a development industry? (Today there are only three medium projects in the company, counting on this)

    • In my opinion, the situation is bizarre at best, but I would like opinions and experiences focusing on a position to be taken in the face of the situation. These two points I quote are important.

    OBS: It is certain that it is not 100% say according to the rules here, but being the lifetime of this limited doubt, the considerations are valid, or suddenly a " that someone with more experience read this question.

        
    asked by anonymous 14.07.2015 / 20:35

    1 answer

    6

    In my view, there are simple and complicated answers, because the thing is half subjective there. But, I'm going to try to be objective.

    1 - What you want in life, remains what you want independent of a particular project.

    It's the next one, whether you're into the project or not. Focus on what you want, if you want to continue, continue, if you do not want to start looking for another. This will involve if you are learning something, if you need the money and a lot of personal things, just look outside the project and think about what you want.

    2 - A tribe can not have 3 bosses.

    Boy, quite directly, if the decision-making power is of the Analyst, then the decision is the analyst's point. I'm not saying that you have to agree, I'm saying that in everything in life, a decision has to be made and in business, the roles are meant to be. What you can do is already done, show other points of view, but in the end the person who has the power of decision can simply decide not to do, this is not necessarily an affront or something bad, he has the responsibility and you can decide, you may disagree, but if you decide to stay on the project, you have to accept that your suggestions will not always be accepted and that it is part of a professional life to accept the decision of others. This is not true for ethical reasons, if you are asked to steal, it is still theft even if it is your boss or analyst. If the ethics is over, then look for a better place.

    3 - Your truth is not always the truth.

    Often, we are so focused on our vision of the problem that we forget to look at others' views with fondness and some people have a tendency to lose focus on what is important and end up focusing simply on winning the discussion. In my view, if you are still trying to convince the Analyst (who has already decided) about the architecture, or are doing it wrong or are wasting the time of the project discussing something that has already been decided, has 4 months of operation and will not lead to Nowhere is it because a refactoring of this size is very unlikely in a project that is in production at 4 months. So my advice is to rethink the positioning of you that may actually be messing up and not helping. This does not stop you from continuing to talk or suggesting other improvements, just change the focus, or change the approach. If you're so frustrated because you're never heard, you're still doing what you do?

    4 - The old case of numbers.

    Do you have any metrics to say whether what was adopted is good or bad? Does the system have bugs? security flaws? how many bugs are in the test? How many go to production? Instead, get sporadic emails about issues or amounts unduly paid because of bugs, set your software and operation process, and start tracking numbers. Crawl the features with the most problems and qualify which types of faults are causing the problems, with numbers it is easier to decide for definitive solutions and do not make a witch hunt, when you have such a report, take a solution before to be tested the place of raising the culprit. Everyone already knows who is to blame, even if it is yours or the analyst, it does not matter and it will not improve your life or the software.

    5 - Functional software is the primary measure of progress. That phrase is not mine and I myself often had to repeat it to myself so as not to strangle some client. I have a technical background and as such, I like to do well-made technical things, I do not like seemingly wrong ways. Accumulate technical debt and goes against what is in my veins. But, the world is not perfect, nor will your software be, and if you can not get it into production, you actually failed much more than if you did it differently than you think. What I mean is that the system is up and running, so you have to start balancing things between technical preciosity and customer satisfaction. So a much more important question after 4 months is: Is your customer satisfied with the software? If so, wonder, better it. If not, find out why otherwise, regardless of the architecture and all the brilliance that might be proposed, you will fail.

    If you use an agile software process, then read: link

    And put a little more of these values into your life.

        
    14.07.2015 / 21:10
    Reverse direction from horizontal to c3js Laravel - Popular a list with files in a directory