Think Scrum, act Scrum Scrum Practitioner like a boss Thibault Clavier.

Slides:



Advertisements
Similar presentations
Agile Software Development Robert Moore Senior Developer Curtin University.
Advertisements

SOFTWARE DEVELOPMENT METHODOLOGIES Methodologies Waterfall Prototype model Incremental Iterative V-Model Spiral Scrum Cleanroom RAD DSDM RUP.
SDLC – Beyond the Waterfall
COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. 1 Agile documentation development methodology Giby Panicker and Judith Benjamin 1-Dec-2012.
PROC-1 3. Software Process. PROC-2 What’s a process? Set of activities in creating software It involves creativity –hard to automate –Requires human judgment.
Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger
AgileMan Consulting So what the heck is Agile? It came about as a response to the high failure rate of software projects (> 60%), where failure means late,
Agile 101.
Agile development By Sam Chamberlain. First a bit of history..
1 Agile Methodologies in DoD Software By Cynthia Johnson.
Agile Programing Methods Drew Arrigoni. The Agile Manifesto ● Individual Interactions over Processes and Tools ● Working Software over Comprehensive Documentation.
Agile Process: Overview n Agile software engineering represents a reasonable compromise to conventional software engineering for certain classes of software.
An Agile View of Process
Introduction to Agile.
Software engineering Process models Pavel Agejkin.
Classical vs. Agile Requirements Development Svetlin Nakov Telerik Software Academy academy.telerik.com Senior Technical Trainer
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
CONFIDENTIALITY © 2010 BA ValueBASE LLP, The concepts and methodologies contained herein are proprietary to BA ValueBASE LLP. Duplication, reproduction.
Software Development Process
Agile Software Development What is Agile? And How are we implementing Agile?
CompSci 230 Software Design and Construction
Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
1 Agile Methodology & Programming Ric Holt July 2009.
Chapter 4 Agile Development
AGILE Methodology. AGILE  derived from the word ‘agile manifesto’, also called the Manifesto for Agile Software Development which is a formal proclamation.
Chapter 5 Software Process Models. Problems with “Traditional” Processes 1.Focused on and oriented towards “large projects” and lengthy development time.
CPSC 371 John D. McGregor Session 22 Process. Specification and design problem solution specification implementation specification.
AgileCamp Presents: Agile 101. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons Attribution.
AGILE SOFTWARE DEVELOPMENT PROCESSES Cheruku Smitha.
Software Life Cycle Models. Waterfall Model  The Waterfall Model is the earliest method of structured system development.  The original waterfall model.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Chapter 2 Iterative, Evolutionary, and Agile You should use iterative development only on projects that you want to succeed. - Martin Fowler 1CS
© 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v
Agile Methodology Paul Mohrbacher. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through.
Agile Software Development By Kshitij Limaye CSC 532.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
Dr. Rob Hasker. What if every project used Scrum?  Why might Scrum not be perfect for every project? Hard to get the big picture Early choices may have.
Module 2: What is Agile? Why use it? TLO: Given a DoD program involved in software development, the student will recognize situations where applying agile.
It’s Agile …. like! A Corkman’s introduction to Agile software delivery.
Agile 101. Feasibility Study SDLC – What is it? Systems Development Life Cycle: The most commonly used, and generally accepted, project management approach..
Over Contract negotiation over Processes and tools over Comprehensive documentation overFollowing a plan over.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Dr. Rob Hasker. Should every project use Scrum?  When might Scrum not be an appropriate model?  What are some of its limitations? Hard to get the big.
Introduction to Agile. Introduction Who is this guy?
Industrial Software Development Process Bashar Ahmad RISC Software GmbH.
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Agile Gintarė Bernotaitytė © 2013.
Software Engineering cosc 4359 Spring 2017.
Agile development: a PM’s perspective
Agile/XP Introduction
Object-oriented Analysis and Design
Appendix B Agile Methodologies
Software Engineering Process
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
Agile Frameworks Individuals and interactions over processes and tools
Agile Software Development
Iterative and Agile Development
Introduction to Software Engineering
Tim Hirner - Flagship Speakers January 23, 2014
How to Successfully Implement an Agile Project
Lecture 2 Revision of Models of a Software Process
Agile Process: Overview
Introduction to Agile Blue Ocean Workshops.
Projects, Assignments, and other Assessments
Project Lifecycle and IT Product Life Cycle
Topic 1: Introduction to the Module and an Overview of Agile
Adapting Agile in Pharmaceutical Industries
Chapter 5: New and Emerging Process Methodologies
System Development Methods
Presentation transcript:

Think Scrum, act Scrum Scrum Practitioner like a boss Thibault Clavier

Presenter Thibault CLAVIER Graduated from mathematical engineering (UCL) 4 years at ARHS Scrum coach Agile minded Personal interest in creativity 2

The Group ITLocal700+ 3

IT Infrastructure Our fields of expertise Digital Trust Business Intelligence Software Development Business Process Management European institutions - 71% Bank - 6% Government - 6% Telco - 6% Industry - 11% 4

Course Objectives 5

Course Program Theory (14h – 15h) 1. Course Setup 2. Introduction to Agile Methodologies 3. Scrum Framework 4. Scrum Lifecycle Practice (14h – 15h) 5. Airplanes Game 6. Conclusion 6 The content of this course is confidential and cannot be shared without the explicit agreement of ARHS.

What is a « project »?

Introduction to Agile Methodologies

Traditional PM methodologies 9 Requirements Design Implementation Verification Maintenance Inception Elaboration Construction Transition Concept of Operations Requirements and Architecture Detailed Design Implementation Integration, Test, and Verification System Verification and Validation Operation and Maintenance Verification and Validation Waterfall RUP V-Model

Traditional PM methodologies 10 Requirements Design Implementation Verification Maintenance Inception Elaboration Construction Transition Concept of Operations Requirements and Architecture Detailed Design Implementation Integration, Test, and Verification System Verification and Validation Operation and Maintenance Verification and Validation Waterfall RUP V-Model Complex systems  Difficult to anticipate everything Emergent requirements  Requirements at T 0 are not the same at T 1 Heterogeneous projects  A procedure cannot fit all projects’ needs Changing technology  Introduces change management Long feedback loops  Changes are identified late

Agile Manifesto Individuals and Interactions Responding to Change Working Software Customer Collaboration over processes and tools over comprehensive documentation over following a plan over contract negotiation 11

Agile Methodologies 12 “Maximize the business value with right sized, just-enough and just-in-time processes and documentation”

Agile Methodologies 13 Major change in the paradigm Constraints RequirementsCostSchedule EstimatesCostScheduleFeatures Plan -driven Value -driven Traditional Predictive Agile Adaptive

Variants of Agile Methodologies 14 Agile KANBAN Scrum XP …

Scrum Framework

What is Scrum? Scrum is NOT an acronym… … it comes from rugby sport! 16

What is Scrum? “A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value”

Scrum Principles Empirical Process Control Self-organization Collaboration Value-based prioritization Time-boxing Iterative development 18

Practice

Game 21

Conclusion

« Patience you must have my young padawan » 23

24 No agility Without trust

Scrum has disadvantages  Hard to put in practice  Might be expensive to implement  Not everyone is suited for Scrum 25

Scrum has strong advantages Focus on high value items Transparency, inspection and adaptability Knowledge sharing Team commitment Better time to market with non complete increments Short feedback loops Lead to hyper-productive teams Reactive to change 26