Cover image for IT best practices : management, teams, quality, performance, and projects
Title:
IT best practices : management, teams, quality, performance, and projects
Personal Author:
Publication Information:
Boca Raton : Taylor & Francis, 2012
Physical Description:
x, 345 p. : ill. ; 24 cm.
ISBN:
9781439868546

Available:*

Library
Item Barcode
Call Number
Material Type
Item Category 1
Status
Searching...
30000010297156 HD30.2 W58 2012 Open Access Book Book
Searching...

On Order

Summary

Summary

Consistent success does not happen by chance. It occurs by having an understanding of what is happening in the environment and then having the skills to execute the necessary changes.

Ideal for project, IT, and systems development managers, IT Best Practices: Management, Teams, Quality, Performance, and Projects details the skills, knowledge, and attributes needed to succeed in bringing about large-scale change. It explains how to incorporate quality methods into the change management process and outlines a holistic approach for transformation management.

Detailing time-tested project management techniques, the book examines management skills with a focus on systems thinking to offer a pragmatic look at effecting change. Its comprehensive coverage spans team building, quality, project methodology, resource allocation, process engineering, and management best practices. The material covered is validated with references to concepts and processes from such business greats as Dr. Deming, Jack Welch, and Henry Ford. Readers will learn the history behind the concepts discussed along with the contributions made by these greatnbsp;minds.

The text supplies an awareness of the factors that impact performance in today's projects to supply you with the real-world insight needed to bring about large-scale change in your organization. Although it is geared around change, most of the concepts discussed can be directly applied to improve efficiencies in your day-to-day activities.


Author Notes

Tom Witt has a B.S. in mathematics, with a minor in coaching, from the University of Wisconsin-Platteville. He has worked in the information technology (IT) environment for almost 30 years. Early in his career, he moved into management for 14 years before entering the project world, in which he has held the titles of office automation manager, project manager, technical manager, technical lead, architect, and system analyst. Most of Tom's experience has been in the insurance industry in addition to threenbsp;years in the magazine fulfillment business and threenbsp;years at an institute of higher education.

Tom has worked on a wide range of projects; he has been a part of the development of new mainframe systems, new web systems, and vendor-purchased imaging systems and system remote workers across the country as well as part of a small team that reengineered a business division for a major insurance company. Many of the projects on which Tom has been involved have affected changes--as many as 200 different systems--throughout the entire enterprise. Tom has acquired knowledge not only through personal experiences but also from outside sources such as external consultants, seminars, books, and a personal network of people. More importantly, he was put into many different types of project and situations that allowed him to apply the many different concepts and knowledge acquired to see the results from a front-line perspective.


Table of Contents

