Change Done Well Change Done Well

Change Done Well

    • $17.99
    • $17.99

Publisher Description

The history of software engineering is riddled with failed attempts to improve quality and productivity without first creating a supportive environment. Many managers spend their money on tools, methodologies, outsourcing, training, and application packages, but these managers rarely spend anything to improve the way in which these hoped-for improvements are adopted and used correctly.
From systems thinking to project management to technology transfer to the interaction of culture and process, Change Done Well analyzes transformation from a broad range of perspectives, providing a breadth of awareness essential for successful transformation to high-quality software creation.
Topics include:
Starting Projects Correctly
Sustaining Projects Correctly
Terminating Projects Properly
Building Faster By Building Smaller
Protecting Information Assets
Managing Design
Introducing Technology
The Diagram of Effects
The Software Engineering Cultural Patterns
The Satir Interaction Model
Control Models
The Three Observer Positions
and much more

IEEE Software says: "If you're grappling with how to improve software development and especially how to improve managing software development, then this might be the right book for you."

GENRE
Computing & Internet
RELEASED
2011
24 May
LANGUAGE
EN
English
LENGTH
212
Pages
PUBLISHER
Gerald M. Weinberg
SELLER
Draft2Digital, LLC
SIZE
1.3
MB
CHANGE: Planned & Unplanned CHANGE: Planned & Unplanned
2011
Quality Software: Volume 1.1: How Software Is Built Quality Software: Volume 1.1: How Software Is Built
2010
Managing the Mechanism Managing the Mechanism
2012
Why Software Gets In Trouble Why Software Gets In Trouble
2010
Agile Development and Business Goals Agile Development and Business Goals
2010
Lean & Agile Project Management Lean & Agile Project Management
2014
An Introduction to General Systems Thinking An Introduction to General Systems Thinking
2011
Becoming a Technical Leader Becoming a Technical Leader
2010
Are Your Lights On? Are Your Lights On?
2011
How to Observe Software Systems How to Observe Software Systems
2010
Exploring Requirements 2: First Steps into Design Exploring Requirements 2: First Steps into Design
2011
Exploring Requirements 1: Quality Before Design Exploring Requirements 1: Quality Before Design
2011