Manifesto for Agile Software Development



Similar documents
Software Processes. Agile Methods

werteorientierte Unternehmenskultur

Agile Overview. 30,000 perspective. Juha Salenius CSPO CSM PMI-ACP PMP SCGMIS Workshop January 23 rd, 2013

Agile Project Management with Scrum

Introduction to Agile Software Development. EECS 690 Agile Software Development

Agile Project Management By Mark C. Layton

Agile Beyond The Team 1

26 May 2010 CQAA Lunch & Learn Paul I. Pazderski (CSM/CSP, OD-CM, CSQA) spcinc13@yahoo.com Cell: AGILE THROUGH SCRUM

Agile QA s Revolutionary Impact on Project Management

Agile Development with C#

Agile on huge banking mainframe legacy systems. Is it possible?

What does it mean to be Agile. Marek Majchrzak, Andrzej Bednarz Wrocław,

Agile Project Management Jim Highsmith. Chapter 1. The Agile Revolution

ITSM Agile Intro Feb 5, 2015

Ingegneria del Software Corso di Laurea in Informatica per il Management. Agile software development

Agile Software Development

Agile Development Overview

History of Agile Methods

Agile Execution for and Beyond IT

Processes in Software Development. Presented by Lars Yde, M.Sc., at Selected Topics in Software Development, DIKU spring semester 2008

Agile Software Development in the Large

The Agile Manifesto August 2001

Aristotle in an Agile World. By Ben Allen

PMBOK? You Can Have Both! June 10, Presented by:

Improving Software Productivity with Agile Methodologies

Digital Transformation of the Enterprise for SMAC: Can Scrum help?

Introduction to Agile Software Development

Role of Agile Methodology in Software Development

Neglecting Agile Principles and Practices: A Case Study


Comparing Scrum And CMMI

What Does Large Mean? Copyright 2003 by N. Josuttis and J. Eckstein 3. Why is Large an Issue?

Agile-Waterfall Hybrid Jessica LaGoy, MS, PMP

Software Development with Agile Methods

Development. Lecture 3

Agile Project Management: Adapting project behaviors to the software development environment

CS435: Introduction to Software Engineering! " Software Engineering: A Practitioner s Approach, 7/e " by Roger S. Pressman

USCIS/SPAS: Product Backlog Items and User Stories 4/16/2015. Dr. Patrick McConnell

This handbook is meant to be a quick-starter guide to Agile Project Management. It is meant for the following people:

Continuous Integration: Improving Software Quality and Reducing Risk. Preetam Palwe Aftek Limited

Scaling Scrum. Colin Bird & Rachel Davies Scrum Gathering London conchango

Agile Fundamentals, ROI and Engineering Best Practices. Rich Mironov Principal, Mironov Consulting

Mitigating Risk with Agile Development. Rich Mironov CMO, Enthiosys

Agile and ITIL And how they integrate. enterprise.bcs.org

How To Understand The Limitations Of An Agile Software Development

The Agility of Agile Methodology for Teaching and Learning Activities

LEAN AGILE POCKET GUIDE

Agile Processes and Distributed Projects: Dream or Nightmare?

Agile Software Development. Mohsen Afsharchi

Adopting Agile Project Management - Corporate Culture Must Match (Apr 15)

Governments information technology

Developing the Agile Mindset for Organiza7onal Agility. Shannon Ewan Managing

Creating a High Maturity Agile Implementation

COMP 354 Introduction to Software Engineering

The Business Case for Scrum

Agile Requirements Generation Model: A Soft-structured Approach to Agile Requirements Engineering. Shvetha Soundararajan

Agile and PRINCE2 And how they integrate. enterprise.bcs.org

Agile Project Management

SCEA 2010 EST06. Estimating Issues Associated with Agile. Bob Hunt. Galorath Incorporated

Distributed Agile Development. Bapiraju Nandury Product Development Manager Bangalore Development Centre

Agile Project Management

Comparative Study of Agile Methods and Their Comparison with Heavyweight Methods in Indian Organizations

AGILE SOFTWARE DEVELOPMENT: INTRODUCTION, CURRENT STATUS & FUTURE Pekka Abrahamsson Jyväskylä

Information Management for National Guard Agribusiness Development Teams: An Agile Development Case Study

