Question: I am a software developer for the last 5 years. I like this work and since I started this career I have been in 3 companies. Each change resulted a good raise of the salary and more interesting projects.
The last months I am feeling that I am getting more and more pushed to the ropes. The tasks that I have to do seem to get more difficult for me but my co-workers seem to struggle as much as they always struggled.

The last two weeks I actually didn't manage to finish what I was supposed to finish (although I was affected and driven backwards by the work that other developers had to do).
I was expecting to get told off for my performance but nothing happened. The meeting went smoothly and I am just expected to make a pull request for my code (I am starting another project and that was decided before the time period I am speaking about).

I don't know if they were expecting me to crash and burn and I didn't and that's why people were happy. I dont know if they are just polite.
I know that openness is a thing where I work and they would tell me something and also developers are hard to find where I live so they would not risk making me want to go for two bad weeks.

So I want to ask, assuming the management identified my bad performance (I am sure they did), why would they not tell me anything about it?

P.S. I have already spoken to a colleague today to have some guidance and work with him to improve myself, but I am sure he didn't have the time to tell to anyone yet.

Answer: 
There are a lot of reasons they might not have said anything. As a leader, here are some reasons I might not:

1. They might have known it was going to be a miss so they weren't surprised. Surprise misses are when my attention gets snagged.
2. If this is a super rare occasion, they might view this as a one off. No one can hit every deadline every time. If it becomes a pattern, it will be time to speak up. They may be allowing you to course correct.
3. It might not be classified as "bad" performance. While to you it may seem poor, it's possible your standards for performance are higher for yourself than theirs.
4. Times are tough right now. Everyone is going through a lot of things both personally and professionally. When someone misses, it doesn't help to pile on unnecessarily.
5. They may be afraid you might leave if your past performance is as good as you hint. It doesn't help to make a big deal of every performance miss. It only adds stress to people.
6. It's just possible they have no idea that you missed because other people around you have missed so much it has become kind of "normal". (really hope this isn't the case)
7. They just might not care.

There will be plenty of other possible reasons. These are the reasons I would apply for myself if I wasn't going to mention a miss. Numbers 1-4 are the primaries for why I don't speak up for when it happens. 5-7 will never be on my personal radar, though I have known leaders for whom it has been true.
> 
> The last two weeks I actually didn't manage to finish what I was supposed to finish **(although I was affected and driven backwards by the work that other developers had to do)**
> 
> 
> 

Two things immediately jump out to me here:

1. Failing to finish a 2-week sprint is not all that unusual, in my experience. It's not ideal, but it happens from time to time.
2. You didn't fail to perform. You were **blocked** by someone else's work.

When this sort of thing happens, in general, the expectation is that you go to your boss (or PM, Scrum master, or whoever is tracking your work) and tell them that you're blocked, what's blocking you, and (if they ask) any other relevant information. Then, you say one of two things:

* "Hey boss, since my work on X is blocked, I'm going to start working on Y instead."
* "Hey boss, my work on X is blocked, and I don't have any other tasks assigned. What would you like me to work on instead?"

After that meeting, you'll either start working on Y, or your boss will assign you something else to work on. Either way, you're no longer blocked, and you're off the hook for X (at least until it gets unblocked).

A couple of additional notes:

* It's somewhat culture-dependent, but in general, you want to avoid making it sound like you're blaming the other developer for your blockage. Focus on the facts, try to stay dispassionate, and (where possible) refer to tickets or bugs rather than people or teams.
* If your bug tracker can keep track of which bugs are blocking other bugs, use this functionality religiously. It makes the PM's job a lot easier when they're trying to figure out why no one has made any progress on X, Y, and Z in the past month.
* If you are struggling to make progress on something, for any reason, it's almost always a good idea to let your boss know as early as possible. They may be able to get you more resources or other help, and even if they can't, they will appreciate the advance notice.
	+ Of course, there's a balance. It wouldn't make sense to inform your boss every time you get stuck on some minor issue for five minutes. Use common sense.