![Improving Process Models for Better Understanding and Analysis Dr. Darius Šilingas Head of Solutions Department @ No Magic Europe Mobile: +370 686 12748 e-mail: [email_address] LinkedIn: http://lt.linkedin.com/in/dariussilingas](https://image.slidesharecdn.com/5-21-10-11-dariussilingas-improvingprocessmodelsforbetterunderstandingandanalysis-111022121142-phpapp01/85/5-21-10-11-darius-silingas-improving-process_models_for_better_understanding_and_analysis-1-320.jpg)
5. 21.10.11-darius silingas-improving-process_models_for_better_understanding_and_analysis
- 1. Improving Process Models for Better Understanding and Analysis Dr. Darius Šilingas Head of Solutions Department @ No Magic Europe Mobile: +370 686 12748 e-mail: [email_address] LinkedIn: http://lt.linkedin.com/in/dariussilingas
- 2. About Instructor Dr. Darius Šilingas Principal Consultant and Head of Solutions Department at No Magic Europe Expert in information system and business modeling, lead ~200 training and consultancy sessions in 20 countries Organizer of annual conference Business Process Management in Practice in Lithuania Owner of LinkedIn BPM discussion group Verslo procesų valdymas (in Lithuania)
- 3. Challenge of Informal Business Process Drawings How to optimize VIP customer service ?
- 4. Komunikacijos standartų poreikis – Babelio pavyzdys
- 5. What Is BPMN? BPMN stands for B usiness P rocess M odel and N otation . BPMN provides a standardized graphical notation for modeling business processes. BPMN is understandable by all stakeholders Business analysts that create the initial drafts of the processes; Excellence people who monitor and optimize those processes; Developers responsible for implementing systems. BPMN 2.0 (Business Process Model and Notation) standard is developed by OMG (Object Management Group): http://www.bpmn.org/ BPMN 1.0 released in 2004 BPMN 2.0 beta1 released in September 2009 BPMN 2.0 beta2 released in June 2010
- 6. BPMN 2.0 Diagrams Process Diagram Collaboration Diagram Choreography Diagram Conversations in Collaboration Diagram
- 7. A Minimal Subset of BPMN Elements
- 8. From Bad Practices to Best Practices Bad Practices Complex Diagrams Mixed Naming Modeling Minor Details Slalom in Diagrams Inventing Bicycle Inconsistent Gateways Repeating Events Best Practices Several Levels of Details Naming Conventions Documenting Minor Details Clear Primary Scenario Applying Process Patterns Consistent Gateways Proper Event Context
- 9. Bad Practice Nr. 1: Over Complex Diagrams
- 10. Best Practice Nr.1 : Several Levels of Details Up to 10 steps in a diagram Question : How many steps can be depicted in 3 levels of details ?
- 11. Bad Practice Nr. 2 : Mixed Naming Mixed naming hides inconsistent understanding
- 12. Best Practice Nr. 2 : Naming Conventions A formulae for naming activities : strong verb + noun Emphasis on achieved result, not on action ! Examples : Prepare Proposal Sign Agreement Handle Defect Report Language influences thinking
- 13. Best Practice Nr.2: Refactored Process
- 14. Bad Practice Nr.3 : Modeling Minor Details There will be other business rules when we should still run class Is it worth putting it all to a diagram ?
- 15. Best Practice Nr.3 : Describing Minor Details If required number of participants is not available , Head of Training Department can make a decision to run class if There is urgent need to train employees Strategic partners/customers are registered to a class Cancellation costs will be higher than running costs
- 16. Bad Practice Nr.4: Slalom in Diagrams Reading BPMN diagram is obscured by : Long, bended and crossing lines Jumping forth and back in time scale Mixture of primary and secondary scenarios
- 17. Best Practice Nr. 4 : Clear Primary Scenario Primary scenario should be visible on one line ( ) It is recommended to start modeling from primary scenario and add secondary ones afterwards
- 18. Bad Practice Nr.5 : Reinventing Bicycle Fresh-baked modelers often invent strange modeling approaches for well-known situations
- 19. Best Practice Nr.5: Process Patterns Process patterns provide bigger modeling components that enable creating simpler and more efficient process diagrams
- 20. Bad Practice Nr.6 : Inconsistent Gateways
- 21. Best Practice Nr.6 : Consistent Gateways
- 22. Bad Practice Nr.7 : Repeating Events
- 23. Best Practice Nr.7: Proper Event Context
- 25. Analysis of KPI Change Over Time
- 26. Quantitative Business Process Management “ You can manage only what you are able to measure ” Metric – a view on statistical data providing insights into important aspects of a business process Key Performance Indicator (KPI) is the most important metric, which reflects business process (in)efficiency Metric examples : Return on investment, profitability Sales percentage from quality leads A ratio of reported defects to existing users Process execution duration and its variability ...
- 27. Measuring Process KPIs Business Process Costs Financial costs Manual work amount Use of physical resources Quality Successful end % Defect rate Customer satisfaction Time Mean execution duration Idle duration Duration variation
- 28. What Can I Measure for a Specific Process? Appropriate start time Quality Assessment (questionnaires) Costs Revenue
- 29. How to Develop BPMN Modeling Culture? BPM Leader Communicates BPM vision Helps other employees to solve BPM problems Guidelines for Implementing Best Practices Naming conventions, diagram layout, bad vs. good examples BPM leader owns the document Regular model reviews Useful to involve external experts Share comments and suggestions Sharing experience inside and outside organization Confidentiality – do not discover concrete numbers Learning from own and others’ mistakes
- 30. More Information Is Available In … Refactoring BPMN Models: From Bad Smells to Best Practices and Process Patterns Darius Šilingas, Edita Milevičienė
- 31. think BIG start SMALL and E V O L V E
- 32. The End Thank You for Attention! Questions ? ? ? Let’s Keep in Touch!
Editor's Notes
- #6: Language: semantics and meaning, simplify language to be accessible to business people No Magic is an active member of OMG. Business Process Modelling Notation (BPMN) is a graphical representation for specifying business processes in a workflow. BPMN was developed by Business Process Management Initiative (BPMI) . In august 2001 the Notation working group was formed. The group was composed of 35 companies, organizations or individuals. May 2004 BPMN 1.0 specification was released to the public. February 2006, BPMN 1.0 was adopted as an OMG standard and is currently maintained by the Object Management Group since the two organizations merged in 2005. As of January 2009, the current version of BPMN is 1.2, with a major revision process for BPMN 2.0 in progress.
- #8: Keep lanes, remove multiple instance, add X notation, leave default sequence flow
- #28: Laikas (vykdymo ir laukimo) Resursų naudojimas (žmonių, sistemų, dokumentų) Defektų kiekis (...) Efektyvumas (...) Dažniausiai analizuojami dinaminiai pokyčiai arba santykiai Proceso sukuriamos “šiukšlės”
- #29: Laikas (vykdymo ir laukimo) Resursų naudojimas (žmonių, sistemų, dokumentų) Defektų kiekis (...) Efektyvumas (...) Dažniausiai analizuojami dinaminiai pokyčiai arba santykiai Proceso sukuriamos “šiukšlės”