SCRUM - an agile software development methodology Scott Mikneus Anthonia Akinde SE470 – Spring 2003.

Slides:



Advertisements
Similar presentations
An Agile Retrospective Clinton Keith Overview Retrospective format What works (clear wins)? What doesn’t work so well? What do we need to start doing?
Advertisements

A little Software Engineering: Agile Software Development C Sc 335 Rick Mercer.
Software development process improvement Ville Wettenhovi Master thesis presentation Supervisor:Professor Jukka Manner Instructor:M.Sc. Markus Aalto Date:23th.
Ni.com Introduction to Agile and Scrum Speaker/Author: Paul Packebush Section Manager, Corporate Metrology Author:Logan Kunitz Staff Calibration Engineer.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Where We Are Now. Where We Are Now Traditional PM versus Agile Methods Traditional PM Approach Concentrates on thorough, upfront planning of the entire.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall B.1.
Agile In Practice Benjamin Booth Spring Proprietary 2 Author/Blogger benjaminbooth.com.
Clinton Keith CTO, High Moon Studios Agile Methodology in Game Development: Year 3.
SCRUM John Drew. SCRUM - overview Scrum is a project management discipline that has evolved since the early 1990s to deliver software that meets business.
NAUG NAUG Knowledge Evening – th February 2007.
Presentation from: See Also: scrumreferencecard.com/ScrumReferenceCard.pdf.
Agile development By Sam Chamberlain. First a bit of history..
SCRUM METHODOLOGY By Kimberly Stoler IS 553. Historical Background  Creator’s  Ken Schwaber  Jeff Sutherland  Named after the game of Rugby  Why.
Agile Software Development Matt Rice November 27, 2006.
SCRUM Software Development Process. Background “Scrum” A rugby term “describes a play in rugby in which the two sets of forwards mass together around.
Introduction to Agile.
An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
Adopting Agile for Enterprise Software Joe Bedell, Software Engineer Jason Breen, Software Engineer Peter Melko, Scrum Master June 15 th, 2015.
Agile Software Development What is Agile? And How are we implementing Agile?
1 Agile Methodology & Programming Ric Holt July 2009.
CSE G674/2009 Project Project Management Section Presented by: Amir Aref Adib.
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.
Agile Software Development with Scrum Shveta Mehtani
Tuesday, June 8 th, Agile Development-Successful Delivery & Implementing Across the Enterprise.
Current Trends in Systems Develpment
Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Agile Development In 2001, a group called the “Agile Alliance” signed a “manifesto” that stated: Individuals and Interactions over processes and tools.
Testing Challenges in an Agile Environment Biraj Nakarja Sogeti UK 28 th October 2009.
Agile In Practice Benjamin Booth Spring Proprietary 2 5 Programmer/Architect.
1 - Agile in a nutshell. 2 - Basic principles ●Relies on an iterative, incremental development mechanism with continuous adaptation to customer requirements.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Scrum Santhosh Srinivasan. Outline What is Scrum What is Scrum Why Scrum Why Scrum Scrum Practices Scrum Practices Why Scrum works Why Scrum works Pros.
Presented by © Advanced Management Services, Inc Adaptive Project Framework A Common Sense Approach to Managing Complexity and Uncertainty Robert.
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
Presentation from: See Also: scrumreferencecard.com/ScrumReferenceCard.pdf.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Think Scrum, act Scrum Scrum Practitioner like a boss Thibault Clavier.
CS 4500: Software Development Software Process. Materials Sommmerville Chapters 1, 2 and 3 Software Cycle and Models:
Scrum Overview. Agenda What is scrum…and what it isn’t Scrum’s Characteristics The Scrum Process Scrum Phases Measurements Key Practices Backlogs Sprint.
A Brief Conversation on Agile and the Scrum Framework
Industrial Software Development Process Bashar Ahmad RISC Software GmbH.
Beyond the BACoE: Developing Business Analysis Maturity.
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Muhammad Adli Aniq bin Lamin ( ) Muhammad Shahrul bin Mohd Yusuf ( ) Khairul Ikhwan bin Mohamad Halim ( ) Methodology for Mobile.
Agile Scrum Development Carter Jasinski. Outline ● Introduction ● Roles ● Artifacts ● Sprints ● Uses.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
Embedded Systems Software Engineering
Agile Project Management
Agile Project Management Athanasios Podaras
AGILE SCRUM METHODOLOGY
Flight Software Conference 2016
Agile Training Day 2 November 17, 2015.
Appendix B Agile Methodologies
Wael Ellithy, Ph.D. Arx ICT
SCRUM Scrum and Agile Software Development Reading:
Agile Software Development Brian Moseley.
Project Management and the Agile Manifesto
Introduction If you have got a call for an Agile testing interview, then congratulations are in order. You may be feeling nervous, but it sure to be felt.
Introduction to Agile Blue Ocean Workshops.
Project Lifecycle and IT Product Life Cycle
Appendix B Agile Methodologies
Chapter 5: New and Emerging Process Methodologies
Agile, Scrum and CMMI Methodologies
Presentation transcript:

SCRUM - an agile software development methodology Scott Mikneus Anthonia Akinde SE470 – Spring 2003

Introduction to SCRUM Scrum is an Agile Software Development Process. Scrum is not an acronym name taken from the sport of Rugby, where everyone in the team pack acts together to move the ball down the field analogy to development is the team works together to successfully develop quality software

Introduction to SCRUM (cont.) Jeff Sutherland (a guru) states: “Scrum assumes that the systems development process is an unpredictable, complicated process that can only be roughly described as an overall progression.” “Scrum is an enhancement of the commonly used iterative/incremental object-oriented development cycle”

