Hello everyone, I am Ling. Today I want to share with you how I use Heptabase to dismantle the book "Scrum". The reason why I want to dismantle this book is not only to understand the SCRUM process and see if it can be applied in this book besides personal management. There are a lot of proper nouns that I have never seen, so I would like to take this opportunity to break them down in detail. The one at the top is first of all, let everyone take a look at the traditional notes I took using Notion or Bear in the past. In most traditional Due to the limitations of note-taking software , I usually make a dotted note with a long content and a linear structure . The structure of the note basically follows the table of contents of the book. When I follow the table of contents and add the fomo mentality, it will be very easy. Writing down content that I find useful but may have been repeated causes the notes to become lengthy and difficult to organize. This does not mean that the author is not concise enough , but that the author often tries to persuade the reader or help the reader quickly understand a new concept . I would have reiterated the key points throughout the book or used various cases and analogies to support my views. For example, in the preface, the author first points out the problems of the (existing) project management method, that is, the waterfall method, and then discusses it. How he proposed a new solution to this problem - SCRUM , so after officially entering the first chapter, he will start to introduce what SCRUM is, its basic idea, the origin of its name, and then explain in more detail its characteristics and specific effects. In the second chapter, the author began to talk about how he designed the SCRUM system . He referred to many models and methodologies , such as OODA for Air Force training, and PDCA, and finally used Aikido's Shou Po Li. This system is a good metaphor to help readers understand the characteristics of SCRUM faster . In subsequent chapters, you can see that the author will talk about the characteristics of SCRUM while explaining how to implement it, including how to select a team, master the time rhythm to eliminate waste, etc. , and will also intersperse it. Some cases are matched . At the end, the author also thoughtfully integrated the execution steps of SCRUM and appended the corresponding number of chapters to let us know the specific details of each step. We can go back to the previous chapters for review, but then we will find that when When all content is presented in a linear form, there will be a big limitation , which is that I will be less efficient when reviewing in the future. I have to keep going back and forth and it will be difficult to understand at a glance. Next, let’s see how Heptabase can help me overcome this. Basically , I still have a linear note at the beginning, which usually comes from the lines and annotations in my reader. After importing the notes into the computer, I will disassemble and reorganize them according to the similarity of the content, or the different dimensions of the content, like When the author points out existing problems at the beginning - the waterfall method, I will pull out the waterfall method and discuss it in its own way. Then I will break down the characteristics of SCRUM in each chapter, its origin or operation method into different The author of the block image also mentioned "agile" in the middle. "Agile" itself has different levels from SCRUM. I will also separate them independently and reorganize them, then refine the contents of each block and finally see if there is any correlation between the different blocks. If you have sex , it can help me understand better. Now you can see the right half. This is the result after I dismantled it (you can ignore this area). We can see that the originally long linear card will eventually grow like this. This is also The last card to be completed in the whole whiteboard comes next. The penultimate one is the SCRUM process system and the green cards in other areas. These green cards all have the function of index or summary. When I want to complete these index cards, I must first I classify and reorganize the content of all other white cards , complete the card subscripts, and then put them back into my summary card . So if necessary in the future, I can even directly search for a single card. That’s enough for me. , what takes the most time is the subscript part of the card , because when I want to refine the reorganized content, I have to think about how to express the key points of the card in one sentence. At the same time, I hope that this sentence can show the causal relationship behind its point of view, allowing me to When I look back in the future, I can clearly understand the context by just relying on this sentence. It is not just important to remember that the action of continuous inspection and adjustment is important , but why it is important and what it can achieve . I can clearly understand it when I return to the opened cards. I see that SCRUM has three major characteristics. One is " finding and making the highest value deliverables through continuous inspection and adjustment. " For me, this sentence alone has replaced many contents in the original linear notes, and then it is the concept of efficient teams. What’s important here is also a rebate to the subscript just mentioned. In the original linear notes, it was only pointed out that efficient teams have four core teams. They must have excellent goals, must be cross-functional and have autonomy, and be small-scale. If I am just like this If I remember it, I actually have to rely on my memory to remember it. But if my title today points out the effects of these four points, I will understand better, instead of just relying on memory and the third point - —It is also good to eliminate unnecessary waste . After sorting out these three characteristics, I suddenly found that these three points can correspond to the three roles in SCRUM, like the part that emphasizes value, which can be rebateed to the product. The person in charge, the product owner , is responsible for defining and identifying the value at the very beginning of the project. He must constantly collect feedback from internal or external sources and coordinate with the development team to see how to create something truly valuable . Refer to the conditions of "building an efficient team". Of course, because they are responsible for execution , several other characteristics will also be related to them and will be applied in the development team. As for reducing waste in the process, it is left to the Scrum Master to perform this role and not participate in product development . He is responsible for guiding everyone to act in accordance with the SCRUM structure to ensure that the overall process is transparent. Then he must also find ways to remove various obstacles that affect progress. When I connected the SCRUM features and roles, I found that the overall structure became very clear. All that was left was Continue to clarify the objects and activities and the relationship between them and roles. For example, the product owner is responsible for managing the product backlog and sorting the items. The refinement meeting of the items will invite the development team who are the executors to discuss together. The development team will then sort the items. Break it into detailed tasks for execution and then produce each sprint backlog. The Scrum Master is responsible for maintaining the transparency of all outputs and also manages a chart called a burndown chart to ensure that everyone's progress and speed are on track. The scrum board we often see is actually a visualization of the sprint backlog. What elements are included in it? I will use lines to connect the corresponding objects and mark the relationship. At first, I was not clear about the definition of increment. I later learned about it. In fact, it is the final result after each sprint. The last thing left is to clarify the activities. I will arrange them from high to low according to the activity level and time point order , and from left to right. Then you will know what the sprint is and what the sprint contains. For example, there will be a planning meeting at the beginning , then several refinement meetings in the middle, and a daily stand-up meeting at the end of the sprint. At the end of the sprint, there will be two review meetings , one to review the content, and one to review the process. In addition, sometimes there will be some additional content that the author may recommend. For evaluation methods, I will use an additional green section. Differentiate this evaluation method outside and then let me know through the connection at which stages these evaluation methods can be applied. Above, it is a disassembled and digested reading note. Through such visual organization, it not only makes everything become If I forget it clearly in the future, or if I want to review specific details, I can easily find the corresponding content . This is how I use Heptabase to take reading notes for today’s book content because I am not a SCRUM expert. If there is anything unclear or personal misunderstanding or over-translation, please bear with me . Finally, if you think the video content is helpful to you , you are welcome to like and share it , or you have any feedback and ideas or want to watch it. If you want to disassemble the type of book, you can also tell me through the message ~ see you again when you have a chance
