Modeling Kanban Scheduling in Systems of Systems Alexey Tregubov, Jo Ann Lane.

Slides:



Advertisements
Similar presentations
Project Management Techniques and tools Move mouse over arrow to enter presentation End Show.
Advertisements

Introduction to Embedded Systems Resource Management - III Lecture 19.
Test Yaodong Bi.
Incremental Commitment Spiral Model, Expedited Engineering, and Kanban Jo Ann Lane and Alexey Tregubov USC CSSE Rich Turner Stevens University.
ECOE 560 Design Methodologies and Tools for Software/Hardware Systems Spring 2004 Serdar Taşıran.
By Eva Freund, The IV&V Group, Inc.
Project Management Workshop. Nick Cook  Citigroup Corporate and Investment Bank  European Technology Business Office Manager Edinburgh University April.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
MotoHawk Training Model-Based Design of Embedded Systems.
W5HH Principle As applied to Software Projects
An Approach to Evaluate Data Trustworthiness Based on Data Provenance Department of Computer Science Purdue University.
SWE Introduction to Software Engineering
Lesson 10 IT Project & Program Management.
Projmgmt-1/33 DePaul University Project Management I - Risk Management Instructor: David A. Lash.
GridFlow: Workflow Management for Grid Computing Kavita Shinde.
Simulation.
1 Software Testing and Quality Assurance Lecture 15 - Planning for Testing (Chapter 3, A Practical Guide to Testing Object- Oriented Software)
Software Project Planning CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 12, 2002.
(c) 2007 Mauro Pezzè & Michal Young Ch 24, slide 1 Documenting Analysis and Test.
System-of-Systems Cost Modeling: COSOSIMO July 2005 Workshop Results Jo Ann Lane University of Southern California Center for Software Engineering.
1 Software Testing and Quality Assurance Lecture 14 - Planning for Testing (Chapter 3, A Practical Guide to Testing Object- Oriented Software)
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Design, Implementation and Maintenance
Software projects Management & Development Alireza Saebi
© 2009 Public Health Informatics Institute Multi-State Learning Collaborative September 17, 2009.
Project planning. Software project management Informal definition of management – The art of getting work done through other people Software project management.
Overview of Lean Six Sigma
Kanban “Signboard”.
Modeling Kanban Scheduling in Systems of Systems Alexey Tregubov, Jo Ann Lane.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Project Management An overview. What is a Project A temporary job to accomplish a specific task A temporary job to accomplish a specific task Attributes.
Project Management Application in Health IT Farrokh Alemi, Ph.D. Geff Garnhart, PMP.
RUP Requirements RUP Artifacts and Deliverables
Software Testing Lifecycle Practice
Introduction to Monte-carlo Analysis for software development
Objectives Understand the basic concepts and definitions relating to testing, like error, fault, failure, test case, test suite, test harness. Explore.
Grid Data Management A network of computers forming prototype grids currently operate across Britain and the rest of the world, working on the data challenges.
Welcome to Session 4 – Project Management Process Overview (continued) Instructor:Phyllis Sweeney Instructor: Phyllis Sweeney Project Management Certificate.
1 TenStep Project Management Process ™ PM00.7 PM00.7 Project Management Preparation for Success * Manage Risk *
1 L U N D S U N I V E R S I T E T P rojektledning och Projektmetodik.
Software Project Management Lecture 11. Outline Brain Storming session  Some simple discussion on questions and their answers  Case studies related.
Defining Procedures for Decision Analysis May & Engr A April 30, 2002 Client & Faculty Advisors –Dr. Keith Adams –Dr. John Lamont –Dr. Ralph.
November, 2012What IHE Delivers XDW (Cross-Enterprise Document Workflow) & XBeR-WD (Cross-Enterprise Basic eReferral Workflow Definition) Workflow Management.
1 Devon M. Simmonds University of North Carolina, Wilmington CSC450 Software Engineering WorkFlow Modeling with Activity Diagrams.
WOOD 492 MODELLING FOR DECISION SUPPORT Lecture 24 Simulation.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
Teaching material for a course in Software Project Management & Software Engineering – part V.
PRJ566 Project Planning & Management Software Architecture.
Data Segmentation for Privacy November 16 th, 2011.
Workforce Scheduling Release 5.0 for Windows Implementation Overview OWS Development Team.
TANZANIA FELLOWSHIP OF EVANGELICAL STUDENTS (TAFES)
© The McGraw-Hill Companies, Inc., Just-in-Time and Lean Systems.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 27 Software Engineering as Engineering.
PROPRIETARY  2003 Data Research Analysis & Consultancy Solutions All Rights Reserved. This is achieved by: Improving availability / reducing stock outs.
Submission doc.: IEEE 11-14/ axr0 May 2014 Chinghwa Yu et al., MediaTek Inc.Slide 1 Comparison of Calibration Methodology for MAC Simulation Date:
CSE Senior Design II Timebox Development Mike O’Dell Based on an earlier presentation by Bill Farrior, UTA, modified by Mike O’Dell.
Design CS 470 – Software Engineering I Sheldon X. Liang, PH.D.
Overview PRINCE Hogeschool Rotterdam. 2 Project definition  A project is a temporary organization that is created for the purpose of delivering.
Asset accounting-29.pptx This course will give an overview of the following Workbreakdown Structure Network Project Builder Project Planning.
IS and Kanban.
P3 Business Analysis. 2 Section F: Project Management F1.The nature of projects F2. Building the Business Case F4. Planning,monitoring and controlling.
Project management. Software project management ■It is the discipline of planning, organizing and managing resources to bring about the successful completion.
Game Design, Development, and Technology
Chapter 16 Nursing Informatics: Improving Workflow and Meaningful Use
Agile concepts in System of Systems engineering Alexey Tregubov
Project Management Complexity, Risks, Failure and Technology
Principles of Management Learning Session # 21 Dr. A. Rashid Kausar.
Agile Project Management and Quantitative Risk Analysis
Presentation transcript:

