Principles of Agile management of software development project 28 November 2014.

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.
Steve Collins Richland County IT Manager Agile.  Have Fun  Learn About Agile  Tell Some Stories.
Software Development Methodologies 1. A methodology is: A collection of procedures, techniques, principles, and tools that help developers build a computer.
Slide Set to accompany Web Engineering: A Practitioner’s Approach
Agile Project Management with Scrum
NAUG NAUG Knowledge Evening – th February 2007.
Agile development By Sam Chamberlain. First a bit of history..
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.
An Agile View of Process
Introduction to Agile.
Software engineering Process models Pavel Agejkin.
DE (est) 2. -Joe Justice What does HR output? Exercise.
DE (est) 2. -Steve Denning -Joe Justice What do these groups output? Exercise.
How Agile Are You? Larry Apke Agile Expert
AgileCamp Presents: Scrum. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons Attribution 4.0.
Dr. Tom WayCSC Software Processes CSC 4700 Software Engineering.
1 Agile Methodology & Programming Ric Holt July 2009.
Software Engineering Modern Approaches
Agile Programming Principles.
The Agile Primer July 2008 © ThoughtWorks 2008.
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.
OPM: the USAJOBS Product Owner Perspective By Alesia Booth & Richard Cheng.
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-
When is Agile the Best Project Management Method? Lana Tylka.
Chapter 5 애자일 개발 Agile Development
Software Engineering Saeed Akhtar The University of Lahore Lecture 5 Originally shared for: mashhoood.webs.com.
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.
By salt-productions. Agenda  RUP  Agile Practices  Scrum  Putting it all together with & for People.
Why (or When) Agile Fails Creating high performance software delivery teams.
Jeff Briggs Senior Consultant Capstone Consulting.
Software Engineering (CSI 321) An Agile View of Process 1.
#AgileEd. Using Agile in the Classroom Cindy Royal, Associate Professor Texas State University slideshare.net/cindyroyal #AgileEd.
- 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
The Agile Manifesto Some thought starters for Ogilvy on how to work with Agile and SCRUM approaches to managing projects.
A Noble Product Owner – Who Can Find? Kim Hardy, Agile Coach CSM & SAFe Program Consultant.
Agile Introduction Emerson Murphy-Hill. Agile Manifesto/Alliance XP, SCRUM, DSDM, Adaptive Software Development, Crystal, FDD February 2001 (Snowbird,
Steve Lundquist, PMP, M.Sc..  As a PMP certified program manager, there are numerous tools, processes, methodologies, and tricks that are available to.
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.
Transforming UX with Fluid UI Nick Goupinets Lead Developer, UTS McMaster University.
AGILE SOFTWARE DEVELOPMENT. Agile software development : Agile software development refers to a group of software development methodologies that promotes.
Baby Steps to Agility How to Grow Into Agile. A little about me A little about Agile Growing into Agile Questions Goals.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
Embedded Systems Software Engineering
Agile Project Management and the yin & yang of
Introduction to Agile Software Development
Principles for Agile Development
Agile Training Day 2 November 17, 2015.
Agile Training – Agile Overview
Chapter 5 Agile Development
Project Management and the Agile Manifesto
Rosa María Torres de Paz
The Agile Manifesto is based on 12 principles
Introduction to Agile Blue Ocean Workshops.
Adjective: Able to move quickly and easily. Principles and Values
Chapter 3: Agile Software Processes
The Manifesto for Agile Software Development
Agile Development.
Presentation transcript:

Principles of Agile management of software development project 28 November 2014

11/28/2014 Agenda Introduction~5 min Contest ~ 40 min Theoretic overview~45 min

11/28/2014

My Team

11/28/2014 Agile Branches  Scrum  Extreme Programming  LEAN

11/28/2014 Agile in Barclays

11/28/2014 Aircrafts Contest

11/28/ minutes Team has to  choose team leader  team name  team logo  bend out a prototype of aircraft 3 minutes End

11/28/2014 1st Iteration

11/28/2014 Planning  In 2 minutes you have to organize into aircraft bending and estimate your capacity – how many aircrafts you can bend in 1 minute. Aircrafts must be bent exactly as prototype and have logo.  You will receive one point for for each planned aircraft that you will build and fly. You will not get point for aircrafts built above the plan. And you will get penalty of two point for each aircraft that you planned but not built.

11/28/ minutes  Estimate capacity of your capacity – how many aircrafts you can bend in 1 minute. Aircrafts must be bent exactly as prototype and have logo.  You will receive one point for for each planned aircraft that you will build and fly. You will not get point for aircrafts built above the plan. And you will get penalty of two point for each aircraft that you planned but not built. 2 minutes End

11/28/2014 Bending – 1 minute

11/28/ minute End

11/28/2014 Flying – 1 minute

11/28/ minute End

11/28/2014 Results

11/28/2014 Retrospective  In the next stage you will have 2 minutes to capture as many positive and negative factors that have influenced your result as you can and provide actions to improve them in the next iteration. You will get half point for each.

11/28/ minute  Positive factors  Negative factors  Actions to improve 1 minute End

11/28/2014 2nd Iteration

11/28/2014 Planing – 1 minute

11/28/ minute  Estimate capacity of your capacity – how many aircrafts you can bend in 1 minute. Aircrafts must be bent exactly as prototype and have logo. 1 minute End

11/28/2014 Bending – 1 minute

11/28/ minute End

11/28/2014 Flying – 1 minute

11/28/ minute End

11/28/2014 Results and discussion

11/28/2014 Overview of Agile process and principles

11/28/2014

 Self-organizing  T principle  Motivated individuals

11/28/2014 Communication  Face-to-face  Business peole and developers must work together daily throughout the project  Continuous process improvement through feedback

11/28/2014 Process  Timely, regular and reliable delivery of business value through short sprints (iterations)  Sustainable development. Team velocity

11/28/2014

Waste elimination in the delivery process

11/28/2014 Product Backlog  Backlog grooming  Welcome changing requirements. Agile processes harness change for the customer‘s competitive advantage

11/28/2014 Planning  We are not good at estimating, but we are good at comparison

11/28/2014 Blog page

11/28/2014 Estimation

11/28/2014 Planning

11/28/2014 Construction Simplicity - the art of maximizing the amount of work not done – is essential The best architectures, requirements, and designs emerge from self-organizing teams

11/28/2014 Delivery and Testing Potentially deployable increments Working software is the primary mesure of progress UAT - User acceptance testing

11/28/2014 Review and Retrospective

11/28/2014