زنده ماندن در پروژه‌های شیءگرا: راهنمای مدیر

Although much has been written about object technology and the benefits of this paradigm, there is still a shortage of compiled knowledge about what to expect and to plan for during project implementation. This book provides information that managers need to combat the unforeseen challenges that await them, allowing them to survive and ultimately succeed with an object-oriented project. To provide practical advice and guidelines for successfully managing an object-oriented project, the author borrows from the seasoned wisdom of numerous experts and successful consultants while also drawing on his personal experience and extensive knowledge. Surviving Object-Oriented Projects: A Managers Guide points out potential hazards and names workable solutions by addressing the important issues of scheduling, budgeting, staffing, and cost justification. Key points are supported and illustrated through short case studies taken from real object-oriented projects, and an appendix collects these workable guidelines and solutions into brief crib sheets ideal for handy reference. Cover......Page 1 Contents......Page 10 Acknowledgments......Page 16 About the Author......Page 18 Foreword......Page 20 Introduction......Page 24 Chapter 1: Sustainable Software Development......Page 36 Sustainable Development......Page 37 Chemical Manufacturing and Sustainable Development......Page 38 Continual Improvement: The Accelerator Button......Page 42 The Genius of the AND versus the Tyranny of the OR......Page 45 Summary......Page 47 Chapter 2: Unsustainable Software Development and its Causes......Page 48 Technical Debt and the Flywheel......Page 50 The Perils of Jumping in Place......Page 51 Project Stresses......Page 52 Project Controls......Page 56 Summary......Page 59 Chapter 3: The Principles of Sustainable Software Development......Page 62 Why Principles Are More Important Than Practices......Page 64 Continual Refinement of the Product and Project Practices......Page 66 A Working Product at All Times......Page 67 Valuing Defect Prevention over Defect Detection......Page 68 Disciplined......Page 71 Leadership......Page 72 Highly Collaborative......Page 73 Risk-Aware......Page 74 Summary......Page 75 Chapter 4: Working Product......Page 76 PRACTICE 1: No “Broken Windows”......Page 84 PRACTICE 2: Be Uncompromising about Defects......Page 85 How to Avoid a Defect Backlog......Page 86 Being Pragmatic about Defects......Page 87 PRACTICE 3: “Barely Sufficient” Documentation......Page 88 PRACTICE 5: Nightly Builds......Page 91 Pay Attention to Build Times......Page 92 PRACTICE 6: Prototyping......Page 94 Throwaway Prototypes......Page 96 PRACTICE 7: Don’t Neglect Performance......Page 97 PRACTICE 8: Zero Tolerance for Memory and Resource Leaks......Page 98 PRACTICE 9: Coding Standards and Guidelines......Page 100 PRACTICE 10: Adopt Standards (Concentrate on Your Value-Add)......Page 102 PRACTICE 11: Internationalize from Day One......Page 103 PRACTICE 12: Isolate Platform Dependencies......Page 104 Summary......Page 105 Chapter 5: Defect Prevention......Page 108 The Role of Quality Assurance......Page 111 PRACTICE 1: Ruthless Testing......Page 113 Unit Tests: Test-Driven Development......Page 115 Integration Tests......Page 116 System Tests......Page 118 Record and Playback......Page 119 Visual Validation Testing......Page 121 Performance Testing......Page 122 Regression Testing......Page 123 User Verification Testing......Page 124 Resources Required for Ruthless Testing......Page 125 Compiler......Page 127 Source Code Analyzer......Page 128 Execution Profiler......Page 129 Memory and Resource Leak Detection......Page 130 Configuration Management......Page 131 PRACTICE 3: Pair Programming and Code Reviews......Page 133 PRACTICE 4: Lightweight Root-Cause Analysis......Page 135 Summary......Page 139 Chapter 6: Emphasis on Design......Page 142 PRACTICE 2: Guiding Principles......Page 147 A Hypothetical Example of Guiding Principles......Page 148 A Real-World Example of Guiding Principles......Page 149 PRACTICE 3: Simple Design......Page 150 PRACTICE 4: Refactoring......Page 152 PRACTICE 5: Design Patterns......Page 154 PRACTICE 6: Frequent Rapid Design Meetings......Page 157 PRACTICE 7: Commitment to Rearchitecture......Page 158 PRACTICE 8: Design for Reuse......Page 163 Summary......Page 165 Chapter 7: Continual Refinement......Page 168 PRACTICE 1: Iterative Development......Page 170 Collaboration and Iterative Development......Page 172 Iteration 0......Page 173 PRACTICE 2: Release Planning......Page 174 PRACTICE 3: Daily Standup Meetings......Page 176 PRACTICE 4: Retrospectives......Page 177 PRACTICE 5: Coaching and Team Development......Page 179 Understanding the Business......Page 180 PRACTICE 6: Make Key Metrics Visible......Page 183 Summary......Page 185 Chapter 8: Culture Change and Sustainable Development......Page 186 Making Change Happen......Page 187 Change Factors and Enablers......Page 190 Change Factors......Page 191 Change Enablers......Page 193 Avoid Transition Plans......Page 197 Turning Unsustainable into Sustainable Development......Page 198 Where to Begin......Page 199 Sustainable Development for New Projects......Page 201 Get Your Defects Under Control......Page 202 Group Refactoring Exercises......Page 203 The Work Environment......Page 204 The Introduction of a Controversial Practice......Page 205 Introducing Agile Development Into a Mature Software Organization......Page 206 Summary......Page 211 Appendix 1: Practice Summary......Page 212 The Four Values of XP......Page 218 XP’s Twelve Practices......Page 219 The Strengths of XP......Page 220 Collaboration......Page 221 The Weaknesses of XP......Page 222 XP Targets Software Developers, and Nobody Else......Page 223 Pair Programming......Page 224 The On-Site Customer......Page 225 Self-Organization and Leadership......Page 226 “No Design”......Page 227 Other Agile Development Methods......Page 228 Summary......Page 229 Appendix 3: Sustainable Software Development and the CMM......Page 230 The Capability Maturity Model (CMM)......Page 231 Agile Development and the CMM......Page 232 Summary......Page 235 Chapters 1: and 2: Sustainable Software Development, Unsustainable Software Development......Page 236 Chapter 3: The Principles of Sustainable Development......Page 238 Chapter 4: Working Product......Page 239 Usability Testing......Page 240 Design Patterns......Page 241 Refactoring......Page 242 Chapter 7: Continual Refinement......Page 243 Chapter 8: Making Culture Change Happen......Page 245 Conclusion......Page 246 References......Page 250 C......Page 254 D......Page 255 E......Page 256 L......Page 257 P......Page 258 R......Page 259 T......Page 260 Z......Page 261

