Effort estimation is a core practice in software projects to help project managers work out the duration and cost of their project. This book compares different industry approaches to effort estimation and explains how to use each in a straightforward way with a real-life case study example so the reader can learn to apply it immediately. The approaches covered here range from more traditional function points to agile story points and Kanban estimation techniques. The reader will also learn how to answer the question all managers dread: “How is your project going?” with earned value analysis. There are exercises for the reader to apply the approaches with answers and explanations provided. This highly readable book is a valuable, go-to resource for software project managers, teachers of software project management, and students of computer science, information systems and software engineering who will become the project managers of the future.

Agile Estimating and Planning is the definitive, practical guide to estimating and planning agile projects. In this book, Agile Alliance cofounder Mike Cohn discusses the philosophy of agile estimating and planning and shows you exactly how to get the job done, with real-world examples and case studies. Concepts are clearly illustrated and readers are guided, step by step, toward how to answer the following questions: What will we build? How big will it be? When must it be done? How much can I really complete by then? You will first learn what makes a good plan-and then what makes it agile. Using the techniques in Agile Estimating and Planning, you can stay agile from start to finish, saving time, conserving resources, and accomplishing more. Highlights include: Why conventional prescriptive planning fails and why agile planning works How to estimate feature size using story points and ideal days–and when to use each How and when to re-estimate How to prioritize features using both financial and nonfinancial approaches How to split large features into smaller, more manageable ones How to plan iterations and predict your team's initial rate of progress How to schedule projects that have unusually high uncertainty or schedule-related risk How to estimate projects that will be worked on by multiple teams Agile Estimating and Planning supports any agile, semiagile, or iterative process, including Scrum, XP, Feature-Driven Development, Crystal, Adaptive Software Development, DSDM, Unified Process, and many more. It will be an indispensable resource for every development manager, team leader, and team member.

Estimating software development often produces more angst than value, but it doesn't have to. Identify the needs behind estimate requests and determine how to meet those needs simply and easily. Choose estimation techniques based on current needs and available information, gaining benefit while reducing cost and effort. Detect bad assumptions that might sink your project if you don't adjust your plans. Discover what to do when an estimate is wrong, how to recover, and how to use that knowledge for future planning. Learn to communicate about estimates in a healthy and productive way, maximizing advantage to the organization and minimizing damage to the people. In a world where most developers hate estimation and most managers fear disappointment with the results, there is hope for both. It requires giving up some widely held misconceptions. Let go of the notion that "an estimate is an estimate" and estimate for the particular need you, and your organization, have. Realize that estimates have a limited shelf-life, and reestimate frequently if it's important. When reality differs from your estimate, don't lament; mine that disappointment for the gold that can be the longer-term jackpot. Estimate in comparison to past experience, by modeling the work mathematically, or a hybrid of both. Learn strategies for effective decomposition of work and aspects of the work that likely affect your estimates. Hedge your bets by comparing the results of different approaches. Find out what to do when an estimate proves wrong. And they will. They're estimates, after all. You'll discover that you can use estimates to warn you of danger so you can take appropriate action in time. Learn some crucial techniques to understand and communicate with those who need to understand. Address both the technical and sociological aspects of estimation, and you'll help your organization achieve its desired goals with less drama and more benefit. What You Need: No software needed, just your past experience and concern for the outcomes.

Often referred to as the “black art” because of its complexity and uncertainty, software estimation is not as difficult or puzzling as people think. In fact, generating accurate estimates is straightforward—once you understand the art of creating them. In his highly anticipated book, acclaimed author Steve McConnell unravels the mystery to successful software estimation—distilling academic information and real-world experience into a practical guide for working software professionals. Instead of arcane treatises and rigid modeling techniques, this guide highlights a proven set of procedures, understandable formulas, and heuristics that individuals and development teams can apply to their projects to help achieve estimation proficiency. Discover how to: Estimate schedule and cost—or estimate the functionality that can be delivered within a given time frame Avoid common software estimation mistakes Learn estimation techniques for you, your team, and your organization * Estimate specific project activities—including development, management, and defect correction Apply estimation approaches to any type of project—small or large, agile or traditional Navigate the shark-infested political waters that surround project estimates When many corporate software projects are failing, McConnell shows you what works for successful software estimation.

Product verifiable, defensible, and achievable software estimates Based on data collected by the International Software Benchmarking Standards Group (ISBSG), Practical Software Project Estimation explains how to accurately forecast the size, cost, and schedule of software projects. Get expert advice on generating accurate estimates, minimizing risks, and planning and managing projects. Valuable appendixes provide estimation equations, delivery rate tables, and the ISBSG Repository demographics. Verify project objectives and requirements Determine, validate, and refine software functional size Produce indicative estimates using regression equations Predict effect and duration through comparison and analogy Build estimation frameworks Perform benchmarks using the ISBSG Repository Compare IFPUG, COSMIC, and FiSMA sizing methods Peter Hill is the chief executive officer and a director of the ISBSG. He has been in the information services industry for more than 40 years and has compiled and edited five books for the ISBSG.

Project estimating plays a vital role in project management. Typically completed in the initial planning stages, accurate project estimation can be a difficult task. Organizations and project managers should use these initial estimates to baseline the project schedule and cost, then refine these estimates as the project develops. Accurate estimation and refinement of the estimates leads to better and earlier decision making, thus maximizing value.Developed within the framework of A Guide to the Project Management Body of Knowledge (PMBOK&® Guide) &– Sixth Edition and other PMI standards, the Practice Standard for Project Estimating &– Second Edition focuses on providing models for the project management profession in both plan-driven and change-driven adaptive (agile) life cycles. This practice standard describes the aspects of project estimating that are recognized as good practice on most projects most of the time and that are widely recognized and consistently applied.PMI practice standards describe processes, activities, constraints, inputs, and outputs for specific discipline subject areas and are targeted to all practitioners within projectized organizations, not just project managers.

Effort estimation is a core practice in software projects to help project managers work out the duration and cost of their project. This book compares different industry approaches to effort estimation and explains how to use each in a straightforward way with a real-life case study example so the reader can learn to apply it immediately. The approaches covered here range from more traditional function points to agile story points and Kanban estimation techniques. The reader will also learn how to answer the question all managers dread: "How is your project going?" with earned value analysis. There are exercises for the reader to apply the approaches with answers and explanations provided. This highly readable book is a valuable, go-to resource for software project managers, teachers of software project management, and students of computer science, information systems and software engineering who will become the project managers of the future.