Reduce Project Delivery Chaos with Graphs
•
1 like•5,460 views
This document discusses how modeling project dependencies as a graph can help reduce waste in software projects using lean principles. It describes representing tasks, components, defects and their relationships as nodes and relationships in a graph. This allows identifying dependency chains, evaluating the impact of changes, detecting defects and prioritizing technical debt to reduce rework, delays and waste. The graph approach provides more insights than tabular views to support lean thinking and drive continuous improvement.
Recommended
Recommended
More Related Content
What's hot
Similar to Reduce Project Delivery Chaos with Graphs
Similar to Reduce Project Delivery Chaos with Graphs (20)
Recently uploaded
Recently uploaded (20)
Reduce Project Delivery Chaos with Graphs
- 1. GraphAware® Lean Dependency Management Luanne Misquitta, Principal Consultant @ GraphAware graphaware.com @graph_aware, @luannem Reduce Project Delivery Chaos with Graphs
- 2. ‣ Lean Principles ‣ Waste in Software Projects ‣ Tabular View ‣ Model dependencies as a graph ‣ Insights into the state of the project ‣ Taking it further Outline GraphAware®
- 3. ‣ Dependencies are everywhere ‣ Supply chain ‣ Business processes ‣ Inventory ‣ Education ‣ Government processes and workflow ‣ Dependencies are a part of life ‣ But they can be streamlined and improved Dependencies GraphAware®
- 4. ‣ Lean principles are derived from the Japanese manufacturing industry ‣ Systematic waste minimisation without sacrificing productivity ‣ Takes into account waste created by overburden and waste through unevenness in workloads ‣ As waste is eliminated, quality improves while production time and cost are reduced ‣ The Toyota Way focuses on improving the flow of work Lean Principles GraphAware®
- 5. 3 M’s of waste GraphAware® Muda Activity or process that does not add value A physical waste of time, resources and money Waiting, over- production, defects Mura The waste of unevenness or inconsistency Mura drives Muda Failure to smooth puts unfair demands on processes and people Muri The waste of overburden Unnecessary stress to people and process Indirect costs
- 6. Waste in IT GraphAware® Waste Defects Over production Motion (excess) People Example Cowboy style system or application changes Unnecessary delivery of low value features Firefighting repetitively Spent time on mundane tasks instead of innovation Business Outcome Poor service, increased costs Business & IT misalignment, increased maintenance Increased cost and energy expended, loss of productivity Talent loss, low engagement
- 7. Lean philosophy regards everything not adding value to the customer as waste. GraphAware®
- 8. ‣ Building the wrong feature ‣ Backlog mismanagement ‣ Rework ‣ Unnecessarily complex solutions ‣ Waiting / multitasking ‣ Rapid switching of people between tasks ‣ Process overhead and management activities Common wastes GraphAware®
- 10. ‣ Scrum, an agile method, has it’s roots in lean thinking ‣ An understanding of dependencies is very important in larger formats such as scrum of scrums or long term software delivery programs ‣ A list based approach does not expose underlying connections between tasks ‣ The time to compose dependency chains in a tabular form does not allow for JIT decision taking ‣ Frequent changes on the ground render previous decisions invalid, and cause waste by re-planning and re-predicting Tabular Views GraphAware®
- 11. ‣ Knowledge is connected information, revealing patterns ‣ Use the power of the graph to derive actionable insights Value in Relationships GraphAware® http://effectivelearninginstructionaldesign.com/blog/idt/learning-from-information-to-knowledge/
- 13. ‣ Built around the Neo4j native graph database ‣ Intuitive, flexible models of networks of related data ‣ Nodes represent entities and they are connected to each other via relationships ‣ Query the graph with Cypher- a declarative graph query language ‣ Visualise results for link analysis or dependency inspection Neo4j Graph Platform GraphAware®
- 14. Model as a graph GraphAware® Task Task Task D EP EN D S _O N PART_OF .
- 15. Find dependency chains with at least one task open GraphAware®
- 16. Path finding with Cypher GraphAware®
- 17. The length or complexity of the chain has no strong correlation with business value. GraphAware®
- 18. D EPEN D S_O N GraphAware® Task value=3 Task value=8 Task value=8 D EP EN D S _O N PART_OF . Task value=2 PART_OF. Task value=2 Task value=2 Task value=1 DEPENDS_ON DEPENDS_ON High business value! Low business value! Capture what matters
- 20. GraphAware® Task Task Task DEPENDS_ON Component Component DEPENDS_ON Task PART_OF BELONGS_TO RELATES_TO Task DEPENDS_ON BELONGS_TO Task BELONGS_TO Extend the model - evaluate impact
- 21. GraphAware® Task Task Task [value=3] DEPENDS_ON Component Component DEPENDS_ON Task PART_OF BELONGS_TO RELATES_TO Task DEPENDS_ON BELONGS_TO Task BELONGS_TO Introducing a change late in the cycle
- 22. GraphAware® Task Task Task [value=3] DEPENDS_ON Component Component DEPENDS_ON Task PART_OF BELONGS_TO RELATES_TO Task DEPENDS_ON BELONGS_TO Task BELONGS_TO Potentially impacts dependent tasks
- 25. ‣ Over time, defects are raised across various releases ‣ New features are to be built ‣ In many cases, waste is generated by prioritising new, lower value features over refactoring to address technical debt Extending the model- prioritisation GraphAware®
- 26. Task Task [value=10] Task PART_OF Task PA R T_O F Defects, risks and muri GraphAware® DEPEN DS_O N Component Component BELONGS_TO BELONGS_TO
- 27. Task Task [value=10] Task PART_OF Task PA R T_O F New tasks with low value GraphAware® Component Component Task [value=4] Task [value=2] BELONGS_TO BELONGS_TO BELONGS_TO BELONGS_TO DEPEN DS_O N
- 31. ‣ Model people, teams, skills and experience ‣ Analyse task distribution and skill fit- squad style organisation ‣ Impact analysis - delays and risks ‣ Detect recurring patterns ‣ Improve efficiency and reduce waste in processes ‣ Other applications in government, supply chain management and inventory control Taking it further GraphAware®