Information Technology Project Management, Fourth Edition

Project Initiation. Determining project goals, determining deliverables, determining process outputs, documenting constraints, documenting assumptions, defining strategies, producing formal documentation.

Project Planning. Refining a project, creating a WBS, developing a resource management plan, determining resource requirements, defining budgets, refining time and costs estimates, establishing project controls, obtaining plan approval.

Project Execution. Committing and implementing resources, managing and communicating progress, implementing quality assurance procedures.

Project Control. Measuring performance, refining control links, taking corrective action, evaluating effectiveness of corrective action, ensuring plan compliance, reassessing control plans, responding to risk event triggers, monitor project activity.

Project Closing. Obtaining acceptance of deliverables, documenting lessons learned, facilitating closure, preserving product records and tools, releasing resources.

Professional Responsibility. Ensuring integrity, contributing to knowledge base, balancing stakeholder interests, respecting differences.

Successful project management is increasingly vital to all organizations, driven by the demands of global competition, rapid technological growth, and faster time to market (just to name a few). For those in technology fields, project management skills are fast becoming a required core competency. And those who have mastered these skills continue to be in high demand worldwide, commanding higher salaries than those around them. But how does one extend those skills or acquire them in the first place? Fundamentals of Technology Project Management is a great place to start.

Of the hundreds of project management books on the market, precious few address the unique needs of the IT project manager. Unlike most other project management books, Fundamentals of Technology Project Management tackles the specific issues that technology professionals must face, such as understanding technology resources, managing project scope and feature creep, and meeting client expectations, among many others.

Whether you're a college student, a software engineer, or an IT professional, Fundamentals of Technology Project Management will help you gain a comprehensive understanding of the project management life cycle and learn how to manage it – from first steps on through to intermediate topics (as well as some advanced ones). Author Colleen Garton explains — in easy-to-understand language— not only the what but the how of IT projects. What's more, unlike general project management books, the examples and case studies in this book are all based on technology projects, making them far more relevant to the learner.

Also included is a content-rich CD-ROM loaded with features to make the life of any IT project manager (or the IT professional with project management responsibilities) far easier. There are document templates you can use for all phases of the project — from the initial RFP to closing reports. Plus, the author steps you through meeting agendas, status reports, cost analysis, technical specifications, and more. In addition to the document templates, you're provided with PowerPoint slides that can be modified and used for reporting progress to users and management.

The continuing rise in importance of project management cannot be denied. Let this book be your guide to becoming a more effective, more efficient IT project manager.

With Fundamentals of Technology Project Management you will:
- Discover the top ten reasons projects fail
- Master the five keys to project success
- Explore the six phases of the project lifecycle, step by step
- Review the documents necessary for good project management and learn how to complete them
- Understand the warning signs of a project in trouble and learn how to get it back on track
- Learn Quality Management and Quality Assurance practices in easy-to-understand terms
- Acquire practical ways to develop effective leadership and team-building skills

Conflicting Processes Names and Knowledge Area Allocations to PMBOK.......2006-05-25