This document discusses software estimation in agile deliveries and how Nesma can provide quick estimates. It notes that traditional function point analysis (FPA) is not well-suited for agile due to lack of documentation and details, and outdated terminology. Nesma offers high-level analysis based on use cases without full details. It provides accurate and fast measurement comparable to other size methods. The document also advertises free example cases to illustrate Nesma's measurement approach.

1. Frank Vogelezang
Counting Practices Committee
November 15, 2018

2. Software Estimation in Agile deliveries
| How Nesma can QuickStart your Software Estimate
Productsize
Schedule time
Must have
Should have
Could have
Won’t have
Backlog
Minimum Viable Product
Velocity

3. Software Estimation in Agile deliveries
| How Nesma can QuickStart your Software Estimate
Actual forecast
Productsize
Schedule time
Sprint 1 Sprint 2 Sprint 3
Must have
Should have
Could have
Won’t have
Backlog
Minimum Viable Product

4. Why FPA was not used in Agile deliveries
 FPA needs documentation we don’t have
 Data Model
 Functional Design
 FPA needs details we don’t have
 Record Element Types
 Data Element Types
 File Types Referenced
 We don’t understand language from the eighties
| How Nesma can QuickStart your Software Estimate

5. The new standard solves these issues
 Focus on High-Level analysis
 Can be applied on standard Use Cases
 Does not need the full details
 Accurate & fast measurement
 As accurate as detailed IFPUG or Nesma size measurements
 Faster than Gartner FFPA
 Terminology has been updated to reflect 21st century practices
| How Nesma can QuickStart your Software Estimate

6. FREE QuickStart examples
 36 examples to illustrate how to measure real-life cases
 Examples can be added without changing the standard
 FREE download
| How Nesma can QuickStart your Software Estimate

7. Focus on the processes
 It is all about the labor involved in processes
 Estimating at Product level is convenient
 The assumption is that underlying processes still apply
| Recap of today’s presentations

8. Agile Delivery Predictability
 “Apples-to-Apples” comparison of story points/sprint velocity
 Greater control with respect to agile operations
 Order coffee
| Recap of today’s presentations

9. Precise, accurate and repeatable estimates
 Poor statements of user needs lead to poor estimates
 Effective User Stories follow a syntax
 Correct, consistent and complete
| Recap of today’s presentations

10. Control over the backlog
 Reliable Scrum
 Sprint Velocity determines the Sprint Size
 Estimates can be used for … everything
| Recap of today’s presentations

11. #NoEstimate is not an option
 Any organization must determine an IT budget
 Estimates are needed to make informed decisions
 CXO’s need estimates for accountability to stake- & shareholders
| Recap of today’s presentations

12. NOT any metric is useful
 A metric is useful as soon as it has a good relation to performance
 Some metrics are more relevant than others
 Aligned metrics are better
| Recap of today’s presentations

13. Finally a real profession
 Key metrics for any agile team
 Estimation maturity and extra cost
 Get certified & IWSM Mensura
| Recap of today’s presentations