...
Indeed. Especially the first. Although I'd be happy to discuss the silliness of applying Agile to EE anytime.
Here in an example of an incident that has now occurred a couple times.
First, consider the lessons learned from "The Mythical Man-Month" by Brooks. [1][2]
Now, apply the core lessons to a project under Jira control. With the Jira concept of frenetic "tasks", the long and complex arcs of development get chopped into slices that are exceedingly tempting for management to distribute out to other engineers. This is effectively in direct violation of the key lessons from Brooks.
In this case my part of the project appeared to be late [3], so another engineer was re-tasked to "help" by taking on part of my collection of tasks and responsibilities. After that sprint we returned to our regular tasks.
Now I have even more to do as I unwind the knots and errors he introduced into my work, while his work is delayed by a sprint cycle.
[1]
https://en.wikipedia.org/wiki/The_Mythical_Man-Month[2] I can't refer to my copy right now. Seven months ago I lent it to a marketing manager, and I've yet to get it back.
[3] That wasn't actually the case. However, according to the Jira backlog, it was.