© 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v. 7.3.1.

Slides:



Advertisements
Similar presentations
© 2007 BigVisible Solutions, Inc. All Rights Reserved Coaching Solutions Agile Project Start v
Advertisements

Agile Software Development Robert Moore Senior Developer Curtin University.
AGILE DEVELOPMENT Outlines : Quick Look of agile development Agility
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,
Software Development Methodologies 1. A methodology is: A collection of procedures, techniques, principles, and tools that help developers build a computer.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall B.1.
Agile development By Sam Chamberlain. First a bit of history..
Software Process and Problem Statements CSSE 371, Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 3, 2004.
Project Management – An Overview Project as a metaphor – a way to approach a series of activities Contexts – construction managementt, IT development,
Agile Architecture? Paul Lund 24 th Nov Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Agile Methods.
The Challenge to Survive in Today’s Software Development Environment Evaluating the Agile Methodology.
CHAPTER 17 Building Software to Support an Agile Organization
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.
CPSC 871 John D. McGregor Processes – a first iteration Module 1 Session 1.
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
BEFORE AGILE METHODS Other Engineering fields development models were used, ie: Waterfall Method: Intensive planning and refactoring before coding is actually.
Transforming Organizations
Business Driven Technology Unit 5 Transforming Organizations McGraw-Hill/Irwin Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved.
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.
Tuesday, June 8 th, Agile Development-Successful Delivery & Implementing Across the Enterprise.
Current Trends in Systems Develpment
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.
© Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
Software Engineering Saeed Akhtar The University of Lahore Lecture 5 Originally shared for: mashhoood.webs.com.
1 The Manifesto for Agile Software Development “We are uncovering better ways of developing software by doing it and helping others do it. Through this.
AGILE COTS Václav Pergl We are uncovering better ways of developing software by doing it and helping others do it. Through this work.
#AgileEd. Using Agile in the Classroom Cindy Royal, Associate Professor Texas State University slideshare.net/cindyroyal #AgileEd.
Lecture 3 – Agile Approach
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
- Discussion of Chapter 1 in Martin and Martin.  We are uncovering better ways of developing software by doing it and helping others do it. Through this.
10 key principles of agile software development
Extreme Programming מתודולוגיה לפיתוח פרויקטי תוכנה.
Agile Center of Excellence. Richard K Cheng Agile is just a high level concept.
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Baby Steps to Agility How to Grow Into Agile. A little about me A little about Agile Growing into Agile Questions Goals.
Project Management Software development models & methodologies
Software Engineering cosc 4359 Spring 2017.
Embedded Systems Software Engineering
Chapter 5 Agile Development Moonzoo Kim KAIST
Principles for Agile Development
Appendix B Agile Methodologies
Agile Software Development
Agile Software Development Brian Moseley.
How to Successfully Implement an Agile Project
Click to edit Master text styles
Agile Process: Overview
Click to edit Master text styles
Introduction to Agile Blue Ocean Workshops.
Click to edit Master text styles
ОПШТЕСТВО ТЕМА: МЕСТОТО ВО КОЕ ЖИВЕАМ Скопје
Projects, Assignments, and other Assessments
Project Lifecycle and IT Product Life Cycle
Click to edit Master text styles
Appendix B Agile Methodologies
Click to edit Master text styles
Chapter 5: New and Emerging Process Methodologies
Presentation transcript:

© 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v

Agile Training Game © 2007 BigVisible Solutions, Inc.. All Rights Reserved 2 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level Trouble With Traditional Project Approach Some Interesting Findings: A study of 8,300+ projects completed by large American companies using traditional methodologies revealed: Most Common Reasons for Failure:  Incomplete or changing requirements  Lack of User Input Only 42% of features originally proposed are implemented Only 16% of projects finished on-time, on- budget with originally defined scope FACT! 66% of Product Features are rarely, if ever, used. FACT! 80% of a Product’s Features are added after the first release

