This post is actually not about beautiful minds but about an instrument allowing your mind to become better organized. And therefore hopefully more beautiful. This instrument is called mind maps.
When I heard the term before it sounded complicated. When I googled the term and looked at the images, they were even more complicated. But once explained by someone who used them in practice, mind maps turned out to be rather simple and useful.
So, how can it be used in software development?
Well, they can help you can eat the elephant piece by piece.
For example, you can split the task into subtasks, and them into more subtasks, and then mark the progress on each small part as you go.
One might say, wait, but we got JIRA. It has tasks, and subtasks, and estimates, and time spent, and time left. It’s got it all!
And here is where one would be both right and wrong.
JIRA will do all that, but it won’t allow you to see the whole picture. You’ll have to drill down into tasks to see what’s left and how much of it. After the second jump you’d probably be hopelessly lost. Mind maps, however, allow you to get into as much or as little detail as you want, and all the picture would still be obvious at a glance!
Well, so at least they are worth a try, right?
And it just shows that one doesn’t have to be afraid of complicated terms. They might be not so scary after all.