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

Slides:



Advertisements
Similar presentations
Chapter: 3 Agile Development
Advertisements

Copyright © by Mark J. Sebern Software Engineering Process I Dr. Rob Hasker L-331, hasker (Adapted.
The Three Friends of Product Development: Service Design, Lean Startup and Agile Development Bruce Scharlau University of
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.
Unit 1, Lesson 4 Software Development Cycle AOIT Introduction to Programming Copyright © 2009–2012 National Academy Foundation. All rights reserved.
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 © by Mark J. Sebern Software Engineering Process I SE Technical debt.
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.
MODULE 11 CONTROL AND CONTROL SYSTEMS “What gets measured happens” What is important to know about the control process? What are some organizational control.
Strategic Perspective to Fleet’s Total Cost of Ownership.
Chapter 18: Controlling – Processes and Systems
14 – Advanced MRP Topics Dr. Ron Tibben-Lembke pp. 478-
© AgiliX Agile Development Consulting Agile Demystified Cesario Ramos.
An Agile View of Process
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.
Fish Infectious Disease Model Case Study BSC417/517.
Dr. Rob Hasker copyright by Mark J. Sebern, Robert W. Hasker.
Prescriptive Process Models
The Successful Business Analyst’s Role in the Scaled Agile Framework®
Intoduction to Unit Testing Using JUnit to structure Unit Testing SE-2030 Dr. Rob Hasker 1 Based on material by Dr. Mark L. Hornick.
Balanced Scorecard Bruce C Hartman MGT 400. Operating Assumptions for the Information Age Cross Functions Links in Supply Chains Customer Segments Global.
Agile Concepts - II “Agile” Estimating & Planning Nupul Kukreja 5 th November, 2014.
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.
SE503 Advanced Project Management Dr. Ahmed Sameh, Ph.D. Professor, CS & IS Agile Principles: Customers and Products.
1 CHAPTER 4 DEVELOPING A BUSINESS PLAN: BUDGETING.
Foundations and Evolutions
 Dr. Syed Noman Hasany.  Review of known methodologies  Analysis of software requirements  Real-time software  Software cost, quality, testing and.
Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.
Lecture 3 – Agile Approach
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
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.
QUERI Robert L Jesse, MD, PhD Chief Consultant Medical Surgical Service.
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)
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.
PowerPoint Presentation to Accompany Chapter 8 of Management Fundamentals Canadian Edition Schermerhorn  Wright Prepared by:Michael K. McCuddy Adapted.
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.
Hello. ASPE & Techtown Training An Introduction to DevOps for Project Managers Today’s Presenters : Chris Knotts, PMP – Enterprise training curriculum.
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.
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
Information about Life Cycles
Disciplined Agile Principles
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
Latent Space Model for Road Networks to Predict Time-Varying Traffic
Step 22: Define the Minimum Viable Business Product (MVBP)
CS 577b: Software Engineering II
Pygmalion Factor #1 – Climate
Guiding principles Balance portfolio of transit projects using multiple transportation modes. Increase mobility for workers to and from major job centers.
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

Jira  What do you want to know? copyright by Mark J. Sebern, Robert W. Hasker

Agile Principles, Revisited  Variability and uncertainty  Prediction and adaptation  Validated learning  Work in progress  Progress  Performance copyright by Mark J. Sebern, Robert W. Hasker For each: how might this principle come into play in SDL this quarter?

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