Practical Approach to Large-Scale Agile Development, A: How HP Transformed LaserJet FutureSmart Firmware (Agile Software Development Series) 1st Edition, Kindle Edition
The Amazon Book Review
Book recommendations, author interviews, editors' picks, and more. Read it now.
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
About the Author
Mike Young is the program manager directing day-to-day efforts across our many distributed teams at HP’s LaserJet Core Firmware Lab. Mike has been involved in development of HP LaserJet Printers for 18 years, and he previously designed satellite control systems for Hughes Aircraft Company. He also is one of the strongest advocates of agile approaches and helped get the organization started down this path before anyone really knew we were doing agile. His hobbies are family (he’s married, with two daughters and two sons) and playing racquetball. In agile, we’ve found that a program manager should spend most of his/her time watching the metrics and quietly coordinating behind-the-scenes to cater to the bottleneck. In our sprint checkpoints, we tend to minimize slideware and maximize problem solving and demos of new user stories.
Pat Fulghum is architect of the HP LaserJet FutureSmart firmware and its development team’s agile toolset. Pat’s been at HP for 24 years. He found out during the past few years that his favorite escape is scuba diving in Maui with his family (he is married and has a son and a daughter). A large-scale agile initiative requires a central architect who can help maintain architectural integrity amid many pressures to do otherwise (which keeps the system enabled for the future) and who has the vision for making sure the architecture supports both firmware development and qualification. Pat still loves to get in and dig deep to solve vexing technical challenges. He also loves to find developer productivity improvements (build time, triage time) and has been the passion behind our “10x productivity improvement” vision.
--This text refers to the paperback edition.
- ASIN : B00A8IYB2W
- Publisher : Addison-Wesley Professional; 1st edition (November 15, 2012)
- Publication date : November 15, 2012
- Language : English
- File size : 10760 KB
- Simultaneous device usage : Up to 5 simultaneous devices, per publisher limits
- Text-to-Speech : Enabled
- Screen Reader : Supported
- Enhanced typesetting : Enabled
- X-Ray : Not Enabled
- Word Wise : Not Enabled
- Print length : 210 pages
- Page numbers source ISBN : 0321821726
- Lending : Not Enabled
- Best Sellers Rank: #475,258 in Kindle Store (See Top 100 in Kindle Store)
- Customer Reviews:
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
This book gives both a great overview of that, along with a lot of practical "how-to" possibilities which helps tremendously to understand how a 400-person, global and multi-site embedded software organization can transform to scaled agile practices and principles. I highly recommend it to any leaders in any organization that is considering CI/CD, automation, and agile.
One big advantage of this book is that they come at the whole question of agile transformation in a very out-of-the-box way. As they state in the book, they didn't go out and get agile consultants involved at the start, so their path is atypical and therefore provides and alternate perspective to what you might run across when looking at other scaled agile literature, such as with the SAFe, LeSS, or DaD frameworks, with some good practical insights on how to manage overall technical architecture, business level prioritization and scheduling, CI/CD test automation, and many similar topics.
Well structured, an easy read that you won't want to put down (if you are crazy like me and like this kind of stuff!) and heartily recommended.
I don't think all of the elements they use as selling points will change everyones mind (i.e. if your leadership is set on existing methodologies, this won't convert them easily), but provide some good talking points to people who are ready and open for change.
Overall, this is an "OK" book, but if you are trying to go from novice-to-expert in your agile/scrum knowledge, I suggest checking out Essential Scrum by Mike Cohn. If you are looking for a book that provides some insight into how other companies implement agile/scrum in real scenarios, this is a good example.
Do not read this book expecting to find a recipe for how you should “implement agile” or complete an “agile transformation” in your enterprise. Rather examine the processes and principles by which HP reached their successful outcomes (some of which they highlight as being somewhat counter to accepted agile thinking).
But do read this book.
If you backup from large scale agile development you come to the start - software development values and principles.
This book focuses on the business needs, innovation and responsiveness, creating and diffusing new knowledge within a team and with your customers AND how to tap into those strengths. The book does a great job of sharing their business context, the decisions they made, the tools they used, the processes they designed/redesigned, the practices they evolved and new metrics they created. The secret sauce stuff! Read this book to come away with new ideas, best practices and approaches to managing change in your journey in moving towards enterprise agility. Enjoy!
As recommendation I think to make it more inspiring, it should include more visual elements.
Top reviews from other countries
This book really helps any organisation who is about to change to an Agile way of working that has a large team of developers, or an organisation that is about to scale up the investment in software development and needs to see real return on investment.
It is not based on pure theory, but describes how the team decided to adopt certain "best practices" but also reasons why other approaches generally considered to be "pure Agile" were not appropriate - and why.
Books like this, written by people who have gone through the pain themselves and know what worked for them and what didn't, what is critical early on and what can be left until later, is a "must read" for anyone about to embark on a similar journey themselves.
It has certainly helped me, as we are intending to massively increase investment in real-time software development and I really needed to know what had happened to people who had trodden this path before me.
- it is real-world example, and has much more concrete HOWTOs, than some of the books of the subject
- it covers experience of applying agile ideas (I tend to agree with Gojko that terminology was not always accurate) to firmware development, which is still considered an off topic when it comes to agile methods of software development, unfortunately
- it is a small book so you can give it to "very busy" colleague/manager. This is not always a plus but I covered it bellow
Yes terminology was not always strict, but you get the ideas, and I believe this is much more important. Since I work at a company with similar business (firmware development, multinational, integration with high-level management systems), a lot of problems/solutions described in the book, are quite useful. The book also contains a lot of pointers to more detailed material and often refers to mistakes made, which is true gem
The only thing I missed more details on handling people related issues - convincing people, tackling conservative opinions. In a big organization there are a lot of people and biggest problem is communicating with people. I am pretty much sure that pushing such change in the organization is about advocating the methods to people from all kinds of levels and groups. In the book there's good chapter on convincing marketing and possible strategy for that, but I am pretty sure similar communication issues raised in all teams of the company, I felt this topic was not very well covered. After all it is a small book and this might have been done on purpose, but probably second edition will be done, who knows ? :)
I worked for a large mobile company and can strongly relate to the experiences and advice in this book. It is the best scaled agile book I've bought AND it's the thinnest. (Lean in more than just title :-) )