Agile Development GROUP 8 Agnes Fitria Utami - 1501142983 Erni - 1501145575 Hanna Septiani - 1501148394 Novie Ratna Sari - 1501151786 Lianto - 1501171724.

Slides:



Advertisements
Similar presentations
Applying Agile Methodologies to Traditional Publishing Kristen McLean Bookigee, Inc. February 12 th, 2011.
Advertisements

Agile Software Development Robert Moore Senior Developer Curtin University.
Unified process(UP) UP is an OO system development methodology offered by Rational(Rational Rose) s/w, now a part of IBM Developed by Booach,Rambaugh,Jacobson--
Agile Software Development کاری از : مهدی هوشان استاد راهنما : استاد آدابی.
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.
SOFTWARE PROCESS MODELS. Software Process Models  Process model (Life-cycle model) -steps through which the product progresses Requirements phase Specification.
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.
Software Project Management
Agile Development By: Kelvina Wibowo ( ) | Ignatius Albert ( ) | Albertus Andika ( ) | Schwanova Lucki.
Alternate Software Development Methodologies
An Agile View of Process
Software engineering Process models Pavel Agejkin.
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
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.
1. 2  Have a basic understanding of the fundamental principles of object-oriented software development.  Understand a selection of the design patterns.
Agile Modeling Theory. 2 Agile Modeling (AM) AM is a chaordic, practices-based process for modeling and documentation AM is a collection of practices.
Agile Methodologies: Comparative Study and Future Direction 林佳蓁 資工 4B.
Extreme/Agile Programming Prabhaker Mateti. ACK These slides are collected from many authors along with a few of mine. Many thanks to all these authors.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Software Engineering Saeed Akhtar The University of Lahore Lecture 5 Originally shared for: mashhoood.webs.com.
K.Ingram 1 Sept 2007 Agile Software Development. K.Ingram 2 Sept 2007 Contents Agile Software Development: 1.What is it? 2.Agile’s Values, Principles,
The Confounding World of Process Methodologies By Thelma Hataria.
© 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v
Cloud Computing and Big Data Group 8 : Agnes Fitria Utami Erni Hanna Septiani Novie Ratna Sari Lianto.
Agile febrian | erlien | beny | ragnar | billy. SLDC Methodologies.
10 key principles of agile software development
Group 6 : - Yesika Kristina Dea Pradana D Sukianti Merianti Meshiya Caterlee
Agile Gintarė Bernotaitytė © 2013.
Project Management Software development models & methodologies
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
Chapter 3 Agile software development 1 Chapter 3 – Agile Software Development.
Agile development: a PM’s perspective
Embedded Systems Software Engineering
Chapter 5 Agile Development Moonzoo Kim KAIST
CS223: Software Engineering
Agile Methods SENG 301.
Agile Project Management and the yin & yang of
Agile Methodology and Scrum
AGILE SCRUM METHODOLOGY
Introduction to Agile Software Development
E-Hospital Group 8 : Agnes Fitria Utami Erni
Feature Driven Development
Appendix B Agile Methodologies
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
Agile Software Development
Agile Software Development Brian Moseley.
MCS morning (3rd semester) Department of CS&IT
Waterfall and Agile Quality Techniques
COMP 350: Object Oriented Analysis and Design Lecture 2
Copyright Scott W. Ambler1 Introduction to Agile Model Driven ( Senior Consultant, Inc.
Agile Software Development
How to Successfully Implement an Agile Project
Rosa María Torres de Paz
Agile Software Processes
Agile Process: Overview
Process Models Coming up: Prescriptive Models.
Introduction to Agile Blue Ocean Workshops.
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
Agile SDLC Methodology
Systems development life cycle (SDLC)
Projects, Assignments, and other Assessments
Appendix B Agile Methodologies
Extreme Programming.
Rapid software development
Agile software development
Adapting Agile in Pharmaceutical Industries
Presentation transcript:

Agile Development GROUP 8 Agnes Fitria Utami Erni Hanna Septiani Novie Ratna Sari Lianto

What is Agile Development?  Software development methodology  Rapidly changing environment

Advantages  Customer satisfaction  Adaptive to changes  Least documentation  Reduces risks of development

Disadvantages  Customer interaction is the key factor  Lack of documentation  Time consuming and wastage of resources  More helpful for the management than the developer

Steps

Practices Iterative and incremental modelling Teamwork Simplicity Validation Documentation Motivation

Iterative and incremental modelling  Use the right models  Create several models in parallel  Iterate frequently  Model in small increments

Teamwork  Model with others  Involve users and other stakeholders  Share ownership of the models  Display the models publicly

Simplicity  Create simple content  Depict the models simply  Use simple tools

Validation  Prove it with code EDOC

Documentation  Discard temporary models  Formalize contract models  Update only when it hurts

Motivation  Model to communicate  Model to understand

Rapid vs. Agile AgileRapid No prototypesPrototypes Break down solution into features Focus on delivering the features of the application by first doing it and improving the code base overtime Democratic : doing by teamIndividual works in silos Self managingManaged by project manager Focus on team communication and designing as a group Works as individual so resulting unmaintainable and poorly designed code Based around disciplined individuals that focused in real software Lack of discipline, because there was no structure to either the process, architecture or engineering practices