> Thing is, working with a developer as a non-technical team member can be a frustrating, opaque experience.
And vice-versa. Imagine knowing something very well, something quite complicated. Then not only knowing how to fix that issue, but explain it to a child. Now, constantly having to handhold that child over every step, even when they don't even need to know, and it is slowing you down having to do that. And maybe not even knowing the solution, but trying different things, and having to explain each to that child.
What you have setup sounds awful. Learn the technical side, or let them get on with the job. The updates you need should be at a daily standup.
> then obviously the non-technical members have no idea what's going on.
You still don't know what is going on, you just pretend you do.
> Developers can forget too, that the one small change might be holding up marketing, sales and customer support
And vice-versa. Imagine knowing something very well, something quite complicated. Then not only knowing how to fix that issue, but explain it to a child. Now, constantly having to handhold that child over every step, even when they don't even need to know, and it is slowing you down having to do that. And maybe not even knowing the solution, but trying different things, and having to explain each to that child.
What you have setup sounds awful. Learn the technical side, or let them get on with the job. The updates you need should be at a daily standup.
> then obviously the non-technical members have no idea what's going on.
You still don't know what is going on, you just pretend you do.
> Developers can forget too, that the one small change might be holding up marketing, sales and customer support
Then make this clear during standup.