Watching "Silicon Valley"... discovering Scrum Methodology
Watching an Silicon Valley episode, it has been emphasized to the Scrum methodology, an iterative and incremental agile software development framework for managing product development. In the episode reference is made to this method to resolve the misunderstandings at work of two bizarre protagonists :)
But as computer science lover, for curiosity, I did a search on the web to better understand how it works. Youtube and Wikipedia helped me a lot. My goal was to share everything with the Steemit Community.
Wikipedia provides a good general explanation of the method:
"It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal", challenges assumptions of the "traditional, sequential approach" to product development, and enables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines involved"
And most importantly:
"A key principle of Scrum is the dual recognition that customers will change their minds about what they want or need (often called requirements volatility) and that there will be unpredictable challenges—for which a predictive or planned approach is not suited. As such, Scrum adopts an evidence-based empirical approach—accepting that the problem cannot be fully understood or defined up front, and instead focusing on how to maximize the team's ability to deliver quickly, to respond to emerging requirements, and to adapt to evolving technologies and changes in market conditions".
Reading on the web, this method has been adopted by many of the most important companies, such as Amazon, Google, Apple and Ferrari. Scrum optimizes resources and avoids waste time.
Do you have episodes in which this method also solved your work problems? :)
In my company we tried, but being a small startup even something like Scrum has proven being overkill. I believe it works flawlessly in mid-big sized companies where teams can focus on their job and nothing else. Thanks for sharing!
It looks more than a kanban process, than scrum, pretty similar indeed. No one methodology will work without developers motivated and compromised with the project. And if you have Motivation and compromise in your team, any methodology will work. You have to look a way to create this drivers in your team. If scrum will be a mean to achieve it. That could be ok.