The Agile Primer July 2008 © ThoughtWorks 2008.

Slides:



Advertisements
Similar presentations
Keith McMillan Principal, Adept Technologies Copyright (C) 2008, Adept Technologies llc.
Advertisements

Colin Weaver The Eleven Essential Behaviours of Successful Agile Project Teams.
E X treme Programming & Agile Modeling Copyright © 2003 Patrick McDermott UC Berkeley Extension
Software Development Methodologies 1. A methodology is: A collection of procedures, techniques, principles, and tools that help developers build a computer.
The Role of Project Managers in Agile Darren Wilmshurst ACIB CITP
Slide Set to accompany Web Engineering: A Practitioner’s Approach
Agile Project Management with Scrum
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.
Agile Methods.
Applying Agile to Everyday Work Will Oleksy Lead Agile Coach IT Services an ERM IT Center for Excellence.
Agile Principles Suradet Jitprapaikulsarn 1. What is Agility? Effective (rapid and adaptive) response to change Effective communication among all stakeholders.
Does it work with Data Warehouses?. “We are uncovering better ways of developing software by doing it and helping others do it. Through this work we.
An Agile View of Process
Introduction to Agile.
Software engineering Process models Pavel Agejkin.
The Agile/Non-Agile Divide -- A first taste!
How Agile Are You? Larry Apke Agile Expert
The Two Faces of Project Management Bendik Bygstad, NITH IFI, 25.Sept 2009.
1 Staffordshire UNIVERSITY School of Computing Slide: 1 Prototyping Agile Software Development 2 Agile Methods and Software Architectures.
The Two Faces of Project Management Bendik Bygstad, NITH IFI, 16.Sept 2008.
1 Agile Methodology & Programming Ric Holt July 2009.
Software Engineering Modern Approaches
Agile Programming Principles.
Agile Web Development C. Daniel Chase University of Colorado at Boulder.
Developed by Reneta Barneva, SUNY Fredonia Agile Development.
Chapter 4 Agile Development
Agile Methods. Agile Process/Method lightweight processes/methods that can be used to manage and control software and product development using iterative,
AgileCamp Presents: Agile 101. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons Attribution.
Project Workflow. How do you do it? -Discussion-
Chapter 5 애자일 개발 Agile Development
CS1: Classic Software Life Cycle “Waterfall” method: 1.Requirements/Analysis Determine the problem to be solved – client-centered 2.Specification.
AGILE COTS Václav Pergl We are uncovering better ways of developing software by doing it and helping others do it. Through this work.
1 11/21/2015 ã 2007, Spencer Rugaber Agile Manifesto February, 2001 XP, SCRUM, DSDM, Adaptive Software Development,
UX meets XP. Overview of core approaches to creating interactive software Waterfall, iterative design, Agile Hybrid methods of evaluation H&P Chapter.
Why (or When) Agile Fails Creating high performance software delivery teams.
Jeff Briggs Senior Consultant Capstone Consulting.
#AgileEd. Using Agile in the Classroom Cindy Royal, Associate Professor Texas State University slideshare.net/cindyroyal #AgileEd.
#2-What is Agile? Why Agile? Subtopics 1- Agile motivation for software / systems 2- Agile tenets and principles 3- Agile as a risk mitigation strategy.
- 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.
Chapter 3 Agile Development
Module 2: What is Agile? Why use it? TLO: Given a DoD program involved in software development, the student will recognize situations where applying agile.
The Agile Manifesto Some thought starters for Ogilvy on how to work with Agile and SCRUM approaches to managing projects.
Agile, TOGAF and Enterprise Architecture: Will They Blend? Kennisavond IlionX 7 mei 1 Danny Greefhorst
Agile Introduction Emerson Murphy-Hill. Agile Manifesto/Alliance XP, SCRUM, DSDM, Adaptive Software Development, Crystal, FDD February 2001 (Snowbird,
By: Isuru Abeysekera AGILE DEVELOPMENT. WHAT IS AGILE DEVELOPMENT? Broad term used to describe several methods for a development process Introduced in.
Industrial Software Development Process Bashar Ahmad RISC Software GmbH.
© 2014 IBM Corporation “Leaders Guide to Radical Management” for DevOps with Steve Denning Chapters 6 and 7: From Bureaucracy to Dynamic Linking by Delivering.
Baby Steps to Agility How to Grow Into Agile. A little about me A little about Agile Growing into Agile Questions Goals.
Project Workflow.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
Embedded Systems Software Engineering
Agile Project Management
Agile Project Management and the yin & yang of
Introduction to Agile Software Development
Principles for Agile Development
Jenna Maghie, Policy Officer
The Agile/Non-Agile Debate
Agile Training Day 2 November 17, 2015.
#2-What is Agile? Why Agile?
Project Management and the Agile Manifesto
Agile Software Development Paradigms
Rosa María Torres de Paz
The Agile Manifesto is based on 12 principles
Introduction to Agile Blue Ocean Workshops.
How Strong is Your Agile Foundation
Adjective: Able to move quickly and easily. Principles and Values
Chapter 3: Agile Software Processes
Projects, Assignments, and other Assessments
Agile Development.
Presentation transcript:

The Agile Primer July 2008 © ThoughtWorks 2008

Hopes and Concerns © ThoughtWorks 2008

Our Roadmap © ThoughtWorks 2008 Software Engineering Agile Methods Agile Values & Principles Agile Practices

Our Roadmap © ThoughtWorks 2008 Software Engineering Agile Methods Agile Values & Principles Agile Practices

The Start © ThoughtWorks 2008

We started with Software Engineering © ThoughtWorks 2008

NASA’s Defect Density Pretty good, right? © ThoughtWorks 2008

NASA’s Defect Density (another data point) © ThoughtWorks 2008

Other Heavy Weight Methodologies SEI/IEEE Project Standards and Definitions Waterfall Project Management Body of Knowledge (PMBOK) Requirements Engineering Sometimes, heavy weight methodologies work, but there are extensive costs, and the risk in using them in dynamic environments is high. © ThoughtWorks 2008

Our Roadmap © ThoughtWorks 2008 Software Engineering Agile Methods Agile Values & Principles Agile Practices

© ThoughtWorks 2008 Agile Scrum XP Crystal Family Lean Software Development DSDM FDD ASD RUP (Rational Unified Process) CMMI ( Capability Maturity Model Integration ) Iterative and Incremental Development (1930) 2 Pass Development (1970) Mercury Space Program (Iterative) (1957)

Our Roadmap © ThoughtWorks 2008 Software Engineering Agile Methods Agile Values & Principles Agile Practices

Agile Manifesto © ThoughtWorks 2008 OVER Processes and Tools Individuals and Interactions OVER Comprehensive Documentation Working Software OVER Contract Negotiation Customer Collaboration OVER Following a Plan Responding to Change That is, while there is value on the right, we value the items on the left more. We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

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

Our Roadmap © ThoughtWorks 2008 Software Engineering Agile Methods Agile Values & Principles Agile Practices

Waterfall Methodology © ThoughtWorks 2008 Effort Analysis Design Coding Testing Deployment Time

Agile Methodology © ThoughtWorks 2008

Iterations Common Agile Practices © ThoughtWorks 2008 Release User Stories User Stories User Stories User Stories User Stories User Stories User Stories User Stories Iterations

Daily stand up Iteration Planning Showcase Retrospective Story writing (future) Development (current iteration) Testing (current iteration) Start of Iteration Co located teams Code reviews What an iteration might look like © ThoughtWorks 2008

Iteration Planning Story writing (future) Development (current iteration) Testing (current iteration) Start of Iteration A specific practice… Daily stand up © ThoughtWorks 2008

The daily stand up… No worries Sure I guess so I spoke to the infrastructure team yesterday and we won’t get a build environment until next week. Can we make do with what we have for now? Hey, that’s great. I’ll need that when I get to the overdue bill story later this week. Can you show me that after stand up? Yesterday, I tried working on that invoice report but couldn’t because our test environment wasn’t up Let’s go see Dylan’s team after this to try and resolve it I worked on the billing agent yesterday and refactored out a common utility for the printout of the bill Today, we’ve got the customer showcase for the last iteration. I’m sure we can get some useful feedback and would be good if everyone heard it firsthand. I’ll be there Me too © ThoughtWorks 2008

Iteration Planning Start of Iteration A specific practice… Daily stand up Co located teams Code reviews Story writing (future) Development (current iteration) Testing (current iteration) © ThoughtWorks 2008

Co-located team + Code reviews This is turning out harder than I thought. Maybe I should for help. Hey Ava, Can I get you to look at this? Sure I’m currently in the middle of … and keep seeing … What do you reckon I should do? So it’s a bit like … and a bit like … Hang on! We can do this and it’d be much simpler Hey Connor. I heard you talk about adding in … When we talked about that story, you remember that the user would be happy with just … instead of that? Really? That makes it really simple then! I’m not sure if I really understand the problem. Let’s white board this Maybe we can try … or … Right! That’s great. Ok, so first … and then … right? type type type... Yup! type type type... © ThoughtWorks 2008