Creating A Software Engineering Culture By Karl E. Wiegers

Creating A Software Engineering Culture By Karl E. Wiegers

Download Free Creating A Software Engineering Culture Pdf

Introduction: Creating A Software Engineering Culture

Getting Started With Creating A Software Engineering Culture, When I first became the supervisor of the Kodak software group in which I had worked for several years, I initiated a simple (and slightly corny) w w recognition program. When someone reached a minor project milestone or made a small contribution such as helping another team member with a problem, I gave him a package of M&M® candies, with a message tag attached expressing congratulations or thanks, as appropriate. Bigger achievements generated bigger bags of M&Ms, or something more tangible. It wasn’t much, but it was more than we were used to.
As I expected, the candy disappeared immediately, but I was pleasantly surprised to see that some people kept the message tags visible around their desks. To them, the important thing was not the bag of candy, but the words indicating that their manager noticed and valued the progress being made. It soon became apparent that group members preferred to have the presentations made publicly at our weekly team meetings, indicating their desire for peer recognition of even small achievements.
M&Ms worked with our group, but some other social recognition technique might work better for you. We also gave this sort of micro-recognition award to people outside the group who helped us in some way. It brought smiles to their faces and goodwill to our relationships. However you choose to do it, appropriate praise and commendation help to build the culture of teamwork and striving for excellence that we all want, and it can motivate your team members to do an even better job in the future since they know you appreciate their efforts.
The form and extent of recognition and reward is a visible indication of an organization’s culture. If managers believe the employees are lucky just to have jobs, they won’t go out of their way to offer even small gestures of appreciation or congratulations. Conversely, in a market characterized by competitive hiring and high staff turnover, an effective recognition program can help retain talented developers. M&Ms won’t make up for low salaries or unpleasant working conditions, but simple recognition is an important step in the right direction.

Creating A Software Engineering Culture Chapters and Sections

Table of Contents For Creating A Software Engineering Culture

 

Part 1: A Software Engineering Culture
Chapter 1: Software Culture Concepts

Culture Defined
Growing Your Own Culture
A Healthy Software Culture
Individual Behaviors
Team Behaviors
Management Behaviors
Organizational Characteristics
A Less Healthy Software Culture
Individual Behaviors
Management Behaviors
Organizational Characteristics
Organizational Options
The Management Challenge
Summary
Culture Builders and Killers
References and Further Reading

Chapter 2: Standing On Principle

Integrity and Intelligence: With Customers
Integrity and Intelligence: With Managers
The Five Dimensions of a Software Project
Summary
Culture Builders and Killers
References and Further Reading

Chapter 3: Recognizing Achievements Great and Small

The Importance of Being Visible
The Importance of Management Attitude
Rewards for a Job Well Done
Summary
Culture Builders and Killers
References and Further Reading

Chapter 4: So Much to Learn, So Little Time

What to Learn
Where to Learn
Professional Seminar Sources
Technical Conferences
Publications
Videotape Instruction
On-Line Information Sources
Professional Societies and Certification
Summary
Culture Builders and Killers
References and Further Reading

Part II: In Search of Excellent Requirements
Chapter 5: Optimizing Customer Involvement

Software Requirements: The Foundation of Quality
The Need for Customer Involvement
The Project Champion Model
Project Champion Expectations
When the Project Champion Model Fails
Summary
Culture Builders and Killers
References and Further Reading

Chapter 6: Tools for Sharing the Vision

Use Cases
Software Requirements Specifications
Dialog Maps
Prototypes
Requirements Traceability Matrices
From Requirements to Code
Summary
Culture Builders and Killers
References and Further Reading

Part III: Improving Your Processes
Chapter 7: Process Improvement Fundamentals

Principles of Process Improvement
Getting Started with Process Improvement
Summary
Culture Builders and Killers
References and Further Reading

Chapter 8: Process Improvement Case Study

Making Change Happen
Sustaining Momentum
Summary
Culture Builders and Killers
References and Further Reading

Chapter 9: Software Process Maturity

The Capability Maturity Model
Level 1: Initial
Level 2: Repeatable
Level 3: Defined
Level 4: Managed
Lévelo: Optimizing
Dissenting Opinions
Process Assessments
Process Maturity and Culture
Summary
Culture Builders and Killers
References and Further Reading

Chapter 10: Software Development Procedures

Standards, Procedures, and Guidelines, Oh My!
Local Development Guidelines
Our Software Development Guidelines
IEEE Standards
Other Standards Sources
Summary
Culture Builders and Killers
References and Further Reading

Part IV: The Bug Stops Here
Chapter 11: The Quality Culture

The Cost of Quality
Assuring Software Quality
How Dense Are Your Defects?
Lines of Code versus Application Functionality
How Good Is Good Enough?
An Assault on Defects
Explicit SQA Responsibilities
Why Do We Think Quality Practices Pay Off?
Summary
Culture Builders and Killers
References and Further Reading

Chapter 12: Improving Quality by Software Inspection

Inspections and Culture
Benefits of Inspections
Inspections, Walkthroughs, and Reviews
Guiding Principles for Reviews and Inspections
Keeping Records
Making Inspections Work in Your Culture
Summary
Culture Builders and Killers
References and Further Reading

Chapter 13: Structured Testing

Testing and the Quality Culture
A Unit Testing Strategy
Cyclomatic Complexity and Testing
Test Management and Automation
Structured Testing Guidelines
Summary
Culture Builders and Killers
References and Further Reading

Part V: Methods, Measures, and Tools
Chapter 14: The CASE for Iteration

Types of CASE Tools
Hypes of CASE Tools
Lessons from Our CASE History
Fitting CASE into Your Culture
Other Benefits from CASE
Culture Change for CASE
Summary
Culture Builders and Killers
References and Further Reading

Chapter 15: Control Change Before It Controls You

Benefits of a Problem Tracking System
A Software Change Management Case Study
The Software Change Control Board
How Change Control Can Simplify Your Life
Learning from Bug Detection Trends
Proactive Failure Reporting
Making Change Management Work in Your Culture
Summary
Culture Builders and Killers
References and Further Reading

Chapter 16: Taking Measures to Stay on Track

Why Measurement Programs Fail
Metrics Programs Don’t Have to Fail
What to Measure
How to Design Your Metrics Program
Summary
Culture Builders and Killers
References and Further Reading

Chapter 17: Case Study: Measurement in a Small Software Group

Software Work Effort Metrics
Trends and Applications
Metrics-Based Project Estimation
Lessons from Work Effort Metrics
Predicting Maintainability with Metrics
Summary
Culture Builders and Killers
References and Further Reading

Chapter 18: If It Makes Sense, Do It

Summary
Culture Builders and Killers
References and Further Reading
Part VI: What to Do on Monday

Chapter 19: Action Planning for Software Managers

Action Item Menu
Summary
References and Further Reading

Chapter 20: Action Planning for Software Engineers

Action Item Menu
Building a Healthy Workplace
Summary
References and Further Reading

Download Now

Note: If you have any question about Download Free Creating A Software Engineering Culture Pdf Then you can comment it.

Related Posts:


Be the first to comment

Leave a Reply

Your email address will not be published.


*