Covering the roles and responsibilities of the project manager, this second edition describes requirement specifications, work breakdown structures, project control and risk management, and offers new information on motivation, matrix arrangements, and project records. Discussing the anatomy of a project planning and control and techniques, the authors describe the project manager's entire range of responsibilities from initial planning to directing personnel, controlling work, and reporting results. The appendices cover work breakdown structure paradigms, cost versus time profiles, and checklists to assess work done.
"Explains how to assess and handle technical risk, schedule risk, and cost risk efficiently and effectively--enabling engineering professionals to anticipate failures regardless of system complexity--highlighting opportunities to turn failure into success."
If the projects you manage don't go as smoothly as you'd like, 97 Things Every Project Manager Should Know offers knowledge that's priceless, gained through years of trial and error. This illuminating book contains 97 short and extremely practical tips -- whether you're dealing with software or non-IT projects -- from some of the world's most experienced project managers and software developers. You'll learn how these professionals have dealt with everything from managing teams to handling project stakeholders to runaway meetings and more. While this book highlights software projects, its wise axioms contain project management principles applicable to projects of all types in any industry. You can read the book end to end or browse to find topics that are of particular relevance to you. 97 Things Every Project Manager Should Know is both a useful reference and a source of inspiration. Among the 97 practical tips: "Clever Code Is Hard to Maintain...and Maintenance Is Everything" -- David Wood, Partner, Zepheira "Every Project Manager Is a Contract Administrator" -- Fabio Teixeira de Melo, Planning Manager, Construtora Norberto Odebrecht "Can Earned Value and Velocity Coexist on Reports?" -- Barbee Davis, President, Davis Consulting "How Do You Define 'Finished'"? -- Brian Sam-Bodden, author, software architect "The Best People to Create the Estimates Are the Ones Who Do the Work" -- Joe Zenevitch, Senior Project Manager, ThoughtWorks "How to Spot a Good IT Developer" -- James Graham, independent management consultant "One Deliverable, One Person" -- Alan Greenblatt, CEO, Sciova
Tap into the wisdom of experts to learn what every engineering manager should know. With 97 short and extremely useful tips for engineering managers, you'll discover new approaches to old problems, pick up road-tested best practices, and hone your management skills through sound advice. Managing people is hard, and the industry as a whole is bad at it. Many managers lack the experience, training, tools, texts, and frameworks to do it well. From mentoring interns to working in senior management, this book will take you through the stages of management and provide actionable advice on how to approach the obstacles you’ll encounter as a technical manager. A few of the 97 things you should know: "Three Ways to Be the Manager Your Report Needs" by Duretti Hirpa "The First Two Questions to Ask When Your Team Is Struggling" by Cate Huston "Fire Them!" by Mike Fisher "The 5 Whys of Organizational Design" by Kellan Elliott-McCrea "Career Conversations" by Raquel Vélez "Using 6-Page Documents to Close Decisions" by Ian Nowland "Ground Rules in Meetings" by Lara Hogan
Presents the fundamental finance and accounting processes, methods, strategies and terminology necessary for engineers and engineering managers to interpret financial data properly - examining topics such as cost and break-even analysis, the time value of money, financial ratios and discounted cash flow techniques. The information is designed to enable engineers and project managers to prepare, appraise, evaluate and approve financial plans to accomplish specific departmental and company objectives.
This compact reference succinctly explains the engineering profession's codes of ethics using case studies drawn from decisions of the National Society of Professional Engineers' (NSPE) Board of Ethical Review, examining ethical challenges in engineering, construction, and project management. It includes study questions to supplement general engineering survey courses and a list of references to aid practicing engineers in exploring topics in depth. Concentrating primarily on situations engineers encounter on a daily basis and offering pragmatic answers to ethical questions, What Every Engineer Should Know About Ethics discusses recent headline-making disasters such as the Challenger explosion, the Chernobyl nuclear catastrophe, and the Hyatt-Regency Hotel collapse; considers the merits and drawbacks of professional codes of ethics; covers the application of the "committee approach" to specific cases; compares and contrasts ethical codes and personal values with alternative approaches to morality; defines professional licensing and registration and enumerates their prerequisites; outlines legal standards for liability; emphasizes the importance of communication, coordination, and documentation; includes a discussion of "whistleblowing;" defines the engineer's primary ethical responsibility; and more.
Thanks to their education, experience, and general philosophical orientation, many engineers fail to notice critical issues in the workplace that can directly impact their career advancement and day-to-day job satisfaction. This text focuses on career management, and the accompanying importance of human and social interactions in the office. Althou
Engineers must possess a range of business communication skills that enable them to effectively communicate the purpose and relevance of their idea, process, or technical design. This unique business communication text is packed with practical advice that will improve your ability to- Market ideas Write proposals Generate enthusiasm for research De
Software startups make global headlines every day. As technology companies succeed and grow, so do their engineering departments. In your career, you'll may suddenly get the opportunity to lead teams: to become a manager. But this is often uncharted territory. How can you decide whether this career move is right for you? And if you do, what do you need to learn to succeed? Where do you start? How do you know that you're doing it right? What does "it" even mean? And isn't management a dirty word? This book will share the secrets you need to know to manage engineers successfully. Going from engineer to manager doesn't have to be intimidating. Engineers can be managers, and fantastic ones at that. Cast aside the rhetoric and focus on practical, hands-on techniques and tools. You'll become an effective and supportive team leader that your staff will look up to. Start with your transition to being a manager and see how that compares to being an engineer. Learn how to better organize information, feel productive, and delegate, but not micromanage. Discover how to manage your own boss, hire and fire, do performance and salary reviews, and build a great team. You'll also learn the psychology: how to ship while keeping staff happy, coach and mentor, deal with deadline pressure, handle sensitive information, and navigate workplace politics. Consider your whole department. How can you work with other teams to ensure best practice? How do you help form guilds and committees and communicate effectively? How can you create career tracks for individual contributors and managers? How can you support flexible and remote working? How can you improve diversity in the industry through your own actions? This book will show you how. Great managers can make the world a better place. Join us.
