BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Presentations Make Your Team's Domain Language Truly Ubiquitous with Concept Maps

Make Your Team's Domain Language Truly Ubiquitous with Concept Maps

Bookmarks
39:19

Summary

James Ross discusses what concept maps are, how to construct one, what to do and what to avoid when creating one, and how to help a team build a shared mental model depicted in a concept map.

Bio

James Ross has played consultant, architect and development manager roles at various organizations. His interests of late have been the Theory of Constraints, and Systems Thinking. James is currently the Engineering Director at Envato Marketplaces. He is the coauthor of Beginning Algorithms, a book that takes a test-driven approach to the teaching of fundamental computer algorithms.

About the conference

Agile Australia is the annual conference for those looking to build better products, teams, and organisations; most recently held in Sydney in June 2015 and sponsored by ThoughtWorks, Accenture, Atlassian, elabor8, HP, Commonwealth Bank, Context Matters, and supported by the Agile Alliance. The 2-day conference is the place to network with thought-provoking international keynote speakers and Agile community leaders from across Australia and New Zealand. www.agileaustralia.com.au

Recorded at:

Jan 10, 2016

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Interesting but...

    by Duraid Duraid,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I think there is a problem with the concept of concept maps. It is normal for people to see things differently and one thing can be described in many different terms. To try and enforce one way of thinking is counter productive and expensive and I don't know if it achieves anything. It's the cathedral v.s. the bazaar.

    The example that was presented is actually a proof of that and not the contrary. The fact that a team that have been working together for a year have no shared concept map is an indication that such thing is not necessary and they can do their job without having one.

    However, I think concept maps can be very beneficial to be used individually as an analysis tool.

  • Re: Interesting but...

    by Dzmitry Lahoda,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    May be part of what you say can be fixed by tooling. E.g. having complex concept map where each node and connection can be tag by aspect. And off or on view of items based on aspect needed. So persons could be provided with specific view for them. E.g. github.com/VUE/VUE/issues/15

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT