Process Visualisation Step-by-Step Guide
•
2 likes•2,273 views
The document discusses process visualization and mapping processes to improve project management. It recommends defining the workflow, responsibilities, and metrics for different levels of work to identify bottlenecks and track progress. Process visualization can be done manually with diagrams or digitally with project management software to provide different views of processes and data tailored to each role.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (11)
Similar to Process Visualisation Step-by-Step Guide
Similar to Process Visualisation Step-by-Step Guide (20)
More from French Kanban User Group
More from French Kanban User Group (12)
Recently uploaded
Recently uploaded (11)
Process Visualisation Step-by-Step Guide
- 3. I still love dead tree books
- 4. We create visual management software
- 5. How do you work?
- 6. “We have a process!” “…maybe two..”
- 7. Everybody knows how he/she works ✓ Multiple meetings ✓ Synchronise information ✓ Explore dependencies ✓ Find the truth
- 8. “If you can't describe what you are doing as a process, you don't know what you're doing.” W. Edwards Deming
- 9. The problems Everybody does everything - there are no responsibilities No understanding what is required for decision making Plans are unclear and failed Communication wastes Hard to start improvements no
- 11. The questions What is the progress of our product / project? What is the status of a release? Are there any delays? What are responsibilities? Are there any blockers?
- 14. The basis by which jobs are grouped Departments Product Elevators Cranes Process Serving Shipping Functional Production Finance Customer Consumer Government Geographical Central Northeast
- 15. The workflow which a team uses Teams Functional Analysts Developers Which other roles are involved in the process? Cross-Functional Project Team Feature Team Do project teams have different process?
- 16. Roles Program manager Project manager Stakeholder CIO Portfolio Managers BA/Dev/QA
- 19. Improve on-time delivery of the racing-related software which will be of immediate benefit to its users
- 20. IT
- 22. IT
- 24. Team Customer
- 25. Solution Product
- 26. Board Design/
- 28. Marketing
- 29. IT
- 31. Team Customer
- 32. Solution Product
- 33. Board Design/
- 36. IT
- 38. Team Customer
- 39. Solution Product
- 40. Board Design/
- 44. Work Types Projects Program Requirements Activities Packages Tasks User Stories Defects Components
- 46. The Guardian.UK government spending Hierarchy
- 47. The Guardian.UK government spending Hierarchy
- 48. The Guardian.UK government spending Hierarchy
- 49. Work hierarchy advantages estimation progress
- 50. Work hierarchy advantages estimation progress 50% 30% 0% 100% 50%40% 45% 20% 40% 85% 95% 90%30% 60% 53% Enterprise PMO in project management hierarchy
- 52. Workflow Visualisation Different levels of work hierarchy might have different workflows
- 53. Initiators, Executors and Responsible Roles +
- 55. + Workflow Visualisation Define a level of work hierarchy What is the name of the flow? Who initiates the process? Put start finish of the workflow Continue with phases and steps Who is responsible for each step? Break the work down Do other teams use the same workflow?
- 57. Visualise important information See bottlenecksMultiple teams backlog Let’s continue! Kanban Board in Targetprocess
- 59. 1 Month 3 Months 1 Week Soon I have no idea How close are you to your project completion?
- 60. Release 3.2 Release 4.0 Scope based planning
- 62. Time based planning Spring Release Summer Release May June July August September
- 64. Planning Decide about scope planning - major or minor releases, iterations Put the duration Define the level of work hierarchy Decide about time planning - milestones Synchronise
- 65. Catch the ideas for improvements
- 67. F1 mission critical software Plans Determinate hierarchy
- 68. Smart action
- 69. Metrics Ask questions Are we on time with a release? What is the reason of the defects? Are requirements well documented? Can we close requirements faster?
- 70. Metrics Define which metrics will help to answer these questions Understand the cadence Dashboards, notifications Ask questions
- 72. Make it visual and easy to access manually Lean process mapping Strategy mapping http://www.jiscinfonet.ac.uk David Sibbet. Visual Meeting
- 73. Don’t forget about the virtual teams
- 74. Make it visual and easy to access digitally Visual mappingFlow diagrams http://www.rc-renovation.com/images/ProcessFlowChart.png Targetprocess VizyPro
- 75. F1 mission critical software Each person in an organisation can benefit from his own view on the same data
- 76. All work items in the organisation Board in Targetprocess
- 77. Planning by quarter Quarter planning in Targetprocess
- 78. Estimation progress with the hierarchy Hierarchical lists in Targetprocess
- 79. Team level Multiple teams planning in Targetprocess
- 80. Time planning Timeline in Targetprocess
- 81. Metrics KPIs Portfolio prioritisation in Targetprocess
- 82. Dashboards for each level Tracking with the dashboard in Targetprocess
- 83. Different vantage points are important
- 84. Tips Tricks Get a representative of each role Establish time frames rules Stop deep discussions Ask questions to keep focus Add pains improvements directly
- 85. Beginners Start transformation Advanced Run improvements Align the interests of each level of your organisation