833 Results for : programmer

  • Thumbnail
    Effective C++ 3/e is a complete update of Effective C++ and Effective C++ 2/e . Like its predecessors, 3/e has 55 guidelines which contain better, more effective ways to write code, backed by specific examples. The second edition published in 1997, and was basically a face-lift of the first edition, keeping most of the same elements, and seven years later is still selling well. Now, Meyers has dramatically rejuvenated the material, including more than 30% brand-new material. Meyers began this edition by asking himself, "What are the 55 most important pieces of advice for practicing C++ programmers in 2005?" He also asked thousands of past users of his books this same question. This resulted in a completely new book. New material includes use of UML notation, thread safety, exception safety, design patterns, and templates. Any older material has been revitalized to reflect new ideas and strides in C++ development. Product Description "Every C++ professional needs a copy of Effective C++. It is an absolute must-read for anyone thinking of doing serious C++ development. If you've never read Effective C++ and you think you know everything about C++, think again." - Steve Schirripa, Software Engineer, Google"C++ and the C++ community have grown up in the last fifteen years, and the third edition of Effective C++ reflects this. The clear and precise style of the book is evidence of Scott's deep insight and distinctive ability to impart knowledge." - Gerhard Kreuzer, Research and Development Engineer, Siemens AG The first two editions of Effective C++ were embraced by hundreds of thousands of programmers worldwide. The reason is clear: Scott Meyers' practical approach to C++ describes the rules of thumb used by the experts - the things they almost always do or almost always avoid doing - to produce clear, correct, efficient code. The book is organized around 55 specific guidelines, each of which describes a way to write better C++. Each is backed by concrete examples. For this third edition, more than half the content is new, including added chapters on managing resources and using templates. Topics from the second edition have been extensively revised to reflect modern design considerations, including exceptions, design patterns, and multithreading. Important features of Effective C++ include: Expert guidance on the design of effective classes, functions, templates, and inheritance hierarchies. Applications of new "TR1" standard library functionality, along with comparisons to existing standard library components. Insights into differences between C++ and other languages (e.g., Java, C#, C) that help developers from those languages assimilate "the C++ way" of doing things. Features + Benefits Revision of the best seller. This is the market leading, second book on programming that every C++ programmer needs. ° Scott Meyers is one of the world's foremost experts on C++ software development. He is an excellent promoter of his books. ° More than 50% new material and complete updates of tried-and-true material to bring it up to 2005 standards. ° There is no better way to bring C++ programmers up to date on cutting edge practices than this book. It's a classic--the #1 book of its kind. Backcover "Every C++ professional needs a copy of Effective C++. It is an absolute must-read for anyone thinking of doing serious C++ development. If you've never read Effective C++ and you think you know everything about C++, think again." - Steve Schirripa, Software Engineer, Google"C++ and the C++ community have grown up in the last fifteen years, and the third edition of Effective C++ reflects this. The clear and precise style of the book is evidence of Scott's deep insight and distinctive ability to impart knowledge." - Gerhard Kreuzer, Research and Development Engineer, Siemens AG The first two editions of Effective C++ were embraced by hundreds of thousands of programmers worldwide. The reason is clear: Scott Meyers' practical approach to C++ describes the rules of thumb used by the experts - the things they almost always do or almost always avoid doing - to produce clear, correct, efficient code. The book is organized around 55 specific guidelines, each of which describes a way to write better C++. Each is backed by concrete examples. For this third edition, more than half the content is new, including added chapters on managing resources and using templates. Topics from the second edition have been extensively revised to reflect modern design considerations, including exceptions, design patterns, and multithreading. Important features of Effective C++ include: Expert guidance on the design of effective classes, functions, templates, and inheritance hierarchies. Applications of new "TR1" standard library functionality, along with comparisons to existing standard library components. Insights into differences between C++ and other languages (e.g., Java, C#, C) that help developers from those languages assimilate "the C++ way" of doing things. Preface xvAcknowledgments xviiIntroduction 1Chapter 1: Accustoming Yourself to C++ 11 Item 1: View C++ as a federation of languages. 11 Item 2: Prefer consts, enums, and inlines to #defines. 13 Item 3: Use const whenever possible. 17 Item 4: Make sure that objects are initialized before they're used. 26 Chapter 2: Constructors, Destructors, and Assignment Operators 34 Item 5: Know what functions C++ silently writes and calls. 34 Item 6: Explicitly disallow the use of compiler-generated functions you do not want. 37 Item 7: Declare destructors virtual in polymorphic base classes. 40 Item 8: Prevent exceptions from leaving destructors. 44 Item 9: Never call virtual functions during construction or destruction. 48 Item 10: Have assignment operators return a reference to *this. 52 Item 11: Handle assignment to self in operator=. 53 Item 12: Copy all parts of an object. 57 Chapter 3: Resource Management 61 Item 13: Use objects to manage resources. 61 Item 14: Think carefully about copying behavior in resource-managing classes. 66 Item 15: Provide access to raw resources in resource-managing classes. 69 Item 16: Use the same form in corresponding uses of new and delete. 73 Item 17: Store newed objects in smart pointers in standalone statements. 75 Chapter 4: Designs and Declarations 78 Item 18: Make interfaces easy to use correctly and hard to use incorrectly. 78 Item 19: Treat class design as type design. 84 Item 20: Prefer pass-by-reference-to-const to pass-by-value. 86 Item 21: Don't try to return a reference when you must return an object. 90 Item 22: Declare data members private. 94 Item 23: Prefer non-member non-friend functions to member functions. 98 Item 24: Declare non-member functions when type conversions should apply to all parameters. 102 Item 25: Consider support for a non-throwing swap. 106 Chapter 5: Implementations 113 Item 26: Postpone variable definitions as long as possible. 113 Item 27: Minimize casting. 116 Item 28: Avoid returning "handles" to object internals. 123 Item 29: Strive for exception-safe code. 127 Item 30: Understand the ins and outs of inlining. 134 Item 31: Minimize compilation dependencies between files. 140 Chapter 6: Inheritance and Object-Oriented Design 149 Item 32: Make sure public inheritance models "is-a." 150 Item 33: Avoid hiding inherited names. 156 Item 34: Differentiate between inheritance of interface and inheritance of implementation. 161 Item 35: Consider alternatives to virtual functions. 169 Item 36: Never redefine an inherited non-virtual function. 178 Item 37: Never redefine a function's inherited default parameter value. 180 Item 38: Model "has-a" or "is-implemented-in-terms-of" through composition. 184 Item 39: Use private inheritance judiciously. 187 Item 40: Use multiple inheritance judiciously. 192 Chapter 7: Templates and Generic Programming 199 Item 41: Understand implicit interfaces and compile-time polymorphism. 199 Item 42: Understand the two meanings of typename. 203 Item 43: Know how to access names in templatized base classes. 207 Item 44: Factor parameter-independent code out of templates. 212 Item 45: Use member function templates to accept "all compatible types." 218 Item 46: Define non-member functions inside templates when type conversions are desired. 222 Item 47: Use traits classes for information about types. 226 Item 48: Be aware of template metaprogramming. 233 Chapter 8: Customizing new and delete 239 Item 49: Understand the behavior of the new-handler. 240 Item 50: Understand when it makes sense to replace new and delete. 247 Item 51: Adhere to convention when writing new and delete. 252 Item 52: Write placement delete if you write placement new. 256 Chapter 9: Miscellany 262 Item 53: Pay attention to compiler warnings. 262 Item 54: Familiarize yourself with the standard library, including TR1. 263 Item 55: Familiarize yourself with Boost. 269 Appendix A: Beyond Effective C++ 273Appendix B: Item Mappings Between Second and Third Editions 277Index 280Effective C++ 3/e is a complete update of Effective C++ and Effective C++ 2/e .Like its predecessors, 3/e has 55 guidelines which contain better, moreeffective ways to write code, backed by specific examples. The second editionpublished in 1997, and was basically a face-lift of the first edition, keeping mostof the same elements, and seven years later is still selling well.Now, Meyers has dramatically rejuvenated the material, including more than50% brand-new material. Meyers began this edition by asking himself, Whatare the 55 most important pieces of advice for practicing C++ programmers in2005? He also asked thousands of past users of his books this same question.This resulted in a completely new book. New material includes use of UMLnotation, thread safety, exception safety, design patterns, and templates. Anyolder material has been revitalized to reflect new ideas and strides in C++development.
    • Shop: buecher
    • Price: 31.99 EUR excl. shipping
  • Thumbnail
    The first step to project success is accurate estimating and realistic planning. Projects with unrealistic expectations affixed to them are likely to derail at an early stage. This book shows the software practitioner how to effectively estimate and properly plan a project within an agile context. The book's content is suitable for projects using any agile or semi-agile process (such as Extreme Programming, Scrum, Feature Driven Development, Crystal, Adaptive Software Development, DSDM or even the IBM Rational Unified Process). The ideas in this book will work with any iterative development process, which greatly broadens the target audience beyond the traditional agile community. Each chapter is supported by a summary and a set of questions that allows readers to assess their ability to estimate and plan a project. The result is an engaging read with pearls of wisdom that can be applied to the reader's next project. Product Description Praise for Agile Estimating and Planning Traditional, deterministic approaches to planning and estimating simply don't cut it on the slippery slopes of today's dynamic, change-driven projects. Mike Cohn's breakthrough book gives us not only the philosophy, but also the guidelines and a proven set of tools that we need to succeed in planning, estimating, and scheduling projects with a high uncertainty factor. At the same time, the author never loses sight of the need to deliver business value to the customer each step of the way. -Doug DeCarlo, author of eXtreme Project Management: Using Leadership, Principles and Tools to Deliver Value in the Face of Volatility (Jossey-Bass, 2004) We know how to build predictive plans and manage them. But building plans that only estimate the future and then embrace change, challenge most of our training and skills. In Agile Estimating and Planning, Mike Cohn once again fills a hole in the Agile practices, this time by showing us a workable approach to Agile estimating and planning. Mike delves into the nooks and crannies of the subject and anticipates many of the questions and nuances of this topic. Students of Agile processes will recognize that this book is truly about agility, bridging many of the practices between Scrum and ExtremeProgramming. -Ken Schwaber, Scrum evangelist, Agile Alliance cofounder, and signatory to the Agile Manifesto In Agile Estimating and Planning, Mike Cohn has, for the first time, brought together most everything that the Agile community has learned about the subject. The book is clear, well organized, and a pleasant and valuable read. It goes into all the necessary detail, and at the same time keeps the reader's burden low. We can dig in as deeply as we need to, without too much detail before we need it. The book really brings together everything we have learned about Agile estimation and planning over the past decade. It will serve its readers well. -Ron Jeffries, www.XProgramming.com, author of Extreme Programming Installed (Addison-Wesley, 2001) and Extreme Programming Adventures in C# (Microsoft Press, 2004) Agile Estimating and Planning provides a view of planning that's balanced between theory and practice, and it is supported by enough concrete experiences to lend it credibility. I particularly like the quote 'planning is a quest for value.' It points to a new, more positive attitude toward planning that goes beyond the 'necessary evil' view that I sometimes hold. -Kent Beck, author of Extreme Programming Explained, Second Edition (Addison-Wesley, 2005) Up-front planning is still the most critical part of software development. Agile software development requires Agile planning techniques. This book shows you how to employ Agile planning in a succinct, practical, and easy-to-follow manner. -Adam Rogers, Ultimate Software Mike does a great follow-up to User Stories Applied by continuing to provide Agile teams with the practical approaches and techniques to increase agility. In this book, Mike provides time-proven and well-tested methods for being successful with the multiple levels of planning and estimating required by Agile. This book is the first to detail the disciplines of Agile estimating and planning, in ways that rival my 1980 civil engineering texts on CPM Planning and Estimating. -Ryan Martens, President and Founder, Rally Software Development Corporation With insight and clarity, Mike Cohn shows how to effectively produce software of high business value. With Agile estimation and planning, you focus effort where it really counts, and continue to do so as circumstances change. -Rick Mugridge, Rimu Research Ltd., and lead author, Fit for Developing Software (Prentice Hall, 2005) Finally! The groundbreaking book my clients have been clamoring for! Agile Estimating and Planning demystifies the process of defining, driving, and delivering great software that matters to the business. Mike's clarity, insight, and experience leap out through every page of this book, offering an approach that is relevant and immediately useful to all members of an Agile project. -Kert D. Peterson, President, Enterprise Agile Group, LLC This isn't yet another generic book on Agile software development. Agile Estimating and Planning fills a gap left by most of the other books and gives you important, practical, down-to-earth techniques needed to be successful on Agile development projects. -Steve Tockey, Principal Consultant, Construx Software Estimation, planning, and tracking is a trinity. If you don't do one of them, you don't need the other two. This book provides very practical knowledge for estimation, planning, prioritizing, and tracking. It should be compulsory subject matter for project managers and their teams, even if they hesitate to call themselves Agile. -Niels Malotaux, Project Coach Effective planning is an important, but often misunderstood, part of any successful Agile project. With Agile Estimating and Planning, Mike Cohn has given us a definitive guide to a wide range of Agile estimating and planning practices. With his clear and practical style, Mike not only explains how to successfully get started planning an Agile project, but also provides a wealth of tips and advice for improving any team's Agile planning process. This book is a must-read for managers, coaches, and members of Agile teams. -Paul Hodgetts, Agile coach and CEO, Agile Logic Mike's writing style captures the essence of agility-just the right amount of information to bring clarity to the reader. This book provides an excellent guide for all Agile practitioners, both seasoned and novice. -Robert Holler, President and CEO, VersionOne, LLC It is as if Mike took the distilled knowledge regarding planning and estimation of a great Agile developer (which he is) and laid out all he knows in an easily understandable manner. More importantly, he has a great mix of concepts with real-world examples finished off with a case study so the reader can relate the information to their own situation. Unless you are already an expert Agile planner and estimator, this book is for you. -Alan Shalloway, CEO, Senior Consultant, Net Objectives, and coauthor of Design Patterns Explained, Second Edition (Addison-Wesley, 2005) Although I had plenty of XP experience before trying out Mike Cohn's Agile planning practices, the effectiveness of the practical and proven techniques in this book blew me away! The book recognizes that people, not tools or processes, produce great software, and that teams benefit most by learning about their project and their product as they go. The examples in the book are concrete, easily grasped, and simply reek of common sense. This book will help teams (whether Agile or not) deliver more value, more often, and have fun doing it! Whether you're a manager or a programmer, a tester or a CEO, part of an Agile team, or just looking for a way to stamp out chaos and death marches, this book will guide you. -Lisa Crispin, coauthor of Testing Extreme Programming (Addison-Wesley, 2003) Mike Cohn does an excellent job demonstrating how an Agile approach can address issues of risk and uncertainty in order to provide more meaningful estimates and plans for software projects. -Todd Little, Senior Development Manager, Landmark Graphics Mike Cohn explains his approach to Agile planning, and shows how 'critical chain' thinking can be used to effectively buffer both schedule and features. As with User Stories Applied, this book is easy to read and grounded in real-world experience. -Bill Wake, author o Features + Benefits Goes beyond the strategy of just enough planning and estimating, and shows readers how to make agile practices truly work organizationally. ° Save time, conserve organizational resources, and manage software projects more efficiently by learning to anticipate future needs ° Key points are supported by case studies derived from real-world projects ° Teaches the nuts and bolts of estimating a project, an iteration, or even a task -- and teaches a variety of approaches to effective estimating Backcover Praise for Agile Estimating and Planning Traditional, deterministic approaches to planning and estimating simply don't cut it on the slippery slopes of today's dynamic, change-driven projects. Mike Cohn's breakthrough book gives us not only the philosophy, but also the guidelines and a proven set of tools that we need to succeed in planning, estimating, and scheduling projects with a high uncertainty factor. At the same time, the author never loses sight of the need to deliver business value to the customer each step of the way. -Doug DeCarlo, author of eXtreme Project Management: Using Leadership, Principles and Tools to Deliver Value in the Face of Volatility (Jossey-Bass, 2004) We know how to build predictive plans and manage them. But building plans that only estimate the future and then embrace change, challenge most of our training and skills. In Agile Estimating and Planning, Mike Cohn once again fills a hole in the Agile practices, this time by showing us a workable approach to Agile estimating and planning. Mike delves into the nooks and crannies of the subject and anticipates many of the questions and nuances of this topic. Students of Agile processes will recognize that this book is truly about agility, bridging many of the practices between Scrum and ExtremeProgramming. -Ken Schwaber, Scrum evangelist, Agile Alliance cofounder, and signatory to the Agile Manifesto In Agile Estimating and Planning, Mike Cohn has, for the first time, brought together most everything that the Agile community has learned about the subject. The book is clear, well organized, and a pleasant and valuable read. It goes into all the necessary detail, and at the same time keeps the reader's burden low. We can dig in as deeply as we need to, without too much detail before we need it. The book really brings together everything we have learned about Agile estimation and planning over the past decade. It will serve its readers well. -Ron Jeffries, www.XProgramming.com, author of Extreme Programming Installed (Addison-Wesley, 2001) and Extreme Programming Adventures in C# (Microsoft Press, 2004) Agile Estimating and Planning provides a view of planning that's balanced between theory and practice, and it is supported by enough concrete experiences to lend it credibility. I particularly like the quote 'planning is a quest for value.' It points to a new, more positive attitude toward planning that goes beyond the 'necessary evil' view that I sometimes hold. -Kent Beck, author of Extreme Programming Explained, Second Edition (Addison-Wesley, 2005) Up-front planning is still the most critical part of software development. Agile software development requires Agile planning techniques. This book shows you how to employ Agile planning in a succinct, practical, and easy-to-follow manner. -Adam Rogers, Ultimate Software Mike does a great follow-up to User Stories Applied by continuing to provide Agile teams with the practical approaches and techniques to increase agility. In this book, Mike provides time-proven and well-tested methods for being successful with the multiple levels of planning and estimating required by Agile. This book is the first to detail the disciplines of Agile estimating and planning, in ways that rival my 1980 civil engineering texts on CPM Planning and Estimating. -Ryan Martens, President and Founder, Rally Software Development Corporation With insight and clarity, Mike Cohn shows how to effectively produce software of high business value. With Agile estimation and planning, you focus effort where it really counts, and continue to do so as circumstances change. -Rick Mugridge, Rimu Research Ltd., and lead author, Fit for Developing Software (Prentice Hall, 2005) Finally! The groundbreaking book my clients have been clamoring for! Agile Estimating and Planning demystifies the process of defining, driving, and delivering great software that matters to the business. Mike's clarity, insight, and experience leap out through every page of this book, offering an approach that is relevant and immediately useful to all members of an Agile project. -Kert D. Peterson, President, Enterprise Agile Group, LLC This isn't yet another generic book on Agile software development. Agile Estimating and Planning fills a gap left by most of the other books and gives you important, practical, down-to-earth techniques needed to be successful on Agile development projects. -Steve Tockey, Principal Consultant, Construx Software Estimation, planning, and tracking is a trinity. If you don't do one of them, you don't need the other two. This book provides very practical knowledge for estimation, planning, prioritizing, and tracking. It should be compulsory subject matter for project managers and their teams, even if they hesitate to call themselves Agile. -Niels Malotaux, Project Coach Effective planning is an important, but often misunderstood, part of any successful Agile project. With Agile Estimating and Planning, Mike Cohn has given us a definitive guide to a wide range of Agile estimating and planning practices. With his clear and practical style, Mike not only explains how to successfully get started planning an Agile project, but also provides a wealth of tips and advice for improving any team's Agile planning process. This book is a must-read for managers, coaches, and members of Agile teams. -Paul Hodgetts, Agile coach and CEO, Agile Logic Mike's writing style captures the essence of agility-just the right amount of information to bring clarity to the reader. This book provides an excellent guide for all Agile practitioners, both seasoned and novice. -Robert Holler, President and CEO, VersionOne, LLC It is as if Mike took the distilled knowledge regarding planning and estimation of a great Agile developer (which he is) and laid out all he knows in an easily understandable manner. More importantly, he has a great mix of concepts with real-world examples finished off with a case study so the reader can relate the information to their own situation. Unless you are already an expert Agile planner and estimator, this book is for you. -Alan Shalloway, CEO, Senior Consultant, Net Objectives, and coauthor of Design Patterns Explained, Second Edition (Addison-Wesley, 2005) Although I had plenty of XP experience before trying out Mike Cohn's Agile planning practices, the effectiveness of the practical and proven techniques in this book blew me away! The book recognizes that people, not tools or processes, produce great software, and that teams benefit most by learning about their project and their product as they go. The examples in the book are concrete, easily grasped, and simply reek of common sense. This book will help teams (whether Agile or not) deliver more value, more often, and have fun doing it! Whether you're a manager or a programmer, a tester or a CEO, part of an Agile team, or just looking for a way to stamp out chaos and death marches, this book will guide you. -Lisa Crispin, coauthor of Testing Extreme Programming (Addison-Wesley, 2003) Mike Cohn does an excellent job demonstrating how an Agile approach can address issues of risk and uncertainty in order to provide more meaningful estimates and plans for software projects. -Todd Little, Senior Development Manager, Landmark Graphics Mike Cohn explains his approach to Agile planning, and shows how 'critical chain' thinking can be used to effectively buffer both schedule and features. As with User Stories Applied, this book is easy to read and grounded in real-world experience. -Bill Wake, author o About the Author xviiForeword by Robert C. Martin xixForeword by Jim Highsmith xxiForeword by Gabrielle Benefield xxvAcknowledgments xxviiIntroduction xxixPart I: The Problem and the Goal 1Chapter 1: The Purpose of Planning 3 Why Do It? 5 What Makes a Good Plan? 8 What Makes Planning Agile? 9 Summary 10 Discussion Questions 10 Chapter 2: Why Planning Fails 11 Planning Is by Activity Rather Than Feature 12 Multitasking Causes Further Delays 15 Features Are Not Developed by Priority 17 We Ignore Uncertainty 17 Estimates Become Commitments 18 Summary 18 Discussion Questions 19 Chapter 3: An Agile Approach 21 An Agile Approach to Projects 23 An Agile Approach to Planning 27 Summary 31 Discussion Questions 32 Part II: Estimating Size 33Chapter 4: Estimating Size with Story Points 35 Story Points Are Relative 36 Velocity 38 Summary 40 Discussion Questions 41 Chapter 5: Estimating in Ideal Days 43 Ideal Time and Software Development 44 Ideal Days as a Measure of Size 46 One Estimate, Not Many 46 Summary 47 Discussion Questions 47 Chapter 6: Techniques for Estimating 49 Estimates Are Shared 51 The Estimation Scale 52 Deriving an Estimate 54 Planning Poker 56 Why Planning Poker Works 59 Summary 60 Discussion Questions 60 Chapter 7: Re-Estimating 61 Introducing the SwimStats Website 61 When Not to Re-Estimate 62 When to Re-Estimate 64 Re-Estimating Partially Completed Stories 66 The Purpose of Re-Estimating 67 Summary 67 Discussion Questions 67 Chapter 8: Choosing between Story Points and Ideal Days 69 Considerations Favoring Story Points 69 Considerations Favoring Ideal Days 72 Recommendation 73 Summary 74 Discussion Questions 75 Part III: Planning for Value 77Chapter 9: Prioritizing Themes 79 Factors in Prioritization 80 Combining the Four Factors 86 Some Examples 86 Summary 88 Discussion Questions 89 Chapter 10: Financial Prioritization 91 Sources of Return 93 An Example: WebPayroll 96 Financial Measures 102 Comparing Returns 108 Summary 109 Discussion Questions 109 Chapter 11: Prioritizing Desirability 111 Kano Model of Customer Satisfaction 112 Relative Weighting: Another Approach 117 Summary 119 Discussion Questions 120 Chapter 12: Splitting User Stories 121 When to Split a User Story 121 Splitting across Data Boundaries 122 Splitting on Operational Boundaries 124 Removing Cross-Cutting Concerns 125 Don't Meet Performance Constraints 126 Split Stories of Mixed Priority 127 Don't Split a Story into Tasks 127 Avoid the Temptation of Related Changes 128 Combining Stories 128 Summary 129 Discussion Questions 129 Part IV: Scheduling 131Chapter 13: Release Planning Essentials 133 The Release Plan 134 Updating the Release Plan 138 An Example 139 Summary 142 Discussion Questions 143 Chapter 14: Iteration Planning 145 Tasks Are Not Allocated During Iteration Planning 147 How Iteration and Release Planning Differ 148 Velocity-Driven Iteration Planning 149 Commitment-Driven Iteration Planning 158 My Recommendation 162 Relating Task Estimates to Story Points 163 Summary 165 Discussion Questions 166 Chapter 15: Selecting an Iteration Length 167 Factors in Selecting an Iteration Length 167 Making a Decision 171 Two Case Studies 173 Summary 175 Discussion Questions 176 Chapter 16: Estimating Velocity 177 Use Historical Values 178 Run an Iteration 179 Make a Forecast 181 Which Approach Should I Use? 185 Summary 186 Discussion Questions 186 Chapter 17: Buffering Plans for Uncertainty 187 Feature Buffers 188 Schedule Buffers 189 Combining Buffers 198 A Schedule Buffer Is Not Padding 199 Some Caveats 199 Summary 200 Discussion Questions 201 Chapter 18: Planning the Multiple-Team Project 203 Establishing a Common Basis for Estimates 204 Adding Detail to User Stories Sooner 205 Lookahead Planning 206 Incorporating Feeding Buffers into the Plan 208 But This Is So Much Work 210 Summary 210 Discussion Questions 211 Part V: Tracking and Communicating 213 Chapter 19: Monitoring the Release Plan 215 Tracking the Release 216 Release Burndown Charts 219 A Parking-Lot Chart 224 Summary 225 Discussion Questions 226 Chapter 20: Monitoring the Iteration Plan 227 The Task Board 227 Iteration Burndown Charts 230 Tracking Effort Expended 231 Individual Velocity 232 Summary 232 Discussion Questions 233 Chapter 21: Communicating about Plans 235 Communicating the Plan 237 Communicating Progress 238 An End-of-Iteration Summary 241 Summary 244 Discussion Questions 245 Part VI: Why Agile Planning Works 247Chapter 22: Why Agile Planning Works 249 Replanning Occurs Frequently 249 Estimates of Size and Duration Are Separated 250 Plans Are Made at Different Levels 251 Plans Are Based on Features, Not Tasks 252 Small Stories Keep Work Flowing 252 Work in Process Is Eliminated Every Iteration 252 Tracking Is at the Team Level 253 Uncertainty Is Acknowledged and Planned For 253 A Dozen Guidelines for Agile Estimating and Planning 254 Summary 256 Discussion Questions 257 Part VII: A Case Study 259Chapter 23: A Case Study: Bomb Shelter Studios 261 Day 1-Monday Morning 262 Estimating the User Stories 270 Preparing for Product Research 281 Iteration and Release Planning, Round 1 284 Two Weeks Later 302 Planning the Second Iteration 303 Two Weeks Later 305 Revising the Release Plan 305 Presenting the Revised Plan to Phil 308 Eighteen Weeks Later 312 Reference List 313Index 319The first step to project success is accurate estimating and realistic planning.Projects with unrealistic expectations affixed to them are likely to derail at anearly stage. This book shows the software practitioner how to effectivelyestimate and properly plan a project within an agile context. The book'scontent is suitable for projects using any agile or semi-agile process (such asExtreme Programming, Scrum, Feature Driven Development, Crystal,Adaptive Software Development, DSDM or even the IBM Rational UnifiedProcess). The ideas in this book will work with any iterative developmentprocess, which greatly broadens the target audience beyond the traditional agilecommunity. Each chapter is supported by a summary and a set of questionsthat allows readers to assess their ability to estimate and plan a project. Theresult is an engaging read with pearls of wisdom that can be applied to thereader's next project.
    • Shop: buecher
    • Price: 33.99 EUR excl. shipping
  • Thumbnail
    Think Like a Programmer - Typische Programmieraufgaben kreativ lösen am Beispiel von C++: ab 3.99 €
    • Shop: ebook.de
    • Price: 3.99 EUR excl. shipping
  • Thumbnail
    Programmer en Java: ab 2.81 €
    • Shop: ebook.de
    • Price: 2.81 EUR excl. shipping
  • Thumbnail
    Programmer en JavaScript: ab 2.81 €
    • Shop: ebook.de
    • Price: 2.81 EUR excl. shipping
  • Thumbnail
    Like A Girl: Programmer: ab 5.49 €
    • Shop: ebook.de
    • Price: 5.49 EUR excl. shipping
  • Thumbnail
    Confident Programmer Debugging Guide: ab 4.99 €
    • Shop: ebook.de
    • Price: 4.99 EUR excl. shipping
  • Thumbnail
    iOS Programming: Starter Guide: What Every Programmer Needs to Know About iOS Programming: ab 4.99 €
    • Shop: ebook.de
    • Price: 4.99 EUR excl. shipping
  • Thumbnail
    How to Become a Successful Programmer Without a Degree: ab 2.99 €
    • Shop: ebook.de
    • Price: 2.99 EUR excl. shipping
  • Thumbnail
    97 Things Every Java Programmer Should Know - Collective Wisdom from the Experts: ab 46.49 €
    • Shop: ebook.de
    • Price: 46.49 EUR excl. shipping


Similar searches: