Thanks for visiting! The site is Under Construction. Please send feed back. Thank you! -Greg

Why Graph Thinking Workshops?

Graph Thinking context: Software Application Development and Scaled Agile Framework

In 1975, Fred Brooks exposed the challenges of software application development. In The Mythical Man-Month, Brooks enumerates and quantifies his observations of large software application development projects. From his work, we can distill a powerful idea to help us estimate the effort required to deliver software applications: Coding is secondary to design, communication, and testing.

For some years I have been successfully using the following rule of thumb for scheduling a software task:
1/3 planning
1/6 coding
1/4 component test and early system test
1/4 system test, all components in hand.
This differs from conventional scheduling in several important ways:
1. The fraction devoted to planning is larger than normal. Even so, it is barely enough to produce a detailed and solid specification, and not enough to include research or exploration of totally new techniques.
2. The half of the schedule devoted to debugging of completed code is much larger than normal.
3. The part that is easy to estimate, i.e., coding, is given only one-sixth of the schedule.
-Fred Brooks, The Mythical Man-Month.

So much is written about the struggle of software application development management since then, I will not. But I can speak personally to the struggle Fred Brooks describes in 1975. Reading Mythical Man-Month today is like reading part of my autobiography, mistakes and lessons I have made and learned after almost 30 years implementing new systems, processes, and software. For the sake of this article, I will end the story of this struggle by pointing out that agile frameworks, for example the Scaled Agile Framework, SAFE, is the best answer to Fred Brooks formula for a successful project. Again, so much is written on this, I will not.

Let us think about Fred Brooks's points about design, communication, and testing. Besides engineers and programmers, who designs, communicates, and tests? Per agile frameworks the stakeholders, business owners, product managers/owners, and clients all play crucial roles in the sofware development life cycle. If we look at an agile framework such as SAFE, can we readily see where the coding happens? No. Why? Because SAFE creates a framework in which design, communication, and testing are prioritized over coding and building. (Engineers and programmers, I know this hurts but it shouldn't. It is all about supporting you, per Fred Brooks and so many others.-GM)

Graph Thinking to Graph Database Application Development

40 years of RDBMS and SQL and NoSQL

We have all seen technology advancements happen and change our world. But consider, how much has database thinking and technology really changed, really, in 40 years? Relational Database Management Systems are the standard for most applications. Structured Query Language is the only ANSI and ISO standard for a database language. RDBMS have gotten bigger as hardware and algorithms enable scaling. We adapted to different data formats because of Big Data with NoSQL databases. As we look more closely at NoSQL variants, aren't they really just variants of tables, fit to model different shapes of rows and columns, or using tables to index documents? For 40 years, rows and columns, tabular, general ledger shapes have molded, and limited, how we think about data. For 40 years, our applications have been built upon row and column data models, our analyses the same.

New Technology Wave of Graph Database Management Systems

There is a new wave of database technology that is hitting, and it is as significant, or more so, than RDBMs and SQL. It will change all transaction systems, all applications, and all data analysis. It will change how we build software applications of all types and sizes. Just as data tables and SQL are found everywhere today, this database technology will be found everywhere in the near future. To get to the future we must learn a new way of thinking about our data and applications. This new wave of database technology is Graph Database Management Systems, GDBMS. The new ANSI and ISO language is currently called GQL, Graph Query Language. The new way of thinking about our data and applications is graph thinking.

Today, if you google graph thinking, you don't get much at all related to how to think about data and applications as graphs. Often there is confusion between graphs and charts. Almost all the web content found is geared toward engineers and data scientists. As business owners, stakeholders, product managers, scrum masters and data analysts do you know about graph thinking, graph databases, and graph analysis? Do you know how to collaboratively look at your domain and create a graph data model? How can we develop the next generation of software applications for our internal and external clients without understanding the advantages, power, and realm of graph theory, graph thinking, graph analysis, and graph databases? How do we design, communicate, and test in terms of graph data?

The most important function that software builders do for their clients is the iterative extraction and refinement of the product requirements. For the truth is, the clients do not know what they want. They usually do not know what questions must be answered, and they almost never have thought of the problem in the detail that must be specified. -Fred Brooks, The Mythical Man-Month

The entire agile team: stakeholder, business owner, product manager, product owner, scrum master, analyst, and engineer must know graph thinking and how to apply it to their domain. Then, our agile teams at any scale will be able to use graph thinking to create new, innovative, valuable, insightful applications. We will be able to ask new questions and get answers to the most complex problems we have. We will create analytical reports and dashboards using graph algorithms and visualizations. By bringing Graph Thinking right into a software development framework like SAFE, we can accelerate the adoption of graph database application development and graph data analysis.

Transition to Graph Thinking

How do we get the agile entire team to a new paradigm? How can we get the the entire agile team graph thinking and delivering cutting edge graph database applications? Graph Thinking Workshops for Agile Development is how. Each workshop is designed for specific agile roles, as defined by SAFE, each agile team member plays. The workshops are not limited to SAFE and agile development. SAFE gives us a proven framework for defining roles. So if you identify with any of these roles these workshops are for you. If you just want to know more about graph thinking and how to become a graph thinker these workshops are for you. If you want your organization to dominate the next generation of digital services, these workshops are for you and your team. If you want to accelerate the wave and ride it, these workshops are for you.

Graph Thinking Workshops for Agile Development Teams

Graph Thinking for Product Management

Graph Thinking for Business Owners and Stakeholders

Graph Thinking for Scrum Masters

Graph Thinking for Architects and Engineers

Graph Thinking for Data Analysts

The website is still under construction but we have workshops under construction as well. If you are interested in Graph Thinking Workshops please contact Greg. I will contact you directly about a workshop for you and your team as well as add you to our mailing list. Your privacy is my priority and I will not share your email.