Co-founder of swipez.in and looks after operations and technology. I started my journey in tech in 2000 as a Perl dev. Before starting Swipez, I was working as a Software Architect for Barclays Bank.
Hi Rafal, Thanks for the comment :) I will try and answer these queries by breaking it down.
1. Sprint planning & customers feedback on usage of mind maps
Mind maps can facilitate sprint planning, as it allows you to focus on a particular section or module of your project and everything that is required to complete it. And visually shows you where this module fits in the full picture.
Customers love seeing their project in this form. As it gives them a visual representation of the solution. It has also helped us to ratify a solution with multiple customers & stakeholders quickly over a meeting or a phone call.
2. Do you have to convince other developers to work with mind maps?
I have found developers liking the idea of using something more visual rather than writing documents. Having said that though, some folks need more convincing than others. Just like how adoption of anything new takes time and effort, this is not going to be any different.
Do you use mind maps to draw only a big picture of a project or do you use it to describe details?
Both, it depends on the nature of your organization and project stakeholders. If they are receptive to the idea of using mind maps then there is no reason why i cannot be used across the board.
I'm focused on developing and expanding my knowledge and skills. Enjoying new challenges. I'm assuming that there are no stupid questions, there are only silly answers.
Hi Rafal, Thanks for the comment :) I will try and answer these queries by breaking it down.
1. Sprint planning & customers feedback on usage of mind maps
Mind maps can facilitate sprint planning, as it allows you to focus on a particular section or module of your project and everything that is required to complete it. And visually shows you where this module fits in the full picture.
Customers love seeing their project in this form. As it gives them a visual representation of the solution. It has also helped us to ratify a solution with multiple customers & stakeholders quickly over a meeting or a phone call.
2. Do you have to convince other developers to work with mind maps?
I have found developers liking the idea of using something more visual rather than writing documents. Having said that though, some folks need more convincing than others. Just like how adoption of anything new takes time and effort, this is not going to be any different.
Do you use mind maps to draw only a big picture of a project or do you use it to describe details?
Both, it depends on the nature of your organization and project stakeholders. If they are receptive to the idea of using mind maps then there is no reason why i cannot be used across the board.
Thank you for detailed answers. Once again very nice article :)