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

Slides:



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

Agile Software Development کاری از : مهدی هوشان استاد راهنما : استاد آدابی.
Presented by Dustin Friel, PMP CSM May 6, 2009 Agile Lessons Learned 1.
SDLC – Beyond the Waterfall
COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. 1 Agile documentation development methodology Giby Panicker and Judith Benjamin 1-Dec-2012.
Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger
Blue Mountain RAM Product Roadmap Jim Erickson, President and CEO Randy Paroda, Director of Product Development.
Agile Process Models. Prescriptive models don’t work It is unrealistic to not have changes. Why? The Agile Manifesto: Individuals and interactions over.
Agile and Medical Device Software
Agile development By Sam Chamberlain. First a bit of history..
© ThoughtWorks, 2008 Improving Productivity and Quality With Agile Patrick Kua.
Agile Methods and Extreme Programming CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 23, 2007.
The Challenge to Survive in Today’s Software Development Environment Evaluating the Agile Methodology.
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:
Programming with eyes wide open. Your host today Subby Angelov Team
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.
Introduction to Agile.
Software engineering Process models Pavel Agejkin.
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.
A Consulting Project. About Me Blog:
Agile Software Development What is Agile? And How are we implementing Agile?
Chapter 4 Agile Development
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.
Pertemuan 5 Introduction to Agile Software Development Mata kuliah: T0144 – Advanced Topics in Software Engineering Tahun: 2010.
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.
By Saravanan Bala. General Report 31 % of Software projects are cancelled 75 % of the software projects are considered failures by the people who initiated.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Agile Assessment Gadi Lifshitz, Ayelet Kroskin, Barak Yagour, Yael Dubinsky.
Extreme Programming (XP). Agile Software Development Paradigm Values individuals and interactions over processes and tools. Values working software over.
Coming up: The Manifesto for Agile Software Development 1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 3 Agile Development Software Engineering:
Chapter 3 Agile Software Development (1/2) Yonsei University 2 nd Semester, 2015 Sanghyun Park.
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.
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,
CS3100 Software Project Management Agile Approaches.
Agile Methodology Paul Mohrbacher. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through.
Software Engineering (CSI 321) An Agile View of Process 1.
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
Cultivating Agile Requirements
PV213 EIS in Practice: 06 – Development process 1 PV213 Enterprise Information Systems in Practice 06 – Development process.
JASS 2006 Agile Software Development. JASS 2006 Agenda.
Extreme Programming מתודולוגיה לפיתוח פרויקטי תוכנה.
Agile Gintarė Bernotaitytė © 2013.
Embedded Systems Software Engineering
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.
Agile Methods SENG 301.
Manifesto for Agile Software Development
AGILE SCRUM METHODOLOGY
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 Frameworks Individuals and interactions over processes and tools
Agile Software Development
Software Engineering: A Practitioner’s Approach, 7/e Chapter 3 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.
Agile Software Development Brian Moseley.
Domains of Agility Being Agile Doing Agile Evan Leybourn, 2016 PROCESS
Software Engineering (CSI 321)
Tim Hirner - Flagship Speakers January 23, 2014
Being Agile Minded: Even if your team is not
Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger Joanne M. Atlee 4th Edition.
Agile Process: Overview
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Adjective: Able to move quickly and easily. Principles and Values
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Introduction to XP.
A quick intro to SCRUM and KANBAN By John Voris.
Presentation transcript:

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

Feb Services Consulting & Engineering Projects R&D Outsourcing Training

The agile manifesto

Feb , The lodge at Mtn. Village Extreme programming Scrum DSDM Crystal Feature Driven Development Pragmatic programming

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: processes and tools

Feb Processes and tools Fixed hierarchy, roles and team structure Many, many rules Management of process, not people Emphasis on process, not customer value

Feb Processes and tools Control Politics Ignorance Blame Apathy Fear

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interaction over processes and tools

Feb Individuals and interaction Collocation Self organizing teams Pair programming Collective code ownership XP Practices:

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: comprehensive documentation Individuals and interaction over processes and tools

Feb Comprehensive documentation ESA Life cycle: –User Requirements Document –Software Requirements Document –Architectural Design Document –Detailed Design Document –Software Transfer Document –Project History Document –Software Project Management Plan –Software Configuration Management Plan –Software Validation and Verification Plan –Software Quality Assurance Plan –Meeting minutes –Progress reports –…

Feb Comprehensive documentation ESA Life cycle: –User Requirements Document –Software Requirements Document –Architectural Design Document –Detailed Design Document –Software Transfer Document –Project History Document –Software Project Management Plan –Software Configuration Management Plan –Software Validation and Verification Plan –Software Quality Assurance Plan –Meeting minutes –Progress reports –…

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interaction over processes and tools Working software over comprehensive documentation

Feb Working software User stories Unit testing Continuous build and integration

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: contract negotiation Individuals and interaction over processes and tools Working software over comprehensive documentation

Feb Contract negotiation

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interaction over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation

Feb Customer collaboration Scrum: Prioritized backlog of user stories Must be accessible for questions Frequent delivery of working software Acceptance testing

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: following a plan Individuals and interaction over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation

Feb Following a plan

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interaction over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan

Feb Responding to change

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interaction 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.

Feb