Colin Weaver The Eleven Essential Behaviours of Successful Agile Project Teams.

Slides:



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

Chapter: 3 Agile Development
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
Project Management – An Overview Project as a metaphor – a way to approach a series of activities Contexts – construction managementt, IT development,
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.
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.
Introduction to Agile.
Software engineering Process models Pavel Agejkin.
How Agile Are You? Larry Apke Agile Expert
The Two Faces of Project Management Bendik Bygstad, NITH IFI, 25.Sept 2009.
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.
The Agile Primer July 2008 © ThoughtWorks 2008.
Agile Web Development C. Daniel Chase University of Colorado at Boulder.
Developed by Reneta Barneva, SUNY Fredonia Agile 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.
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,
Why (or When) Agile Fails Creating high performance software delivery teams.
Jeff Briggs Senior Consultant Capstone Consulting.
#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
Chapter 5 Agile Development Moonzoo Kim KAIST
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?
Teaching Agile Methods CSEE&T 2017, Savannah, Georgia
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
The Manifesto for Agile Software Development
Projects, Assignments, and other Assessments
Agile Development.
Presentation transcript:

Colin Weaver The Eleven Essential Behaviours of Successful Agile Project Teams

The Agile Manifesto Individuals and interactions Working software Customer collaboration Responding to change "That is, while there is value in the items on the right, we value the items on the left more." over processes and tools. over comprehensive documentation. over contract negotiation. over following a plan.

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. Principles Behind The Agile Manifesto

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 maximising the amount of work not done -- is essential. The best architectures, requirements, and designs emerge from self-organising teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly. Principles Behind The Agile Manifesto

Product Backlog Sprint Backlog Daily Scrum Meeting Potentially Shippable Product Increment 24 hrs 2-4 weeks

11

1

Courage

If you’re going to fail, fail fast satisfy the customer Welcome changing requirements Deliver working software frequently Business people and developers must work together daily motivated individuals/trust face-to-face conversation Working software as a measure constant pace technical excellence and good design Simplicity self-organising the team reflects Courage

2

Desire to Improve

Courage Improve satisfy the customer Welcome changing requirements Deliver working software frequently Business people and developers must work together daily motivated individuals/trust face-to-face conversation Working software as a measure constant pace technical excellence and good design Simplicity self-organising the team reflects Desire to Improve Agile is a mindset change

3

Collaborative

Courage Improve Collaborate satisfy the customer Welcome changing requirements Deliver working software frequently Business people and developers must work together daily motivated individuals/trust face-to-face conversation Working software as a measure constant pace technical excellence and good design Simplicity self-organising the team reflects Collaborative Encourage rather than criticise

4

Openness

satisfy the customer Welcome changing requirements Deliver working software frequently Business people and developers must work together daily motivated individuals/trust face-to-face conversation Working software as a measure constant pace technical excellence and good design Simplicity self-organising the team reflects Courage Improve Collaborate Openness Be honest / admit weaknesses

5

Trust

satisfy the customer Welcome changing requirements Deliver working software frequently Business people and developers must work together daily motivated individuals/trust face-to-face conversation Working software as a measure constant pace technical excellence and good design Simplicity self-organising the team reflects Courage Improve Collaborate OpennessTrusting Trust “You must trust and believe in people or life becomes impossible”

6

Simplicity

"The ability to simplify means to eliminate the unnecessary so that the necessary may speak" - Hans Hofmann Maximise what you don't do. satisfy the customer Welcome changing requirements Deliver working software frequently Business people and developers must work together daily motivated individuals/trust face-to-face conversation Working software as a measure constant pace technical excellence and good design Simplicity self-organising the team reflects Courage Improve Collaborate OpennessTrustingSimplicity

7

Pride

Courage Improve Collaborate OpennessTrustingSimplicity satisfy the customer Welcome changing requirements Deliver working software frequently Business people and developers must work together daily motivated individuals/trust face-to-face conversation Working software as a measure constant pace technical excellence and good design Simplicity self-organising the team reflects Pride Be the best you can

8

Focused

Courage Improve Collaborate OpennessTrustingSimplicity satisfy the customer Welcome changing requirements Deliver working software frequently Business people and developers must work together daily motivated individuals/trust face-to-face conversation Working software as a measure constant pace technical excellence and good design Simplicity self-organising the team reflects PrideFocused Deliver business value

9

Motivated

Courage Improve Collaborate OpennessTrustingSimplicity satisfy the customer Welcome changing requirements Deliver working software frequently Business people and developers must work together daily motivated individuals/trust face-to-face conversation Working software as a measure constant pace technical excellence and good design Simplicity self-organising the team reflects PrideFocusedMotivated Deliver the team commitment

10

Proactive

Courage Improve Collaborate OpennessTrustingSimplicity satisfy the customer Welcome changing requirements Deliver working software frequently Business people and developers must work together daily motivated individuals/trust face-to-face conversation Working software as a measure constant pace technical excellence and good design Simplicity self-organising the team reflects PrideFocusedMotivatedProactive Contribute and help the team find solutions

11

Responsible

Courage Improve Collaborate OpennessTrustingSimplicity satisfy the customer Welcome changing requirements Deliver working software frequently Business people and developers must work together daily motivated individuals/trust face-to-face conversation Working software as a measure constant pace technical excellence and good design Simplicity self-organising the team reflects PrideFocusedMotivatedProactive Responsible Collective responsibility. Succeed or fail as a team

Agile Principles [ ] Good Governance Agile Evolved