Scrum may be most widely associated with software development, but there’s no reason it can’t be utilized across any industry.
As Alex Brown, Chief Operating Officer and Chief Product Owner at Scrum Inc. explains in this short video, nothing about Scrum is unique to software. While it was first widely adopted in the creative team environment of software development, adapting Scrum to other environments is easy and effective.
According to Brown, there are three things to consider when adapting Scrum to your own unique environment:
- What’s the right sprint length to use? Most software companies choose somewhere between 1-2 weeks for their sprints, because it’s generally easy to create a meaningful increment in the product in that amount of time. That may not be the case if you’re working in hardware, for example, in which case you might need to work with longer sprints. That said, you don’t want to incorporate so much time that you lose your sense of urgency, Brown warns.
- What is the product? In software, it’s relatively straight-forward, but in other environments and industries “product” may need to be defined.
- What team functions are necessary to complete a sprint? In software, the roles are typically developers, testers, etc. In other environments, roles and the relationships between them may be more complex. A challenge can be getting all the people necessary to accomplishing a meaningful increment onto one team that can utilize Scrum effectively.