Member-only story
The secret sauce to agile success? Adding software architects and content strategists to your design squads.
Agile is an awesome concept. Moving fast, constant communication to avoid hiccups, sitting in pods, the thought is great. So why is it failing for so many orgs?
The first issue is that orgs call themselves agile that are DEF not agile at all. Relabeling your waterfall process and switching up where people sit does not an agile team make.
So where are the rest of the main fail points?
At the company where I worked previously, we started out going full scrum. We had a scrum master, passed a ball around in the morning (which gave me massive anxiety since I’m basically the clumsiest person in the universe—catching a ball pre-3rd cup of coffee was a nightmare), tracked the daylights out of every task, wall papered with post its, we were in the zone.
The methodology worked for us for several months, until we split out into a mobile team and a desktop team. Suddenly scrum became a trial and tribulation. We were spending more time tracking tasks than we were actually completing them. The 15 minute meetings in the morning were dreaded, we started spiraling into a state of constant frustration. Our poor scrum master was getting the evil eye on the daily and the tracking software became the enemy…