Chapter 1 Introductionp. 1
Acquiring Knowledgep. 7
Content Materialp. 8
Chapter 2 Management Best Practicesp. 11
Leadershipp. 14
Negotiationp. 16
Problem Solvingp. 217
Decision Makingp. 26
Ability to Influence the Organizationp. 28
Communicationp. 33
Meetings for Informational Purposesp. 34
Meetings to Sell an Idea or Get Approvalp. 35
Meetings to Gather Informationp. 35
Improving Management Best Practice Disciplinesp. 42
Bad Management Practicesp. 49
Summaryp. 51
Chapter 3 Five Disciplines of a Learning Organizationp. 53
Chapter 4 The Effects of Management on Subordinatesp. 57
Chapter 5 Management Typesp. 63
Manager of Maintenance Workp. 65
Technical Managerp. 67
Project Managerp. 70
System Resource Managerp. 72
Chapter 6 Crisis Managementp. 77
Chapter 7 Jack Welch and Managementp. 85
Chapter 8 Robert Greenleaf and Servant Leadershipp. 93
Chapter 9 Management Wrap-Upp. 97
Chapter 10 Business Modelp. 99
Chapter 11 High-Performance Teamsp. 105
Defining High-Performance Teamsp. 105
HPT Member Classificationp. 106
HPT Characteristicsp. 110
High-Performance Team Life Cyclep. 113
Chapter 12 Qualityp. 121
Introduction to Definition of Qualityp. 121
Generalist versus Specialistp. 122
Tasks Grouping and Qualityp. 125
Reporting Quality and Performancep. 126
Measuring Quality and Performancep. 128
Chapter 13 W. Edwards Deming, Father of Qualityp. 133
Continuous Quality Improvementp. 143
Theory of Constraintsp. 145
Chapter 14 Process Engineeringp. 147
Chapter 15 Lean Managementp. 155
Chapter 16 Six Sigmap. 163
Chapter 17 Workplace Efficiencies and Distractionp. 167
E-mailp. 167
Internetp. 171
Instant Messagingp. 172
Controlling Workplace Inefficienciesp. 173
Getting Started for the Workdayp. 174
Chapter 18 Technologyp. 177
Chapter 19 Contractorsp. 187
Contractor Behaviorp. 187
Contractors for Knowledgep. 188
Contractors for Filling a Resource Voidp. 189
Using Contractors Successfullyp. 191
Overseas Contractorsp. 192
Chapter 20 Defectsp. 199
Effects of Defectsp. 199
Causes of Defectsp. 201
Chapter 21 Knowledge Base for Project Workp. 205
Chapter 22 Project Selection Criteriap. 207
Chapter 23 Project Characteristicsp. 21J
Project Success versus Failurep. 413
Successfulp. 213
Challengedp. 214
Failedp. 214
Law of Cause and Effectp. 215
Identifying the Causep. 216
Chapter 24 Effects of Project Failurep. 219
Chapter 25 Controlling Failurep. 223
Chapter 26 Project Methodologyp. 227
Chapter 27 Project Phasesp. 237
Documentationp. 237
Phasesp. 240
Initiationp. 241
Analysis (Solution Scoping)p. 243
Designp. 245
Developmentp. 247
Testingp. 248
Summary of Testing Stepsp. 250
Implementationp. 251
Postimplementationp. 252
Chapter 28 Factors That Affect Projectsp. 255
Project Estimates and Staffingp. 255
Chapter 29 Spiral and Linear Project Methodologyp. 261
Spiral Project Methodologyp. 261
Scrump. 266
Extreme Programming (XP)p. 267
Dynamic Systems Development Method (DSDM)p. 271
Studyp. 272
Functional Modelingp. 272
Design and Buildp. 273
Implementationp. 273
Feature-Driven Development (FDD) Methodp. 274
Develop Overall Modelp. 274
Build Feature Listp. 275
Plan by Featurep. 275
Design by Featurep. 275
Build by Featurep. 276
Cowboy Development Methodp. 276
Learning about Spiralp. 278
Linear Project Managementp. 284
Linear Waterfall-Crashing the Timelinep. 287
Law of 20-80p. 288
Linear versus Spiralp. 294
Spiral Strengthsp. 294
Spiral Weaknessesp. 295
Linear Strengthsp. 296
Linear Weaknessesp. 297
Working Environmentp. 299
Chapter 30 Project Management Improvementp. 303
Knowledge Areas of a Projectp. 304
Scope and Integrationp. 307
Timep. 308
Communicationp. 308
Human Resource Allotmentp. 309
Qualityp. 309
Riskp. 310
Leadershipp. 310
Negotiationp. 311
Problem Solvingp. 311
Decision Makingp. 312
Influencing the Organizationp. 312
Communicationp. 313
Leadership of the Different Project Phasesp. 314
Project Sizes and the Amount of Form and Art Neededp. 315
Small Project Characteristicsp. 316
Resourcesp. 316
Areas Affectedp. 316
Documentationp. 316
Simple Design and Developmentp. 316
GOOD: Project manager leads the projectp. 317
BEST: Technical manager or leader leads the projectp. 317
Medium Project Characteristicsp. 317
Resourcesp. 317
Areas Affectedp. 318
Documentationp. 318
Design and Developmentp. 318
BAD: Technical manager or leader leads the projectp. 319
GOOD: Project manager is assigned without a technical lead or technical managerp. 319
BEST: Project manager leads with a technical lead assignedp. 319
Large Project Characteristicsp. 320
Resourcesp. 320
Areas Affectedp. 320
Documentationp. 320
Complex and Difficult Design and Developmentp. 320
BAD: Project manager leads the project with a technical lead assignedp. 321
BEST: Project manager leads the project with a technical manager assignedp. 321
Never Assume, Always Validatep. 325
Chapter 31 Conclusionp. 329
Bibliographyp. 331
Indexp. 333
Author Biographyp. 345