SlideShare uma empresa Scribd logo
1 de 31
Baixar para ler offline
ÉCOLE DE TECHNOLOGIE SUPÉRIEURE – MONTRÉAL - CANADA




          Improving Estimations in Agile Projects:
                   Issues and Avenues


                             Luigi Buglione & Alain Abran




                           4th Software Measurement European Forum
                                   9-11 May 2007, Rome, Italy
SMEF 2007 – Rome (Italy)               L.Buglione, A.Abran © 2007    1
     May 10, 2007
Agenda
         •     Introduction
         •     Agile Methodologies (AM)
                     A Musical Analogy
                     The Agile Manifesto
                     Agile and SLC phase coverage
                     Agile and SPI Methods
         •     Estimation Issues in an Agile Sw Development Project
                     XP – Extreme Programming
                     SCRUM
                     Crystal Family
                     FDD – Feature Driven Development
                     DSDM – Dynamic Systems Development Method
                     Other studies - proposals
         •     Discussion on Estimation practices in AM
                     NFR – Non-Functional Requirements
                     Sizing Units
                     Historical Data
                     Standards
         •     Conclusions

SMEF 2007 – Rome (Italy)                        L.Buglione, A.Abran © 2007   2
     May 10, 2007
Introduction
        (Sw) Project Management: Common Problems (Req’s)




      What the customer           What the project            How analysts                 What programmers         What consultant said
      asked for                   manager understood          projected it                 did                      it was needed




                   How the project was           What was effectively         What the customer          How maintenance                   What the customer
                   documented                    installed                    had to pay                 was run                           would have needed



SMEF 2007 – Rome (Italy)                                                L.Buglione, A.Abran © 2007                                                             3
     May 10, 2007
Introduction
        (Sw) Project Management: Common Problems (Staffing)
                                                  Staffing




SMEF 2007 – Rome (Italy)    L.Buglione, A.Abran © 2007        4
     May 10, 2007
Introduction
        Agility: Background

      • “Old” paradigms to be overcome during the ’90s
                  Shorter time-to-market
                  More compressed project schedules
                  Requirements more and more instable
                  Heavyweight vs lightweight (or agile) methods/approaches
                                                 agile
      • “Agile” Methods (AM) as the new paradigm for Sw
        Development
                  A more flexible answer to manage projects
                  Common characteristics and ways to express an iterative-
                  incremental SLC
                  Plenty of methods between mid ’90 and the start of Y2K,
                  grouped under the Agile Alliance umbrella
                           XP, SCRUM, FDD, DSDM, Crystal, ….



SMEF 2007 – Rome (Italy)                      L.Buglione, A.Abran © 2007     5
     May 10, 2007
Introduction
        Agility: Definition & Research Issue

      • Agility does not means “quicker”, “faster” but…




        Q:…but what about Estimation practices in Agile Methods?
SMEF 2007 – Rome (Italy)          L.Buglione, A.Abran © 2007       6
     May 10, 2007
Agenda
         •     Introduction
         •     Agile Methodologies (AM)
                     A Musical Analogy
                     The Agile Manifesto
                     Agile and SLC phase coverage
                     Agile and SPI Methods
         •     Estimation Issues in an Agile Sw Development Project
                     XP - ExtremeProgramming
                     SCRUM
                     Crystal Family
                     FDD – Feature Driven Development
                     DSDM – Dynamic Systems Development Method
                     Other studies - proposals
         •     Discussion on Estimation practices in AM
                     NFR – Non-Functional Requirements
                     Sizing Units
                     Historical Data
                     Standards
         •     Conclusions

SMEF 2007 – Rome (Italy)                        L.Buglione, A.Abran © 2007   7
     May 10, 2007
Agile Methodologies (AM)
        A Musical Analogy
                              Symphonic Orchestra                                   Jazz Group
                                      Heavyweight                                  Lightweight-Agile




              Project      • Each music session is a replay          • Each music session is a sort of “prototype”
                           of a “production series”

              Process      • Structured process in a rigid           • Dynamic and adaptive process (no music
                           manner (following the music               book)
                           partition ‘as is’ in the music book)

                Team       • Many people well synchronized           • Tight-knit team with few (and skillful)
                           with actions                              musicians


               Output      • Stable and predictable outcomes         • Improvised and variable, but staying with
                                                                     established beats


SMEF 2007 – Rome (Italy)                        L.Buglione, A.Abran © 2007                                           8
     May 10, 2007
Agile Methodologies (AM)
        The 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”




      Source: www.agilemanifesto.org

SMEF 2007 – Rome (Italy)                       L.Buglione, A.Abran © 2007              9
     May 10, 2007
May 10, 2007
SMEF 2007 – Rome (Italy)
                                                                                                              Agile and SLC Phases Coverage




            L.Buglione, A.Abran © 2007
                                                                                                                                          Agile Methodologies (AM)




                                         Source: Abrahamsson P., Salo O., Ronkainen J. & Warsta J., Agile Software
                                         Development Methods. Review and Analysis, VTT Publication # 478, 2002
                   10
Agile Methodologies (AM)
        Agile and SPI Methods
                                                                                                  Rating Compliance
             ML                              Sw-CMM KPA                                          XP              SCRUM
             2             RM - Requirements management                                          ☺                ☺
              2            SPP - Software project planning                                       ☺                ☺
              2            SPTO - Software project tracking and oversight                        ☺                ☺
              2            SSM - Software subcontract management
              2            SQA - Software quality assurance                                                       ☺
              2            SCM - Software configuration management
              3            OPF - Organization process focus
              3            OPD - Organization process definition
              3            TP - Training Program
              3            ISM - Integrated software management
              3            SPE - Software product engineering                                    ☺                ☺
              3            IC - Intergroup co-ordination                                         ☺                ☺
              3            PR - Peer reviews                                                     ☺
              4            QPM – Quantitative Project Management
              4            SQM – Software Quality Management
              5            DP – Defect Prevention
              5            TCM – Technology Change Management
              5            PCM – Process Change Management

          Legend:                                  Partially addressed;   ☺ Largely addressed;   Not addressed

SMEF 2007 – Rome (Italy)                                   L.Buglione, A.Abran © 2007                                    11
     May 10, 2007
