SE503 Advanced Project Management Dr. Ahmed Sameh, Ph.D. Professor, CS & IS Agile Principles: Customers and Products.

Slides:



Advertisements
Similar presentations
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 1.
Advertisements

Chapter: 3 Agile Development
BAM! Business Analysis Methodologies. Change-driven or Plan-driven?
Agile Planning Dealing with Reality. Reality Basic agile principle – don’t expect static plans to hold, be flexible and expect changes.
A GILE SOFTWARE DEVELOPMENT : S ELF - ORGANIZING TEAM Egle Niitvägi TTU Health Care Technology.
Steve Collins Richland County IT Manager Agile.  Have Fun  Learn About Agile  Tell Some Stories.
PROC-1 3. Software Process. PROC-2 What’s a process? Set of activities in creating software It involves creativity –hard to automate –Requires human judgment.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
 © Ian Sommerville A software process model is an abstract representation of a process. It presents a description of a process from some particular perspective.
Alternate Software Development Methodologies
SCRUM John Drew. SCRUM - overview Scrum is a project management discipline that has evolved since the early 1990s to deliver software that meets business.
Ryan G. Rosandich, Ph.D. Associate Professor, MIE Agile Project Management.
CS 5150 Software Engineering
Software Engineering.
COMP 350: Object Oriented Analysis and Design Lecture 2
Software Engineering Lecture No:12. Lecture # 7
An Agile View of Process
AGILE DELIVERY FACILITATION Agile Project Manager should see his stakeholders as kids and aim to help them be successful in their respective goals, each.
How to Manage the Organizational Change LaMarsh & Associates, Inc.
SE503 Advanced Project Management Dr. Ahmed Sameh, Ph.D. Professor, CS & IS The Agile Revolution.
Object-Oriented Analysis and Design Iterative Development and the Unified Process.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
SE503 Advanced Project Management Dr. Ahmed Sameh, Ph.D. Professor, CS & IS Agile Principles: Leadership-Collaboration.
1 Chapter 5 Practice: A Generic View Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman.
Software Processes.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Agile Development In 2001, a group called the “Agile Alliance” signed a “manifesto” that stated: Individuals and Interactions over processes and tools.
Industrial Software Project Management Some views on project managing industrial and business software projects.
Software Engineering Management Lecture 1 The Software Process.
1 Software Process Models-ii Presented By; Mehwish Shafiq.
Project Management for Agile Projects. Introduction The Project Management Job Day to day administration Managing the process Managing external relationships.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
General Capacity Building Components for Non Profit and Faith Based Agencies Lakewood Resource and Referral Center nd Street, suite 204 Lakewood,
Chapter 2 Iterative, Evolutionary, and Agile You should use iterative development only on projects that you want to succeed. - Martin Fowler 1CS
High Performance Work Systems (HPWS). HR Alignment Planning and Job Design Recruiting and Selection Training and Development Performance Management Compensation.
Chapter 2 – Software Processes Lecture 2 1Chapter 2 Software Processes.
SE503 Advanced Project Management Dr. Ahmed Sameh, Ph.D. Professor, CS & IS Introduction.
Chapter 2 Software processes. Topics covered Software process models Process activities Coping with change.
CS CS 5150 Software Engineering Lecture 2 Software Processes 1.
SE503 Advanced Project Management Dr. Ahmed Sameh, Ph.D. Professor, CS & IS The Explore Phase (Ch. 7)
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
AP-1 4. Agile Processes. AP-2 Agile Processes Focus on creating a working system Different attitude on measuring progress XP Scrum.
SE503 Advanced Project Management
Chapter 3 Agile Development
WATERFALL DEVELOPMENT MODEL. Waterfall model is LINEAR development lifecycle. This means each phase must be completed before moving onto the next!!! WHAT.
Stand Up Comedy Project/Product Management
Agile. Processes Waterfall Traditional With prototyping Sprial Agile Dynamic Systems Development Method (DSDM) Scrum Crystal eXtreme Programming (XP)
Chapter 2 – Software Processes Lecture 2 1Chapter 2 Software Processes.
SE503 Advanced Project Management Dr. Ahmed Sameh, Ph.D. Professor, CS & IS Critical Chain Project Management.
10 key principles of agile software development
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
CS223: Software Engineering Lecture 16: The Agile Methodology.
SE503 Advanced Project Management Dr. Ahmed Sameh, Ph.D. Professor, CS & IS Agile PM Issues (Ch. 9 and Ch. 10)
CS 4500: Software Development Software Process. Materials Sommmerville Chapters 1, 2 and 3 Software Cycle and Models:
TIK 302 Rekayasa Perangkat Lunak Agile Proses. Agile View of Process Represents a reasonable compromise between conventional software engineering for.
Agile Center of Excellence. Richard K Cheng Agile is just a high level concept.
SOFTWARE DEVELOPMENT Presented By : Emporiumtech This presentation is brought you by
CS 389 – Software Engineering Lecture 2 – Part 2 Chapter 2 – Software Processes Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed.
Chapter 5 Agile Development Moonzoo Kim KAIST
SE503 Advanced Project Management
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
Game Design, Development, and Technology
COMP 350: Object Oriented Analysis and Design Lecture 2
How to Successfully Implement an Agile Project
Chapter 2 Software Processes
Chapter 2 – Software Processes
SNS College of Engineering Coimbatore
Agile software development
Presentation transcript:

SE503 Advanced Project Management Dr. Ahmed Sameh, Ph.D. Professor, CS & IS Agile Principles: Customers and Products

Customer Value Through Innovative Products Focus on delivering customer value Iterative feature-based delivery Technical excellence

Project Types Production – Defined outcome – Optimization – Planning and control – Administrative compliance – Product focus Exploration – Defined vision – Innovation – Agile execution – Iterative delivery of customer value – Customer focus

Customer Value What they are willing to pay Meeting expectations – Product performance (now and later) – Cost/budget – Schedule/delivery Expectations and requirements – Requirements are fixed and stated up front – Expectations evolve with the project

Customers value… Innovation Adaptability Tangible progress and delivery Ease of use and/or implementation Technical excellence

Minimize Compliance Activities Little customer value Tend to grow, not shrink “We don’t ever want that to happen again” Some compliance is necessary – Internal – External – Minimizing it increases its importance Compliance stifles creativity and innovation

Project Participants Deliver Value Everyone has the vision – Goals known – Customer known – Motivated, self-directed participants Decision making at the lowest level

Iterative Development Short iterations Real deliverables Incremental improvements Lower cost commitment per iteration Product representations – Models – Simulations – Prototypes

Earlier Benefits, Reduced Risk Tradeoffs and decisions as early as possible Realistic evaluations and expectations Frequent reviews and communication Frequent customer feedback Re-evaluation of project priorities Risk control – Technical risk – Feature risk

Technical Excellence Agile methods seem loose, undisciplined Customers value technical excellence Technology evolves rapidly Technical excellence is more important than administrative excellence Agile project managers are champions of technical excellence