Dr. Rob Hasker copyright 2012-2014 by Mark J. Sebern, Robert W. Hasker.

Slides:



Advertisements
Similar presentations
Chapter: 3 Agile Development
Advertisements

© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Can’t Live With It, Can’t.
Copyright © by Mark J. Sebern Software Engineering Process I Dr. Rob Hasker L-331, hasker (Adapted.
Kanban & Gunnison’s Visual Test Management Solution Presented to: Gunnison Date: 4/25/2013.
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.
Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger
29 September Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will.
Adopting Agile THE PRACTICES BEHIND THE THEORY. Agile Manifesto Individuals and interactions over process and tools Working software over comprehensive.
Where We Are Now. Where We Are Now Traditional PM versus Agile Methods Traditional PM Approach Concentrates on thorough, upfront planning of the entire.
© AgiliX Agile Development Consulting Agile Software Architecture Cesario Ramos.
Copyright © 2012 by Mark J. Sebern Technical Debt What is debt (in a financial sense)?
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall B.1.
An Introduction to Agile Project Management CHAPTER SEVENTEEN PowerPoint Presentation by Charlie Cook Copyright © 2014 McGraw-Hill Education. All Rights.
Chapter 6 Prototyping, RAD, and Extreme Programming
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Agile Project Management PMI Metrolina PDD Saturday September 27, 2014 UNCC Uptown Mike Ryan.
An Agile View of Process
Introduction to Agile.
An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
WHY AGILE IS FAILING IN LARGE ORGANIZATIONS twitter.com/mcottmeyer facebook.com/leadingagile.
SE503 Advanced Project Management Dr. Ahmed Sameh, Ph.D. Professor, CS & IS The Agile Revolution.
Agile Software Development Brian Link
SE503 Advanced Project Management Dr. Ahmed Sameh, Ph.D. Professor, CS & IS Agile Principles: Leadership-Collaboration.
Agile Modeling Theory. 2 Agile Modeling (AM) AM is a chaordic, practices-based process for modeling and documentation AM is a collection of practices.
The Successful Business Analyst’s Role in the Scaled Agile Framework®
Balanced Scorecard Bruce C Hartman MGT 400. Operating Assumptions for the Information Age Cross Functions Links in Supply Chains Customer Segments Global.
Dr. Rob Hasker copyright by Mark J. Sebern, Robert W. Hasker.
Copyright © 2012 by Mark J. Sebern Scrum Overview (from
University of Southern California Center for Systems and Software Engineering Agile Project Management Tools Supannika Koolmanojwong CSCI 577a.
The Confounding World of Process Methodologies By Thelma Hataria.
Basic Approach Development driven by time boxing May sacrifice requirements in order to keep schedule (time boxed) Steer project as you go based on user.
Copyright © by Mark J. Sebern Software Engineering Process I The case for agile processes.
Pragmatic Testing in Agile Projects Dr Stuart Reid Testing Solutions Group Test Management Summit, London 28 th January, 2009.
SE503 Advanced Project Management Dr. Ahmed Sameh, Ph.D. Professor, CS & IS Agile Principles: Customers and Products.
Foundations and Evolutions
Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
Sprint Plans and Burndown Charts David Millard | davidmillard.org.
Dr. Rob Hasker. What if every project used Scrum?  Why might Scrum not be perfect for every project? Hard to get the big picture Early choices may have.
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.
It’s Agile …. like! A Corkman’s introduction to Agile software delivery.
Introduction Requirements and the Software Lifecycle (3)
A Kanban Technique Joshua Rowell Agile Coach & DARK MATTER PLANNING.
You Don’t Need to Change Survival is Optional Gaetano Agile42.
Dr. Rob Hasker. Should every project use Scrum?  When might Scrum not be an appropriate model?  What are some of its limitations? Hard to get the big.
Leffingwell et al. © 2015 Scaled Agile, Inc. All Rights Reserved 1 Foundations of the Scaled Agile Framework ® Values, Principles, Practices, Implementation.
Copyright 2015, Robert W. Hasker. Classic Model Gathering Requirements Specification Scenarios Sequences Design Architecture Class, state models Implementation.
Think Scrum, act Scrum Scrum Practitioner like a boss Thibault Clavier.
TIK 302 Rekayasa Perangkat Lunak Agile Proses. Agile View of Process Represents a reasonable compromise between conventional software engineering for.
Kanban Advanced Software Engineering Dr Nuha El-Khalili.
Agile = regular iterations, releases time-boxed incremental regular heartbeat streamlined collaboration co-located team on-site customer face-face communication.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
3-Basic Agile Concepts Subtopics 1-The agile methods landscape 2-Common agile concepts and practices 3-Differences between traditional development and.
Agile Project Management Athanasios Podaras
CEN 4010 Intro to Software Engineering Professor Alex Roque
Appendix B Agile Methodologies
Disciplined Agile Principles
Introduction to Eclipse Process Framework: EPF Composer and OpenUP
By: By: Agile Scrum Master Online Training.
Case Studies Motivating Efficiency as a Spendable Quantity
CSCE 741 Software Process Lecture 04 Availability
CEN 4010 Intro to Software Engineering Professor Alex Roque
Project Management and the Agile Manifesto
How to Successfully Implement an Agile Project
Scrum Overview.
CS 577b: Software Engineering II
Appendix B Agile Methodologies
09 | Kanban Steven Borg | Co-Founder & Strategist, Northwest Cadence
Business Agile 101 Learn the basics of the agile methodology and how you and your team can take steps to apply it to your workflow.
Presentation transcript:

Dr. Rob Hasker copyright by Mark J. Sebern, Robert W. Hasker

Agile Principles  Variability and uncertainty  Prediction and adaptation  Validated learning  Work in progress  Progress  Performance copyright by Mark J. Sebern, Robert W. Hasker (From Essential Scrum)

Variability and Uncertainty  Enhance helpful variability  Employ iterative and incremental development  Leverage variability through inspection, adaption, and transparency  Reduce all forms of uncertainty simultaneously copyright by Mark J. Sebern, Robert W. Hasker

Prediction & Adaptation  Keep options open  Accept that you can’t get it right up front  Favor an adaptive, exploratory approach  Embrace change in an economically sensible way  Balance predictive up-front work with adaptive just-in-time work copyright by Mark J. Sebern, Robert W. Hasker

Validated Learning  Validate important assumptions fast  Leverage multiple concurrent learning loops  Organize workflow for fast feedback copyright by Mark J. Sebern, Robert W. Hasker

Work in Progress  Use economically sensible batch sizes  Recognize inventory and manage it for good flow  Focus on idle work, not idle workers  Consider cost of delay copyright by Mark J. Sebern, Robert W. Hasker

Progress  Adapt to real-time information and replan  Measure progress by validating working assets  Focus on value-centric delivery copyright by Mark J. Sebern, Robert W. Hasker

Performance  Go fast but never hurry  Build in quality  Employ minimally sufficient ceremony copyright by Mark J. Sebern, Robert W. Hasker

Why the list?  Enhance variability  Iterative, incremental development  Variability  Reduce all uncertainty simultaneously  Keep options open  Accept can’t get it right up front  Favor adaption, exploration  Embrace change  Balance predictive/adaptive  Validate important assumptions fast  Concurrent learning loops  Workflow: fast feedback  Sensible batch sizes  Manage inventory  Focus on idle work  Consider cost of delay  Adapt and replan  Measure progress by working assets  Value-centric delivery  Go fast but never hurry  Build in quality  Minimally sufficient ceremony copyright by Mark J. Sebern, Robert W. Hasker