Agenda
         •     Introduction
         •     Agile Methodologies (AM)
                     A Musical Analogy
                     The Agile Manifesto
                     Agile and SLC phase coverage
                     Agile and SPI Methods
         •     Estimation Issues in an Agile Sw Development Project
                     XP – Extreme Programming
                     SCRUM
                     Crystal Family
                     FDD – Feature Driven Development
                     DSDM – Dynamic Systems Development Method
                     Other studies - proposals
         •     Discussion on Estimation practices in AM
                     NFR – Non-Functional Requirements
                     Sizing Units
                     Historical Data
                     Standards
         •     Conclusions

SMEF 2007 – Rome (Italy)                        L.Buglione, A.Abran © 2007   12
     May 10, 2007
Estimation Issues in AM
        XP – eXtreme Programming

      • (Functional) Requirement = User Stories (US)
                                                 US
                  Non-technical Language
                  Focus only on the Functional Side of Requirements
                  US is not a Use Case (UC)
                                            US Title                           Implementation
                                                                                  Priority

        Funct.
         Test
                                                                                                    Relative
                                                                                                  Productivity
                                                                                                  /Estimation




                           (funct.)
                           H/L Req

                                                                    Source:   open.ncsu.edu/se/tutorials/coffee_maker/


SMEF 2007 – Rome (Italy)               L.Buglione, A.Abran © 2007                                                   13
     May 10, 2007
Estimation Issues in AM
        XP – eXtreme Programming
       • Relative Productivity / Estimation concepts:
                   Story Point   a (variable) no. of days needed to realize the US
                   Ideal Time   “the time without interruption where you can concentrate
                   on your work and feel fully productive”
                   Velocity   “to measure the project velocity you simply count up how
                   many user stories or how many programming tasks were finished during
                   the iteration. Total up the estimates that these stories or tasks receive”
                   Load Factor “The load factor equals actual calendar days to complete
                   a task divided by the developer's estimated "ideal" days to do it”
       • Planning Game
                                                           Summarizing…:
                                                           • XP estimates by experience/analogy,
                                                           estimating the effort needed mainly
                                                           based on the request of series of
                                                           functionalities


SMEF 2007 – Rome (Italy)                   L.Buglione, A.Abran © 2007                              14
     May 10, 2007
Estimation Issues in AM
        SCRUM
       • From ASD to APM
                   SCRUM is an Agile Project Management (APM) method
                                                         APM
                   SCRUM is a general-purpose APM, not only for software projects!
       • The Process




SMEF 2007 – Rome (Italy)                  L.Buglione, A.Abran © 2007                 15
     May 10, 2007
Estimation Issues in AM
        SCRUM
       • Planning / Monitoring / Estimation concepts:
            Backlog  two levels: product (project) & Sprint (30-days iteration)
                   Features    User Req’s to be allocated and worked
                   Micro-Planning    within each Sprint, a WBS with detailed task
                   Daily Meeting    the (daily) progress meeting for the project (risk mgmt)
                   Burndown chart     a graph “burning” the total hours of a Sprint
                   NB: no sizing measure!




SMEF 2007 – Rome (Italy)                   L.Buglione, A.Abran © 2007                          16
     May 10, 2007
Estimation Issues in AM
        SCRUM




         Summarizing…:
         • SCRUM estimates by experience/analogy, estimating directly the effort (in
         man-days or man-hours) for tracking both product and Sprints using the
         burndown chart that is, a graph showing how much time remains to
         complete the feature/tasks planned in such iteration, describing the project
         “velocity” the team is running.




SMEF 2007 – Rome (Italy)               L.Buglione, A.Abran © 2007                       17
     May 10, 2007
Estimation Issues in AM
        Crystal Family
       • Crystal is a family of ASD
                   Two criteria: Size of the Project & Criticality of the System
                       criteria




SMEF 2007 – Rome (Italy)                    L.Buglione, A.Abran © 2007             18
     May 10, 2007