Modeling Kanban Scheduling in Systems of Systems Alexey Tregubov, Jo Ann Lane

Outline 2 Modeling Kanban scheduling in System of Systems:  Why do we need to model?  Overview of KSS Network  Key aspects of Kanban scheduling technique  Simulation model  Example of KSS Network  Results & future work

Why do we need to model? 3 Applications of modeling in System of System environments:  Hypothesis testing  Process improvement  Business decision support  Cost and effort estimation

Health care example of KSS Network 4

Key aspects of Kanban scheduling 5 Kanban principles embedded in prioritization algorithm:  Eliminate waste  Minimize context switching  Limit work in progress  Make process more visible and transparent  Kanban boards  Increased value delivered earlier  Value-based work prioritization  Reduce governance overhead

Key aspects of Kanban scheduling (continued) 6 Work prioritization algorithm based on the following:  All work items (WI) prioritized according to their business value  Every WI has a class of service: Standard, Important, Date Certain, Critical Expedite  Limiting work in progress: work in progress is never interrupted unless new work has a Critical class of service

Simulation model 7 Discrete event simulation:  Inputs:  Event scenario: a sequence of events that describes how network evolves over course of their execution  Team configuration: structure of teams, resource/specialties allocation  Simulation configuration: stop condition  Outputs:  Sequence of network states  Analysis: various indicators of effectiveness

Simulation model: definitions 8 Discrete event simulation – network state & transition algorithm Network state objects:  Kanban board – demand log, work items in progress  Team – group of resources (e.g. software development team)  Work item – task that requires effort to completed  Aggregation Nodes – logical group of work items, such as requirements, capabilities  Kanban network – teams, Kanban board, and their work items Transition algorithm:  Trigger events according to the scenario  Apply work prioritization algorithm

Health care example 9

Example: capabilities to requirements to products 10

Example: network structure & scenario 11

Example: outputs 12

Example: workflow 13

Example: result analysis 14 Value:

Conclusion: results 15  Simulation model  Simulator implementation: KSS Simulator  Two prioritization algorithms implemented  Several scenarios analyzed

Conclusion: future work 16  Pilot the Kanban scheduling with several organizations  Fine-tune the simulator using empirical data and organizations feed back  Scale up the cases we run through the simulator  Refine and calibrate cost models

Questions & answers 17