"Over the years I have seen the software development pendulum swing from one extreme to the other, as deficiencies in 'best practices' at one end of the spectrum spawned a new set of 'best practices' at the opposite end. Kevin Tate's book has finally brought the pendulum to a screeching halt, right about dead center. This book provides a balanced and practical guide to what's important if your goal is to develop software that lasts."

—Mary Poppendieck, Poppendieck.LLC. Author of "Lean Software Development"

"1) In this very practical and accessible book interspersed with real-world examples and personal opinions, Kevin has distilled his years of developing quality software into a set of principles and practices that have been proven to work. If you are thinking of introducing an agile development environment (ADE) into your organization or of improving the one you already have, this book will help you clearly understand the benefits of a sustainable ADE, establish the practices to make it happen and coach you through the follow-up required to change the culture of your organization to make sure the changes take hold.

I am currently faced with exactly this challenge and this book has already given me several ideas I am looking forward to trying out.

2) In an industry plagued with missed deadlines despite long overtime hours, this book offers a refreshing alternative: a set of guiding principles and simple practices to follow that allow you to get the job done by working smarter, not harder. Drawing on the author's extensive experience developing quality software, the book clearly explains the principles behind a sustainable agile development environment, why it works, the practices to make it happen and the follow through required to turn these practices into habits."

—Peter Schoeler, Technical Director, Artificial Mind & Movement

"It's a familiar scene—the schedule's tight, people are putting in heroic efforts to get everything done, then at the last minute a change request comes in that wipes out the gains you had finally managed to make in meeting your ship date. Looks like it's pizza at your desk for the weekend again! An unfortunate situation to be in but a pattern that repeats itself all too often. "Sustainable Software Development" offers hope to break this cycle. It shows how a change in mindset can free you from the tyranny of unrealistic expectations and brings development realities out onto the table for everyone to see. By following these techniques you will be able to define and manage a software development environment that will work for the long haul."

—Kevin Picott

Software development for immediate success and long-term sustainability

Sustainable Software Development brings together principles and practices for building software that is technically superior, delivers exceptional business value, and can evolve rapidly to reflect any change to your business or technical environment.

Kevin Tate shows how to eliminate practices that make development unsustainable and replaces these practices with a sustainable approach that draws on the best ideas from both agile and conventional development. Tate demonstrates how to balance rapid releases and long-term sustainability, achieving both rich functionality and superior quality. You'll learn how to build a development organization that is more productive and can continually improve its capability to handle complexity and change.