Estimation Issues in AM
        Crystal Family
       • Planning / Monitoring / Estimation concepts:
                   Blitz Planning (technique #3)           the Crystal equivalent of XP User
                   Stories, called Blitz Planning Cards
                   Delphi Analysis (technique #4)       asd
                   Burn Charts (technique #9)           both burn-up (as in EVMS) and burn-
                   down (as in Scrum)
                   Ideal Days      estimated as in XP



           Summarizing…:
           • Crystal estimates by experience/analogy, estimating directly the effort (in
           ideal days to be refined into Estimated Elapsed Days) using Delphi analysis
           by some experts in the domain on the basis of counting content elements of
           such specific task (i.e. number of screens, business classes, …).
           •The project progress is tracked, as in Scrum, with “Burn” Charts

SMEF 2007 – Rome (Italy)                  L.Buglione, A.Abran © 2007                       19
     May 10, 2007
Estimation Issues in AM
        FDD – Feature Driven Development
       • From ASD to APM
                   Structured into a series of processes (current version: v1.3)
                                                                           v1.3
                   Process #2: Build the (functional-business) features list
                           #2
                   Process #3: Plan by Feature
                           #3

       • The Overall Process




SMEF 2007 – Rome (Italy)                   L.Buglione, A.Abran © 2007              20
     May 10, 2007
Estimation Issues in AM
        FDD – Feature Driven Development
       • Planning / Monitoring / Estimation concepts:
                   Feature    User Requirement
                   Feature Duration
                           no longer than 2 weeks each to be completed
                           If longer, to be split into more granular ones
                   Plan by Feature     Process #3: it includes completion dates for each
                   planned feature (month/year), properly assigned to team members



           Summarizing…:
           • FDD estimates by experience/analogy, estimating directly the effort (in
           man-days or man-hours) for tracking planned features




SMEF 2007 – Rome (Italy)                          L.Buglione, A.Abran © 2007           21
     May 10, 2007
Estimation Issues in AM
        DSDM – Dynamic Systems Development Method
       • SLC Characteristics
                   Three Main Stages (Pre-Project; Project; Post-Project)
                   Several Iterations within the project lifecycle
                   Prototype-based method
       • The Process




SMEF 2007 – Rome (Italy)                   L.Buglione, A.Abran © 2007       22
     May 10, 2007
Estimation Issues in AM
        DSDM – Dynamic Systems Development Method
       • Planning / Monitoring / Estimation concepts:
                   NFR   DSDM takes care also of Non-Functional Req’s
                   Four major (estimation) phases (Pre-Project, Planning at Project Start,
                   (re)Planning during the Project lifetime, Planning at the increment end)
                   Usage of Contingencies
                   Two estimation approaches:
                           Top-Down: based on business requirements, an early estimate is derived
                           from high-level requirements, from a very high-level view on the project (i.e.
                           estimation by analogy).
                           Bottom-up:        based on tangible systems, figuring out for low-level
                           components, take time to be prepared, need sufficiently detailed information,
                           provide a good basis for planning the project (i.e. Function Point Analysis,
                           Estimating from System Components, Collaborative Estimating).

           Summarizing…:
           • DSDM estimates by experience/analogy, estimating directly the effort (in
           man-days or man-hours) for tracking planned features but taking care of
           NFR and data gathering (“it is essential to collect metrics from projects so that
           they can be validated and refined for use in estimating future projects, i.e. to provide
           continuous improvement of the estimating process”)
SMEF 2007 – Rome (Italy)                         L.Buglione, A.Abran © 2007                             23
     May 10, 2007
Estimation Issues in AM
        Other Studies - Proposals
       • The Funnel of Increasing Accuracy (R.Thomsett)
                   “Radical” Project Management approach
                   WBS-based, through wide-band Delphi estimates and Sensitivity
                   Analysis (best, likely, worst cases)
                   Estimation “adjusted” according to quality’s requirements




                                                            Summarizing…:
                                                            • Radical PM estimates always by
                                                            experience/analogy,        estimating
                                                            directly the effort (in man-days or
                                                            man-hours)      but takes care of
                                                            quality requirements as further filter
                                                            towards the final estimated value


SMEF 2007 – Rome (Italy)                   L.Buglione, A.Abran © 2007                                24
     May 10, 2007
Agenda
         •     Introduction
         •     Agile Methodologies (AM)
                     A Musical Analogy
                     The Agile Manifesto
                     Agile and SLC phase coverage
                     Agile and SPI Methods
         •     Estimation Issues in an Agile Sw Development Project
                     XP – Extreme Programming
                     SCRUM
                     Crystal Family
                     FDD – Feature Driven Development
                     DSDM – Dynamic Systems Development Method
                     Other studies - proposals
         •     Discussion on Estimation practices in AM
                     NFR – Non-Functional Requirements
                     Sizing Units
                     Historical Data
                     Standards
         •     Conclusions

SMEF 2007 – Rome (Italy)                        L.Buglione, A.Abran © 2007   25
     May 10, 2007
Discussion Estimation Practices in AM
        Main (missing) points identified

            NFR: Non-Functional Requirements
                   the focus of AM on evaluating features, user stories, or more general
                   high-level user requirements mainly from a functional viewpoint does
                   not include the non-functional perspective of the projects.
                   explicitly, only few methods such as DSDM propose in their practices
                   to consider them for estimation and planning purposes.
            Sizing Units
                   general AM approach to estimation experienced-based, mainly founded
                   on functional analysis and not supported by historical data.
                   effort and schedule are the time-related expressions corresponding to
                   “how much” work will be performed; they do not mention the functional
                   requirements measurement with a recognized quantitative measurement
                   method. In this AM approach to estimation, size is only considered as
                   “implicit” in the estimators’ minds.
                   Story Points and Velocity concepts represent a “delivery rate” based only
                   on the experience and knowledge of such particular team, applicable
                   with success in small and stable teams. But it is much more challenging
                   in larger organizations where the composition of a project team is not
                   necessarily as stable over time.

SMEF 2007 – Rome (Italy)                   L.Buglione, A.Abran © 2007                          26
     May 10, 2007
Discussion Estimation Practices in AM
        Main (missing) points emerged

            Historical Data
                   the practice to collect data from projects is not required by most
                   AM (except for DSDM).

            Standards
               each methodology and each team applying a certain AM uses its
               own definitions;
               adequate measurements require to be based on standards and
               require inputs with a validated, quality level.




SMEF 2007 – Rome (Italy)                 L.Buglione, A.Abran © 2007                     27
     May 10, 2007
Agenda
         •     Introduction
         •     Agile Methodologies (AM)
                     A Musical Analogy
                     The Agile Manifesto
                     Agile and SLC phase coverage
                     Agile and SPI Methods
         •     Estimation Issues in an Agile Sw Development Project
                     XP – Extreme Programming
                     SCRUM
                     Crystal Family
                     FDD – Feature Driven Development
                     DSDM – Dynamic Systems Development Method
                     Other studies - proposals
         •     Discussion on Estimation practices in AM
                     NFR – Non-Functional Requirements
                     Sizing Units
                     Historical Data
                     Standards
         •     Conclusions

SMEF 2007 – Rome (Italy)                        L.Buglione, A.Abran © 2007   28
     May 10, 2007
Conclusions

      • Agile Methods (AM) represent interesting solutions for projects with
                          AM
        unstable requirements, iterative SLC, short-term milestones and small
        teams.
      • Only in the last five years, attention was shifted from ASD to APM
        (Agile Project Management). Through this interest, planning and
        scheduling practices have been tailored to agile methodologies, but
        with much less attention to the estimation process.
      • AM still being a young approach to software development, much work
        remains to be done to improve the way AM manage estimates,
        including tailoring relevant practices from well-established and proven
        “heavyweight” methodologies.
      • Next steps will include analyses of the impact on size, effort and
        productivity of non-functional requirements in agile projects to
        improve estimates right from the Requirement Elicitation phase using,
        for example, a new User Story structure called US2 (2nd generation of
        User Stories).
                                   Coby’s Observation:
                Math is a fact, but problem data quite often are not “facts”
SMEF 2007 – Rome (Italy)              L.Buglione, A.Abran © 2007                  29
     May 10, 2007
Q&A




SMEF 2007 – Rome (Italy)   L.Buglione, A.Abran © 2007   30
     May 10, 2007
Grazie! Thank you!




                           luigi.buglione@computer.org, alain.abran@etsmtl.ca


SMEF 2007 – Rome (Italy)                   L.Buglione, A.Abran © 2007           31
     May 10, 2007

Mais conteúdo relacionado

Semelhante a Improving Estimations in Agile Projects: Issues and Avenues

Agile Overview As V1.2
Agile Overview As V1.2Agile Overview As V1.2
Agile Overview As V1.2Anjan Roy
 
The Role of a BA on a Scrum Team IIBA Presentation 2010
The Role of a BA on a Scrum Team IIBA Presentation 2010The Role of a BA on a Scrum Team IIBA Presentation 2010
The Role of a BA on a Scrum Team IIBA Presentation 2010scrummasternz
 
Planificación del proyecto estimación
Planificación del proyecto   estimaciónPlanificación del proyecto   estimación
Planificación del proyecto estimaciónProColombia
 
The Business Analysts Role in Agile Software Development
The Business Analysts Role in Agile Software DevelopmentThe Business Analysts Role in Agile Software Development
The Business Analysts Role in Agile Software Developmentallan kelly
 
The BA role in Agile software development
The BA role in Agile software developmentThe BA role in Agile software development
The BA role in Agile software developmentallan kelly
 
Is Project Management Discipline Relevant in an Agile World?
Is Project Management Discipline Relevant in an Agile World?Is Project Management Discipline Relevant in an Agile World?
Is Project Management Discipline Relevant in an Agile World?Steve Nunziata
 
Geyer.m.sasaki.c
Geyer.m.sasaki.cGeyer.m.sasaki.c
Geyer.m.sasaki.cNASAPMC
 
PMICOS Webinar: Building a Sound Schedule in an Enterprise Environment
PMICOS Webinar: Building a Sound Schedule in an Enterprise EnvironmentPMICOS Webinar: Building a Sound Schedule in an Enterprise Environment
PMICOS Webinar: Building a Sound Schedule in an Enterprise EnvironmentAcumen
 
Key Considerations for a Successful Hyperion Planning Implementation
Key Considerations for a Successful Hyperion Planning ImplementationKey Considerations for a Successful Hyperion Planning Implementation
Key Considerations for a Successful Hyperion Planning ImplementationAlithya
 
Administering a substantial fpc program in a large organisation
Administering a substantial fpc program in a large organisationAdministering a substantial fpc program in a large organisation
Administering a substantial fpc program in a large organisationGraeme Prescott
 
GT Agile-UX - présentation Agile
GT Agile-UX - présentation AgileGT Agile-UX - présentation Agile
GT Agile-UX - présentation AgileFlupa
 
PMI-ACP Lesson 01 Nugget 2 Agile Methodologies-ii
PMI-ACP Lesson 01 Nugget 2 Agile Methodologies-iiPMI-ACP Lesson 01 Nugget 2 Agile Methodologies-ii
PMI-ACP Lesson 01 Nugget 2 Agile Methodologies-iiThanh Nguyen
 
Ppwithagileyannhamonqconbeijing 090423081417-phpapp02
Ppwithagileyannhamonqconbeijing 090423081417-phpapp02Ppwithagileyannhamonqconbeijing 090423081417-phpapp02
Ppwithagileyannhamonqconbeijing 090423081417-phpapp02youzitang
 
Dnv Improving Your Process Performances With Agile
Dnv   Improving Your Process Performances With AgileDnv   Improving Your Process Performances With Agile
Dnv Improving Your Process Performances With AgileGeorge Ang
 
Evolution of Agile Testing
Evolution of Agile TestingEvolution of Agile Testing
Evolution of Agile TestingOdd-e
 
Agile Mëtteg series - Session 4
 Agile Mëtteg series - Session 4 Agile Mëtteg series - Session 4
Agile Mëtteg series - Session 4Agile Partner S.A.
 

Semelhante a Improving Estimations in Agile Projects: Issues and Avenues (20)

Agile Overview As V1.2
Agile Overview As V1.2Agile Overview As V1.2
Agile Overview As V1.2
 
The Role of a BA on a Scrum Team IIBA Presentation 2010
The Role of a BA on a Scrum Team IIBA Presentation 2010The Role of a BA on a Scrum Team IIBA Presentation 2010
The Role of a BA on a Scrum Team IIBA Presentation 2010
 
Planificación del proyecto estimación
Planificación del proyecto   estimaciónPlanificación del proyecto   estimación
Planificación del proyecto estimación
 
The Business Analysts Role in Agile Software Development
The Business Analysts Role in Agile Software DevelopmentThe Business Analysts Role in Agile Software Development
The Business Analysts Role in Agile Software Development
 
The BA role in Agile software development
The BA role in Agile software developmentThe BA role in Agile software development
The BA role in Agile software development
 
Is Project Management Discipline Relevant in an Agile World?
Is Project Management Discipline Relevant in an Agile World?Is Project Management Discipline Relevant in an Agile World?
Is Project Management Discipline Relevant in an Agile World?
 
Introduction to Lean, Agile, Scrum, & XP
Introduction to Lean, Agile, Scrum, & XPIntroduction to Lean, Agile, Scrum, & XP
Introduction to Lean, Agile, Scrum, & XP
 
Geyer.m.sasaki.c
Geyer.m.sasaki.cGeyer.m.sasaki.c
Geyer.m.sasaki.c
 
PMICOS Webinar: Building a Sound Schedule in an Enterprise Environment
PMICOS Webinar: Building a Sound Schedule in an Enterprise EnvironmentPMICOS Webinar: Building a Sound Schedule in an Enterprise Environment
PMICOS Webinar: Building a Sound Schedule in an Enterprise Environment
 
Key Considerations for a Successful Hyperion Planning Implementation
Key Considerations for a Successful Hyperion Planning ImplementationKey Considerations for a Successful Hyperion Planning Implementation
Key Considerations for a Successful Hyperion Planning Implementation
 
Administering a substantial fpc program in a large organisation
Administering a substantial fpc program in a large organisationAdministering a substantial fpc program in a large organisation
Administering a substantial fpc program in a large organisation
 
2011 lean kanban-scrum
2011 lean kanban-scrum2011 lean kanban-scrum
2011 lean kanban-scrum
 
GT Agile-UX - présentation Agile
GT Agile-UX - présentation AgileGT Agile-UX - présentation Agile
GT Agile-UX - présentation Agile
 
PMI-ACP Lesson 01 Nugget 2 Agile Methodologies-ii
PMI-ACP Lesson 01 Nugget 2 Agile Methodologies-iiPMI-ACP Lesson 01 Nugget 2 Agile Methodologies-ii
PMI-ACP Lesson 01 Nugget 2 Agile Methodologies-ii
 
Ppwithagileyannhamonqconbeijing 090423081417-phpapp02
Ppwithagileyannhamonqconbeijing 090423081417-phpapp02Ppwithagileyannhamonqconbeijing 090423081417-phpapp02
Ppwithagileyannhamonqconbeijing 090423081417-phpapp02
 
Dnv Improving Your Process Performances With Agile
Dnv   Improving Your Process Performances With AgileDnv   Improving Your Process Performances With Agile
Dnv Improving Your Process Performances With Agile
 
Evolution of Agile Testing
Evolution of Agile TestingEvolution of Agile Testing
Evolution of Agile Testing
 
Andriy bahlay
Andriy bahlay   Andriy bahlay
Andriy bahlay
 
SDLC Smashup
SDLC SmashupSDLC Smashup
SDLC Smashup
 
Agile Mëtteg series - Session 4
 Agile Mëtteg series - Session 4 Agile Mëtteg series - Session 4
Agile Mëtteg series - Session 4
 

Mais de Luigi Buglione

DevOps & ITIL: Friends or Foes?
DevOps & ITIL: Friends or Foes?DevOps & ITIL: Friends or Foes?
DevOps & ITIL: Friends or Foes?Luigi Buglione
 
The missing links in software estimation: Work, Team Loading and Team Power
The missing links in software estimation: Work, Team Loading and Team PowerThe missing links in software estimation: Work, Team Loading and Team Power
The missing links in software estimation: Work, Team Loading and Team PowerLuigi Buglione
 
Risk Management: Achieving Higher Maturity & Capability Levels through the LE...
Risk Management: Achieving Higher Maturity & Capability Levels through the LE...Risk Management: Achieving Higher Maturity & Capability Levels through the LE...
Risk Management: Achieving Higher Maturity & Capability Levels through the LE...Luigi Buglione
 
L4A - Lean for (being) Agile - Some thoughts and tips for a progressive path ...
L4A - Lean for (being) Agile - Some thoughts and tips for a progressive path ...L4A - Lean for (being) Agile - Some thoughts and tips for a progressive path ...
L4A - Lean for (being) Agile - Some thoughts and tips for a progressive path ...Luigi Buglione
 
From Software to Service Sustainability: a still Broader Perspective
From Software to Service Sustainability: a still Broader PerspectiveFrom Software to Service Sustainability: a still Broader Perspective
From Software to Service Sustainability: a still Broader PerspectiveLuigi Buglione
 
The Significance of IFPUG Base Functionality Types in Effort Estimation - An ...
The Significance of IFPUG Base Functionality Types in Effort Estimation - An ...The Significance of IFPUG Base Functionality Types in Effort Estimation - An ...
The Significance of IFPUG Base Functionality Types in Effort Estimation - An ...Luigi Buglione
 
Software or Service? That’s the question!
Software or Service? That’s the question!Software or Service? That’s the question!
Software or Service? That’s the question!Luigi Buglione
 
A Murphological View on Software Measurement: a serious joke or a funny seri...
A Murphological View on Software Measurement:  a serious joke or a funny seri...A Murphological View on Software Measurement:  a serious joke or a funny seri...
A Murphological View on Software Measurement: a serious joke or a funny seri...Luigi Buglione
 
Do we really re-use our knowledge (or not)?
Do we really re-use our knowledge (or not)?Do we really re-use our knowledge (or not)?
Do we really re-use our knowledge (or not)?Luigi Buglione
 
Balanced Measurement Sets: Criteria for Improving Project Management Practices
Balanced Measurement Sets: Criteria for Improving  Project Management PracticesBalanced Measurement Sets: Criteria for Improving  Project Management Practices
Balanced Measurement Sets: Criteria for Improving Project Management PracticesLuigi Buglione
 
PIF or SNAP? That's the Question! Or maybe it's not? - A panel
PIF or SNAP? That's the Question! Or maybe it's not? - A panelPIF or SNAP? That's the Question! Or maybe it's not? - A panel
PIF or SNAP? That's the Question! Or maybe it's not? - A panelLuigi Buglione
 
Software Sustainability: a Broader Perspective
Software Sustainability: a Broader PerspectiveSoftware Sustainability: a Broader Perspective
Software Sustainability: a Broader PerspectiveLuigi Buglione
 
An ISO/IEC 33000-compliant Measurement Framework for Software Process Sustain...
An ISO/IEC 33000-compliant Measurement Framework for Software Process Sustain...An ISO/IEC 33000-compliant Measurement Framework for Software Process Sustain...
An ISO/IEC 33000-compliant Measurement Framework for Software Process Sustain...Luigi Buglione
 
Measurement Process: Improving the ISO 15939 Standard
Measurement Process: Improving the ISO 15939 StandardMeasurement Process: Improving the ISO 15939 Standard
Measurement Process: Improving the ISO 15939 StandardLuigi Buglione
 
Sizing The Entire Development Process
Sizing The Entire Development ProcessSizing The Entire Development Process
Sizing The Entire Development ProcessLuigi Buglione
 
The LEGO Strategy: Guidelines for a Profitable Deployment
The LEGO Strategy: Guidelines for a Profitable DeploymentThe LEGO Strategy: Guidelines for a Profitable Deployment
The LEGO Strategy: Guidelines for a Profitable DeploymentLuigi Buglione
 
ICEBERG: a different look at Software Project Management
ICEBERG: a different look at Software Project ManagementICEBERG: a different look at Software Project Management
ICEBERG: a different look at Software Project ManagementLuigi Buglione
 
Improving Measurement Plans from multiple dimensions: Exercising with Balanci...
Improving Measurement Plans from multiple dimensions: Exercising with Balanci...Improving Measurement Plans from multiple dimensions: Exercising with Balanci...
Improving Measurement Plans from multiple dimensions: Exercising with Balanci...Luigi Buglione
 
Improving the User Story Agile Technique Using the INVEST Criteria
Improving the User Story Agile Technique Using the  INVEST CriteriaImproving the User Story Agile Technique Using the  INVEST Criteria
Improving the User Story Agile Technique Using the INVEST CriteriaLuigi Buglione
 
Leveraging Reuse-related Maturity Issues for Achieving Higher Maturity & Capa...
Leveraging Reuse-related Maturity Issues for Achieving Higher Maturity & Capa...Leveraging Reuse-related Maturity Issues for Achieving Higher Maturity & Capa...
Leveraging Reuse-related Maturity Issues for Achieving Higher Maturity & Capa...Luigi Buglione
 

Mais de Luigi Buglione (20)

DevOps & ITIL: Friends or Foes?
DevOps & ITIL: Friends or Foes?DevOps & ITIL: Friends or Foes?
DevOps & ITIL: Friends or Foes?
 
The missing links in software estimation: Work, Team Loading and Team Power
The missing links in software estimation: Work, Team Loading and Team PowerThe missing links in software estimation: Work, Team Loading and Team Power
The missing links in software estimation: Work, Team Loading and Team Power
 
Risk Management: Achieving Higher Maturity & Capability Levels through the LE...
Risk Management: Achieving Higher Maturity & Capability Levels through the LE...Risk Management: Achieving Higher Maturity & Capability Levels through the LE...
Risk Management: Achieving Higher Maturity & Capability Levels through the LE...
 
L4A - Lean for (being) Agile - Some thoughts and tips for a progressive path ...
L4A - Lean for (being) Agile - Some thoughts and tips for a progressive path ...L4A - Lean for (being) Agile - Some thoughts and tips for a progressive path ...
L4A - Lean for (being) Agile - Some thoughts and tips for a progressive path ...
 
From Software to Service Sustainability: a still Broader Perspective
From Software to Service Sustainability: a still Broader PerspectiveFrom Software to Service Sustainability: a still Broader Perspective
From Software to Service Sustainability: a still Broader Perspective
 
The Significance of IFPUG Base Functionality Types in Effort Estimation - An ...
The Significance of IFPUG Base Functionality Types in Effort Estimation - An ...The Significance of IFPUG Base Functionality Types in Effort Estimation - An ...
The Significance of IFPUG Base Functionality Types in Effort Estimation - An ...
 
Software or Service? That’s the question!
Software or Service? That’s the question!Software or Service? That’s the question!
Software or Service? That’s the question!
 
A Murphological View on Software Measurement: a serious joke or a funny seri...
A Murphological View on Software Measurement:  a serious joke or a funny seri...A Murphological View on Software Measurement:  a serious joke or a funny seri...
A Murphological View on Software Measurement: a serious joke or a funny seri...
 
Do we really re-use our knowledge (or not)?
Do we really re-use our knowledge (or not)?Do we really re-use our knowledge (or not)?
Do we really re-use our knowledge (or not)?
 
Balanced Measurement Sets: Criteria for Improving Project Management Practices
Balanced Measurement Sets: Criteria for Improving  Project Management PracticesBalanced Measurement Sets: Criteria for Improving  Project Management Practices
Balanced Measurement Sets: Criteria for Improving Project Management Practices
 
PIF or SNAP? That's the Question! Or maybe it's not? - A panel
PIF or SNAP? That's the Question! Or maybe it's not? - A panelPIF or SNAP? That's the Question! Or maybe it's not? - A panel
PIF or SNAP? That's the Question! Or maybe it's not? - A panel
 
Software Sustainability: a Broader Perspective
Software Sustainability: a Broader PerspectiveSoftware Sustainability: a Broader Perspective
Software Sustainability: a Broader Perspective
 
An ISO/IEC 33000-compliant Measurement Framework for Software Process Sustain...
An ISO/IEC 33000-compliant Measurement Framework for Software Process Sustain...An ISO/IEC 33000-compliant Measurement Framework for Software Process Sustain...
An ISO/IEC 33000-compliant Measurement Framework for Software Process Sustain...
 
Measurement Process: Improving the ISO 15939 Standard
Measurement Process: Improving the ISO 15939 StandardMeasurement Process: Improving the ISO 15939 Standard
Measurement Process: Improving the ISO 15939 Standard
 
Sizing The Entire Development Process
Sizing The Entire Development ProcessSizing The Entire Development Process
Sizing The Entire Development Process
 
The LEGO Strategy: Guidelines for a Profitable Deployment
The LEGO Strategy: Guidelines for a Profitable DeploymentThe LEGO Strategy: Guidelines for a Profitable Deployment
The LEGO Strategy: Guidelines for a Profitable Deployment
 
ICEBERG: a different look at Software Project Management
ICEBERG: a different look at Software Project ManagementICEBERG: a different look at Software Project Management
ICEBERG: a different look at Software Project Management
 
Improving Measurement Plans from multiple dimensions: Exercising with Balanci...
Improving Measurement Plans from multiple dimensions: Exercising with Balanci...Improving Measurement Plans from multiple dimensions: Exercising with Balanci...
Improving Measurement Plans from multiple dimensions: Exercising with Balanci...
 
Improving the User Story Agile Technique Using the INVEST Criteria
Improving the User Story Agile Technique Using the  INVEST CriteriaImproving the User Story Agile Technique Using the  INVEST Criteria
Improving the User Story Agile Technique Using the INVEST Criteria
 
Leveraging Reuse-related Maturity Issues for Achieving Higher Maturity & Capa...
Leveraging Reuse-related Maturity Issues for Achieving Higher Maturity & Capa...Leveraging Reuse-related Maturity Issues for Achieving Higher Maturity & Capa...
Leveraging Reuse-related Maturity Issues for Achieving Higher Maturity & Capa...
 

Improving Estimations in Agile Projects: Issues and Avenues

  • 1. ÉCOLE DE TECHNOLOGIE SUPÉRIEURE – MONTRÉAL - CANADA Improving Estimations in Agile Projects: Issues and Avenues Luigi Buglione & Alain Abran 4th Software Measurement European Forum 9-11 May 2007, Rome, Italy SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 1 May 10, 2007
  • 2. Agenda • Introduction • Agile Methodologies (AM) A Musical Analogy The Agile Manifesto Agile and SLC phase coverage Agile and SPI Methods • Estimation Issues in an Agile Sw Development Project XP – Extreme Programming SCRUM Crystal Family FDD – Feature Driven Development DSDM – Dynamic Systems Development Method Other studies - proposals • Discussion on Estimation practices in AM NFR – Non-Functional Requirements Sizing Units Historical Data Standards • Conclusions SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 2 May 10, 2007
  • 3. Introduction (Sw) Project Management: Common Problems (Req’s) What the customer What the project How analysts What programmers What consultant said asked for manager understood projected it did it was needed How the project was What was effectively What the customer How maintenance What the customer documented installed had to pay was run would have needed SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 3 May 10, 2007
  • 4. Introduction (Sw) Project Management: Common Problems (Staffing) Staffing SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 4 May 10, 2007
  • 5. Introduction Agility: Background • “Old” paradigms to be overcome during the ’90s Shorter time-to-market More compressed project schedules Requirements more and more instable Heavyweight vs lightweight (or agile) methods/approaches agile • “Agile” Methods (AM) as the new paradigm for Sw Development A more flexible answer to manage projects Common characteristics and ways to express an iterative- incremental SLC Plenty of methods between mid ’90 and the start of Y2K, grouped under the Agile Alliance umbrella XP, SCRUM, FDD, DSDM, Crystal, …. SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 5 May 10, 2007
  • 6. Introduction Agility: Definition & Research Issue • Agility does not means “quicker”, “faster” but… Q:…but what about Estimation practices in Agile Methods? SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 6 May 10, 2007
  • 7. Agenda • Introduction • Agile Methodologies (AM) A Musical Analogy The Agile Manifesto Agile and SLC phase coverage Agile and SPI Methods • Estimation Issues in an Agile Sw Development Project XP - ExtremeProgramming SCRUM Crystal Family FDD – Feature Driven Development DSDM – Dynamic Systems Development Method Other studies - proposals • Discussion on Estimation practices in AM NFR – Non-Functional Requirements Sizing Units Historical Data Standards • Conclusions SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 7 May 10, 2007
  • 8. Agile Methodologies (AM) A Musical Analogy Symphonic Orchestra Jazz Group Heavyweight Lightweight-Agile Project • Each music session is a replay • Each music session is a sort of “prototype” of a “production series” Process • Structured process in a rigid • Dynamic and adaptive process (no music manner (following the music book) partition ‘as is’ in the music book) Team • Many people well synchronized • Tight-knit team with few (and skillful) with actions musicians Output • Stable and predictable outcomes • Improvised and variable, but staying with established beats SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 8 May 10, 2007
  • 9. Agile Methodologies (AM) The 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” Source: www.agilemanifesto.org SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 9 May 10, 2007
  • 10. May 10, 2007 SMEF 2007 – Rome (Italy) Agile and SLC Phases Coverage L.Buglione, A.Abran © 2007 Agile Methodologies (AM) Source: Abrahamsson P., Salo O., Ronkainen J. & Warsta J., Agile Software Development Methods. Review and Analysis, VTT Publication # 478, 2002 10
  • 11. Agile Methodologies (AM) Agile and SPI Methods Rating Compliance ML Sw-CMM KPA XP SCRUM 2 RM - Requirements management ☺ ☺ 2 SPP - Software project planning ☺ ☺ 2 SPTO - Software project tracking and oversight ☺ ☺ 2 SSM - Software subcontract management 2 SQA - Software quality assurance ☺ 2 SCM - Software configuration management 3 OPF - Organization process focus 3 OPD - Organization process definition 3 TP - Training Program 3 ISM - Integrated software management 3 SPE - Software product engineering ☺ ☺ 3 IC - Intergroup co-ordination ☺ ☺ 3 PR - Peer reviews ☺ 4 QPM – Quantitative Project Management 4 SQM – Software Quality Management 5 DP – Defect Prevention 5 TCM – Technology Change Management 5 PCM – Process Change Management Legend: Partially addressed; ☺ Largely addressed; Not addressed SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 11 May 10, 2007
  • 12. Agenda • Introduction • Agile Methodologies (AM) A Musical Analogy The Agile Manifesto Agile and SLC phase coverage Agile and SPI Methods • Estimation Issues in an Agile Sw Development Project XP – Extreme Programming SCRUM Crystal Family FDD – Feature Driven Development DSDM – Dynamic Systems Development Method Other studies - proposals • Discussion on Estimation practices in AM NFR – Non-Functional Requirements Sizing Units Historical Data Standards • Conclusions SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 12 May 10, 2007
  • 13. Estimation Issues in AM XP – eXtreme Programming • (Functional) Requirement = User Stories (US) US Non-technical Language Focus only on the Functional Side of Requirements US is not a Use Case (UC) US Title Implementation Priority Funct. Test Relative Productivity /Estimation (funct.) H/L Req Source: open.ncsu.edu/se/tutorials/coffee_maker/ SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 13 May 10, 2007
  • 14. Estimation Issues in AM XP – eXtreme Programming • Relative Productivity / Estimation concepts: Story Point a (variable) no. of days needed to realize the US Ideal Time “the time without interruption where you can concentrate on your work and feel fully productive” Velocity “to measure the project velocity you simply count up how many user stories or how many programming tasks were finished during the iteration. Total up the estimates that these stories or tasks receive” Load Factor “The load factor equals actual calendar days to complete a task divided by the developer's estimated "ideal" days to do it” • Planning Game Summarizing…: • XP estimates by experience/analogy, estimating the effort needed mainly based on the request of series of functionalities SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 14 May 10, 2007
  • 15. Estimation Issues in AM SCRUM • From ASD to APM SCRUM is an Agile Project Management (APM) method APM SCRUM is a general-purpose APM, not only for software projects! • The Process SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 15 May 10, 2007
  • 16. Estimation Issues in AM SCRUM • Planning / Monitoring / Estimation concepts: Backlog two levels: product (project) & Sprint (30-days iteration) Features User Req’s to be allocated and worked Micro-Planning within each Sprint, a WBS with detailed task Daily Meeting the (daily) progress meeting for the project (risk mgmt) Burndown chart a graph “burning” the total hours of a Sprint NB: no sizing measure! SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 16 May 10, 2007
  • 17. Estimation Issues in AM SCRUM Summarizing…: • SCRUM estimates by experience/analogy, estimating directly the effort (in man-days or man-hours) for tracking both product and Sprints using the burndown chart that is, a graph showing how much time remains to complete the feature/tasks planned in such iteration, describing the project “velocity” the team is running. SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 17 May 10, 2007
  • 18. Estimation Issues in AM Crystal Family • Crystal is a family of ASD Two criteria: Size of the Project & Criticality of the System criteria SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 18 May 10, 2007
  • 19. Estimation Issues in AM Crystal Family • Planning / Monitoring / Estimation concepts: Blitz Planning (technique #3) the Crystal equivalent of XP User Stories, called Blitz Planning Cards Delphi Analysis (technique #4) asd Burn Charts (technique #9) both burn-up (as in EVMS) and burn- down (as in Scrum) Ideal Days estimated as in XP Summarizing…: • Crystal estimates by experience/analogy, estimating directly the effort (in ideal days to be refined into Estimated Elapsed Days) using Delphi analysis by some experts in the domain on the basis of counting content elements of such specific task (i.e. number of screens, business classes, …). •The project progress is tracked, as in Scrum, with “Burn” Charts SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 19 May 10, 2007
  • 20. Estimation Issues in AM FDD – Feature Driven Development • From ASD to APM Structured into a series of processes (current version: v1.3) v1.3 Process #2: Build the (functional-business) features list #2 Process #3: Plan by Feature #3 • The Overall Process SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 20 May 10, 2007
  • 21. Estimation Issues in AM FDD – Feature Driven Development • Planning / Monitoring / Estimation concepts: Feature User Requirement Feature Duration no longer than 2 weeks each to be completed If longer, to be split into more granular ones Plan by Feature Process #3: it includes completion dates for each planned feature (month/year), properly assigned to team members Summarizing…: • FDD estimates by experience/analogy, estimating directly the effort (in man-days or man-hours) for tracking planned features SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 21 May 10, 2007
  • 22. Estimation Issues in AM DSDM – Dynamic Systems Development Method • SLC Characteristics Three Main Stages (Pre-Project; Project; Post-Project) Several Iterations within the project lifecycle Prototype-based method • The Process SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 22 May 10, 2007
  • 23. Estimation Issues in AM DSDM – Dynamic Systems Development Method • Planning / Monitoring / Estimation concepts: NFR DSDM takes care also of Non-Functional Req’s Four major (estimation) phases (Pre-Project, Planning at Project Start, (re)Planning during the Project lifetime, Planning at the increment end) Usage of Contingencies Two estimation approaches: Top-Down: based on business requirements, an early estimate is derived from high-level requirements, from a very high-level view on the project (i.e. estimation by analogy). Bottom-up: based on tangible systems, figuring out for low-level components, take time to be prepared, need sufficiently detailed information, provide a good basis for planning the project (i.e. Function Point Analysis, Estimating from System Components, Collaborative Estimating). Summarizing…: • DSDM estimates by experience/analogy, estimating directly the effort (in man-days or man-hours) for tracking planned features but taking care of NFR and data gathering (“it is essential to collect metrics from projects so that they can be validated and refined for use in estimating future projects, i.e. to provide continuous improvement of the estimating process”) SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 23 May 10, 2007
  • 24. Estimation Issues in AM Other Studies - Proposals • The Funnel of Increasing Accuracy (R.Thomsett) “Radical” Project Management approach WBS-based, through wide-band Delphi estimates and Sensitivity Analysis (best, likely, worst cases) Estimation “adjusted” according to quality’s requirements Summarizing…: • Radical PM estimates always by experience/analogy, estimating directly the effort (in man-days or man-hours) but takes care of quality requirements as further filter towards the final estimated value SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 24 May 10, 2007
  • 25. Agenda • Introduction • Agile Methodologies (AM) A Musical Analogy The Agile Manifesto Agile and SLC phase coverage Agile and SPI Methods • Estimation Issues in an Agile Sw Development Project XP – Extreme Programming SCRUM Crystal Family FDD – Feature Driven Development DSDM – Dynamic Systems Development Method Other studies - proposals • Discussion on Estimation practices in AM NFR – Non-Functional Requirements Sizing Units Historical Data Standards • Conclusions SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 25 May 10, 2007
  • 26. Discussion Estimation Practices in AM Main (missing) points identified NFR: Non-Functional Requirements the focus of AM on evaluating features, user stories, or more general high-level user requirements mainly from a functional viewpoint does not include the non-functional perspective of the projects. explicitly, only few methods such as DSDM propose in their practices to consider them for estimation and planning purposes. Sizing Units general AM approach to estimation experienced-based, mainly founded on functional analysis and not supported by historical data. effort and schedule are the time-related expressions corresponding to “how much” work will be performed; they do not mention the functional requirements measurement with a recognized quantitative measurement method. In this AM approach to estimation, size is only considered as “implicit” in the estimators’ minds. Story Points and Velocity concepts represent a “delivery rate” based only on the experience and knowledge of such particular team, applicable with success in small and stable teams. But it is much more challenging in larger organizations where the composition of a project team is not necessarily as stable over time. SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 26 May 10, 2007
  • 27. Discussion Estimation Practices in AM Main (missing) points emerged Historical Data the practice to collect data from projects is not required by most AM (except for DSDM). Standards each methodology and each team applying a certain AM uses its own definitions; adequate measurements require to be based on standards and require inputs with a validated, quality level. SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 27 May 10, 2007
  • 28. Agenda • Introduction • Agile Methodologies (AM) A Musical Analogy The Agile Manifesto Agile and SLC phase coverage Agile and SPI Methods • Estimation Issues in an Agile Sw Development Project XP – Extreme Programming SCRUM Crystal Family FDD – Feature Driven Development DSDM – Dynamic Systems Development Method Other studies - proposals • Discussion on Estimation practices in AM NFR – Non-Functional Requirements Sizing Units Historical Data Standards • Conclusions SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 28 May 10, 2007
  • 29. Conclusions • Agile Methods (AM) represent interesting solutions for projects with AM unstable requirements, iterative SLC, short-term milestones and small teams. • Only in the last five years, attention was shifted from ASD to APM (Agile Project Management). Through this interest, planning and scheduling practices have been tailored to agile methodologies, but with much less attention to the estimation process. • AM still being a young approach to software development, much work remains to be done to improve the way AM manage estimates, including tailoring relevant practices from well-established and proven “heavyweight” methodologies. • Next steps will include analyses of the impact on size, effort and productivity of non-functional requirements in agile projects to improve estimates right from the Requirement Elicitation phase using, for example, a new User Story structure called US2 (2nd generation of User Stories). Coby’s Observation: Math is a fact, but problem data quite often are not “facts” SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 29 May 10, 2007
  • 30. Q&A SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 30 May 10, 2007
  • 31. Grazie! Thank you! luigi.buglione@computer.org, alain.abran@etsmtl.ca SMEF 2007 – Rome (Italy) L.Buglione, A.Abran © 2007 31 May 10, 2007