Agile Project Management Athanasios Podaras

Slides:



Advertisements
Similar presentations
Basic SDLC Models.
Advertisements

Agile Software Development کاری از : مهدی هوشان استاد راهنما : استاد آدابی.
AGILE DEVELOPMENT Outlines : Quick Look of agile development Agility
SOFTWARE DEVELOPMENT METHODOLOGIES Methodologies Waterfall Prototype model Incremental Iterative V-Model Spiral Scrum Cleanroom RAD DSDM RUP.
SDLC – Beyond the Waterfall
AgileMan Consulting So what the heck is Agile? It came about as a response to the high failure rate of software projects (> 60%), where failure means late,
THE SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)
Lean-Agile Software Development
Sharif University of Technology Session # 3.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
Where We Are Now. Where We Are Now Traditional PM versus Agile Methods Traditional PM Approach Concentrates on thorough, upfront planning of the entire.
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 Life Cycles ECE 417/617: Elements of Software Engineering
1 Software Testing and Quality Assurance Lecture 34 – SWE 205 Course Objective: Basics of Programming Languages & Software Construction Techniques.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Iterative development and The Unified process
2-1 Copyright © 2013 McGraw-Hill Education (Australia) Pty Ltd Pearson, Larson, Gray, Project Management in Practice, 1e C HAPTER 2 Popular Frameworks.
WHY AGILE IS FAILING IN LARGE ORGANIZATIONS twitter.com/mcottmeyer facebook.com/leadingagile.
Project Closure & Oversight Project Closure & Oversight Chapters 14 and
Chapter 11 McGraw-Hill/Irwin Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved.
Agile Software Development Brian Link
Chapter 5 Software Process Models. Problems with “Traditional” Processes 1.Focused on and oriented towards “large projects” and lengthy development time.
Tuesday, June 8 th, Agile Development-Successful Delivery & Implementing Across the Enterprise.
By Saravanan Bala. General Report 31 % of Software projects are cancelled 75 % of the software projects are considered failures by the people who initiated.
Chapter 2 Software processes. Topics covered Software process models Process activities Coping with change.
Software Development Overview CPSC 315 – Programming Studio Spring 2013.
2  Examine effects of using agile methods for creating Internet products on customer satisfaction and firm performance  Agile methods are informal,
1 Discipline vs. Agility. 2 Topics What is discipline? What is agility? What are the misconceptions? Contrasts and home grounds Five critical factors.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Agile Gintarė Bernotaitytė © 2013.
Project Management Software development models & methodologies
Software Engineering cosc 4359 Spring 2017.
Embedded Systems Software Engineering
Software Development Overview
Popular Frameworks and Methodologies
Introduction to Agile Software Development
Principles for Agile Development
Agile Training Day 2 November 17, 2015.
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Appendix B Agile Methodologies
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
Game Design, Development, and Technology
Fundamentals of Information Systems, Sixth Edition
Popular Frameworks and Methodologies
Valuable Project Management Tools and Techniques
Software Development methodologies
Software Engineering: A Practitioner’s Approach, 7/e Chapter 3 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Agile Software Development Brian Moseley.
Information Technology Project Management – Fifth Edition
Lecture Software Process Definition and Management Chapter 2: Prescriptive Process Models Dr. Jürgen Münch Fall
Software Engineering (CSI 321)
Copy rights  Exam Eligibility  Exam Pattern  Pre requisites  Content Distribution  Tools and Techniques  Domains and Tasks for.
Project Management and the Agile Manifesto
Popular Frameworks and Methodologies
How to Successfully Implement an Agile Project
Agile Software Processes
Agile Process: Overview
Creating an Agile Cultural Transformation
Project Lifecycle and IT Product Life Cycle
Appendix B Agile Methodologies
Agile Development.
Adapting Agile in Pharmaceutical Industries
Chapter 5: New and Emerging Process Methodologies
System Development Methods
Agile, Scrum and CMMI Methodologies
SD5953 Successful Project Management AGILE SOFTWARE DEVELOPMENT
Presentation transcript:

Agile Project Management Athanasios Podaras 2015-2016

Traditional PM versus Agile Methods Traditional PM Approach Concentrates on thorough, upfront planning of the entire project. Requires a high degree of predictability to be effective. Agile Project Management (Agile PM) Relies on incremental, iterative development cycles to complete less-predictable projects. Is ideal for exploratory projects in which requirements need to be discovered and new technology tested. Focuses on active collaboration between the project team and customer representatives.

Traditional Project Management versus Agile Project Management Design up front Continuous design Fixed scope Flexible Deliverables Features/requirements Freeze design as early as possible Freeze design as late as possible Low uncertainty High uncertainty Avoid change Embrace change Low customer interaction High customer interaction Conventional project teams Self-organized project teams TABLE 17.1

Agile Project Management Agile PM Is related to the rolling wave planning and scheduling project methodology. Uses iterations (“time boxes”) to develop a workable product that satisfies the customer and other key stakeholders. Stakeholders and customers review progress and re-evaluate priorities to ensure alignment with customer needs and company goals. Adjustments are made and a different iterative cycle begins that subsumes the work of the previous iterations and adds new capabilities to the evolving product.

Iterative, Incremental Product Development

Agile Project Management (cont’d) Advantages of Agile PM: Useful in developing critical breakthrough technology or defining essential features Continuous integration, verification, and validation of the evolving product. Frequent demonstration of progress to increase the likelihood that the end product will satisfy customer needs. Early detection of defects and problems.

Agile PM Principles Focus on customer value Iterative and incremental delivery Experimentation and adaptation Self-organization Continuous improvement

Popular Agile PM Methods Crystal Clear RUP (Rational Unified Process) Dynamic Systems Development Method (DSDM) Scrum Extreme Programming Agile Modeling Rapid Product Development (PRD) Lean Development

Applying Agile to Large Projects Scaling Is using several teams to work on different features of a large scale project at the same time. Staging Requires significant up-front planning to manage the interdependences of different features to be developed. Involves developing protocols and defining roles to coordinate efforts and assure compatibility and harmony.

Limitations and Concerns of Agile PM It does not satisfy top management’s need for budget, scope, and schedule control. Its principles of self-organization and close collaboration can be incompatible with corporate cultures. Its methods appear to work best on small projects that require only five-nine dedicated team members to complete the work. It requires active customer involvement and cooperation.