Leading Culture Change in Your Software Organization: Delivering...

Features

• Cover Type: Paperback with 424 pages
• Published by: Management Concepts September 7, 2003
• Written in: English
• ISBN 10 Number: 156726123X
• ISBN 13 Number: 978-1567261233
• Book Dimensions: 8.7 x 6 x 1.1 inches
• Weighs: 1.4 pounds

Product Description
The Effective Way to Produce Improvements for Project Management and software Engineering! Leading Culture Change in Your software Organization: Delivering Results Early is the first industry-specific guide to managing change. You ll find today s best strategies for quick wins and long-term gains when managing software Process Improvement (SPI) and culture change. You ll: Learn how to deliver successful outcomes, using a targeted set of recommended actions, effective leadership, and social and psychological drivers Get first-hand knowledge from organizations that have successfully transformed the work habits and practices of their software professionals Discover techniques that you can apply immediately to maximize project success regardless of your organization s infrastructure or level of technical sophistication.

About The Author
Rita Chao Hadden specializes in software best practices, process improvement, and corporate culture change. She has been a software practitioner, project manager, software engineering process group (SEPG) leader, change agent, software Engineering Institute authorized lead assessor, software director, and executive. She has provided leadership, coordination, and coaching for more than 75 complex software projects in the private and public sectors. She is currently Director of software Development at Datatel, Inc., a market leader in Enterprise Resource Planning for higher education.

Reader Reviews
If you're involved in any aspect of software implementations, and you desire to improve your product delivery for your user community, then this book is a must have. It offers practical approaches along with useful examples. What I particularly like is the incremental approach using the five best practices in Chapter 2. The big-bang hammer approaches, which I have lived through and can, relate to in Chapter 4, just don't work! I have used the author's best practices for my last three projects and the results were very successful: Project 1 - no major bugs found during end user acceptance testing, implemented three days early; Project 2 - implemented on-time with a satisfied user community; Project 3 - again, no showstopper issues during user acceptance resulting in a product that was delivered as expected by the user community. The suggested best practices do in fact work. This book is my guide and reference for managing software implementations. I highly recommend it! Comment | | (Report this)