Typically retrofitted on top of a defunct process, with separate requirement analysts, "software architects" whatever that means, and a lot of control functions and processes inherited from the manufacturing industry.
What makes that work is probably the few people that actually understands software development - typically a low percentage of the massive overhead in a typical business software development center.
But you've got to start somewhere.
The Agile ceremonies are not bad, but relatively useless if there is no "real Agile" beneath. Unfortunately, they are easy to implement whereas "real" agile is not.
And what is "real" agile: The core agile ideas (the manifesto), the focus on flow-control, the incremental analysis-build-analysis cycle, continuous improvement, multi-disciplined teams, knowledge sharing, analysis methods that involves multiple people (like story mapping), empowerment (self governing teams, but also product owners).
Perhaps above all, the idea that software development processes should not be defined by business administrators, but instead by people that are actually qualified.
I guess it could be labeled as "common sense", but a few things are typically hard to reason about for a lot of people, for instance the flow-control part (such as kanban), as dynamic efficiency is harder to "see" than static efficiency.
But getting good at that is actually hard. Adding 1000 fields and workflows to Jira is easy.
Many teams start out productive, but they also tend to degrade over time. How many 10 year old projects have you been happy to start working on? How about 20?
Those are the places most in need of someone to cut the bullshit.
You just described my last job...
Not every manager can understand every facet of the operation two levels down. Methodologies not only give them an understandable metric of what is going on, they also have something to point to when upper-upper management is considering a lower manager for a promotion or trying to figure out why things are taking too long or not working as expected.
Development methodologies have a place, that's for sure, but structure for structure's sake - in my experience - tends to exist primarily for the benefit of the managers, rather than the engineers.
And agile coach, at least as I know them, guides several teams in their use of agile, without being part of the team. They have to be experts at recognizing whether a team functions well, which aspects need improving, and handing the team the tools to improve. It's a bit more distant from a team than a scrum master is.
That's because even my Software Engineering textbook first published in the early 80's warned about it, and presented iterative, agile-like, models and referenced the article by Royce that first described waterfall (without naming it) as an example of a broken model in the early 70's... Iterative processes have been widely taught since the late 70's at least.
That ridiculous expectation is probably a symptom of some pretty dysfunctional management in general.
For someone involved in non-technical delivery, I would expect they had experience delivering agile projects.
(Of course, agile projects typically call them product owners instead, a subtle distinction.)
I've been involved with agile projects since 2006 and I am still learning new ways of delivering software that solves the right problem, developing team cohesion, surfacing risk early, and other things you don't learn in the 3 day class.
I can teach Scrum in 30 minutes, but there should be an actual expert around until enough of the group has internalized the reasons for the concepts and feel like they can adjust it to suit their situation without fear of dogma. (This expert, however, won't usually cost $200,000 unless they signed the manifesto themselves or are otherwise agile-famous.)
(Here's the 30 seconds if you don't have anyone around. Start with trying to group the next most important thing to do in a 2 week chunk. Every day, talk with each other and make sure to surface any problems and risks as fast as possible. Have at least one person who will use the software sitting with the team to answer questions as they pop up. And every week, take an hour to figure out what's working well, what isn't, and what you need to adjust to make things work more smoothly. There are dozens of technical and organizational practices to go through and try, but the best is to keep the ones that work for you, ditch the ones that don't.
Standups and Demos are just 2 of those organizational processes. Use them if they work, ditch them if they don't. For example, I'm currently working with expert practitioners and we're not doing a standup because we're small enough, work close enough together, and have worked with each other long enough to just talk.
Pretty darn good summary.
SCRUM Master role is the closest to a Project Manager.
The product owner, however, controls the backlog, and the yes/no in what defines the product is most often the most important (and difficult) position of the PM.
That's different from the Project Manager who works on resourcing and timing of a project.
For example I remember receiving calls from recruiters looking for devs with 5+ years of .NET experience when .NET was less than 5 months old.
Came to post this
> (Spanish dev here --working abroad obviously--.)
Same here ;)
It is not competitive at all compared to the US of other european countries. That along with the "special" office politics and extreme inefficiency that plague Spanish companies, makes it extremely uninviting to come back to Spain.
The one thing that does not fly is developers that does not know the business case, or worse, those that don't care and acts like the company's purpose is to give them new toys (frameworks) to play with. But grokking a business case is marginally harder than resolving a merge-conflict so most people are actually presentable in a steering committee meeting.
Anyway; 200.000 € is probably not a developer, but possibly someone with a development background.
Unfortunately only a few people can sell things to the (non-tech) management - that is typically harder for us square-headed developers, as you have to be able to skimp some details in order to convey the big idea. But selling ideas is a unique skill anyway.
This is hilarious. Say that to Amancio Ortega :-)
> But such people are thin on the ground in Spain. It takes at least eight months for an experienced software developer to earn an Agile qualification and they also need the ability to deal with senior executives, limiting the pool of people who could potentially fill the roles.
That part of the article is hilarious, not only because 200K euros is completely made up and untrue (by far surpasses best salaries in other more decent countries), but because of the Agile qualification mention. Do we have Agile certifications now? What a load of bullshit.
The only truth in the article is this:
> Spanish executives are less-skilled than their competitors in Germany, France or Italy, according to a study of 11 European countries. Only Greece came out worse.
And that's the reason why the executives don't find workforce. Being less-skilled means they don't value the engineering profession up to the required level to compromise and give good salaries.
(Spanish dev here --working abroad obviously--.)