Being able to challenge the PO's requirements.
I mean: not accepting every demands without any question.
Being able to understand the business needs and feeling comfortable enough to say no when a user story adds no value to the product.
I’m going to hop in and say the opposite is also valuable. Sometimes acceding to the needs of business, a particular customer, or another team is absolutely in everyone’s best interest, even if you can’t immediately figure out what the value is, or the value seems marginal. I know that when I was starting out, I would gripe about seemingly pointless work (and I still do, working on it 😃) where the reality was that costs had been weighed well before I heard about the decision. I think that the intuition to judge whether a given solution is necessary, and whether it is solving the problem being described, is the thing that comes with time.
Yes, you're right. And it also comes with better knowing your team.
This sounds great and all, but you have to play office politics sometimes unfortunately.
Hey Boris, was curious what PO stands for?
I'm guessing Product Owner.
Be bold enough to stand against the wrong things even if it's your boss. That's it. You are going to leave your mess for your future self or whoever is going to work on it in the future.
That's it. You must absolutely avoid having an over-configurable app, with features that may be never used because you will have to maintain all of this in the future.
We’re a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.