The Challenge to Survive in Today’s Software Development Environment Evaluating the Agile Methodology.

Slides:



Advertisements
Similar presentations
Feb Alten Group Started in France in 1988 Currently more than people Presence in 10 countries Active in The Netherlands since 2002.
Advertisements

Agile Software Development Robert Moore Senior Developer Curtin University.
AGILE DEVELOPMENT Outlines : Quick Look of agile development Agility
SDLC – Beyond the Waterfall
Software Development Life-Cycle Models
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.
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,
BUSINESS DRIVEN TECHNOLOGY
Blue Elephant Tony DiCola Mauktik Gandhi Jeff Mathew Tim McConnell Todd Sahl Eugene Talagrand.
Agile Process Models. Prescriptive models don’t work It is unrealistic to not have changes. Why? The Agile Manifesto: Individuals and interactions over.
1 Agile Methodologies in DoD Software By Cynthia Johnson.
Agile Methodology: The New Wave in Software Development By Patricia Cleary Thesis Hypothesis: The agile methodologies are better than the current methodology.
Agile Software Development Matt Rice November 27, 2006.
Developing for continuous change UCD demands a different model for development An iterative approach is suitable.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Coming up: The Manifesto for Agile Software Development 1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 3 Agile Development Software Engineering:
The Agile Alliance By Mark Rucker. The Agile Alliance What is the Agile Alliance? History of the Agile Alliance What is the Agile Alliance today? The.
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 Methodologies and Concepts Roy Osherove Principal, Team Agile Blog : ISerializable.com.
Classical vs. Agile Requirements Development Svetlin Nakov Telerik Software Academy academy.telerik.com Senior Technical Trainer
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Chapter 4 An Agile View of Process
Chapter 4 Agile Development 1. The Manifesto for Agile Software Development 2 “We are uncovering better ways of developing software by doing it and helping.
IS2210: Systems Analysis and Systems Design and Change Twitter:
CPSC 371 John D. McGregor Session 22 Process. Specification and design problem solution specification implementation specification.
Distributed Software Development
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Coming up: The Manifesto for Agile Software Development 1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 3 Agile Development Software Engineering:
© Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
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.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 4 Agile Development Discussion of Agile Development and Agile Process.
CS3100 Software Project Management Agile Approaches.
© 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.
Chapter 3 Agile Development
Agile Software Development By Kshitij Limaye CSC 532.
Lecture 3 – Agile Approach
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Agile. Processes Waterfall Traditional With prototyping Sprial Agile Dynamic Systems Development Method (DSDM) Scrum Crystal eXtreme Programming (XP)
ICS 61 – The Game Improves through Iteration Based on Schell, ch. 8 Winter, 2015.
JASS 2006 Agile Software Development. JASS 2006 Agenda.
Copyright 2015, Robert W. Hasker. Classic Model Gathering Requirements Specification Scenarios Sequences Design Architecture Class, state models Implementation.
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
1 The economies of ALL developed nations are dependent on software The economies of ALL developed nations are dependent on software More and more systems.
Agile Gintarė Bernotaitytė © 2013.
Agile/XP Introduction
Chapter 5 Agile Development Moonzoo Kim KAIST
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Software Engineering Process
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Agile Software Development
Iterative and Agile Development
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Agile Software Development Brian Moseley.
Domains of Agility Being Agile Doing Agile Evan Leybourn, 2016 PROCESS
Introduction to Software Engineering
Agile Software Development
Lecture 2 Revision of Models of a Software Process
Agile Process: Overview
Chapt 2 Iterative Evolutionary Agile.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Project Lifecycle and IT Product Life Cycle
Topic 1: Introduction to the Module and an Overview of Agile
Adapting Agile in Pharmaceutical Industries
System Development Methods
Presentation transcript:

The Challenge to Survive in Today’s Software Development Environment Evaluating the Agile Methodology

Thesis Hypothesis b The agile methodologies are better than the current methodology that is in place at a company that will be used for analysis purposes. This company’s current methodology is similar to Waterfall.

Why the need for software development processes? b Build quality software b On time b On budget b Meets the customer’s requirements

Waterfall Process

Waterfall Example 1. Develop an Idea 2. Justify 3. Review and approve 4.Develop a solution 5.Quality Assurance 6. Implementation

Develop an Idea b Idea to improve system functionality, increase the business’ bottom line, or make individuals more productive b Business requirement is written by customer

Justify b Assess the risks and benefits of proposed idea b Ballpark estimate

Review and Approve b Approve or reject request b Prioritize approved request

Develop A Solution b Develop Functional Specification b Develop Detailed Specification b Reestimate time to develop b Code and unit test b Code inspection b Risk analysis spreadsheet b QA begins test cases b Documentation is started

Quality Assurance b Test cases are exercised b Regression testing is performed b Developer is available for code rework

Implementation b Software delivery b User training b Documentation is given to user b User acceptance testing b Sign off on deliverable

History of Agile b Several agile processes were developed during the 1990’s b Group of individuals gathered at lodge in February 2001 b Developed Agile Manifesto b Formed Agile Software Development Alliance

Agile Processes b Extreme Programming (XP) b Coad’s Feature Driven Development b Highsmith’s Adaptive Software Development b Cockburn’s Crystal Family b Open Source b Scrum

Why Agile? b Light weight b People focus b Adaptive b Less Documentation Intensive b Handles changing requirements better

Agile Manifesto Values  “Individuals and interactions over processes and tools  Working software over comprehensive documentation  Customer collaboration over contract negotiation.  Responding to change over following a plan.” [Agile Manifesto]

Feature Driven

Thesis Hypothesis b The agile methodologies are better than the current methodology that is in place at a company that will be used for analysis purposes. This company’s current methodology is similar to Waterfall.

Goal Of Thesis b Describe agile processes of Extreme programming, Feature Driven, and Adaptive b Evaluate if the company used as an example should stay with waterfall, reengineer, or change to an agile methodology b Estimated Completion: Fall 2002

Sources