Scrum combat -- agile software project management and development after trial reading

Scrum combat--agile software project management and development I
have always seen the topic of agile software, but I have never had an in-depth understanding of it. Participating in this reading activity gave me a real in-depth understanding of the relevant content of agile software.
As can be seen from the cover of the book, scrum provides a practical working guide for project teams to solve real-world problems with actionable information, and the specific solutions in the book can be used in various software projects.
The 5 and 6 pages of the trial reading are the praises of many masters about the book, and seeing these praises makes me think this book is worth reading. Increased interest in reading.
From the translator's preface, we know that scrum is a kind of agile framework. This book is a summary of the best practices of the success of scrum projects by the original author of this book based on his personal practical experience.
The preface gives a brief introduction to the contents of each chapter of the book, which is clear at a glance and I like it very much. This book uses 6 pages to introduce the content that different characters can skip to read this book, so that we can sit down with ourselves, read the chapters related to ourselves as soon as possible, and at the same time, we can also have a question about what our boss cares about. It is generally understood that, after all, you are in your position and you are looking for a job. Different positions focus on one thing differently.
The trial chapters are the first three chapters. The first chapter introduces the basics of agile and scrum, understands the basics of agile software development and project management, understands the origin of scrum, and why agile and scrum are effective in software project management.
The second chapter introduces the content of finance, understands some things about project investment that I don't know, and the algorithm of return on investment that project investors are concerned about. The progress of the comparison project needs the support of funds, and the people who invest always need a return.
The third chapter introduces how to communicate with managers at all levels. Introduces in detail how to communicate effectively with the top managers of the enterprise, the top managers of IT, and the middle managers of IT. The importance of maintaining day-to-day cooperation with middle managers is emphasized here.
This concludes all trial chapters. After reading these chapters, I hope to get the whole book as soon as possible and look forward to it. . . .