Agile Aeroplanes GM Digital Day January 2020 1

Agile Aeroplanes GM Digital Day January 2020 1

Today’s Agenda Understand the basic concept of Agile delivery including; applications, core values, principles and key methodologies. Using the Scrum methodology in a team game to bring Agile delivery to life. 2

Agile Overview • Agile Introduction • Applications of Agile • Agile Manifesto; • Overview • Core values • Principles • Key Agile methodologies 3

Intro to Agile • Agile methodology is a type of project management process, mainly used for software development, where demands and solutions evolve through the collaborative effort of self-organising and cross-functional teams and their customers. • Stemming from the values and principles of the Agile Manifesto, it was created as a response to the inadequacies of traditional development methods such as the Waterfall method. • The software industry is a highly competitive market because software is something that can be continuously upgraded. This means that developers need to constantly improve and innovate their products to keep on top of the game — and the linear, sequential approach of the Waterfall method just wasn’t cutting it. 4

Applications of Agile 5

Intelligence is the ability to adapt to change. Stephen Hawking 6

The Agile Manifesto is a statement of core values and principles for software development. The Agile Manifesto for software development was set up in 2001 and it is a declaration of 4 vital rules and 12 principles that serve as a guide for people in agile software development. It was created by 17 professionals who already practiced agile methods. 7

Four core values of Agile 01 Individuals and interactions over processes and tools It’s crucial to value people more highly than processes or tools. It is the people who respond to business needs and drive the development process. When the development is driven by the process or tools, then the team is less responsive to changes and less likely to meet customer needs. 02 Working software over comprehensive documentation Documentation has its place and can be a great resource or reference for users and co-workers alike. The main goal of software development, however, is to develop software that offers business benefits rather than extensive documentation. 03 Customer collaboration over contract negotiation Development teams must work closely and communicate with their customers frequently. By listening to and getting feedback, teams will understand what all stakeholders really want. 04 Implementation Changes are a reality in Software development, a reality that your Software process should reflect. A project plan must be flexible enough to change, as the situation demands. 8

12 Principles of Agile Twelve Principles of Agile CUSTOMER SATISFACTION TRUST & EMPOWER GOOD DESIGN Provide customer satisfaction by early and continuous delivery of valuable products Build projects around motivated individuals, give them the environment and support they need, and trust them to get the job done Continuous attention to technical excellence and good design enhances agility REQUIREMENTS CHANGE FACE TO FACE IS THE BEST SIMPLICITY Welcome changing requirements, even late in development Face-to-face conversations are the most efficient and effective way to communicate The art of maximizing the amount of work not done is essential DELIVER WORKING SOFTWARE FREQUENTLY WORKING FEATURES SELF-ORGANIZING Working features are the principal measure of progress Best architectures, requirements, and designs emerge from self-organizing teams BUSINESS & IT COLLABORATION SUSTAINABLE CONTINUOUS IMPROVEMENT Close, daily cooperation between business people and IT/developers Sustainable development, able to maintain a constant pace At regular intervals, the team reflects on how to become more effective and adjusts Working features are delivered frequently in weeks, rather than months 9

Agile Methodologies Agile is an umbrella term for several methods and practices. Some of the popular methodologies are: • Scrum • Extreme Programming (XP) • Adaptive Software Development (ASD) • Dynamic Software Development Method (DSDM) • Feature Driven Development (FDD) • Kanban • Behavior Driven Development (BDD) 10

https: //www. digite. com/agile-methodology/ 11

Paper Plane Activity The purpose of this activity is to demonstrate the power of time-box or Sprint that makes the heartbeat of an agile framework like Scrum. 12

Instructions • Teams of 5 -6 members • 50 sheets of A 6 for each team • Only one sheet of paper can be used for each airplane • You cannot screw the paper up into a ball and throw it • There will be three sprints (6 minutes each) • A team member can perform only one-fold at a time, they then need to pass it to another team member • The team with most correct airplanes wins! 13

Definition of done …or ‘Correct’ The paper airplane is … 1. Built and tested as agreed 2. Able to fly 3. Accepted by the product owner 14

The Sprint Each 6 -minute sprint will be broken down into the following ceremonies: • Sprint planning (1 minute): estimation • Sprint work (3 minutes): fold lots of airplanes • Sprint review (1 minute) prove business value • Sprint retrospective (1 minute): improvement 15

The score board This is how we will keep track of business value delivered by each team. Estimate Actual Sprint 1 Sprint 2 Sprint 3 Total Each team will provide their estimate after sprint planning, the actual will be verified by the product owner during the sprint review. 16

Sprint 1 Goal Build as many airplanes as you can! Acceptance Criteria 1. The plan must fly 3 metres 2. The plane should have the team logo on both sides 3. The plane should have the team name on it 17

Ready to go? Sprint 1 • Sprint planning (1 minute): estimation • Sprint work (3 minutes): fold lots of airplanes • Sprint review (1 minute) prove business value • Sprint retrospective (1 minute): improvement 18

Sprint 2 Goal Build as many airplanes as you can! Acceptance Criteria 1. The plan must fly 4 metres 2. The plane should have the team logo on both sides 3. The should have the team name on it 4. Pattern should be on the top of the wings 19

Ready to go? Sprint 2 • Sprint planning (1 minute): estimation • Sprint work (3 minutes): fold lots of airplanes • Sprint review (1 minute): prove business value • Sprint retrospective (1 minute): improvement 20

Sprint 3 Goal Build as many airplanes as you can! Acceptance Criteria 1. The plan must fly 4 metres 2. The plane should have the team logo on both sides 3. The should have the team name on it 4. Pattern should be on the top of the wings 21

Definition of done UPDATED! …or ‘Correct’ The paper airplane is … 1. Built and tested as agreed 2. Able to fly 3. Accepted by the product owner 4. Compliant with safety regulations: no pointed points 22

Ready to go? Sprint 3 • Sprint planning (1 minute): estimation • Sprint work (3 minutes): fold lots of airplanes • Sprint review (1 minute): prove business value • Sprint retrospective (1 minute): improvement 23

The winning team is. . ! 24

Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. Albert Einstein 25

Debrief: Each table talks about… • What made them improve over the three iterations • What would have happened if the time box was not there • Who made the final design decisions in the team • Any wastes they removed from the system that helped them get better 26

Instructor guide • • Create teams of 5 -6 members Handout different coloured pens to each team Handout c 50 A 6 pages to each team The team who can deliver the most value (airplanes) wins. In the case of equal scores, the team that has the estimates closest to the actuals wins • Keep track of the score on a flip board/white board as shown on slide 16 • Keep track of the timings using a stopwatch on the board or on phone etc. • Print out and handout / stick up on the wall the acceptance criteria and definition of done for each sprint so the development team can see the changing criteria • There are notes in most slides if required 27

© 2019 Slalom, LLC. All rights reserved. The information herein is for informational purposes only and represents the current view of Slalom, LLC. as of the date of this presentation. SLALOM MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.