Webinar: Agile Estimation Using Functional Metrics Revisited

Transcription

1 Your logo here Webinar: Agile Estimation Using Functional Metrics Revisited September 23, :00 AM 12:30 PM 1 ITMPI005

2 Tom Cagley David Consulting Group Vice President & Director of Software Process Improvement, Software Measurement and IT Performance Improvement Consulting Practices ITMPI005

3 About Presenter s Firm At the David Consulting Group, we believe in the value of software measurement, estimation and process improvement. Our mantra is Measure. Improve. Deliver. Our approach is agile. We deliver value to our clients regularly and frequently, irrespective of the best practices we utilize. We believe in the Declaration of Interdependence. 3

4 Estimation v Planning v Budgeting Budgeting Defines how much we have to spend and influences scope Tends to ignore the cone of uncertainty Estimation Rough or approximate size extent or nature Focused by the cone of uncertainty Planning Definition of tasks and allocation of resources Focused on the narrow part of the cone of uncertainty

5 Basics: Inputs and Outputs Inputs Estimate Outputs Sized Requirements Effort Skills Cost People Equipment All data should be leveraged when planning Planning Outputs Schedules Resource Allocation

6 Basic Estimation Model What How With What Functional Size Function Points Use Case Points Story Points Tee Shirt Sizing Behavioral Attributes Process Disciplines Sourcing Model Skills Technical Complexity Security Languages Architecture Productivity and Duration Signatures

7 What Are Your Options Time Resources Functionality

8 Customer Satisfaction? Promptness Credibility Empathy Problem Solving Competence Reliability

9 So Why Doesn t This Stuff Always Work? Uncertainty Self Knowledge Consistency of Method

10 Uncertainty You start projects knowing very little (as compared to when a project is implemented) Unknowns Cone of Uncertainty Knowledge Budgeting Initiation Implementation Words are the only thing typically known before a project is initiated (usually not very many)

11 Johari Window Known to Self Not Known to Self Known to Others Open Blind Not Known to Others Hidden Unknown 11

12 Many Methods of Estimating Budgeting Sprint Planning Analogy Bottom Up Parametric Iteration Planning Estimating Sprint Planning

13 Planning Onion and Timing Budgeting Analogy Estimating Parametric - Light Mike Cohn s Planning Onion Planning Integration Planning Standup Meetings

14 A Proposed Solution Generate Initial Backlog Size Backlog Quick and Early Function Points Parametric Estimation Sprint Planning Owner Prioritization Business Need Cohesion (grouping) Iteration Planning Planning Poker Task / activity management 14

15 QEFP: The Logical View External Input External Output External Inquiry Other Applications External Input External Output Internal Logical File Internal Logical File Application Boundary External Interface File Other Applications

16 Revisiting Grade School English Sentence Diagramming Noun Verb Predicate Nominative Or Adjective In case you forgot - a predicate is an expression that can be true of something (the car is yellow)

17 Translation Function Point Diagramming ILF, EIF EI, EO, EQ DET, RET or FTR Data Transaction Identifier The goal is not diagram the whole requirement sentence but rather to to use the logic of the diagramming process to get to the measureable component.

18 Translation Tool: Trigger Words Nouns Verbs Data Functions ILF EIF Transactions Functions EI EO EQ Function Points

19 Sprint Planning In This Environment Product Owner Prioritizes Teams Sequence Apply Estimates Team Commits

20 Translating Size Into An Estimate Input: Sized Backlog Disaggregation and Resize Estimation Worksheet And / or Commitment Planning Poker (factor in attributes and technical )

21 Case One Large software development firm, hierarchical culture and one very large project and many smaller Mixed SCRUM/XP (recent addition) and Plan Based project environment Strenuous budgeting process with tax accruals Significant discovery was required to define, design and develop the large project Experienced based estimation based on bottom up task planning questionable on the large project!

22 The Answer Techniques Used QEFP for sizing backlog QEFP for sizing items added during sprint planning Planning Poker Impact Improved product owner satisfaction Increased perception of consistency Reduced number of stories escaping sprints

23 Case Two Large consumer product firm, hierarchical culture and many very large projects and many, many smaller Outsourced Plan Based project environment Strenuous budgeting process with tax accruals Difficult to determine whether they are getting value for their money Experienced based estimation based on bottom up task planning 23

24 Solution Inputs Consumed Outputs Core Estimates Requirements PROJECT Cost Project Price Internal Effort Vendor Effort Functionality Defects Duration Size Function Points Story Points Knowledge Gap) Duration 24

25 Questions? 25

26 Tom Cagley David Consulting Group Vice President & Director of Software Process Improvement, Software Measurement and IT Performance Improvement Consulting Practices