Making Things Happen. Mastering Project Management. Scott Berkun. O’ REILLY8. Beijing • Cambridge • Farnham • Koln • Paris • Sebastopol • Taipei • Tokyo. Making Things Happen doesn’t cite specific methods, but focuses on Microsoft project veteran Scott Berkun offers a collection of essays on. Available in: Paperback. In the updated edition of this critically acclaimed and bestselling book, Microsoft project veteran Scott Berkun offers a.
|Genre:||Health and Food|
|Published (Last):||11 October 2016|
|PDF File Size:||9.82 Mb|
|ePub File Size:||18.12 Mb|
|Price:||Free* [*Free Regsitration Required]|
In our case we get requests from internal and external customers, who come into a prioritized list, which move into sprints with a clear vision, closer but short specs built into a word breakdown structure per responsible. Coming from the rare perspective of someone who fought difficult battles on Microsoft’s biggest projects and taught project design and management for MSTE, Microsoft’s internal best practices group, this is valuable advice indeed.
See our FAQ or contact customer service:. Fantastic introduction to the profession with an emphasis on software development but can easily be applied hapen other projects.
You can ask these questions: It will serve you well with your current work, and on future projects to come.
Review of Making Things Happen by Scott Berkun – Oliver Thylmann’s Thoughts
This is actually one reason we often build thingx in the sprint before they are implemented, to have a bigger feedback cycle. Is everything you do focussed on that goal? I liked his starting point that a project manager might actually not be needed as a dedicated position if you can distribute the responsibilities to different people on the team, which we are hzppen here actually.
There’s a lot of good advise in there, drawn from both Berkun’s personal experience with Microsoft and from third-party sources. Because it’s so general, some individual ideas and recommendations come across as common sense.
All excerpts from the book are published under agreement with the publisher. Then comes the people problem. Contents A brief history of project management and why you should care. Account Options Sign in. I want to read this book cause my lecturer. By the end, you’ll feel like sallying forth into your project meeting happsn with a whiteboard, dry-erase marker, and flexible confidence.
Based on his nine years of experience as a program manager for Internet Explorer, and lead program manager for Windows and MSN, Berkun explains to technical and non-technical readers alike what it takes to get through a large software or web development project. Feb 05, Zerg rated it liked it.
Review of Making Things Happen by Scott Berkun
Remember, and this is why we have short sprints, communication is still the biggest problem, see Tower of Babel as a story. Though the examples come from IT, they apply to a broad range of sectors.
Apr 08, Tyan rated it really liked it.
Chapter 1 A brief history of project management and why you should care Using history Web development, kitchens, and emergency rooms The role of project management Program and project management at Microsoft The balancing act of project management Pressure and distraction The right kind of involvement Summary Exercises PART ONE: I took a class in software management and the professor used this book This book is really happej.
Subscribe to Josh Kaufman’s email newsletter.
Making Things Happen doesn’t cite specific methods, but focuses on philosophy and strategy. The value comes from how the ideas support each other. Berkun makes the point that the usefulness of these suggestions depends highly on the company but I don’t think he emphasizes this point enough.
But what is a good vision? This project management book is all about Why Projects Fail — case studies, analysis of failed projects, suggestions and recommendations on how to improve your project management processes so your project will succeed. Simple and honest, at times very humorous writing.
All of these are illustrated with plenty of great examples — both successes and failures makung from his own career as a project manager at Microsoft. Yet this book does not include practical techniques, such as how to come up with a work breakdown structure, how to make halpen, etc.
The leadership and management lessons presented in this book are universal to all projects, making this revised edition a must-read. My only complaint is that the book is very wordy, though well organized.
If you’re happenn any agile or feature driven development, this will be very useful. Happeb is must read for everyone who wants to get things done and plan better in any business! I think this book is great for experienced project managers, but for beginners, it’s good to scan and skim at the first few times and get to understand the content tnings gradually.
Topics in this new edition include:.
You should start your design from the customer perspective and mull over it with a diverse set of people to get lots of different experiences involved. Audio thinsg of the book. I think this is a book that I’ll want to return to again as my career evolves and I find myself handling different kinds of projects.
This learning from the past also means from different professions. Coming from the rare perspective of someone who fought difficult battles on Microsoft’s biggest projects and taught project design and management for MSTE, Microsoft’s internal best practices group, this is valuable advice indeed. Can I suggest a book for your review?
Then comes the decision part: No other part is more difficult to rectify later. He is the author of two international bestsellers: This thints very long-winded read. Feb 01, Blake Kanewischer rated it it was amazing Shelves: A product manager is the one the ties between the market and the people who are building the product.
Jul 20, Tri Le rated it really liked it Shelves: May 03, Wendy rated it really liked it Recommends it for: This book actually provides many helpful solutions. Thanks for your response! The book makes an effort to recognize that processes should support the workers, not the other way around, so the topics are not obsessed with schedules and charts and the rigidity you find in most pm books. Have you created a guidebook for teachers or group leaders to use for discussion of the chapters?