Where have you witnessed Scrum being used outside of the IT industry?
Where have you witnessed Scrum being used outside of the IT industry?
Scrum is an agile framework that, if applied properly, can boost the efficiency of teamwork. It is known to be versatile enough, so it could be applied in basically any sort of productive teamwork, even beyond IT (e.g. bakeries, government organizations, etc.)
However, I've never ever seen it being used anywhere else other than in software development, therefore I've always been curious if Scrum is actually being used outside of IT somewhere.
Any time I’ve heard of Scrum being implemented, it’s usually a negative thing. I’ve had a few friends where their workplace tries it, and the smart ones usually drop it. The others just lose people instead. Biggest complaint I’ve seen is the daily meetings that 110% could have been an email. I think it just doesn’t get applied “correctly”.
Why we don’t see it elsewhere is it’s not really applicable elsewhere in a lot of ways. I work in healthcare and I do not know how that would be implemented into my job. It’s not like we have team goals or projects even, we’re just out here scanning patient’s and processing their images. I’m sure management has goals but we're so short staffed that I don’t pay any attention to it. I’ve got more important things to worry about than patient satisfaction scores or how many open appointments we have.
Yeah management types hear "daily meetings" and don't realize that scrum meetings are meant to be less than 5 minutes.
"What did you do yesterday? What are you doing today? Do you have any blockers?" Done.
I was part of a project that was run on a 5 minute standup and it was wonderful. Everything after that has been bad to awful.
If folks are discussing implementation details during the meeting, it's awful.
We used to have the meeting first thing in the morning.
"What are you doing today?"
"No clue, you decided to have a meeting instead of letting me check my email and Jira responses."
"What are your blockers?"
"No clue, you decided to have a meeting instead of letting me check my email and Jira responses."
That format makes it into a round of status reports, especially if the manager is present. Better is: “What are you blocked on, who will help, or who’s time do you need today - confirm it now, right after this meeting is best!”
One of the former managers wanted me to implement agile programming, as it would be so much better, he had heard. I am the only programmer in my specialized field in the company...
I swear some of these managers don’t even have two brain cells to rub together
I’m in healthcare and education, and find morning huddles are very helpful. We run the patient list, identify who might need us to track some results down, and assign learners to patients they know or who appear to have presentations they should prioritize for their learning. Reception joins to see if any changes are needed to make sure patients have the right amount of time allocated, or if we have room for some squeeze ins. If there are any priority issues (patients we MUST see that day) that gets shared so no matter who gets the call, we are able to react appropriately. Whole thing takes well under 10min, and is hugely helpful.
Some genius added another huddle first thing in the afternoon schedule, which is rather useless, but since we never get to eat lunch, this leaves a bit of time before the chaos of the afternoon strikes to grab a bite or run to the bathroom.
See I work in imaging and it’s mostly pointless for us. Maybe if I did nursing I could see the benefits. We even have procedures but I can see all that information in Epic. I genuinely do see some benefits to it but I think it gets overdone with meetings etc.
It also doesn’t help that at huddle they talk about things that don’t relate to me really. I don’t care about hospital census or the three day metric they just started using for appointments. Most of it just doesn’t apply to me, and doesn’t help me to do my job. Like oh goodie there’s 30 people here with COVID, nice! That doesn’t help me at all with me 09:00 patient.
I do two scrum-style a week and go daily if we're busy. Team of 5, I set the time limit to 3 mins which means we're realistically done in 4-5. I'll also sometimes do sprint-style stuff for quick turnover projects with 2+. Usually this is a big chunk of analytics or report that needs to get done, so it's best to break apart the requirements and designate people that specialise at different parts onto each job. I also use digital boards for projects and larger tasks since there can be a lot going on at once. This helps me clear blockers and re-prioritise upcoming tasks or redesignate someone's capacity to assisting with other tasks if need.
My fav part is the team having everything cleared and all that's left is blockers I've already actioned for movement. If anyone asks why we're idle and doing a jigsaw puzzle or personal development, I can just show the board. The transparency is sweet justice for senior management which are often involved in the blocks.
I make sure to not go full agile because it's just not really compatable. I pluck the basic parts and the general concept and use what works and ignore what won't.
Because a project management framework does not work for operations jobs.
How does Susan and Emma in accounts express their work as a sprint? How does Steve or Sarah running a bakery express their work as a sprint?
How does Susan and Emma in accounts express their work as a sprint? How does Steve or Sarah running a bakery express their work as a sprint?
Probably much the same way anything non-trivial gets split into sprints in IT: Just fudge it to keep the PM from moaning too much while you try to actually get some work done in between all the fucking "rituals".
A proper project management framework should work for all types of projects, not just IT.
Steve or Sarah launching a new bread product can make use of the framework. Renovating the bakery can use the framework.
The point is that most of their job duties are operational, not part of a project.
I had the unpleasant experience of being in a group that applied SCRUM to research. Yes, the work involved software implementation, but research is largely antithetical to SCRUM. Yes, you need good research practices but a key aspect is that you don't know where you will end up. The stand up meetings became 30 minutes twice a week. Arrrg.
It’s a pretty common term on the rugby pitch.
Rugby.
oh how I would love to see scrum applied to cooking:
"chef, this customer wants their food ASAP! scrum it!"
chef laughs in everybody wants their food asap
Line cooking is essentially scrum. Each ticket is a story. They are added to the backlog as they come in and added to the sprint when you start cooking.
I've seen it turn into utter disasters in tendering large construction contracts on both sides of the fence. I'm usually only peripherally involved, but every time I hear someone runs them in a scrum, it just breaks down.
You can't place a bid with a few less features because you're out of time. You can't break down the process into stories you can close, because one detail can throw all your previous work away. You can't summarize highly specialised work in a stand-up because most people aren't event in the same field as you (listing blockers still works though).
I worked for a big commercial real estate company years ago. Think buying and selling whole apartment complexes. We adopted scrum in our IT department, then saw the sales support team start doing it. Each sale was treated like an epic and each task a story. Actually worked pretty well for them.
We had something like it in my previous job. Maritime electronics - outfitting ships with radars and navigation systems.
We had a very short meeting every morning to cover the status and the plan. Basically to sort out any blockers or if one project needed additional hands.
I have a friend whose team uses Scrum as an internal auditor at a utilities company. Their audits are treated as epics while specific deliverables or findings are stories. After a few weeks of growing pains, he likes it a couple of years after implementation.
Myself? I've had mostly bad experiences working in various IT and Dev roles both as a IC and team manager. Maybe it's because I've been trained on using it, but I still believe in the methodology and blame greedy implementations. I see management/customers count or haggle points, sizes, or hours and it's like staring down a speeding freight train.
The whole 9-5 realm is a joke. To give you an example, I noticed IT bois works on tickets like each email comms are tickets but same is not the case of any other department. If the same was across whole organization, people will be more productive and will be held accountable.
I've dealt with many IT managers, product owners etc and have noticed something that these guys are willing to bend over for smallest of things but with other departments managers, there will be a pushback.
In education there are self-directed learning centers that follow agile principles with some of the features of SCRUM.
I once heard of a sport called rugby
I like using a variation of it to keep track of my projects at home.
We just started using a kanban board with monthly "sprints". We have a backlog of things to choose from. Then we pick out a few that we know we can complete this month. Move them to in progress when we start working on them. Then move them to complete so we have something to "show for it".
I've done this before