 Overview of agile project management  Key concepts and terminology  Available resources and tools  Applicability of agile project management to different.

Slides:



Advertisements
Similar presentations
Program Management School Agile & ADDIE Add-Up (AAAU) Elliott Masies Learning 2012 October 21-24, 2012.
Advertisements

AGILE DEVELOPMENT Outlines : Quick Look of agile development Agility
Agile Development Primer – Using Roundtable TSMS in an Agile Shop Michael G. Solomon Solomon Consulting Inc.
SDLC – Beyond the Waterfall
COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. 1 Agile documentation development methodology Giby Panicker and Judith Benjamin 1-Dec-2012.
Agile and Scrum: Executive Summary June 2, 2011 Bob Schommer, CSP, PMP, MCTS Senior Project Manager Skyline Technologies, Inc.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Clinton Keith CTO, High Moon Studios Agile Methodology in Game Development: Year 3.
Agile Project Management with Scrum
Process and tools Individuals and interactions over Following a plan Responding to change over Comprehensive documentation Working software over Contract.
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
Agile Process Models. Prescriptive models don’t work It is unrealistic to not have changes. Why? The Agile Manifesto: Individuals and interactions over.
An Introduction to Agile Project Management CHAPTER SEVENTEEN PowerPoint Presentation by Charlie Cook Copyright © 2014 McGraw-Hill Education. All Rights.
Agile development By Sam Chamberlain. First a bit of history..
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Managing a Project Using an Agile Approach and the PMBOK® Guide
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.
Agile Methodologies for Project Management By – Komal Mehta.
AgileCamp Presents: Scrum. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons Attribution 4.0.
Chapter 4 Agile Development
Agile Software Development Brian Link
What is Scrum Process? Where is it used? How is it better?
Chapter 4 An Agile View of Process
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.
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
Current Trends in Systems Develpment
By Saravanan Bala. General Report 31 % of Software projects are cancelled 75 % of the software projects are considered failures by the people who initiated.
© 2013 Scrum Inc. Burndown Chart Makes Team’s Velocity and its Implications Visible Sprint/Time Points Sprint/Time Points.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Agile Assessment Gadi Lifshitz, Ayelet Kroskin, Barak Yagour, Yael Dubinsky.
THE AGILE MENTALITY CHAPTER Topics  Why Use Agile and Scrum?  Agile Development –Manifesto for Agile Software Development  Scrum Methodology.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
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,
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 4 Agile Development Discussion of Agile Development and Agile Process.
Software Engineering (CSI 321) An Agile View of Process 1.
Presentation from: See Also: scrumreferencecard.com/ScrumReferenceCard.pdf.
Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.
#AgileEd. Using Agile in the Classroom Cindy Royal, Associate Professor Texas State University slideshare.net/cindyroyal #AgileEd.
Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
SCRUM © University of LiverpoolCOMP 319slide 1. SCRUM history In 1986, Hirotaka Takeuchi and Ikujiro Nonaka More an observation of good practise in manufacturing.
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
JASS 2006 Agile Software Development. JASS 2006 Agenda.
TIK 302 Rekayasa Perangkat Lunak Agile Proses. Agile View of Process Represents a reasonable compromise between conventional software engineering for.
Created By:-
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Agile Gintarė Bernotaitytė © 2013.
CMPS 116 Software Design Project. Introduction Instructor: Dr. Huahai Yang IBM Research – Almaden Former SUNY Albany Programming.
Agile/XP Introduction
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Manifesto for Agile Software Development
Agile Project Management
AGILE SCRUM METHODOLOGY
Agile Training Day 2 November 17, 2015.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Agile Software Development Brian Moseley.
Navigating an Agile Transformation
Rapid software development
Tim Hirner - Flagship Speakers January 23, 2014
روش‌های سريع الانتقال (چابک) توسعه نرم افزار
Agile Process: Overview
Adjective: Able to move quickly and easily. Principles and Values
Topic 1: Introduction to the Module and an Overview of Agile
Presentation transcript:

 Overview of agile project management  Key concepts and terminology  Available resources and tools  Applicability of agile project management to different types of IT projects

TraditionalAgile Product defined upfrontProduct evolves Requirements defined upfrontFeatures developed overtime Adherence to requirements & planResponsiveness to changing needs Perfection focussedGood-enough focussed

RequirementsDesignImplementationTestingMaintenance

 SCRUM  Feature Driven Development (FDD)  Crystal Methods  Extreme Programming  Dynamic Systems Development Method (DSDM)

Product backlogRelease 1 Sprint 1Sprint 2Sprint 3Sprint 4 Release 2 Sprint 1Sprint2Sprint 3Sprint 4

 Can have requirements (e.g., legislative)  Focus is on features (stories, tasks, tests)  Product backlogs consist of features  Features prioritized into releases & sprints

 Product testing can be built into a sprint/iteration  Product testing can be a sprint for a release  User-acceptance testing important  Product issues/bugs addressed daily & by sprint end

TraditionalAgile Project sponsorProduct owner Project managerScrum master / project manager The team Developers Analyst Testers The team Developers Analyst Testers

Source: Agile Project Management, Second Edition, Jim Highsmith  People & communication = successful projects  Prioritize features & deliver working deliverables early  Focus on what ‘can’ be done within time & budget (positive vs. haggling)  Get feedback regularly and modify scope accordingly Value Individuals and interactions over processes and tools Working software [products] over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan

In order to work agile projects need:  Co-located teams (collaborative teams)  Daily meetings (daily scrums)  Regular product owner involvement

 No Earned Value or baselining  Focus is on velocity & burndown charts  Concept of story points (vs. time estimates)  Velocity: progress calculated by summing up the number of story points completed during a sprint/ iteration  Sprint burndown: Effort remaining vs. date  Project burndown: Points outstanding vs. iteration

 Software development projects  Feature, module, plug-in development  Web application & mobile apps

Online  “Scrum Master in Under 10 Minutes” otation_id=annotation_ otation_id=annotation_ Books  Agile Project Management: Creating Innovative Products, Second Edition, Jim Highsmith  Managing Agile Projects: The Project Management Essentials Library, Kevin Aguanno Tools  VersionOne Courses  Agile Project Management, Waterloo Centre for Extended Learning

???