Sure, but that's why you have scrum masters, product managers, product owners, etc. who routinely check up on progress, beyond the daily and push the buck down on items suffering delays. So at one point, the non technical people will ask the senior technical people "why wasn't task X been delivered, according to planning it should have been done by now".
So they have a senior dev look at the requirements of the task to check maybe the estimations was wrong or the way it was formulated was bad, and also have a look at what that developer in questioned has checked into Git and start asking questions on why the slow process.
You can bullshit the non technical people, but you can't really bullshit your peers/seniors for too long before they realize your underperforming, when they start looking into your work.