SCRUM for Dummies Email domenico Francesco de angeliscern

SCRUM for Dummies Email: domenico. Francesco. de. angelis@cern. ch Supervisor : M. Pezzetti Unit: TE-CRG-CE 09/04/2019

SCRUM “Scrum itself is a simple framework for effective team collaboration on complex products. Scrum is not a process, technique, or definitive method. Rather, it is a framework within which you can employ various processes and techniques. Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment. ”

SCRUM is Agile Methodology and based on iterative and incremental model of development. Difference between iterative and incremental development Iterative and incremental

The Scrum Values Before the manufacturing and how to design, we have the values. COURAGE FOCUS OPENESS COMMITMENT RESPECT

Empirical process control theory Three pillars uphold every implementation of empirical process control Inspection Transparency Adaptation

SCRUM TEAM • Product Owner is who knows what the customer wants and the relative business value of those wants. • Scrum Master help to keep the team accountable to their commitments to the business and also remove any roadblocks that might impede the team’s productivity. • Development Team are structured and empowered by the organization to organize and manage their own work.

Scrum’s Event Now we can see the Scrum’s core: The Event

First of all, Envisioning Vision Exploration of requirement in order to understand the problem and build the solution’s vision. It shouldn't last too long. (max 2 week) Product Backlog Envisioning’s result. Contain a list of everything that is known to be needed in the product. A Product Backlog is never complete The Product Owner is responsible for the Product Backlog

SPRINT 20 -90 times Sprint Planning Daily Scrum In order to decide the Sprint Goal and How will the work needed to deliver the Increment be achieved. The Development Team plans work for the next 24 hours. Time-Boxed: 2 -3 hours Time-Boxed: 15 -30 minutes Team work Time-Boxed: 1 day Sprint Review Sprint Retrospective At the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. This is an opportunity to inspect itself and create a plan for improvements during the next Sprint. Time-Boxed: 15 -30 minutes

Event on Scrum Team

Artifacts Product The most important artifacts of SCRUM is 3 Product Backlog Sprint Backlog • List of user story with priority • Is subset of product backlog, chooses in Sprint Planning Incremental Product • The Product increment is a piece of working software that creates transparency to all the stakeholders.

Definition of DONE This is the definition of “Done” for the Scrum Team and is used to assess when work is complete on the product Increment, to ensure the transparency. The same definition guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning. The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current definition of “Done. ”

Common Tools for SCRUM • Configuration Managment • Versioning Control System (GIT, Mavent) • Release Managment

Commons Errors… • We underestimate the complexity of software development • We do more trust in the tool of management • Fall into the Waterfall • Scrum Master Not Present • Definition of “Done” Imposed • Directive Scrum Master • Urgent Interruptions • Product Owner Specifies Solutions

SCRUM is beautiful, but is the real story? In real situation more company adapt SCRUM to their models. Practical example. In Industries, SCRUM is not directly recommended, they shall adapt their model with SCRUM.