by Admin
Posted on 12-01-2023 10:16 AM
This article explores the adoption of agile methods for the management of projects in collaborative research initiatives. The use of the scrum framework, a specific set of agile principles and practices for self-organizing cross-functional teams in software development projects, is currently being expanded to other types of organizations and knowledge management processes. The study addresses the extent to which key principles and tools usually used in scrum, due to their potentially positive influence on team dynamics and efficiency, can contribute to the collaborative management and coordination of tasks in research processes. The responses from interviews with 17 researchers, as well as participant observation and analysis of online activity, are examined and presented as a case study on the adoption of scrum practices in a distributed research centre dedicated to the evaluation of public policies.
If you are just getting started, think of scrum as a way to get work done as a team in small pieces at a time, with continuous experimentation and feedback loops along the way to learn and improve as you go. Scrum helps people and teams deliver value incrementally in a collaborative way. As an agile framework, scrum provides just enough structure for people and teams to integrate into how they work, while adding the right practices to optimize for their specific needs. You may be thinking, that sounds great! but, how do i get started? it starts with understanding the scrum framework which is defined in the scrum guide and was first introduced to the world in 1995 as a better way of team collaboration for solving complex problems.
Another important event was the publication of “the new new product development game” by hirotaka takeuchi and ikujiro nonaka in the harvard business review in 1986. Both of them had examined six product development projects and thereby worked out the superiority of what they called the “rugby approach” over the traditional waterfall approach. There, the term: “moving the scrum downfield” was coined for the first time. The results of this study ultimately served as the basis for the framework presented by jeff sutherland and ken schwaber at the oopsla conference in 1995, which they had developed together in the years before.
Over last scrum courses i started explaining scrum as having several layers: scrum values – what is important for us? scrum principles – why we do what we do? scrum framework – what and how we do it? good practices – what are ideas we should try? bad practices – what are ideas we should avoid? core scrum consists of layers 1-3. The remaining two layers are practices different teams and organizations tried with different results, so these are either things you could try, or avoid yourself. Just to give you few examples, daily scrum will be part of scrum framework. Task board and burn down charts are good practices and most electronic ‘scrum tools’ are usually bad practices.
The scrum master is essentially a leadership role. Most job descriptions in this category will look for someone who can align their software development practices with agile principles and the scrum framework, coordinating between the product owner and developers. This involves the following roles and responsibilities: roles of a scrum master.
Popularized by elon musk, utilizing first principles thinking to solve problems in an innovative, creative, and less biased way has proven popular in the tech community. Given that its sibling empiricism is an integral part of scrum as a framework, applying scrum first principles thinking is also a useful exercise. Learn more about how to elon musk the scrum guide.