Cost Estimation in Agile Software Development: Utilizing Functional Size Measurement Methods
()
About this ebook
This book illustrates, how size metrics can be utilised profitably in software development processes oriented towards agile values. It points out differences and restrictions, how the accuracy of cost estimations can be increased with each sprint and examines the feasibility of automated measurements.
Read more from Stefan Luckhaus
Increasing Productivity of Software Development
Related to Cost Estimation in Agile Software Development
Related ebooks
Group Project Software Management: A Guide for University Students and Instructors Rating: 0 out of 5 stars0 ratingsAgile Leadership: A Leader’S Guide to Orchestrating Agile Strategy, Product Quality and It Governance Rating: 0 out of 5 stars0 ratingsThe Chartered Agile Project Manager Rating: 0 out of 5 stars0 ratingsIT Technical best practices: How to Reduce Agile cycle time with reusable code? Rating: 0 out of 5 stars0 ratingsHybrid Application Project Management A Complete Guide - 2020 Edition Rating: 0 out of 5 stars0 ratingsSoftware Testing Interview Questions You'll Most Likely Be Asked: Job Interview Questions Series Rating: 0 out of 5 stars0 ratingsCloud Migration Strategy A Complete Guide - 2019 Edition Rating: 0 out of 5 stars0 ratingsAgile Product Management Rating: 0 out of 5 stars0 ratingsPMOs Standard Requirements Rating: 0 out of 5 stars0 ratingsRequirements Management Plan A Complete Guide - 2019 Edition Rating: 0 out of 5 stars0 ratingsBlameless Continuous Integration: A Small Step Towards Psychological Safety of Agile Teams Rating: 0 out of 5 stars0 ratingsAgile Tools A Complete Guide - 2019 Edition Rating: 0 out of 5 stars0 ratingsIT Delivery Model Complete Self-Assessment Guide Rating: 0 out of 5 stars0 ratingsProcess architecture Complete Self-Assessment Guide Rating: 0 out of 5 stars0 ratingsKPI Based Standard Requirements Rating: 0 out of 5 stars0 ratingsService Management Complete Self-Assessment Guide Rating: 0 out of 5 stars0 ratingsManaging Technical Debt A Complete Guide - 2021 Edition Rating: 0 out of 5 stars0 ratingsAgile Aggravations Rating: 3 out of 5 stars3/5Data Hub Architecture The Ultimate Step-By-Step Guide Rating: 0 out of 5 stars0 ratingsHow to successfully implement an ERP Rating: 0 out of 5 stars0 ratingsEnterprise Architect A Complete Guide - 2019 Edition Rating: 0 out of 5 stars0 ratingsIT Management Process Maturity Complete Self-Assessment Guide Rating: 0 out of 5 stars0 ratingsIT Operations Management A Complete Guide - 2020 Edition Rating: 0 out of 5 stars0 ratingsRequirements analysis Complete Self-Assessment Guide Rating: 5 out of 5 stars5/5Software Change, Configuration and Release Management Complete Self-Assessment Guide Rating: 0 out of 5 stars0 ratingsEvent-driven SOA Complete Self-Assessment Guide Rating: 0 out of 5 stars0 ratingsIT PMO Complete Self-Assessment Guide Rating: 0 out of 5 stars0 ratingsFunctional Requirement A Complete Guide - 2019 Edition Rating: 0 out of 5 stars0 ratingsProduct breakdown structure A Complete Guide Rating: 1 out of 5 stars1/5Agile Bank Management A Complete Guide - 2021 Edition Rating: 0 out of 5 stars0 ratings
Technology & Engineering For You
The Art of War Rating: 4 out of 5 stars4/5Elon Musk: Tesla, SpaceX, and the Quest for a Fantastic Future Rating: 4 out of 5 stars4/5The Big Book of Hacks: 264 Amazing DIY Tech Projects Rating: 4 out of 5 stars4/5Electrical Engineering 101: Everything You Should Have Learned in School...but Probably Didn't Rating: 5 out of 5 stars5/5How to Write Effective Emails at Work Rating: 4 out of 5 stars4/580/20 Principle: The Secret to Working Less and Making More Rating: 5 out of 5 stars5/5The Big Book of Maker Skills: Tools & Techniques for Building Great Tech Projects Rating: 4 out of 5 stars4/5The 48 Laws of Power in Practice: The 3 Most Powerful Laws & The 4 Indispensable Power Principles Rating: 5 out of 5 stars5/5The CIA Lockpicking Manual Rating: 5 out of 5 stars5/5Ultralearning: Master Hard Skills, Outsmart the Competition, and Accelerate Your Career Rating: 4 out of 5 stars4/5The ChatGPT Millionaire Handbook: Make Money Online With the Power of AI Technology Rating: 0 out of 5 stars0 ratingsMy Inventions: The Autobiography of Nikola Tesla Rating: 4 out of 5 stars4/5Pilot's Handbook of Aeronautical Knowledge (Federal Aviation Administration) Rating: 4 out of 5 stars4/5Understanding Media: The Extensions of Man Rating: 4 out of 5 stars4/5The Systems Thinker: Essential Thinking Skills For Solving Problems, Managing Chaos, Rating: 4 out of 5 stars4/5Broken Money: Why Our Financial System is Failing Us and How We Can Make it Better Rating: 5 out of 5 stars5/5Smart Phone Dumb Phone: Free Yourself from Digital Addiction Rating: 0 out of 5 stars0 ratingsU.S. Marine Close Combat Fighting Handbook Rating: 4 out of 5 stars4/5The Art of War Rating: 4 out of 5 stars4/5How to Disappear and Live Off the Grid: A CIA Insider's Guide Rating: 0 out of 5 stars0 ratingsLogic Pro X For Dummies Rating: 0 out of 5 stars0 ratingsThe Fast Track to Your Technician Class Ham Radio License: For Exams July 1, 2022 - June 30, 2026 Rating: 5 out of 5 stars5/5Summary of Nicolas Cole's The Art and Business of Online Writing Rating: 4 out of 5 stars4/5Rust: The Longest War Rating: 4 out of 5 stars4/5The Invisible Rainbow: A History of Electricity and Life Rating: 4 out of 5 stars4/5No Nonsense Technician Class License Study Guide: for Tests Given Between July 2018 and June 2022 Rating: 5 out of 5 stars5/5
Reviews for Cost Estimation in Agile Software Development
0 ratings0 reviews
Book preview
Cost Estimation in Agile Software Development - Stefan Luckhaus
Introduction
Indirect estimations of development costs, which put the methodically determined size of planned software into relation with a precisely measured value of the own productivity, are a best practice approach for planning software development projects. However, utilizing them requires a minimum degree of specification. Briefly described user stories must be refined by use cases and elementary processes. As a consequence, the size of the planned software will be rendered measurable, while the measurement process is lean and does not require much effort.
This book describes briefly and based on the author’s own experience the basics of methodological cost estimations. It demonstrates that this approach agrees well with agile development and especially supports principles such as
•the flexible consideration of new or changed requirements and
•continuous improvement due to retrospectives.
Characteristics and Importance of Agile Software Development
Genesis
At the beginning of the 90s many large-scale projects ran into difficulties – due to their long process times, rigid roles and inflexible structures in conjunction with frequently changing requirements. In this context the C3 project of the Chrysler group (Chrysler Comprehensive Compensation) is often mentioned, which had applied the waterfall model in the beginning. In these days, many US companies experimented with lightweighted development processes and found out that shorter process times, a closer and selfresponsible collaboration of the project teams or the uncomplicated handling of change requests lead to a better mitigation of typical risks and in consequence to more successful projects - successful in terms of early benefits by the customer. Process models such as Scrum or Crystal were developed. The Chrysler C3 project could be prevented from failing by introducing some of these lightweighted methods, which afterwards became popular as Extreme Programming [Wells 2009].
In February 2001, experts exchanged their experience with software development processes at a meeting in Utah (USA) and formulated a system of values, laying the foundation for the way of software development which, since then, is called agile – the Agile Manifesto [Agile Manifesto 2001]:
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions
over processes and tools
Working software
over comprehensive documentation
Customer collaboration
over contract negotiation
Responding to change
over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
The Agile Manifesto is often misinterpreted. It is commonly used as an excuse to forego any documentation. However, especially the last paragraph makes it evident that it is just a matter of priorities, and that activities such as documentation are adjudged as certainly valuable.
This system of values was refined by the following twelve principles [Agile Manifesto Principles 2001]:
1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
3. Deliver working software