Writing for developers, architects, project leaders, and other software team members, Tate shows how to:

• Take control of your development environment, so you can outship your competitors, leveraging new technologies and responding to new business opportunities
• Maintain a consistent pace that optimally balances short- versus long-term requirements
• Keep your code base in a "near-shippable" state between releases
• Prevent defects, rather than just recognizing and fixing them
• Invest continually and cost-effectively in software design improvements
• Leverage the fundamentals of the craft of software development
• Integrate sustainable processes with Agile and traditional methodologies

today, Many Organizations Claim Competitive Market Advantages Resulting From The Application Of Object-oriented Technology And Approaches In Their Software Development Efforts. As The Use Of Object Technology Has Become Increasingly Widespread And Mainstream, A Growing Number Of Project Managers Are Faced With A Daunting Task: Keeping The Object Technology Project On Track And Within Budget. These Project Managers Are Burdened By The Weight Of Knowing That The Survival And Ultimate Success Of The Project Hinges On Their Insight When Planning The Project And Their Responses To Events That Lie Ahead. Unfortunately, Hidden Costs, Unpleasant Surprises And Unrealistic Expectations Lie In Wait For The Unprepared Manager.

Although Much Has Been Written About Object Technology And The Benefits Of This Paradigm, There Is Still A Shortage Of Compiled Knowledge About What To Expect And To Plan For During Project Implementation. This Book Provides Information That Managers Need To Combat The Unforeseen Challenges That Await Them, Allowing Them To Survive And Ultimately Succeed With An Object-oriented Project.

To Provide Practical Advice And Guidelines For Successfully Managing An Object-oriented Project, The Author Borrows From The Seasoned Wisdom Of Numerous Experts And Successful Consultants While Also Drawing On His Personal Experience And Extensive Knowledge. surviving Object-oriented Projects: A Manageris Guide Points Out Potential Hazards And Names Workable Solutions By Addressing The Important Issues Of Scheduling, Budgeting, Staffing, And Cost Justification. Key Points Are Supported And Illustrated Through Short Case Studies Taken From Real Object-orientedprojects, And An Appendix Collects These Workable Guidelines And Solutions Into Brief Icrib Sheetsio Ideal For Handy Reference.

booknews

synthesizing The Insights Of Managers And Consultants Who Have Lived To Tell The Tale, Offers Advice On Keeping A Software Development Project Using Object-oriented Technology And Approaches On Track And Within Budget Despite The Inevitable Pitfalls That Await. Includes A Tear-out Crib Sheet With Handy Data And Some Soothing Mantras To Chant. Annotation C. By Book News, Inc., Portland, Or.

Surviving Object-Oriented Projects is an extraordinary compendium of useful strategies for organizing object-oriented projects. Independent of language or programming environment, it explains how to build good OO software despite all the conflicting forces at work. For all those OO projects that have set sail with no more than high concepts and a shiny new language, this book is the compass that will see them safely through."- Jeremy Raw, Independent Consultant Today , many organizations claim competitive market advantages resulting from the application of object-oriented technology and approaches in their software development efforts. As the use of object technology has become increasingly widespread and mainstream, a growing number of project managers are faced with a daunting keeping the object technology project on track and within budget. These project managers are burdened by the weight of knowing that the survival and ultimate success of the project hinges on their insight when planning the project and their responses to events that lie ahead. Unfortunately, hidden costs, unpleasant surprises and unrealistic expectations lie in wait for the unprepared manager. Although much has been written about object technology and the benefits of this paradigm, there is still a shortage of compiled knowledge about what to expect and to plan for during project implementation. This book provides information that managers need to combat the unforeseen challenges that await them, allowing them to survive and ultimately succeed with an object-oriented project. To provide practical advice and guidelines for successfully managing an object-oriented project, the author borrows from the seasoned wisdom of numerous experts and successful consultants while also drawing on his personal experience and extensive knowledge. Surviving Object-Oriented A Manager's Guide points out potential hazards and names workable solutions by addressing the important issues of scheduling, budgeting, staffing, and cost justification. Key points are supported and illustrated through short case studies taken from real object-oriented projects, and an appendix collects these workable guidelines and solutions into brief "crib sheets"- ideal for handy reference. The survival and ultimate success of an object-oriented software development project hinges on the project manager's prior planning and knowledge of what to expect and his or her active management to keep the project on track. This guide will help managers gain that background as it explores issues of scheduling, budgeting, staffing, and cost justification, all supported and illustrated by short case studies of actual projects.