SCRUM framework

Revision as of 18:36, 19 February 2021

Developed by Sana Ilyas

Scrum is an Agile framework that helps organizations, teams and people to generate value through adaptive solutions for complex problems ^[1]. The word Scrum originates from rugby to describe a formation of players in a complex game and were first introduced in the context of product development by Hirotaka Takeuchi and Ikujiro Nonaka in 1986 to increase speed and flexibility by implementing a cross functional team working in overlapping phases ^[2].

Taking inspiration from this formation, Scrum framework is founded on empiricism, proclaiming that knowledge is derived from experience and decision making based on the observed, and lean thinking which is designed to reduce waste and focus on the essential ^[1]. Together with the Agile manifesto for software development <refname=Manifesto> http://agilemanifesto.org/ </ref> , Scrum framework encourages iterative and incremental practices to deliver working software in dynamic environments. Unlike traditional Waterfall mythology, Scrum encourages not to have a defined scope but iteratively decide scope as the project progresses and to actively work in cross functional teams while regularly integrating end-users in order to constantly validate and prioritize outputs of the processes. Comparing the two methodologies using the Iron triangle, Waterfall have a fixed Scope and quality to be delivered while Scrum have a fixed time for when the project should finish along with fixed cost in terms of resources allocated^{[3] [1]}

In order to understand and implement Scrum, the team must understand the 3 pillars and 5 values that serves as a roadmap for of Scrum:

3 pillars of Scrum^[4]:

• Transparency is an important pillar of the Scrum setup where the outcome and process are visible and clear to stakeholders involved in the project in order for them deliver what is agreed and to give feedback and approve the outcome.
• Inspection is done frequently to avoid undesirable variances in the process and deliverable thus meeting the fixed release date.
• Adaption refers to the ability to adjust to change in processes, scope or any relevant change discovered during inspection. By adjusting to change as soon as possible, the team minimize further deviation going forward .

5 Values of Scrum

• Commitment
• Focus
• Openeness
• Respect
• Courage

Before implementing the Scrum framework, hte team must consider the following pre-requisites to ensure an successful implementation and application:

• Scrum require an Agile mindset where flexibility, honesty and communication are at the center. Accepting the Agile manifesto means the lack of a detailed workplans, timelines and scope which can be a big change of mindset and the way a team works^[5].
• The project team must be committet to the values of Scrum
• Scrum does not in particular tell you how to prioritize, estimate or plan. Figuring out how many hours each tasks requires includoing team velocity (number of stories or tasks the team can handle in 1 sprint) is to be determined by the team^[4].

Scrum overview

What does Scrum look like

Scrum is a framework consisting of 6 artifacts, 5 roles and 4 activities.

Sprint: In a Scrum setup, the project is divided into short iterative cycles called Sprints that can vary in duration from weeks to months. Here, the focus lies on development of features in the Sprint Backlog to reach the Sprint goal. The output of the Sprint is partial product deliverables/features called increments that together form a possible shipable product. Although not all product features must be incorporated at the end of the sprint, it should be sufficient enough to be released as a functioning product^[3]. A sprint can result in 1 or more increments, depending on the size and complexity of the Sprint backlog and team velocity.

Roles

Recipe for Scrum application

Limitations and challenges

^[6]

^{[1] [2] [3] [4] [5]}