"Each project or task has certain risks of an unexpected wind disrupting the work."
Project Management for Automotive Engineers: A Field Guide is a book that can act as guidance or manual for automotive engineers to manage a project and aspects that they need to prioritize. Written by Jon M. Quigley and Roopa Jha Shenoy, project managers and engineers with experience in automotive engineering, this book gives some useful insights on project management and challenges that may occur in it.
This book consisted of 10 chapters and it begins with Chapter 1 which is Overview of Managing Projects. The next chapter is Business Case and Product Development Models. Moves to Chapter 3 are Vehicle Subsystem and Concept Generation meanwhile in Chapter 4, the authors will discuss Product Development. In Chapter 5, the topic is Process Development and Chapter 6 is about Product Life Cycle and Testing. Chapter 7 features Design to Ram-Up Production and Chapter 8 is about Early Production. Moves to Chapter 9 which is Project Closure and few things related to it and closing remarks or conclusion in the last chapter.
At a first glance, I thought this book is difficult to read since it discusses automotive engineering which is not everyone's cup of tea. But when I begin to explore it, I never expected that this book is a little bit easy to digest if compared to other books on the same topic. Using their expertise for years in automotive engineering, the authors explained the concepts in a new refreshing perspective with a pedagogical approach to which blended the theory and practice of learning. It is written in a straightforward tone, clear and no bombastic or confusing words since this topic is already heavy. It also provided statistics, pictures, graphs, illustrations, and the 'Box Moments' to highlights important facts to readers.
An interesting part of this book for me is, how the authors feature a fable story written by Arnold Lobel in 1972 entitled "A-List" which depicts the tale of a toad and a frog who are friends. The rest you can read in the book. It is some kind of analogy used by the authors to explain certain topics in it. The lesson from it is project managers must know how to react when something unexpected happens. They must have elaborate time plans according to the authors. If something happened, they know how to handle it. Sometimes, we must ready to expect or predict something so that if anything happened, in case of the bad one, we know how to manage it. In other words, something that I called 'positive pessimism' on a lighter scale.
Besides, the purpose of this book also is to look at the field of project management as a risk-based making activity and focusing some crucial skills needed to successfully execute the project. It also stated three important aspects that will decide whether the project is successful or else which are quality, schedule, and cost.
Finally, from this book, an important word that became been highlighted is a crisis. As John F. Kennedy says about it, "When written in Chinese the word crisis is composed of 2 characters. One represents danger, and the other represents opportunity." In this context, project management is a risky task just like the author said. But with clear strategies and guides that are given in this book, it can be an achievement. For aspiring engineers or project managers out there, this book should be on your list. Easy to understand and the messages are clearly delivered, I give 5-star rates for this book.
Probablemente uno de los mejores libros de gestión de proyectos que puedes leer. Si tu trabajo está relacionado con el campo de la automoción es indispensable. Pero aunque no lo esté, la profundidad y sencillez con la que explica todo el proceso desde el germen de de un nuevo proyecto, a su planteamiento inicial, valoración, inversión, desarrollo, gestión de problemas, información de inversores, control de proveedores, evaluación de costes, mejoras, estimaciones temporales, etc. Todos hemos alabado el uso de métodos lean, de gestión agile o de cualquier otra herramienta o forma de desarollo de un proyecto que nos ayude a ahorrar tiempo y dinero y mejorar procesos, pero este libro te enseña con errores reales, soluciones tomadas y la explicación de todo su proceso de desarrollo a tomar decisiones tras valorar cada información desde muchos puntos distintos y con resultados predecibles. Una auténtica joya que pasa a formar parte de mis libros de cabecera y que utilizaré como libro de referencia durante muchos años sin duda.
Like a thriller novel, the story of Project Management in the Automotive Industry has many pitfalls and dangers that are faced on a daily basis. Project Management is not for the faint of heart. It’s fast paced, multi-layered, challenging and highly visible. You have to think in this job. Focus. Weigh the decision-making pro’s and con’s and then take ownership of your decision. A Project Manager must have good communication skills, an in depth understanding of the goal, technical interdependencies and a meaningful grasp of all stakeholder concerns. A Project Manager juggles. There is a certain personality type that can do this job successfully. Do you, dear reader, qualify for a career like this? Read Project Management in the Automotive Industry to find out. If (and only if) you can fill these shoes, you are headed for an interesting ride where YOU can be the hero at the end of the story.
There are other paybacks. Creativity. Working with technically proficient people. Sometimes what a PM learns can end up being a patentable idea. The job satisfaction meter can be high.
I love the way important points are visually depicted in this book. The pacing is good, keeps the reader’s attention.
Below are some detailed comments:
Chapter One Suggest Figure 1.11 Project Organization include the Requirements Team because traceability of requirements is hooked to test cases that validate requirements.
Chapter Three Glad to see Figure 3.7. It demonstrates requirement detail and traceability.
Section 3.6 Is there a Quality Assurance person that reviews the review for robustness? How do you police a quality review?
I loved this => “This relationship between OEM and Tier 1 suppliers becomes more complex during a time of environmental instability, such as a global financial crisis. In the case of the financial meltdown of 2008/2009, both the supply chain and the supply base for the automotive industry were affected worldwide due to complex interdependencies between Tier 1 and multiple automotive companies.”
Figure 3.10 Quarterly census of employment and establishment for North America is excellent. Gave me pause in thinking about external influences in the world market and how everyone down to the individual contributor are affected.
Project Managers have to know the broad vision but also appreciate the details outlined in the specifications and requirements.
Chapter Four I did not know the Cloud is widely used in the software industry in the automotive business. This is not my experience because of copyright infringement and sometimes national security concerns. Think of China who does not honor copyright and will give intellectual property away (for a price) to a company’s competitors.
I learned something else – mules.
I loved the description of innovation blindness. The team energy has good intentions but the direction -cost/benefit - faulty. This is where effective people management comes into play. You don’t want to diffuse the energy BUT you do want to direct its focus.
Section 4.3 “Experience suggests that design engineers underestimate the time required to develop the initial requirements and prototypes, and that results in compression of time for testing time of the iteration.” I found this to be discouraging. How does innovation come about? The answer is probably innovation is removed from a deliverable path and put into R&D.
Section 4.4.1 People management challenges – excellent summary, good ideas and where to be cautious.
Chapter Five “Confusion – poorly articulated decision or direction as well as contradictory or misunderstood goals and metrics. This can be due to poor communication within the project.” Here is an opportunity for an example that will make the reader laugh. A new employee was hired in an elementary school cafeteria. The manager asked the employee to make potato salad, instructing her to put the potatoes in a pot as one of the steps. The employee did exactly as she was told BUT she did not take the potatoes out of the potato bag. No potato salad was served that day. True story.
Chapter Six I appreciate comments regarding the fear factor if tests fail. This speaks to effective relationships that a good Project Manager must form. Trust. I also appreciate the observation regarding the environment where the end product must operate. Again, I learned something.
I love the idea of planning a buffer in the test plan, however, my experience is one where a superior would remove that buffer to make himself look good. There’s always a price in these decisions.
Chapter Seven As I read, I wondered about something and then you would answer my question. That gave me confidence that I was on the right track in my thinking.
I liked the warning that made me lift my eyebrows: “Each year there are numerous examples of unsuccessful product launches due to toothless attempts at controlling the technology to serial production.” Wow. Project Managers must have backbone!
For me, I learned about ramp-up. It feels to me like “living on the edge” because discovery can still take place.
In ramp-down you don’t retrofit? Ah, you called it carry-over parts.
Under Supply Chain Decisions, this was a big thing for me: Off-shore production—does it make a difference? I loved your comments regarding “real transfer value”.
Regarding international affairs – tariff changes, political power changes that affect industries. I remember “Emerging Markets” that affected many businesses. This was a plan to give business opportunities to developing countries. High risk stuff. Didn’t the automotive industry experience some of this? I assume they did BUT there was always a fallback plan to mitigate the risk, I assume.
Ah, this is mentioned in section 8.2.1 but my suggestion still stands for chapter 7 on a broader brush scale. Chapter 8 has a nice example with Brazil.
Chapter Eight Loving figure 8.2 Complexity of Parts Coming Together in Supply Chain.
In reference to this phrase, “…the longer the logistics chain, the more opportunities there are for supply chain disruption.” My question is, “Isn’t this decision mandated on a higher level outside the influence of the Program Manager?” My gut tells me a VP might enforce this for some reason and then toss problem resolution to the PM (i.e. make miracles happen). I noticed you hinted at this in Chapter 9.2 “Make sure to note these events and present to the executive management the challenges these changes may have inflicted upon the project.”
Chapter Nine Loved this => “…take a moment to acknowledge the work and sacrifices the team has made to reach the end of the project. Review the fruit of the team’s labor…”. This is plain, good ol’ leadership. Great message.
I laughed at your comment regarding pet (strategic) projects (section 9.4.1). Great point BUT how does one stay away from a mandate? Fancy footwork, I presume. Maybe it’s time to schedule that medical operation you’ve been delaying? Seriously, when something like this happens, I document the heck out of everything as a CYA activity and communicate, communicate, communicate.
“Value project: Made in XXXXX”. This is a powerful message with terrible consequences. A reputation lost is not recoverable -OR- it takes a long, long time.
Maybe Chapter 9 should be read first? It is tantalizing.
Chapter Ten I like the closing remarks tying into the Frog and Toad analogy in the Preface. Good summary.
I think this book is one of those things a PM wants to keep in their hip pocket. Most of the time things happen quickly and on different levels at the same time. This guide will help a PM keep the straight and narrow; something to jog a memory, a strategy when ticklish things come up, a reminder. Well done.
A must read for anyone considering a career in Project Management in the Automotive Field. Terms and concept were carefully explained with examples that can be understood with ease. It gives a detailed outline of what is expected of a Project Manager and what he/she should do when an unforeseen event occurs in the AUTOMOTIVE FIELD. The book not only gives explicit details into the day to day lives of the project manager at work, but also how to make certain decisions, use certain tools, communicate with suppliers, stakeholders and team members. I am currently a student of AUTOMOBILE TECHNOLOGY and this book has helped me see the automotive field in a new light, and the importance of planning & decision making. The use of diagrams and graphs to explain concepts made the book fun to read. I believe this book would help a lot of people aspiring to be PM to fully understand what it takes to be PROJECT MANAGERS not just in the AUTOMOTIVE FIELD but in other various field. It would also help team members, Engineers, Suppliers and every stakeholder involved in a particular project to better understand project management. A big thumb up to the authors, a lot of work and effort was obviously put into writing the book. Project Management for Automotive Engineers: A Field Guide
Project Management for Automotive Engineers: A Field guide is a very useful reference for Project Managers in Automotive Industry. While PMBOK has an exhaustive theoretical foundations universal to project across various business segments, This books sets itself apart from PMBOK, in a way that its like a living through evolution of projects and its associated challenges in an automotive industry. The books also emphasizes best practices and approaches in specific scenarios across automotive industry/ organization of eminence, important tools and techniques. Book covers well application of Agile approach to meet challenges in VUCA world of automotive project Management, AIAG standards, importance of Systems approach and thinking, LEAN Management and has a comprehensive discussion on Risk Management. Book addresses the practical approaches to deal with engineering and management challenges in a project and establishes baseline principles of successful project execution. Author empathizes well with the dilemmas of Project Manager, and discusses leadership and communication challenges in working with team, top management and other stakeholders. It helps identifies the pitfalls of project management and exit strategies for an unviable projects. Author successfully demonstrates how challenges manifest in an increasingly complex business environments of automotive businesses, where several projects vie for resources, sometimes located across globes with multitude of suppliers in myriad legal requirements. The book will serve as a valuable resource to young project managers, and shall improve the learning curve of practising project managers.
Overview of Project Management
Covers fundamentals aspects of project scope, organizational structure, stake and stakeholders, dimensions of project management, risk management, and basics of contracts. Chapter will help acclimatize with language of project managers.
Business Case and Project Development Models
Covers important aspects of business case and its justification, models of project development and project life cycle. Discusses well the basics of Agile in context of automotive project management. Application of Pugh Matrix in prioritization of issues and their resolution is very relevant.
Vehicle Subsytem and Concept Generation
As Projects evolve they grow in complexity and are influenced by many stakeholders and may turn out to be either something unwanted/unviable or radically different from customer requirements. Chapter rightfully discusses using important tools like VOC, concepts of traceability and Configuration Management in Project Management.
Product Development
Discusses Project Scheduling, interdependencies, review of project using commonly employed gate criteria, importance of simulation/virtual testing and prototyping in product development including its advantages as well as pitfalls, using right tools and processes including work package transfers. Discussion on Key product characteristics is important from the point of view of QMS requirements also.
Process Development
Again Process is key to successful project management and manufacturing, and is therefore also fundamentally important to important QMS standards. Chapter discusses concept of Processes, Process metrics and Process control.Chapter begins with introduction to Lean, Lean as a culture has found place in manufacturing industries worldwide as culture is key to the process sustainability and meaningful engagement of employees.
Product Life Cycle and Testing
Good test strategies are integral to successful product development, Chapter elaborates on developing effective test strategies which comprehensively covers the product specifications and customer requirements. Application of Agile perspectives to Testing is relevant and bring in fresh perspectives to domain of testing in automotive industry. Often beginners get confused in realizing the difference between basic concepts like product verification and validation, Author is painstakingly diligent in covering all essential and fundamental concepts.
Design to Ramp up Production
Projects culminates into operations, and bring in fresh set of challenges in terms of establishing capability of manufacturing and scaling up production. Introduction to AIAG requirements of Part approval processes, Planning Supply chain, utilizing IMDS are key takeaways.
Early Production.
Scaling up rate of production, partnering with suppliers, establishing customer services for introduced products and stabilization of quality of product in manufacturing is critical to success of product in particular and business in general. Authors have elaborately discussed all these activities with specific issues of exports and customization.
Project Closure and Something More
Explains the meaning of Project closure and importance of Knowledge Management, Knowledge management provides competitive edge to successful business and every project executed provides lessons in each of project management areas, When this knowledge is absorbed, it effects the change in organizational process and way future projects are executed. Chapters helps in Identifying critical knowledge in executing projects. Chapter goes on further to discuss characteristics of Megaprojects, Projects of low profitability, Projects arising out of legal requirements, and influence a project Manager can create in a failing project. Project Management is an art, and Chapter aptly contains a section on soft skills for project Managers which is key to tactfully and intuitively manoeuvring a project to success.
This book provides the main good point for the Automotive engineers to improve their skills as project management.
The book gives the overview of managing the Automotive Projects and why project management for the Automotive industry has so much importance.
The automotive industry has many disciplines, challenging sourcing, and enhanced security and pollution standards that must be met. This makes Project management challenges for the Automotive industry.
Coupled with higher investment in R&D budges, and lengthy-time to compilation,
In the first chapter, these books give an overview of Project Scope, Cost Management, Timing, and scheduling. Risk Management and impact of organizational influence on the project. It discusses the roles and responsibilities of the stakeholders and Sponsors, and the importance of good communication for the better management of the project.
Chapter two is mainly about the Business case and project development models. Books explain that how each project is created for the profitability of the business. Wrong assumptions can lead to miscalculations that can cost a business a huge amount of money. How incorrect data or inaccurate models can lead to a disaster. The second chapter also touches on the financial aspect of the project by discussing the return on investment, cash flow impact, calculating the payback period, and internal rate of Return. It then gives the overview of a Project life cycle and discusses various models of how the project can be executed.
This chapter then gives an overview of Agile Scrum Methodology and its fundamental ruins like Project backlog, Sprint backlog, Sprint, burndown chart, and retrospective meeting. The chapter discusses the various models of development that are commonly used in the Automotive development process that includes Waterfall, V-Model, Toyota Model.
Chapter 3 is all about Vehicle subsystem and concept generation. This chapter gives an overview of the project risk and opportunity involved in the project. Projects should strive hard to minimize the risk and improve the profitability using proven good concepts. The chapter suggests Voice of Customers and Competitive intelligence to drive the product strategy. Later in the chapter, the book deals with requirement gathering and Change Management and how requirements traceability and Configuration Management plans are created.
Chapters 4 and 5 are about Produce development and Process Development.
Chapter 6 deals with the Product Life Cycle and testing. Testing the project is a source of great risk for any product. An established process should exist for testing and reporting the bug. This chapter gives detail on how to develop procedures for better testing. The testing process has become complex and automated. The product manager should set the key performance metrics for the testing. Later in the chapter, the author defines the difference between the Verification and Validation process and gives insights on how to conduct the validation process.
In chapter 7, “Design to Ramp up Production”, the author talks about ramp up production.
For the automotive industry, ramp up to production cost is another major cost incurred in the project life cycle, primarily due to heavy investment cost internally and cost incurred by the suppliers. It is also another opportunity for success or failure. Author then gives details of critical activities to support the ramp up process and its Environmental impacts.
In chapter 8 “Early Production”, the author enlists scaling up the rate of production and other issues.
Scaling up rate of generation, joining forces with providers, setting up client administrations for presented items and stabilization of quality of item in fabricating is basic to victory of item in specific and trade in common. Creators have examined all these exercises with particular issues of trades and customization
Last chapter is about Project Closure and Something More.
Clarifies the meaning of Extend closure and significance of Information Administration, Information administration gives competitive edge to effective commerce and each extend executed gives lessons in each of venture administration regions, When this information is retained, it impacts the altar in organizational preparation and way future ventures are executed. Chapters make a difference in Recognizing basic information in executing ventures. Chapter goes in advance to talk about characteristics of Megaprojects, Ventures of moo productivity, Ventures emerging out of legitimate necessities, and impact a Director can make in a falling flat venture. Venture Administration is an craftsmanship, and Chapter apropos contains a area on delicate abilities for venture Directors which is key to prudently and naturally moving a extend to success
BOOK:PROJECT MANAGEMENT FOR AUTOMOTIVE ENGINEERS:A FIELD GUIDE BY JON M.QUIGLEY AND ROOPA.J.SHENOY
BOOK REVIEWER:- OKOKO AYEZU TAMARAPREYE
SYNOPSIS:-
This SAE book is one on the nitty gritty of managing automotive projects from development time; testing time;validation time;verification time; to launch date looking at cost implications; complying with import ;export;safety and pollution laws while not forgetting legal requirements in various markets around the globe.The book looks at the role of the various actors in the sector in project delivery from executives in the sector;team members;legal team;stakeholders and sponsors.It highlights the various skills needed by a project manner ranking communication as a top skill.There is also a touch on the business justification for venturing into an automobile project which may range from a variety of reasons mentioned including entering into a new market segment;meeting legal requirements or fixing quality issues.
LESSONS LEARNT FROM THE BOOK READ:-
📞Automobile companies resought to a phase gate product development process to ensure there is maximum return on investment.
📞There is need to put risk mitigation plan on the fore for project delivery.
📞Cost management in product and project cost is important for project acceptance and improving the company's position in the market while creating a new market.
📞Need to decide who makes estimations in cost for delivery whether the team;executives or management.
📞Need to know the role played by government in time line setting and also to know who determines the timeline.
📞In meeting timeline there is need to understand task interdependence.
📞Automotive products have their advantages and disadvantages
📞There's need for prioritizing;juggling of priorities;information management and passing down information to prevent talent erosion and delays in project delivery.
📞Not to over utilise human resources to avoid project risks.
📞Each organization in the automotive industry is influenced by its culture,footprint, size ,age,level of regulation and technology in its project delivery.
📞The various organizational structures when applied have their advantages and disadvantages.
📞There is need for co location and distribution of members across the globe to enable large distribution in an automotive company.
📞Procurement in the sector involves various contract types.
📞The importance of the use of the cloud in software industry and automotive industry in finding solutions to issues quickly.
APPLICATION OF LESSONS LEARNT:-
The lessons learnt in the book can be seen worldwide as automotive companies embark on projects developing new product models to meet quality demands. A legal practioner with interest in this sector has a lot to learn from the book also
Project Management for Automotive Engineers: A Field Guide - By Jon M. Quigley and Roopa J. Shenoy
This is a book which has been designed with a view to describe the principles of project management within the context of the automobile industry. From start to finish, from basic planning to merging the entire range of thinking processes, the book formulates a working plan in application in order to guide and control the sum of all activities through the implementation of the project.
Essentially the book is broken down into a description of the several fundamental steps that when placed together in sequence, will generate the complete blueprint for the methodical execution of the project in pursuit of the final goal of project delivery.
The book is divided into the following sections -
-Overview of Managing Automotive Projects -Business Case and Product Development Models -Vehicle Subsystem and Concept Generation -Product Development -Process Development -Product Life Cycle and Testing -Design to Ramp Up Production -Early Production -Project Closure and Something More -Closing Remarks
Lucidly and methodically written from a depth of industrial experience and academic observation, the book enables the reader to grasp the core tenets of project development with the application of knowledge and research and all the ideas and concepts to take a design from the drawing board to the completed physical product for the consumer market. The book fairly balances practical design assumptions within the parameters of risk and cost assessments. Stage by stage the project activities are described in great detail with a view of achieving the project requirements through the cycle of project development for an Automotive Project.
The skillful presentation of the book maybe used as a reference guide for other industries and concepts besides the Automobile Industry for essentially the book represents the quintessential description on how ideas can be organized and fashioned to the final creation of a product or service that may satisfy the consumer need.
"Project Management for Automotive Engineers: A Field Guide" is an AWESOME read! Seriously.
This topic has long since needed lowbrow mocking, and yours truly is here to say, "Hold my beer": Come for the comparison and contrast of agility versus rigidity! Stay for the over-utlization of human resources! Set your modus operandi by explaining severity of consequences! Successful leadership leads to reduced impacts...and improved performance. Keep in mind the exit strategy and mutually satisfactory conclusions between whip-, no I mean, stake-holders and clients. A fantastic read for so many applications covering everything including processes and floor layouts!
-Learn to torment rather than be tormented with Gantt -Wield the PDA -Discover the fun in role assignments -Quote the inestimable Yogi Berra to your captive audience -Estimate the risks to various approaches that are desired -Always keep in mind motivations and justifications in the Return on this Investment of time, energy, and resources -Avoid sinking, costly conditions -Advanced techniques, used for delightful suffering, such as Pee-ew, no I mean, Pugh -As with everything, there are laws and professional standards, which by themselves can be delightful especially when read out in a monotone (lawyers and engineers love it) -If you want to find out what you can do with "Scrum", "Burn", and "Waterfall", you just have to buy the book
Project Management books, as the authors themselves state, are present aplenty in the market today. What sets the book apart is the clear and concise content and the focus on practical applications of the concepts taught.
Instead of focusing solely on theory, tools and technology - the book shifts the thought process around project management from task based methodology to risk based decision making that aligns closely with the actual stages of product development. This helps the reader learn how to apply the various tools they hear about to the day to day working process which is rarely ideal.
The book lays equal emphasis on preemptive risk identification, periodic assessment and reassessment of project objectives and milestones as well as critically analysing failures along with the learnings from the happy path.
Each chapter is broken down to focus on a specific stage of the product development process and holistically covers all aspects related to it. Learnings and principles to follow are written in an accessible manner with examples and visual aids that help the reader understand better.
Sections of the book also focus on how project management is applied when the organisation is spread out geographically reflecting the modern automotive industry which has supply chains around the world.
Overall, as a field guide for engineers looking to learn about Project Management and its application to the automotive industry in specific, the book does an excellent job.
I was surprised when I started to read this book because I was not expecting to understand simply and directly the complexities involved in the Manufacturing of a Product with that many systems as an Automobile. It guides the reader through all the elements that are part of one of the motors in the world economy: The Automotive Industry. This is a must read for all those who work in this Industry, because involves subjects from management such as the steps to use a schedule and breakdown the work structure to achieve the necessary plans to control an Automotive Company. But this work does more that only explain the management and technicalities involved in the Industry. You can also learn about the financial aspect of the project such as how to communicate to the stakeholders and sponsor management or define the importance to justify the business. But as anyone who have participated in complex enterprises, you need to consider the scope and risk of the project, keep a proper documentation and know how to handle the issues with suppliers and their deficiencies. All of this is possible to learn in this book.
Project Management for Automotive Engineers is one of the kind of books I have read this year. I am not into Automotive Industry but still picked this book to gain knowledge. The book throws lots of light on practices and approaches of the automotive industry. It mentions automotive project Management, AIAG standards,LEAN Management and Risk Management. I could know about practical approaches towards engineering and management challenges and the way to have it done successfully. Coming from business management background I could understand the fundamentals covered in this book such as project scope, organizational structure, stake and stakeholders, dimensions of project management, risk management, and contracts, which are further discussed - important aspects of business case till the project end. This book is highly suggested to project managers in Automotive Industry which help them to be great in their work.
Starting from the management, which gives clear definitions and examples to guide a student or a reader to understand the book more, where it discuss the project scope, cost management, time schedule and risk management. The roles and responsibilities of the group manager on strategizing a good project are also mentioned in the book; communication and contra types that explain further on managing. Later chapters’ talks about the calculations for correct assumptions or conclusion afterwards it now discusses how to execute the project, prototypes, the V and W-cycle graphics for good quality products; and many more to learn on the following chapters.
I will give this book 5 shining stars and two big thumbs up! Everything is made easy and understandable to understand the concept, so no need to worry.
This book is a wealth of info relating to auto design and production strategies - I am not an Engineer, by schooling, yet as a 30 year auto tech who specializes in modifications and difficult repairs I enjoyed the perspective of the ever present compromise in the design and engineering of a production vehicle the need for balance and that the product and the process are integrated over the development to production with so many in the supply chain. The Project manager's success is a great product and the mistakes must be caught and corrected. This is a great introduction to the field and is also insite filled for an outsider like me. I could imagine this being a great book for a Class or study group in Engineering programs.
This 137 page book can be summarised in 3 words; clear, concise and catchy.
From inception to execution, this book will take you through the magnificent world of project management, providing all the information, as and when required. Also, this is one of the very few books on automotive project management techniques. Instead of the usual concentration on project management tools (Six Sigma, agile, etc), the authors have explained the actual PM strategies in a detailed and step by step manner. The work is such laudable that you can directly jump to the testing and development sections, without losing any information. This book is a must read for anyone planning to brush up their skills and methodologies in PM.
This book was a Best of the Best for the month of November, as selected by Stevo's Book Reviews on the Internet and Stevo's Novel Ideas. From basic planning to merging the entire range of thinking processes, the book effectively formulates a working plan to guide and control all activities through a successful implementation of the project.
It's an interesting project management book for anyone even if not directly in the field of automotive. The principles of project management starting with properly defining WBS, measurable goals and tracking of project remain same in any industry. Most stuff though is automotive related and is interesting to know about inner workings of an industry employing millions of people worldwide. Supply chain is the very important aspect related to any production business and automotive is no exception. It would be interesting to see any sequel of management related book specially in the post-covid world.
Critical yet simple - This sentence best describes the book. It rightfully grabs the basis of the dynamic nature of project management and not only enlists but also provides input on essential skills to take risk based decisions during execution of the projects. It covers basic concepts to help in better understanding and as well as covers all points to help in leadership. The matter is presented in a systematic way with adequate diagrams and charts throughout the book to make it more understandable. I found the book to be informative.
Project Management for Automotive is a comprehensive guide for anyone in Automotive and Manufacturing aspiring to become Project Manager / Leader. The ease with which it explains difficult technical topics is commendable. The book covers entire aspect of Automotive industry processes - product development, process development, ramp-up and early production which enhances the practicality and relevance.
This book is an excellent, comprehensive resource for project managers, not just in automotive engineering, but in many industries. Numerous clear diagrams and illustrations make complex topics comprehensible.
This is a comprehensive and summary work on project management. Things went a bit fast and understandable.. This is really recommended for potential project managers in engineering, engineering related fields and other fields. It also makes it clear that project management is a powerful business tool that can deliver many advantages to businesses of all sizes and gives you repeatable processes, guidelines and techniques to help you manage the people and the work involved in your projects. Really great work