Software Project Management explains the latest management strategies and techniques in software developments. It covers such issues as keeping the team motivated, cost-justifying strategies, deaflines and budgets.

How to be sure your first important project isnþt your last.

Project initiation; Project planning; Project execution and termination.

Project Management in Practice, 4th Edition focuses on the technical aspects of project management that are directly related to practice.

In the 2nd edition, this book conveys updated content and, in addition to classic project management, now also agile project management in a practical manner and serves as a toolbox for projects. To this end, the most important terms and phases of project management are first explained in a standard-compliant manner. Then this book deals with cross-project cross-sectional topics and project phase-specific content, divided into agile and classic project management. Tips and hints, examples, templates and checklists from project practice in the automotive and IT environment complement the contents. For student readers, there is also an extensive question catalog to consolidate the knowledge learned. This gives readers good and quick access to the topic of project management and helps them to be able to carry out their projects successfully.

The rules and practices for Scrum—a simple process for managing complex projects—are few, straightforward, and easy to learn. But Scrum’s simplicity itself—its lack of prescription—can be disarming, and new practitioners often find themselves reverting to old project management habits and tools and yielding lesser results. In this illuminating series of case studies, Scrum co-creator and evangelist Ken Schwaber identifies the real-world lessons—the successes and failures—culled from his years of experience coaching companies in agile project management. Through them, you’ll understand how to use Scrum to solve complex problems and drive better results—delivering more valuable software faster. Gain the foundation in Scrum theory—and practice—you need to: Rein in even the most complex, unwieldy projects Effectively manage unknown or changing product requirements Simplify the chain of command with self-managing development teams Receive clearer specifications—and feedback—from customers Greatly reduce project planning time and required tools Build—and release—products in 30-day cycles so clients get deliverables earlier Avoid missteps by regularly inspecting, reporting on, and fine-tuning projects Support multiple teams working on a large-scale project from many geographic locations Maximize return on investment!