Trying to understand Scrum outside of a development context – and what it means to the non-technically-oriented crowd – often becomes unnecessarily difficult, according to tech blogger James Conway.
Developers are used to thinking in an extremely abstract way. They take a complicated problem and simplify it to a point where it is simple enough to describe in a list of instructions sent to a computer processor. This mindset is very useful for software developers and not everyone can think like this. This is why not everyone is a software developer.
When it comes to dissecting the advantages and disadvantages of scrum, Conway also addresses the monetary cost of planning sprints, standup meetings, reviews and how they take away from actual development time. He acknowledges that some amount of planning and review is ultimately worth the time, but from a strictly business point of view the downtime doesn't look good on paper.
Additionally, there is a clear divide between client-facing team members and behind-the-scenes team members; scrum capitalizes on this to the detriment of the team's long-term health sometimes.