Mapping tool for Feature/Story breakdown

Challenge – We were starting a new project and got a high-level demo of the application. I am a  business analyst and we follow agile scrum framework. I had to work with the team  (managers/stakeholders/architects/developers/Quality analysts) to come up with high level  Epics/Features and stories and a high-level estimate. This project is for the migrating the current  application experience from the legacy systems to the new cloud-based experience and optimize the  same experience for clients. This also included covering the scenarios for third party collaborations on  the client website and prioritize the features. The whole application was vast and there was a need to  see all the functionalities to categorize them and prioritize them. Challenge was to brainstorm on  features and then prioritization with virtual meetings as team is situated in different geographical  locations.

Selection – To capture all the functionalities and then to depict them in a tool was the need. I started  with excel (the most used tool) but brainstorming was becoming difficult also it was not very helpful for  prioritization. Then while doing the course Jeanne mentions about mind mapping. I analyzed the tool  and found that this would help us give a clear, consolidated and compact picture. Mind mapping tool  was chosen as it had options to prioritize as well as the whole picture was visible. Gave the ease of  updating as well as for brainstorming new ideas too.

Mind mapping tool gives you the option of categorization, add level and sub levels, add markers and  priorities. It’s an open/blank slate best for brainstorming as well best for when teams are situated in  different geographical locations and meet virtually.

Application and Insights – We started with brainstorming and started discussing the highest level of  categorization. Then we identified the features and added them as features. Which were then further  divided into stories. While we were at the feature level, we also identified the priorities and added  them, so we pick up work based on priority. The technical requirements (non- functional) were  identified and prioritized too. The dependency on third party teams were also discussed and  represented. Mind map gives you visual depiction to understand categories, prioritization, levels,  dependency. We were also able to track the completion at story level which in turn helped us track  completion at project level, which was a big add-on. The modification also was easier, and we could see  everything visually, so the brainstorming became better and clearer. We always had something to refer  to for project level questions with clients

Its compact nature helped us in maintenance of artifact. We were also able to capture new ideas and  enhancements. Mind mapping tool was an experiment that now helps us in each iteration and is a must  artifact for new projects. Mind map tool is a powerful tool that helped our project in aligning to  prioritized features and track progress. It gave us a medium to communicate clearly with client and  visually.

Approach: When we are in projects where we have lots of unknowns and need lot of brainstorming,  mind mapping works best. The first approach was to use classical ways of excel or word but then I  wanted to try a more design thinking oriented approach. When I started the goal was only  categorization and prioritization but later realized the full potential of the tool is much more. In the first  phase it was only identifying the epics/features but then we used it to track progress, capture  dependencies, for updating the clients. A visual depiction gave an extra advantage and the discussion  became more fruitful.

Mind mapping tool helped us in brainstorming as well. We were able to eliminate many ideas too that  were not good for the project.

Example: used login for easy understanding


Mapping tool for Feature / Story breakdown Challenge – We were starting a new project and got a high - level demo of the application . I am a business analyst and we follow agile scrum framework . I had to work with the team ( managers / stakeholders / architects / developers / Quality analysts ) to come up with high level Epics / Features and stories and a high - level estimate . This project is for the migrating the current application experience from the legacy systems to the new cloud - based experience and optimize the same experience for clients . This also included covering the scenarios for third party collaborations on the client website and prioritize the features . The whole application was vast and there was a need to see all the functionalities to categorize them and prioritize them . Challenge was to brainstorm on features and then prioritization with virtual meetings as team is situated in different geographical locations . Selection – To capture all the functionalities and then to depict them in a tool was the need . I started with excel ( the most used tool ) but brainstorming was becoming difficult also it was not very helpful for prioritization . Then while doing the course Jeanne mentions about mind mapping . I analyzed the tool and found that this would help us give a clear , consolidated and compact picture . Mind mapping tool was chosen as it had options to prioritize as well as the whole picture was visible . Gave the ease of updating as well as for brainstorming new ideas too . Mind mapping tool gives you the option of categorization , add level and sub levels , add markers and priorities . It ’s an open / blank slate best for brainstorming as well best for when teams are situated in different geographical locations and meet virtually . Application and Insights – We started with brainstorming and started discussing the highest level of categorization . Then we identified the features and added them as features . Which were then further divided into stories . While we were at the feature level , we also identified the priorities and added them , so we pick up work based on priority . The technical requirements ( non- functional ) were identified and prioritized too . The dependency on third party teams were also discussed and represented . Mind map gives you visual depiction to understand categories , prioritization , levels , dependency . We were also able to track the completion at story level which in turn helped us track completion at project level , which was a big add - on . The modification also was easier , and we could see everything visually , so the brainstorming became better and clearer . We always had something to refer to for project level questions with clients Its compact nature helped us in maintenance of artifact . We were also able to capture new ideas and enhancements . Mind mapping tool was an experiment that now helps us in each iteration and is a must artifact for new projects . Mind map tool is a powerful tool that helped our project in aligning to prioritized features and track progress . It gave us a medium to communicate clearly with client and visually . Approach : When we are in projects where we have lots of unknowns and need lot of brainstorming , mind mapping works best . The first approach was to use classical ways of excel or word but then I wanted to try a more design thinking oriented approach . When I started the goal was only categorization and prioritization but later realized the full potential of the tool is much more . In the first phase it was only identifying the epics / features but then we used it to track progress , capture dependencies , for updating the clients . A visual depiction gave an extra advantage and the discussion became more fruitful . Mind mapping tool helped us in brainstorming as well . We were able to eliminate many ideas too that were not good for the project . Example : used login for easy understanding