Software Development Pearls

Lessons from Fifty Years of Software Experience

Paperback Engels 2021 1e druk 9780137487776
€ 39,34
Niet leverbaar.

Samenvatting

Accelerate Your Pursuit of Software Excellence by Learning from Others' Hard-Won Experience "Karl is one of the most thoughtful software people I know. He has reflected deeply on the software development irritants he has encountered over his career, and this book contains 60 of his most valuable responses." -- From the Foreword by Steve McConnell, Construx Software and author of Code Complete "Wouldn't it be great to gain a lifetime's experience without having to pay for the inevitable errors of your own experience? Karl Wiegers is well versed in the best techniques of business analysis, software engineering, and project management. You'll gain concise but important insights into how to recover from setbacks as well as how to avoid them in the first place." --Meilir Page-Jones, Senior Business Analyst, Wayland Systems Inc.

Experience is a powerful teacher, but it's also slow and painful. You can't afford to make every mistake yourself! Software Development Pearls helps you improve faster and bypass much of the pain by learning from others who already climbed the learning curves. Drawing on 25+ years helping software teams succeed, Karl Wiegers has crystallized 60 concise, practical lessons for all your projects, regardless of your role, industry, technology, or methodology.

Wiegers's insights and specific recommendations cover six crucial elements of success: requirements, design, project management, culture and teamwork, quality, and process improvement. For each, Wiegers offers First Steps for reflecting on your own experiences before you start; detailed Lessons with core insights, real case studies, and actionable solutions; and Next Steps for planning adoption in your project, team, or organization. This is knowledge you weren't taught in college or boot camp.

It can boost your performance as a developer, business analyst, quality professional, or manager. Clarify requirements to gain a shared vision and understanding of your real problemCreate robust designs that implement the right functionality and quality attributes and can evolveAnticipate and avoid ubiquitous project management pitfallsGrow a culture in which behaviors actually align with what people claim to valuePlan realistically for quality and build it in from the outsetUse process improvement to achieve desired business results, not as an end in itselfChoose your next steps to get full value from all these lessons Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details.

Specificaties

ISBN13:9780137487776
Taal:Engels
Bindwijze:paperback
Aantal pagina's:336
Druk:1
Verschijningsdatum:6-10-2021
Hoofdrubriek:IT-management / ICT

Lezersrecensies

Wees de eerste die een lezersrecensie schrijft!

Inhoudsopgave

Foreword xix
Acknowledgments xxi
About the Author xxiii

Chapter 1: Learning from Painful Experience 1
My Perspective 1
About the Book 2
A Note on Terminology 4
Your Opportunity 5

Chapter 2: Lessons About Requirements 7
Introduction to Requirements 7
First Steps: Requirements 11
Lesson 1: Get the requirements right or the project will fail 12
Lesson 2: Requirements development delivers shared understanding 15
Lesson 3: Stakeholder interests intersect at the requirements 17
Lesson 4: Favor a usage-centric approach to requirements 21
Lesson 5: Requirements development demands iteration 25
Lesson 6: Agile requirements aren't different from other requirements 28
Lesson 7: Recording knowledge is cheaper than acquiring it 33
Lesson 8: Requirements are about clear communication 37
Lesson 9: Requirements quality is in the eye of the beholder 41
Lesson 10: Requirements must be good enough to reduce risk 44
Lesson 11: People don't simply gather requirements 46
Lesson 12: Elicitation brings the customer's voice to the developer 51
Lesson 13: Telepathy and clairvoyance don't work 55
Lesson 14: Large groups have difficulty agreeing on requirements 57
Lesson 15: Avoid decibel prioritization 61
Lesson 16: Define scope to know whether your scope is creeping 64
Next Steps: Requirements 69

Chapter 3: Lessons About Design 71
Introduction to Design 71
First Steps: Design 75
Lesson 17: Design demands iteration 76
Lesson 18: It's cheaper to iterate at higher levels of abstraction 79
Lesson 19: Make products easy to use correctly, hard to use incorrectly 84
Lesson 20: You can't optimize all desirable quality attributes 87
Lesson 21: An ounce of design is worth a pound of recoding 92
Lesson 22: Many system problems take place at interfaces 94
Next Steps: Design 100

Chapter 4: Lessons About Project Management 103
Introduction to Project Management 103
First Steps: Project Management 108
Lesson 23: Work plans must account for friction 109
Lesson 24: Don't give anyone an estimate off the top of your head 114
Lesson 25: Icebergs are always larger than they first appear 116
Lesson 26: Data strengthens your negotiating position 121
Lesson 27: Use historical data to improve estimates 124
Lesson 28: Don't change an estimate just to make someone happy 127
Lesson 29: Stay off the critical path 129
Lesson 30: Incomplete tasks get no partial credit 132
Lesson 31: A project team needs flexibility to adapt to change 136
Lesson 32: Uncontrolled project risks will control you 140
Lesson 33: The customer is not always right 145
Lesson 34: We do too much pretending in software 149
Next Steps: Project Management 151

Chapter 5: Lessons About Culture and Teamwork 153
Afgekapt op 60 regels

Managementboek Top 100

Rubrieken

Producten

    Auteurs

      Trefwoorden

        Artikelen

          Software Development Pearls