Agile Training Game © 2007 BigVisible Solutions, Inc.. All Rights Reserved 3 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level What is Agile? ► Agile Software Development processes were first formulated in the early 1990’s ► The Agile core set of values was articulated in the Agile Manifesto in 2001 We Value:  Individuals and interactions over processes and tools  Working software over comprehensive documentation  Customer collaboration over contract negotiation  Responding to change over following a plan “That is, while there is value in the items on the right, we value the items on the left more” ► Agile processes present light-weight methodologies that focus on incremental, iterative development ► Agile implementations focus on rapid value delivery, minimizing waste and continuous improvement

Agile Training Game © 2007 BigVisible Solutions, Inc.. All Rights Reserved 4 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level Goals of Agile ► Faster Release Cycles  Reduced time to market ► Better Productivity  Team focused on product development ► Increased Quality  Quality controls embedded throughout lifecycle ► Focus on Delivering True Value  Value can only be recognized in the form of completed product ► Responsive to Change  No change control process required

Agile Training Game © 2007 BigVisible Solutions, Inc.. All Rights Reserved 5 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level Why does it work? ► Focus on Business Objectives  Deliver maximum business value ► Measure Progress in the Form of Completed Product  Tested, customer-accepted product ► Build a Culture of Continuous Improvement  Continuous incremental gains ► Responsive to Feedback and Learning  Facilitates changes that improve product ► Maximize Team Productivity  Laser-focus on delivering product

Agile Training Game © 2007 BigVisible Solutions, Inc.. All Rights Reserved 6 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level The Agile Principles ► Deliver customer value early and often ► Frequent, iterative delivery of accepted product ► Embrace change ► Closely integrated team ► Minimize waste ► Strive for highest level of collaboration ► Success is built around motivated self-organizing teams ► Continuously seek ways to improve

Agile Training Game © 2007 BigVisible Solutions, Inc.. All Rights Reserved 7 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level Traditional/Waterfall Process Analysis Design Development QA Deliverable: Requirements Document Deliverable: Design Specification Deliverable: Integrated Code Deliverable: Tested, Accepted Product Typical Waterfall/Traditional SDLC

Agile Training Game © 2007 BigVisible Solutions, Inc.. All Rights Reserved 8 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level Waterfall/Traditional Value Delivery Analysis Design Development QA AnalysisDesignDevelopmentQA

Agile Training Game © 2007 BigVisible Solutions, Inc.. All Rights Reserved 9 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level AnalysisDesignDevelopmentQA Waterfall/Traditional Value Delivery AnalysisDesignDevelopment 0 QA Value Growth: Traditional Project Week In traditional projects: Real value cannot be recognized during the majority of the process In traditional projects: Value is only delivered at the completion of the QA phase of the project. In traditional projects: Maximum value is achieved at product launch Value/Quality Software Delivered

Agile Training Game © 2007 BigVisible Solutions, Inc.. All Rights Reserved 10 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level Agile Value Delivery Week Value/Quality Software Delivered In Agile projects: Customer realizes value as early as the completion of the first iteration In Agile projects: Frequent integration at the end of each iteration ensures product quality early in the product lifecycle In Agile projects: Each iteration delivers incremental functionality intended to continuously reflect the customer chosen direction for the product ► Reduce Risk  Minimize Business Risk  Minimize Product Risk  Minimize Project Risk

Agile Training Game © 2007 BigVisible Solutions, Inc.. All Rights Reserved 11 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level The Agile Principles ► Deliver customer value early and often ► Frequent, iterative delivery of accepted product ► Embrace change ► Closely integrated team ► Minimize waste ► Strive for highest level of collaboration ► Success is built around motivated self-organizing teams ► Continuously seek ways to improve

Agile Training Game © 2007 BigVisible Solutions, Inc.. All Rights Reserved 12 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level Common Agile Misconceptions ► Agile Abandons all Rigor  Agile is very rigorous in its principles ► Agile does not scale  Agile has been scaled to hundreds of product developers ► Agile is not for Distributed Teams  Agile supports the model of multiple distributed teams that adopt the same principals and practices ► Agile = ‘No Documentation’  Agile stresses product documentation ► Agile Focuses Cost Reduction  Agile does not directly address project or resource costs ► Agile Ignores Architecture  Agile stresses continuous architecture and design evolution ► Agile Means ‘No Planning’  Agile stresses the importance of short-term and long-term planning