Advanced Software Engineering Agile Software Engineering. Version 1.0

Agile Project Management. What it is and what it isn t

(General article) An Empirical Study of Agile Software Development. Ajay Deep a* Department of Information Technology, OITM, Hisar

Risikominimering I IKT-prosjekter - experiences from the Danish Government

USAGE OF KANBAN METHODOLOGY AT SOFTWARE DEVELOPMENT TEAMS

Agile Projects 7. Agile Project Management 21

How to manage agile development? Rose Pruyne Jack Reed

A Review of Agile Software Development Methodologies

CSSE 372 Software Project Management: Managing Agile Projects

AGILE BUSINESS INTELLIGENCE

Case Study on Critical Success Factors of Running Scrum *

White Paper Security in Software Development Life Cycle

Bottlenecks in Agile Software Development Identified Using Theory of Constraints (TOC) Principles

Jukka Mannila KEY PERFORFORMANCE INDICATORS IN AGILE SOFTWARE DEVELOPMENT

Outline. Agile Methods. Converse of Conway s Law. The Silver Bullet Fantasy (Brooks, 1986)

PROJECT MANAGEMENT MASTER PROGRAM SCHOOL OF MANAGEMENT UNIVERSITY OF QUEBEC AT MONTREAL. Agenda. Masters in Project Management Program

COMPARATIVELY ANALYSIS OF AGILE SOFTWARE DEVELOPMENT

Agile & the Declaration of Interdependence: A new approach to Process Improvement

AGILE - QUICK GUIDE AGILE - PRIMER

Waterfall to Agile. DFI Case Study By Nick Van, PMP

Atomate Development Process. Quick Guide

Gothenburg 2015 Jan Marek com CA Technologies Introducing Agile development methodologies to Session S601 mainframe development teams

Transcription:

Rocky Mountain Information Management Association Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: 1. Individuals and interactions over processes and tools 2. Working software over comprehensive documentation 3. Customer collaboration over contract negotiation 4. 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. http://agilemanifesto.org/ 1

Working software Responding to change Results People Individuals and interactions Customer collaboration Process Processes and tools Documentation Contract negotiation Following a plan PMI ten knowledge areas are: 1. Integration Management 2. Scope Management 3. Time Management 4. Cost Management 5. Quality Management 6. Human Resource Management 7. Communications Management 8. Risk Management 9. Procurement Management 10. Stakeholders Management 2

Human Resource Management Communications Management Stakeholders Management Integration Management Scope Management Time Management Cost Management Quality Management Risk Management Procurement Management The Agile movement is not anti-methodology, in fact many of us want to restore credibility to the word methodology. We want to restore a balance. We embrace modeling, but not in order to file some diagram in a dusty corporate repository. We embrace documentation, but not hundreds of pages of nevermaintained and rarely-used tomes. We plan, but recognize the limits of planning in a turbulent environment. Jim Highsmith, History: The Agile Manifesto [ 3

We follow these principles: 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 4. Business people and developers must work together daily throughout the project. 5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 7. Working software is the primary measure of progress. 8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 9. Continuous attention to technical excellence and good design enhances agility. 10. Simplicity--the art of maximizing the amount of work not done--is essential. 11. The best architectures, requirements, and designs emerge from self-organizing teams. 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. 1. Satisfy the customer 2. Work together 3. Motivated individuals 4. Face-to-face conversation 5. Team reflects and adjusts its behavior accordingly 4

1. Welcome changing requirements even late in development 2. Simplicity 3. Technical excellence and good design 4. Self-organizing teams 1. Deliver working software frequently 2. Working software primary measure 3. Maintain a constant pace indefinitely 5

1. Welcome changing requirements even late in development 2. Simplicity 3. Technical excellence and good design 4. Self-organizing teams 1. Satisfy the customer 2. Work together 3. Motivated individuals 4. Face-to-face conversation 5. Team reflects and adjusts its behavior accordingly 1. Deliver working software frequently 2. Working software primary measure 3. Maintain a constant pace indefinitely High results Inverted U Curve Low results Do More High results High results Low results Do More Low results Do More 6

Working software Responding to change Results People Individuals and interactions Customer collaboration Process Processes and tools Documentation Contract negotiation Following a plan 7