Mind Mapping and the Software Development Life Cycle
I’ve recently started looking into how mind mapping is used in the software/system development life cycle. One of my passions (and profession) is software design and development. Since I started mind mapping a few years ago, I’ve been slowly introducing mind maps at my current job.
I began using mind maps (courtesy of Mindjet’s MindManager Pro) to help streamline the process of researching new technologies and products. I discovered that this technique was much more efficient than trying to use traditional bookmarks (or del.icio.us for that matter), or knowledge managers (like General Knowledge Base or DevonThink). And, I could quickly share with others, without needing to create a separate document to summarize my findings.
Over time I increased my usage of mind maps to encompass capturing meeting notes, product requirements, and technical design discussions. Although I wouldn’t typically use mind mapping techniques during any whiteboard sessions, I would capture meeting notes afterwards and convert to a mind map. When sharing maps with others, I would upload to our intranet in both MindManager format and export as HTML for people who hadn’t yet downloaded the mind map viewer.
As a whole, I would say the feedback and general acceptance of using mind maps for our projects has been very positive. On numerous occasions, team members would still be consulting the maps even months after a meeting had taken place. And, I personally think that reviewing the mind maps after a tradional meeting/whiteboard session can really improve communication and recall of the information later on.
I became curious as to how other individuals and organizations are using mind maps in their development process. After reading Chuck Frey’s excellent Mind Mapping Survey, I discovered that a large percentage of the survey respondents (500 people in total) are using mind mapping for project planning (52%) and business process mapping (30%). And, of the people that listed their mind map use as “other” (9%), there was mention of documenting software requirements, and software development and modeling.
I decided to start Googling on this topic and came up with some interesting results. The following are some links and resources related to the use of mind maps in various phases of the SDLC (Software Development Life Cycle).
Mind-mapping tools are finding a home in corporate IT
Using mind mapping software for web research
Turning systems models into projects
(Related to ORM – Outcome Relationship Model)
Funnel timeline: A visual approach to project planning
Project estimating – Mindmaps are a tool in the armory
How to use mind mapping software for project management
Mind Mapping and Project Management
Mind maps provide a view for collaboration
Agile Modeling with Mind Map and UML (StickyMinds Article)
MindManager for Software Development: Part 2 – Requirements Gathering
Sharp Development – Mind Mapping for OOAD (Object-Oriented Analysis and Design)
UML Modeling Tool – JUDE
(Convert Mind Maps to UML)
Generative Programming with MindManager and XSLT
Mind Maps Foster Thorough Test Design
Mind Mapping for Test Planning
MindManager for Software Development: Part 1 – Help Authoring
In the near future, as mind mapping becomes more mainstream, I can imagine that various mind mapping techniques and products will be used to streamline the software development process. Personally, I think it would be a great use of time to come up with a set of common mind map templates for use in software development projects. Something along the lines of ReadySet, or Steve McConnell’s Software Project Survival Guide templates. This sounds like a great pet project for 2007.
In the meantime, I’d be interested in hearing any feedback on how individuals or organizations are currently using mind maps in their development process.