 My talk is not about Dramon. My talk today is about mind mapping. Mind mapping is a visualization tool for everybody. I would like to show you how to use mind mapping in the context of software development, especially in agile development. But before that, I would like to introduce myself and Japan a bit, because we have 90 minutes. Wow. So maybe it's going to be a little bit shorter, but I'll do first part, starting with my introduction, self-introduction, and I will talk a bit about Japan and agile. Then I'm going to go into what is a mind map and why you are going to use mind map, the benefit you are getting from. Then I will do user wish mind mapping that capture user's wish into user stories. I will do some demonstration with Satomi there, and I'll do a conclusion. Before I came here, I just did a bit of research about India and found that this thing, Doraemon is so famous in India, so surprised, but do you know this cat is from the future? Oh, everybody knows. Wow. Then do you know that why he doesn't have any ears? Read minds now, sorry, because his ears were eaten by mouse. That's why he hate mouse. Yes, because this thing is my elementary school days character. I'm 46 years old, but this thing was when I was six years old. So 40 years old character, I was so surprised. Also, I will show you some interesting picture from Japan. This describes crumb in Japanese cartoon, ladies' girls' crumb. Isn't it fascinating? Like this. Interesting of this one, I really like this, stakeholders looks a bit mean, isn't it? So we are good at cartoons, right? And to Japanese or to me, India is like yoga thing, and Krishna or what's the elephant? Ganesha, Ganesha, Ganesha is the famous God. Is he an incarnation of God? I'm not sure, but it's famous in Japan too. And to me, India is like this. It's like... We really love this movie in Japan. I'm glad you like it. Oh, sorry, I'm glad we like it. But a bit of myself, I have been in this agile world for more than 10 years, 13 years. Like 13 years, and I'm a book translator. I introduce those books into Japanese, like old C++ Jim Copeland's book and some extreme programming books, like 2002 or 2003, and Mary Popendix's Lean Soft Development books, and Azure Project Management by Jim Heismith, and the art of agile development by, yes, James Shaw. Yes. And I am a writer also in Japanese, object-oriented books or UML books, design pattern books, and mind-mapping book in Japanese, sorry. And I recently published in this January, Agile Development and Scrum, with co-authored by Ikujiro Nonaka. Do you happen to know him? Ikujiro Nonaka. Somebody knows him? Okay, I'll tell you later. And I'm also a CEO of a tool vendor called Asta, which is a UML and mind-mapping integrated tools. In this room, do you know how many of you know about Asta? Jude, yes, it was once called Jude. Thank you, one. Jude is very famous in Japan and Brazil. Last year I visited Brazil and I talked to the audience like this, and 80% knows about this tool. They are very keen to educating object-oriented software design, so this software is very much used in college or universities. And this is Nonaka Ikujiro-san, who we together co-wrote the book, newly book. And this is me and this is Jeff Sutherland who developed or created Scrum. The word Scrum is from his paper. The paper is called this one, The New New Product Development Game, which is written in 1986. He studied Japanese way of new product development and found some interesting aspects in it and described how fast Japanese can do new product development. Recently we are going down, but in 80s we're going so fast. So he described to the world. That's his work. And here you can see here. Stop running the relay race and take up rugby. Meaning that this picture is also from his paper. He studied NASA New Product Development, then Fuji Xerox and Honda and he found that NASA development is gate-phased. And Xerox has some overlapping area between the gates and Honda, those phases are almost merged into one. So this is a relay race passing batons between the phase, right? And this one is Scrum passing balls around and we together go into the goal. So this metaphor was referenced by Jeff Sutherland and he articulated, he made words on top of his words using his Scrum concept. So last year I was proud that Jeff Sutherland invited him to Japan and meet Nonaka-san. That's what happened in 2018, sorry, in 2011 in Japan. And this is an overview of the world of Lean, Agile, and Japan. Here is manufacturing industries. We are good at manufacturing or factory producing things. So manufacturing industry in Japan, Nonaka-san first wrote the New New Product Development Game by the way, there are two news about, first new is new, meaning new, and the second one is new product. So it's about new product development game which is new way of doing that. And of course we have Toyota production system. Is Toyota around here? Oh yes. And it's called TPS. Toyota production system is TPS and it was analyzed and abstracted into Lean or Lean thinking and applied to different industry areas, a lot of services, healthcare and lots. And Mary took this idea into Agile movement so that to explain how Agile is working well to executive or business people. So now the word Lean and Agile is kind of combined to express this whole movement. And Kanban spawn or spin-off from Agile and Kanban itself is a Japanese term. Did you know that? Yes, of course. So Kanban is a card passing around. So and Lean startup movement came after that from Lean and Agile. So this is the picture of the history I have. By the way, this picture is drawn by Yasunobu Kawanguchi-san who is working in Rakuten in Japan. Yes. Oh really? Kenbeksetsuo, Nonaka-san's paper. Good, good. Because XP and Xcram also have the same parent called Patterns. And in Patterns community, Jim Cappelline explained things and Kenbeks was the shepherd of Jim Cappelline and so socially it's very connected. Right, thank you. And I forgot something to say. And of course Xcram programming, the second edition of Xcram programming has a chapter called TPS. So it is directly influenced by this thinking too. Okay. And a short history but I'm gonna skip. So left is Nonaka's text and Agile's scrum. But most important part is he coined the word scrum but he is very famous in knowledge management. Knowledge management, KM, Knowledge Management Area. And he wrote a lot of books and he also studied American US Marine, the Organization of Strategy Patterns. And he recently wrote in Harvard Business Review, Wise Leadership, all those are connected in his brain. So I wrote with him the links between Azure World and his thought. So this is, it's published in Japanese only, sorry. So if you, in this room there is a publisher, please talk to me later. So that I can publish this in English. And a little bit of statistics. I tried to search, tried the search of Agile keyword. This is a trend, Google trend of Agile. What, is it funny? Because Google trend starts from 2004 or so, so the data starts from 2005. So India is always very high level. Yes, yes, so the denominator is very big, right? So my guess is that 2000, 2001 or two, India became, has some shoot up or soar. And now Brazil is shooting up. Do you know why? Why Brazil? You have friends there? I've never seen it. Oh, thanks. Brazil. I visited Brazil and found that they are doing scypes and TV conference with US customers. So they can talk real time. I mean, not in, Indian people cannot talk with US people real time, unless you wake, woke up late in the morning. So what I'm going to say here is, Japan is very low here. So I'm struggling with this situation right now. Yes, I'm not sure. But you didn't see it this time, you didn't see it this time. Yeah, she said more money came in at this timing. Yeah, this timing. So this shooting is not error, it has some meaning there. Thanks. So yeah, geographically like this. And I will show you some data I got from Asia Scrum Alliance last week. This is the number of certified scrum masters by countries. It says US is only, it's out of scale. So here, UK, China, Denmark, Brazil, like this. And Japan, here. Very few. Wow, sorry, this board should be. I can't do that, sorry. But India is like this, wow. So I think India is a lot ahead from Japan. So you win. Okay, okay, that's a small introduction about Japan and Scrum. And I will talk, this is my main talk from here. So I will talk about mind mapping and user story gathering from mind mapping. So what is a mind map? British person, Tony Bousin created this method. It's a, how many of you taking notes with mind map, using mind mapping? Oh, thank you, thank you. Okay, thank you, more than 10. It's a very good number. In Japan, it's getting popular now. And it's a graphical note-making technique. It's this shape of radiant structure. Or, and it's, to me, it's a note-taking technique, but to Tony Bousin, it's more than that. It's more education, changing life, changing people, making mindset and a whole brain thing is mind mapping. But I don't want to go into that part, but I'm concentrating on this note-taking technique today. And it's visualized thoughts in this radiant structure. And I will recommend this book. This book is the Bible, that mind map book. It's also translated into Japanese, which you don't read. And I have a book called Mind Maps for Kids. I strongly recommend this one. This one is the book. It has a very nice picture in them, and good for kids. And I will show you later. If somebody wants to see this, I'll pass this around. Okay, why mind map? This is a picture or text from Da Vinci. Lots of people know about his things, like he was left-handed or he can write in mirror or like this. But here, he used those text and picture at the same time. So the great brains in the world are using pictures or drawings and text or words at the same time. So mind mapping is the shape, shape, and words at the same time. Noble Peace Prize, sorry, Nobel Prize winner Roger Sperry found that there is two cortex in your brain, and one is called right brain, the other is called left brain. It's not that simple, but this idea is well-accepted and still many brain scientists use this concept. And it says that right hand controls, sorry, this is right hand, right hand side, sorry, right hand side of the brain uses or manages emotional expression and spatial things or music or creativity, imagination, pictures, drawings, images, instinct, things like that. And a gestalt, do you know this word, gestalt? Yes, gestalt is a whole. So you look at things and capture it as a whole, as a picture, it's called gestalt. If something's lacking, you wanted to fill this up. That's called gestalt. And left hand side, I'm really sorry, this screen should be up more. Left hand side is doing writing or language and scientific thinking or mathematics and lists or making logic, rational things. So these two brains working together to be a human. So what I'm gonna say is picture and text at the same time is very meaningful to your brain. Tony Busan used the word it's brain friendly to use text and picture at the same time. I found this very, very interesting YouTube, video, which I don't show you today, which you see later at home. She is a brain scientist, Jill Bolt-Taylor. It's a TED conference, very, very interesting. She once herself was attacked by stroke. So she is talking about how she felt at that moment. Very interesting. When right brain is up, she felt the world is into me, sensing a smell image coming to her and all those are parallely processed and no me in it. It's just me or world, she doesn't know. So it's like emotional, just image and thinking, just sensing and when left side comes back, he suddenly making decisions and orders, logics. And then right side, she was so happy, one of the part of the, being part of the world. So she was describing this so emotionally, it's like an act, so you should see this. She is a brain scientist. So it's very rare a brain scientist was attacked by a stroke and she described in an analytic way how it was, so it's so interesting. So, mind mapping. This is a mind mapping of mind mapping. I will explain, I will try to explain. Okay, it's a note-taking, note-taking. Why do you do that? It says to see important thing, to recognize keywords, keywords, to see to recognize keywords. And it's in one piece, so structure is clear and it can be viewed quicker and you can remember later as a picture. This thing, this thing, this whole gestalto is in your brain and you can remember thing. So that's why part and how you are gonna take notes with this mind mapping. Several things here, but I don't explain today. But important thing is, I show this to you and one month later, when you see this, you will remember today's context. Oh, that picture, somewhere I saw and that was the Agile India 2013 in some funny Japanese guy speaking in a room and something like that. The context itself is enclosed into this. Actually, it's not enclosed in this, it's in your brain. Tony Busan says that every experience is stored in your brain, but you cannot extract it. But mind mapping, mind map works as a index or key to that memory which is completely stored, which you can't extract, but stored. So this works as an index to that big memory to review that moment as a playback of DVD or something. So important thing is, this picture works as a key and this picture holds this context or holds an index to your brain that holds context of this moment. I use this like this. This is a picture, sorry, this is a book I like and when I read books, I try to make mind map as you read chapters. So it says author chapter number one, chapter number two and so on. When I didn't know about mind mapping, I just read and what do you call this? Flip, fold, dog ears? Dog ears, kinda like that. But, but, yes, I found something in this book. I know that, but I cannot find any part. I cannot remember where it was described at once. After I, using mind map, I stick this mind map onto this front page or the other back of the page to see, okay, what was this book? Open it, mind mapping. Okay, that timing, at that time I wrote this. It works as an index to your brain. So, okay, that was in here. So, okay, I can remember all the stories in it at once at a glance of mind mapping. So, I will show some examples of mind mappings. Because this is an agile conference, I took one from Kentex XP Second. He says XP is composed of values, principles and practices and so on. It's very nice brush painting here. Simple but strong. It's on the back cover of the XP Second book. This one was, we wrote, we developed software. So, we wrote a mind mapping for the next release so that we can remember the whole next release, image of the next release as a picture. And this one is about the talk I did two days ago, you may be missed. And it's a learning kaizen from Twitter. And I draw this mind mapping so that I can remember how to talk about how to talk in the session. This one, this one was drawn by Bruce Taylor. Is he happened to be here? No, he is in the agile India conference and he sent this one to me. This is strictly saying this is not mind mapping. It doesn't have branches and it's not radiant. But picture and words at the same time so that he remembers the context or knowledge in the air. So, and this is a project Christmas planning mind mapping. I will show you some examples in my tool. Okay, this is a, it has a mind mapping always have center some image is would be nice so that you can remember that whole thing. So, this is, this first branch is called BOI which is basic ordering idea which works as a framework of your thought. So, this has when, what, why, who, where, result. So, six branches. It's an interesting because you don't talk about how but result. It's very, I thought it's very business oriented thinking instead of thinking about how but result. But interestingly, this format, this framework, five W and one R is introduced in this book, kids. Four kids, mind mapping four kids. So, this is a project Christmas planning mind mapping when it's a, oh, it's quite old but 2000 somewhere sometime we do retrospect and party. What are we gonna do this in this? We do retrospectives and demonstration of the beta two and then party, self introduction, cake, games, why are we gonna do that? We have more communication, congratulation of beta release and tour of our project room. Tour to customer, bring customers in and have fun. And who is gonna come? Development team members and customers, where? The project room and dining room of headquarter and the result we expect would be customer satisfaction and build women relationship and good memory and so on. So, this one page captures the concept of project Christmas party. Next one, this book I made it, I showed it before is Sustainables of the Development, written back and it's about author is Kevin Tate forwarded by Jim High Smith and it's about metaphor software. It should be from building to ecosystem. To do that, he present principles. Two big balls and four small balls. Two big balls are feature and bank fixing and small balls are working product, defect prevention, design emphasis, continuous refinement and then jungle this ball to make software. And working product is there are some practices and defect prevention has practices and all those have practices. But what I'm gonna say is I just spent one minute for this but you'll capture all those concept instantly and you can remember this picture as a image of the book. I'll show some more others. I'll do my mapping a lot in the meeting, especially not for me for audience, I mean for attendees to keep them in one page. So, the my map for meeting would be, first we prepare those things like item, sorry, time, place, attendee and conclusion is left blank, to do is left blank and agenda here. And when you start talking, using this overhead projector, you enter keywords what you are talking about so that everybody can see like this. Topic two, okay, blah, blah, you speak about this and somebody speak about this and you can add icons like, oh, topic 10 is very interesting or topic 11 is a puzzling idea or topic 15 is connected to topic 10 and topic 14 and around this idea should be emphasized to do later or something like that. So this my maps works as a minute or captured context of the meeting and you can copy this one, I'll edit copy. I'll show you, this is essentially a tree structure, right? Tree structure, so if you just drag and drop this my map into Excel, guess what happens? I will paste this like this, it's a tree. So it works as a minute too, time and place, attendee, conclusion, to do agenda. And also this is a tree structure in Excel expressing illities or qualities of software, usability, efficiency, functionalities and so on. You can copy this tree structure into mind mapping. I would say software quality and paste it. Guess what happens? Like this, it's tree structure, so you can go back and forth and good point about mind mapping is you can move around one thing, like testability is now in maintainability but I think it's in functionalities so you can move this around and stability here to here or this here to here like this. You cannot do this in Excel. So when you're doing discussion you can gather ideas and moving around and connecting, gathering, clustering things. Mind mapping works very well. And if you want to, you can export to PowerPoint, export. Guess what happens? It's like this, software quality, usability, so on. So when I make a presentation I always make a mind mapping first to organize your thought and then going into details. This is how I use mind mapping in daily work. And I'll show you some more, some more. I am a guitar player. So in order to remember the chords, I use mind mapping, yeah. So this is a C major Lydian chord. It has several forms. Root string, root six string, five string, fifth string, fourth string, third string, like so. It's boring to non-guitar players but I like this mind mapping. Yes, I will. Do you play guitars? Oh, I will share this, yeah. And... A very nice question. This software is called Asta, which I developed. And I'm also selling. And I'm happy to give you for free afterwards if you wouldn't like to contact me. And a bit about this software. It started as a UML editor software. But in Azure world, do you use UML? Yes, yes. We use UML. But UML is too strict. You always have to think about this dotted line or arrows which way or things about that. But mind mapping is just keywords. So very quick to type in and a gathering idea is much more capability in this mind mapping than class diagrams or use case diagram or any other strictly semantic, strictly syntactic notations. So I started using mind mapping in Azure context. So I will talk about this later, next. But for the record, just for the record, we have like class diagrams or the state chart things a lot. You can add classes, you can add attributes, you can add operations, and you can connect with relations like this. But I don't go into it today. Okay, okay. And one more example from this book, Mastering the Requirements. It's written by Suzanne and James Robertson. It's a famous book about requirements. And the authors nicely send me a mind map of a persona. Persona, do you know the word persona? Yeah, it's a imaginary customer but concrete customer. So the persona, person's name is Pam and her family and her work and her hobbies like this. Okay, so about mind mapping. It is keyword oriented. You don't usually use sentences, just keywords, short keywords, so it's easy to type in. It's very fast, you can make notes quickly. And it has loose syntax and semantics than UML or any other software related technique. So you don't have to think about it. The line only means association, so very soft relationship. But you can categorize them into one branches or you can move it around. So it's very flexible but loose syntax, fast and easy. And it is one page so it's high level view of an idea. And one thing, when you take notes linearly, linear linearly, it gets longer and longer, right? But in mind mapping, it gets denser and denser. So in one picture is the most important thing. So it can be stored into brain. And it's evocative. By this, I mean, you can remember the context or the scene you wrote this mind map. So as I said before, your brain memories all this situation as a videotape, whole life. But you cannot access to that area of your brain instantly. So mind mapping works as a trigger to evoke that memory part. So it's like Google search to your brain. You have a mind mapping, you will Google search your brain to, sorry, my English, extract or to regain that memory quickly. By the way, I use mind mapping when I do wedding speech because in the paper, I don't use tools for that purpose. The branches is like, how do I met Bright, Groom, and when he was in elementary school, something. And an episode of his bad things. And some words from my friends and some nice words to Bright or something like that. So I draw that in this size index card, I keep seeing it. And in Japan, we usually use train to go to the venue of the wedding party. So I close it into this pocket and on the train, I just look at it. Memory, memory, just memory, okay, okay, okay, okay, okay. And in the speech, I don't see the memo but visualize the memo in my brain. Okay, right hand upper part, yes, okay, how I met him, okay. Then, okay, this part. So it works as a, also a index or a prompter. Prompter, yeah, visual prompter for me to do the speech. And the last one, explore and gather idea is what we are going to talk next is group mind mapping or interview mind mapping, I would say. It works when you gather idea from someone else. Like minute taking, note taking I showed you before is when you do a conference on anything, you gather idea into one mind mapping. So I'll talk about this then. Usually I do some workshop but today it's full so if we have time we will do this but today I will skip this ice breaker workshop today and go on. But I would like to say that this is my self introduction mind map, very simple one. Kenji is my name so and I draw always Japan thing because here Japan is my identity and it's very well. And what or favorite things and something else. You can choose those BOI, BOI is a basic ordering idea. Those branches, first branches but you can explore and grow the branches. So I will skip this workshop but I will show another example. This is a self introduction mind map of my friend Amano Ryosu-san and it says he likes balloon, actually he's a pilot and those like those areas and he loves wine and he said sake and oh sorry, beer, wine, Japanese sake, everything and he says here he likes cheese and he likes soba as a noodle, Japanese noodle and saying that cheese goes with wine and soba goes with Japanese sake. And he says that he once had a stroke too, interesting but he survived the stroke and so on. Okay, I'm going into the agile context of the talk. User stories, user stories been for a long time and it's first used the term as story. As you know, Kentback didn't say user story, just story because the point of story is telling, not writing. So the word requirements is the most bad keyword in the software industry, that's what Kentback said and he changed the word requirements to story so that you can tell to the people in person, I mean. So when you start writing, you write and write and write and write and you don't talk. So the point is just prepare a card and write a story, simple story and stick it on the wall so that you can pick up and go to user and talk about it. That's the original idea of story. So Ron Jeffries says this term like three C's. Three C's, so here's three C's of user stories. It's written on cards. So card is a works as a note, key to conversation. So conversation is the key, so detail behind what happened. The three C's of story card, user story. And Mike Kohn also says a lot about user stories. Thank you, Ron, thank you very much. And he's always also talks about user stories in this, user story applied. And he also talks, says that shift focus from writing to talking is the key. And a metaphor of trolling, which is written by Suzanne and James Robertson in that requirement book I showed you before. The requirements can be captured with different size net. So if you first try to use a fine net, you will lose. You will start from a coarse net to capture the rough idea first, then mature the requirements. That's the point of the book. And somebody, which I don't know, suggested this format in order to do something as a someone, I want to do this. It's called one of the user story format. How can I move this up? I don't know, yeah, here. In order to do something as a someone, I want to do something. This is a canonical form of a user story. Very simple, but the point is this part. In order to do something. So you can do something else if you can have this benefit. So you can choose between solutions. So that's one key to this one idea in this. Okay, so why mind maps and user story fit? So what I'm going to do is capture user's idea into mind mapping. So it's about shifting from writing to talking and trolling the requirements by coarse size net first. And also it's important to capture the context of the talking. You capture emotions or things. Once I worked with a customer who wants to printing, who wants printing in Java application? At that time, printing in Java is very poor, but I can't do that. So customer was very angry about that first, but she said that, okay, if you have a printing, what do you do with that printing? She said that I will take this and move this counter and enter this into this here, she said. So I suddenly thought that we can easily move this data without printing from here to here by programming. So she and she said, wow. So the point is when you capture just to do or requirements, you lose lots of information from that. Capture information, emotion. She was angry or she was confused about doing this, but when you capture this, her emotion, I found that I can do something. So emotional thing is also important. Use your right brain and colors and pictures so that you can remember what she's talking about in mind mapping. Okay, so, okay. From here, I would like to do a demo or a bit or a short act here with Mrs. Satomi to demonstrate how I can do mind mapping with users. Hi, Satomi. Pretend that I'm visiting her. She's a user of a system and I'm doing a mind mapping user requirement capturing using mind mapping. Okay, okay. And here's your mic. This is a mind mapping I usually use for capturing users' requirements first time. I am visiting a city library, which is in Bengaluru, which I don't know, but you should have one. Okay, I'll start, I will start this kit. It's gonna be three minutes. Just give you an idea of how I can do mind mapping with users, okay? Oh, nice, nice library here. Oh, hi, hi, hi. Knock, knock, knock, knock, knock, knock. I am Kenji Hiranabe. I have an appointment with Ms. Joba. Yes, hello, Mr. Hiranabe. I'm Satomi Joba. Please call me Satomi. Nice to meet you. Nice to meet you, thank you very much. I heard that you are planning to build a software system in your library. So I am here to talk with you about that today. Yes, thank you for coming all the way from Japan. Thank you. Yep. Oh, by the way, on the way here, some staff members of your library talk to me or say hello to me very nicely. I really like that. Do you usually do that? Yes, we have this program to greet customers and visitors when they come to greet and say hello. And this week is a say hello week, we call. So we try to be nice and say hello to the visitors who come in so they feel welcome and want to come here again and often. That's very nice. Thank you. When I put this note here, I will get back. I mean, get out of this skit. I will tell you something here. Note, in interview, this is a context interview to users. In the interview, you say one good thing about customers first so that your client will be nice. That's one tip from me during interview. Okay, well, I often use mind maps to get an idea of how we can build systems. So may I take notes when you speak to me? Sure, may I see that? Yes, sure. This is a mind map I prepared. And to avoid forgetting important questions and answers. So there are four branches in this mind map. I'm going to ask you in this order. Why, who, when, but say anything you want to say anything you anytime you think of. Okay, great. Great. Note, this type of interview, it's a pre-written, but anything you can say can be captured. It's called semi-structured interview. Structured interview is like a filling form. And a non-structured interview is just interview, but semi-structured is somewhat structured, but you can accommodate things later. So mind mapping is a very good tool for semi-structured interview. And also, mind mapping is called semi-structured. Like database is called structured. It has metadata and data. Mind mapping, it has metadata and you can get data, but from data you can make another metadata instantly. So data, metadata is fuzzy. So that's the point of mind mapping too. Okay, Satomi, to begin with, I'd like to ask you about the motivation of the system. Why did you think you want to introduce a new system in this library? Well, one thing is the budget. We have wanted to this kind of system, which is very common in every library nowadays. And finally, we just got the budget through. Okay, so budget passed. Good, good, good. And what else? Well, currently we use paper forms and records, a lot of paper. It is very time consuming to deal with all the information by paper. Staff members here overwork every day for this paperwork, and I want to reduce it. Overwork. Is that happened to this Bangalore area all the time? Yes, over time. So you overwork. So what else? Yes, another thing is a long waiting line of the book borrowers. Returning book is easy, but when people come in to borrow the books, our staff members at the counter have to write a lot of information on the paper called borrowing form. So borrowers have to wait for a long time. Okay, thank you. I just noted here your pain points. Okay. Thank you. What does this blue face mean? Blue face means I don't like, you don't like this point. Okay. Pain points, which I call. That things I want to improve. Okay, good, good. Okay. So let me confirm. So overwork is the viewpoint of staff, and long waiting line is the viewpoint of visitors, right? Visitors, correct. Okay, like this. Okay, then I would like to ask you about who is going to use the system? Well, this system is mainly for our staff members called Clark. Clark? Yes, Clark's our service staff at the counter who helps the visitors borrow the book. Okay, counter. So Clark works. Coonter. Nevermind. Clark serves a visitors, okay? Staff. What else? Who else? Does the visitors use the system? No. Of course. Wait, yes, actually, yes. They may want to search books by themselves. Okay. Well, but the system is mainly a backend system helping library staff. So don't think about visitors first. We want to focus on the staff. Staff part. Yes. Okay, so visitors, I will say future. Yes. In the future, you will. We'll like to talk about the, yes. Okay, okay, visitors, okay. And you said Clark will use the system? Yes. Who else is using? Who else? Oh, when? When? When is it? First of all, when visitors borrow books. Okay, borrow books. As I mentioned earlier, visitors have to wait in a long line to borrow books at the counter. I see. Mm-hmm. And? Also, when they return books. This is an easy part, I guess. Okay. And? And maybe you don't know about this, but there are a lot of work after the library is closed. Oh, you work after the library is closed? Yes, after the library is closed, we work hard, like registering new books when they come into the library. Okay. And also returning the return books to their original shelves. So who do this book registering? Staff member. Okay. Called Librarian. Okay, so he's different from Clark. Yes. Right? Okay, so there is another actor. I.D. people call this actor, but I don't use the term. But what was that? Librarian. Librarian. And he is registering a book, right? Yes. Like this. Mm-hmm. I see. I'm getting to see the picture. Oh, it is almost time. Isn't it? Oh, oh, sorry, sorry. It's almost time. Or if you wanna go. Yeah, I'm getting confused about the scripts. Okay, thank you, thank you very much. So, okay, you have other things, but I will ask you later. Okay. So I will add some homework part here. Okay. So that you can remember. One is you list services for visitors? Yes. So serve this for, okay. And when with the next meeting is? How's the next Monday? Okay, so next Monday. May I visit here again? In Bangor, yes. In Bangor, or how about in Japan? Could do that, I'm leaving tomorrow, okay. Sorry, sorry. I will come to your library again. So it's very nice talking with you, thank you. It was nice. Before that, may I just go through, quick to see what was the interview like? Yes, please. Okay. This one, city library, city library user story. Okay, I just use this one. So, okay, so why when you are gonna make the system? Budget passed and paper form is so bad, you do overwork. And there are long line of visitors, right? Yes. And staff called clerk is going to use the system. Yes. And librarian also use the system. Yes. And a certain book. And visitors can use the system, but it's going to be a future discussion. Yes. Not right now. Not right now. And this homework here is you will list the service. Sorry, services for visitors, right? Mm-hmm. Okay. Okay, thank you very much. It was nice talking to you. Nice talking to you. It was nice talking with you. It was a great start. I didn't see the picture of the system, but now thanks to you, it is beginning to show up. Okay, thank you very much. Thank you. Thank you. Okay. It was not a very nice act, but it's actually like that. So after this mind mapping, mind mapping like this will show up. So using this why, who, when, and who part is used as a user role or actors in the use case terms. And when ideas is going to be a user story or use cases or anything you want. It's a scene when user is going to use. So capturing those things from users can be done in semi-structured mind mapping with users. And this whole picture can be remembered by you and also by the users. So that next time you visit her, we both can remember what happened last time and reboot the next session. Okay, so I will do almost doing the summary and how I can use this into a user stories. So this is a user story mind map I wrote from the interview. So there's a story called borrow book. This can be user story or use case, whichever you want. It says in order to borrow book as a click, I want to read in book ID and member ID. This is not talked in that session, but later you will define this part. And return book use case says in order to return book as a click, I want to read ID book ID and confirm member name or when register book in order to register book into system as a librarian here, I want to fill in something blah, blah, blah or I want to search book in order to get information on the book to read the book shelf or to borrow the book as a visitor, I want to search book like this. So you can make a stories. And in order to, this is also a mind mapping. So I can just copy it and I prepare the user story mind mapping format in Excel. You can just paste it like this. Oops. So that you can easily print it out or you can also convert this into a PowerPoint so that you can print out like this. It's a very simple format. So I can convert it into, this is a PowerPoint but anything. Almost all my mapping tool has this features. You can drag and drop into Excel or anything. So this is a use cases I draw from mind mapping and this is a user story mind mapping. I will show you how to do a use case part. I'm sorry, render. Yes, yes, I just entered. I mean, I edited so that it looks pretty. Afterwards, so capturing the idea is one important thing and then you can discuss or edit to make it more nicer format if you want to. So like this, I will open a use case diagram and drag and drop this staff here as a actor and also you can drag and drop this borrow book, return book, register book, this drag and drop into use cases so that you can draw this a use case diagram very quick. And there's a link here. You can double click this staff link to this mind map staff or you can jump from borrow book. You can jump from here, sorry, from here to this here so that you can go in between. Okay, okay. So the big picture is like this. There is a user wish which is not structured well. So you go to users and talk using mind mapping and capture the context which you and the user is living and make a big picture as a mind map. So the branches would be like why, who, when and from that information, you can make user stories or use cases. And then you can do estimation or task breakdown or planning or testing, preparing testing and like that. Okay, so the conclusion. Mind mapping is effective when gathering information or exploring topics freely, which is not formatted well. So my talk is about from vague idea into more concrete idea using mind mapping, conveying ideas from vague area to more concrete area. And user interview mind map is semi-structured, meaning that it has branches preset but you can add anything into it. And it gives you a high level overview of the system and creates a big picture with the users, shared ideas. And why, who, when are the good questions, first questions to the users. And this topic is covered by this Sticky Minds article called My Aja Modeling with Mind Mapping and UML. You can search it by my name and Sticky Minds and the whole idea is like this, from soft vague idea into structured idea. And this is the last part, so I came from Japan and I'm very glad to be able to speak here. So we are engineers but we will make this software engineering world more better place. Thank you very much. Oh, by the way, if you want this software, ask me, I can give you freely because I'm an executive. Windows, Macintosh, Linux. Yes, I am. Now, not yet. Yes. I've been doing this for 11 years. I can send you a link from which you can download freely. Thank you.