Historical Background Jeff Sutherland first person to apply concepts of Scrum to software development in 1993 A variation of Sashimi Japanese designed an all at once approach after their bad experiences with Waterfall The initial use of the word "Scrum" was used in 1987 to describe time-boxed, self- organizing, teams in product development

Historical Background (cont.) Jeff Sutherland and Ken Schwaber collaborated to define the process through In 1996 wrote the seminal article for Scrum Software Development process jointly used and improved Scrum at a variety of software development organizations from 1996 until now now promoting the idea of certifying ScrumMasters

Description Overview Scrum is named after the game of Rugby in which a group is responsible for picking up the ball and moving it forward. It is an iterative, incremental process for developing any product or managing any work. Scrum focuses on the entire organization for its implementation to be a success.

Description Overview (cont.) Scrum principles include: Quality work: empowers everyone involved to be feel good about their job. Assume Simplicity: Scrum is a way to detect and cause removal of anything that gets in the way of development. Embracing Change: Team based approach to development where requirements are rapidly changing. Incremental changes: Scrum makes this possible using sprints where a team is able to deliver a product (iteration) deliverable within 30 days.

Scrum Methodology

Description Components Roles: Scrum Master Developer QA Documentation member Project manager

Description Components (cont.) Processes: Pregame Planning and Architecture: - Identify project - Prioritizing functional requirements - Identify resources available - Establishing the target environment

Description Components (cont.) Processes: Game Sprints:- lasts for 30 days - Analysis, Design, Develop - Testing (this happens throughout sprint) - Review - Adjust Postgame - Closure (this includes delivering a functioning deliverable, sign-off, start next sprint.

Description Components (cont.) Values: Flexible deliverable Flexible schedule Small teams Frequent reviews Collaboration Team Empowerment Adaptability

Scrum Process Flow

Process Comparison

Description Advantages Extreme value - reduces risk in ROI Supports business value driven S/W Dev. Control of very complex process of product development Allows Developers to focus on delivering a usable functionality to the client Generates productivity improvements by implementing a framework that empowers teams and thrives on change Insists that the Client prioritize required functionality. Ability to respond to the unpredictable in any project requirements.

Description Advantages (cont.) Flexibility Knowledge sharing between Developers Collective ownership OO technology

Description Disadvantages Scrum is not effective for small projects Expensive to implement Training is required

Usage Guidelines – When to use requirements are not clearly defined. work is delivered in increments work is measured and controlled productivity is maximized by applying known technologies organizations are willing to do anything and everything for a project to succeed project is important and no one has confidence that any existing approach will work. control and management is Empirical

Usage Guidelines – When to avoid there isn’t a flexible environment corporate culture isn’t conducive to this of development environment teams of developers are more than 10. Six is ideal. Cost is a major issue No management support No formal training available

Usage Guidelines – Implementation Need for an extra member just in case an active member is absent, the documentation member substitutes Location: Although not impossible, its hard to implement Scrum when all team members are not in the same location Non-Supportive management Cost Lack of Customer Involvement Collective ownership Isolation of sprint team

Scrum Success Factor

Scrum and CMM CMM advocates Repeated Defined problems, solutions, Developers and organizational environment. Scrum says that this is not entirely possible because developers change from one project to another. Scrum assumes that the development process is always empirical and not defined. Scrum says uncertainties are impossible to measure, therefore, looks beyond the repeatable /defined approach

Marketplace Analysis – Key players/Gurus Jeff Sutherland one of the co-developers of the Scrum process. Jeff invented many of the first ideas and practices for Scrum. Owner of the website: Ken Schwaber one of the co-developers of the Scrum process. Co-author of the book Agile software Development with Scrum. Mike Beedle owner of e-Architects Inc., a technical and management consulting company that specializes in adaptive software development. Co-author of the book Agile software Development with Scrum.

Marketplace Analysis – Organizations Agile Alliance website states: “The AgileAlliance is a non-profit organization dedicated to promoting the concepts of agile software development, and helping organizations adopt those concepts.” Object Mentor, Inc. Website “The Object Mentor mission is to provide the technical and business leadership that helps our customers get their projects done” ADM Advanced Development Methodologies a 15 year-old process development company that develops processes, provides process consulting to its customers, and develops tools to support the use of these processes

Marketplace Analysis – Products controlchaos.com offers certification to become ScrumMaster Website states: Attendees will be thoroughly trained in the Scrum methodology and software. Upon successful completion, each attendee will become a Certified ScrumMaster and receive an individual license to the methodology and software.

Marketplace Analysis – Products (cont.) controlchaos.com cost for a session is $500 The description of their product “Scrum is a suite of products for Agile software development. Scrum’s iterative, incremental practices allow development teams to rapidly deliver functionality to customers.”

Market Data / Forecasts Advanced Development Methods (ADM) involved in the certification of ScrumMasters and they have certified 50 ScrumMasters to date. Specific statistics could not be found on how quickly Scrum is being adapted Some companies that have implemented Scrum successfully: Borland, Canon, Easel Corporation, Elementrix Technologies, Fujitsu, Honda, and Nike Securities in Chicago

Conclusion Scrum offers: a high degree of flexibility promises a high probability of success Scrum benefits: an anticipating culture increases the sense of urgency promotes the sharing of knowledge encourages dense communications facilitates honesty among developers

Recommendations We recommend Scrum as an adaptive and flexible development methodology that creates a culture of communication, knowledge sharing and teamwork within an organization.

References Schwaber, Ken and Mike Beedle. Agile software Development with Scrum. Prentice Hall, Sutherland, Jeff. “Inventing and Reinventing Scrum in five companies”, 21 September agilealliance.com/articles/articles/InventingScrum.pdf jeffsutherland.com/

The End. Thank you Questions or comments