SlideShare ist ein Scribd-Unternehmen logo
1 von 65
Downloaden Sie, um offline zu lesen
Session 4

WBS, Estimation & Scheduling
Emanuele Della Valle
http://home.dei.polimi.it/dellavalle
Credits                                                           2

    This slides are largely based on Prof. John Musser
    class notes on “Principles of Software Project
    Management”
    M            t”
    Original slides are available at
    http://www.projectreference.com/
    htt //           j t f           /
    Reuse and republish permission was granted




 Planning and Managing Software Projects – Emanuele Della Valle
Today & Next Week                                                3

   Review Session 3
   Work Breakdown Structures (WBS)
   Estimation
   Network Fundamentals
   N t   kF d      t l
   PERT & CPM Techniques
   Gantt Charts
   This slide set will likely roll-over to next week
                            y




Planning and Managing Software Projects – Emanuele Della Valle
Session 3 Review                                                  4

    Full Lifecycle
      • Know your pure waterfall, 7 phase model
      • Understand the steps in each phase
      • Know the primary issues and goals of each
    Methodologies
      • Know a representative sample
      • Waterfall and variation, 1-2 iterative ones
      • Learn a bit about XP and other Agile methods
    Planning (introduction)
      • Primary Planning Steps
      • Documents




 Planning and Managing Software Projects – Emanuele Della Valle
Introduction to session 4 and 5
Estimation                                                        5

    “Predictions are hard, especially about the future”,
    Yogi Berra
    2 Types: Lucky or Lousy?




 Planning and Managing Software Projects – Emanuele Della Valle
Introduction to session 4 and 5
Planning, Estimating, Scheduling                                  6

    What’s the difference?
    Plan: Identify activities. No specific start and end
    dates.
    Estimating: Determining the size & duration of
     st at g     ete      g t e s e du at o o
    activities.
    Schedule: Adds specific start and end dates,
                      p                        ,
    relationships, and resources.




 Planning and Managing Software Projects – Emanuele Della Valle
Introduction to session 4 and 5
Project Planning: A 12 Step Program                                                  7

    Set goal and scope                                            Identify tasks
    Select lifecycle                                              Estimate size
    Set org./team form                                            Estimate effort
    Start team selection                                          Identify task
                                                                  dependencies
    Determine risks
                                                                  Assign resources
    Create WBS
                                                                  Schedule work




 Planning and Managing Software Projects – Emanuele Della Valle
Introduction to session 4 and 5
How To Schedule                                                   8

1. Identify “what” needs to be done
      • Work Breakdown Structure (WBS)
2. Identify “how much” (the size)
      • Size estimation techniques
3. Identify the dependency between tasks
      • Dependency graph, network diagram
4. Estimate total duration of the work to be done
      • The actual schedule




 Planning and Managing Software Projects – Emanuele Della Valle
Introduction to session 4 and 5
WBS & Estimation                                                  9

    How did you feel when I asked
      • “How long will your project take?”
    Not an easy answer to give right?
    At least not if I were are real customer on a real
    project
    How can you manage that issue?
            y       g




 Planning and Managing Software Projects – Emanuele Della Valle
Introduction to session 4 and 5
Partitioning Your Project                                         10

    You need to decompose your project into manageable
    chunks
    ALL projects need this step
    Divide & Co que
        de Conquer
    Two main causes of project failure
      • Forgetting something critical
           g     g          g
      • Ballpark estimates become targets
    How does partitioning help this?




 Planning and Managing Software Projects – Emanuele Della Valle
Introduction to session 4 and 5
Project Elements                                                  11

    A Project: functions, activities, tasks




 Planning and Managing Software Projects – Emanuele Della Valle
Work Breakdown Structure: WBS                                    12

   Hierarchical list of project’s work activities
   2 Formats
     • Outline (indented format)
     • Graphical Tree (Organizational Chart)
   Uses a decimal numbering system
     • Ex: 3.1.5
   Includes
     • Development, Mgmt., and project support tasks
   Shows “i contained in” relationships
   Sh    “is   t i d i ” l ti      hi
   Does not show dependencies or durations




Planning and Managing Software Projects – Emanuele Della Valle
WBS
Contract vs. Project WBS                                                                13

    Contract WBS (CWBS)                                           Project WBS (PWBS)
      • First 2 or 3 levels                                       • Defined by PM and team
      • Hi h l
        High-level t
                   l tracking
                         ki                                         members
                                                                  • Tasks tied to
                                                                    deliverables
                                                                  • Lowest level tracking




 Planning and Managing Software Projects – Emanuele Della Valle
WBS
A Full WBS Structure                                              14

    Up to six levels (3-6 usually) such as




    Upper 3 can be used by customer for reporting (if part
    of RFP/RFQ)
    Different level can be applied to different uses
      • Ex: Level 1: authorizations; 2: budgets; 3: schedules




 Planning and Managing Software Projects – Emanuele Della Valle
WBS
Chart Example                                                    15




Planning and Managing Software Projects – Emanuele Della Valle
WBS
Outline Example                                                   16

Retail Web Site
1.0 Project Management
2.0 Requirements Gathering
3.0 Analysis & Design
4.0
4 0 Site Software Development
  4.1 HTML Design and Creation
  4.2 Backend Software
      4.2.1 Database Implementation
      4.2.2 Middleware Development
      4.2.3 Security Subsystems
      4.2.4 Catalog Engine
      4.2.5
      4 2 5 Transaction Processing
  4.3 Graphics and Interface
  4.4 Content Creation
5.0 Testing and Production
 Planning and Managing Software Projects – Emanuele Della Valle
WBS
Types                                                            17

   Process WBS
     • a.k.a Activity-oriented
     • Ex: Requirements Analysis Design Testing
           Requirements, Analysis, Design,
     • Typically used by PM
   Product WBS
     • a.k.a. Entity-oriented
     • Ex: Financial engine, Interface system, DB
     • Typically used by engineering manager
   Hybrid WBS: both above
     • This is not unusual
     • Ex: Lifecycle phases at high level with component or
       feature-specifics within phases
     • Rationale: processes produce products




Planning and Managing Software Projects – Emanuele Della Valle
WBS
Product WBS                                                      18




Planning and Managing Software Projects – Emanuele Della Valle
WBS
Process WBS                                                      19




Planning and Managing Software Projects – Emanuele Della Valle
WBS
Outline WBS with Gantt Chart                                      20




 Planning and Managing Software Projects – Emanuele Della Valle
WBS
WBS by PMI Process Groups                                        21




Planning and Managing Software Projects – Emanuele Della Valle
WBS
Less Frequently Used Alternatives                                 22

    Organizational WBS
      • Research, Product Design, Engineering, Operations
      • Can be useful for highly cross functional projects
                                 cross-functional
    Geographical WBS
      • Can be useful with distributed teams
      • NYC team, San Jose team, Off-shore team




 Planning and Managing Software Projects – Emanuele Della Valle
WBS
Work Packages                                                    23

   Generic term for discrete tasks with definable end
   results
   Typically the “leaves” on the tree
   The “one-to-two” rule
     e o e to t o u e
     • Often at: 1 or 2 persons for 1 or 2 weeks
   Basis for monitoring and reporting p g
                      g       p     g progress
     • Can be tied to budget items (charge numbers)
     • Resources (personnel) assigned
   Ideally shorter rather than l
    d ll h            h    h   longer
     •     Longer makes in-progress estimates needed
     •     These are more subjective than “done”
                               j
     •     2-3 weeks maximum for software projects
     •     1 day minimum (occasionally a half day)
     •     Not so small as to micro-manage
                              micro manage


Planning and Managing Software Projects – Emanuele Della Valle
WBS
Wrap Up (so far)                                                  24

    List of Activities, not Things
    List of items can come from many sources
      • SOW, Proposal, brainstorming, stakeholders, team
    Describe activities using “bullet language”
                            g            g g
      • Meaningful but terse labels
    All WBS paths do not have to go to the same level
    Do not plan more detail than you can manage




 Planning and Managing Software Projects – Emanuele Della Valle
WBS
WBS & Chosen Lifecycle                                           25

   PM must map activities to chosen lifecycle
   Each lifecycle has different sets of activities
   Integral process activities occur for all
     • Planning, configuration, testing
              g,      g       ,       g
   Operations and maintenance phases are not normally
   in plan (
      p    (considered p
                       post-project)
                            p j    )
   Some models are “straightened” for WBS
     • Spiral and other iterative models
     • Linear sequence several times
   Deliverables of tasks vary by chosen lifecycle




Planning and Managing Software Projects – Emanuele Della Valle
WBS
Techniques                                                       26

   Top-Down
   Bottom Up
   Bottom-Up
   Analogy
   Brainstorming
   B i t     i
     • Post-its on a wall
   Rolling Wave
     • 1st pass: go 1-3 levels deep
     • Gather more requirements or data
     • Add more detail l
                 d    il later




Planning and Managing Software Projects – Emanuele Della Valle
WBS -Techniques
Top-down                                                          27

    Start at highest level
    Systematically develop increasing level of detail
    Best if
      • The problem is well understood
            p
      • Technology and methodology are not new
      • This is similar to an earlier project or problem
    But is also applied in majority of situations




 Planning and Managing Software Projects – Emanuele Della Valle
WBS -Techniques
Bottom-up                                                         28

    Start at lowest level tasks
    Aggregate into summaries and higher levels
    Cons
      • Time consuming
                     g
      • Needs more requirements complete
    Pros
      • Detailed




 Planning and Managing Software Projects – Emanuele Della Valle
WBS -Techniques
Analogy                                                           29

    Base WBS upon that of a “similar” project
    Use a template
    Analogy also can be estimation basis
    Pros
    P
      • Based on past actual experience
    Cons
      • Needs comparable project




 Planning and Managing Software Projects – Emanuele Della Valle
WBS -Techniques
Brainstorming                                                      30

    Approach
      • Generate all activities you can think of that need to be
        done
      • Group them into categories
    Both Top-down and Brainstorming can be used on the
         Top down
    same WBS
    Remember to get the p p who will be doing the
                  g      people             g
    work involved (buy-in matters!)




 Planning and Managing Software Projects – Emanuele Della Valle
WBS
WBS are Basis of Many Things                                      31

    Network scheduling
    Costing
    Risk analysis
    Organizational structure
    O    i ti    l t    t
    Control
    Measurement




 Planning and Managing Software Projects – Emanuele Della Valle
WBS
Guidelines Part 1                                                 32

    Should be easy to understand
    Some companies have corporate standards for these
    schemes
    So e top e e te s, e oject g t a e
    Some top-level items, like Project Mgmt. are in WBS
                                                      S
    for each project
      • Others vary by project
    What often hurts most is what’s missing
    Break down until you can generate accurate time &
    cost estimates
    Ensure each element corresponds to a deliverable




 Planning and Managing Software Projects – Emanuele Della Valle
WBS
Guidelines Part 2                                                 33

    How detailed should it be?
      • Not as detailed as the final MS-Project plan
      • Each level should have no more than 7 items
      • It can evolve over time
    What tool should you use?
      • Excel, Word, Project
      • Org chart diagramming tool (Visio, etc)
      • Specialized commercial apps
    Re-use a “template” if you have one




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations
Introduction                                                      34

    Very difficult to do, but needed often
    Created, used or refined during
      •     Strategic planning
      •     Feasibility study and/or SOW
      •     Proposals
      •     Vendor and sub-contractor evaluation
      •     Project planning (iteratively)
    Basic process
      •     Estimate the size of the product
      •     Estimate the effort (man-months)
      •     Estimate the schedule
      •     NOTE: Not all of these steps are always explicitly
            performed




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations
Introduction (cont.)                                                35

    Remember, an “exact estimate” is an oxymoron
    Estimate how long will it take you to get home from
    class tonight
      •     On what basis did you do that?
      •     Experience right?
      •     Likely as an “average” probability
      •     For most software projects there is no such ‘average’
    Most software estimations are off by 25-100%




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations
Target vs. Committed Dates                                        36

    Target:
      • Proposed by business or marketing
      • Do not commit to this too soon!
    Committed:
      • Team agrees to this
      • After you’ve developed a schedule




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations
Cone of Uncertainty                                               37




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations
Size                                                              38

    Small projects (10-99 FPs), variance of 7% from post-
    requirements estimates
    Medium (100-999 FPs), 22% variance
    Large (1000-9999 FPs) 38% variance
     a ge ( 000 9999   s)      a a ce
    Very large (> 10K FPs) 51% variance




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations - Size
Methodologies                                                     39

    Top-down
    Bottom up
    Bottom-up
    Analogy
    Expert J d
    E    t Judgment
                  t
    Priced to Win
    Parametric or Algorithmic Method
      • Using formulas and equations




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations - Size
Top-down Estimation                                               40

    Based on overall characteristics of project
      • Some of the others can be “types” of top-down
        (Analogy,
        (Analogy Expert Judgment and Algorithmic methods)
                        Judgment,
    Advantages
      • Easy to calculate
      • Effective early on (like initial cost estimates)
    Disadvantages
              g
      • Some models are questionable or may not fit
      • Less accurate because it doesn’t look at details




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations - Size
Bottom-up Estimation                                              41

    Create WBS
    Add from the bottom-up
                 bottom up
    Advantages
      • Works well if activities well understood
    Disadvantages
      • Specific activities not always known
      • More time consuming




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations - Size
Expert Judgment                                                   42

    Use somebody who has recent experience on a similar
    project
    You get a “guesstimate”
    Accuracy depends on their ‘real’ expertise
     ccu acy depe ds o t e      ea e pe t se
    Comparable application(s) must be accurately chosen
      • Systematic
         y
    Can use a weighted-average of opinions




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations - Size
Estimation by Analogy                                             43

    Use past project
      • Must be sufficiently similar (technology, type,
        organization)
      • Find comparable attributes (ex: # of inputs/outputs)
      • Can create a function
    Advantages
      • Based on actual historical data
    Disadvantages
      • Difficulty ‘matching’ project types
      • Prior data may have been mis-measured
                                    mis measured
      • How to measure differences – no two exactly same




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations - Size
Priced to Win                                                     44

    Just follow other estimates
    Save on doing full estimate
    Needs information on other estimates (or prices)
    Purchaser must closely watch trade-offs
    P   h        t l    l    t ht d     ff
    Priced to lose?




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations - Size
Algorithmic Measures                                              45

    Lines of Code (LOC)
    Function points
    Feature points or object points
    Other
    Oth possible
            ibl
      • Number of bubbles on a DFD
      • Number of of ERD entities
      • Number of processes on a structure chart
    LOC and function points most common
      • ( f the algorithmic approaches)
        (of h    l   ih i          h )
    Majority of projects use none of the above




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations - Size
Code-based Estimates                                              46

    LOC Advantages
      • Commonly understood metric
      • Permits specific comparison
      • Actuals easily measured
    LOC Disadvantages
      •     Difficult to estimate early in cycle
      •     Counts vary by language
      •     Many costs not considered (ex: requirements)
      •     Programmers may be rewarded based on this
              – Can use: # defects/# LOC
      • Code generators produce excess code




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations - Size
LOC Estimate Issues                                               47

    How do you know how many in advance?
    What about different languages?
    What about programmer style?
    Stat:
    St t avg. programmer productivity: 3 000 LOC/yr
                            d ti it 3,000 LOC/
    Most algorithmic approaches are more effective after
    requirements (or have to be after)




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations - Size
Function Points                                                   48

    Software size measured by number & complexity of
    functions it performs
    More methodical than LOC counts
    House analogy
     ouse a a ogy
      • House’s Square Feet ~= Software LOC
      • # Bedrooms & Baths ~= Function points
      • Former is size only, latter is size & function
                       only
    Three basic steps




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations - Size
Function Point Process                                             49

1. Count # of biz functions per category
      • Categories: outputs, inputs, db inquiries, files or data
        structures,
        structures and interfaces
2. Establish Complexity Factor for each and apply
      • Simple, Average, Complex
      • Set a weighting multiplier for each (0->15)
      • This results in the “unadjusted function-point total”
3. Compute an “influence multiplier” and apply
      • It ranges from 0.65 to 1.35; is based on 14 factors
4. Results in “function point total”
      • This can be used in comparative estimates




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations - Size
Wideband Delphi                                                   50

    Group consensus approach
    Rand corp. (http://www.rand.org/) used orig. Delphi
    approach to predict future technologies
    Present experts with a problem and response form
      ese t e pe ts t      p ob e a d espo se o
    Conduct group discussion, collect anonymous opinions,
    then feedback
    Conduct another discussion & iterate until consensus
    Advantages
      • Easy, inexpensive, utilizes expertise of several people
      • Does not require historical data
    Disadvantages
      • Difficult to repeat
      • Ma fail to reach consensus, reach wrong one, or all may
        May           ea h onsens s ea h    ong one o       ma
        have same bias
 Planning and Managing Software Projects – Emanuele Della Valle
Estimations - Size
Parametric Method Issues                                          51

    Remember: most projects you’ll run into don’t use
    these
    Which is ‘normal’, so don’t be surprised
      • Or come-in to new job and say “Hey, let’s use COCOMO”
    These are more effective on large projects
      • Where a past historical base exists
    Primary issue for most projects are
      • Lack of similar projects
              – Thus lack of comparable data

    Catch-22: how to get started
      • See http://en.wikipedia.org/wiki/Catch-22_( g )
               p //       p       g/    /         (logic)




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations - Size
Code Reuse & Estimation                                           52

    Does not come for free
    Code types: New, Modified, Reused
    If code is more than 50% modified, it’s “new”
    Reuse f t
    R     factors have wide range
                  h     id
      • Reused code takes 30% effort of new
      • Modified is 60% of new
    Integration effort with reused code almost as
    expensive as with new code




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations
Effort Estimation                                                 53

    Now that you know the “size”, determine the “effort”
    needed to build it
    Various models: empirical, mathematical, subjective
    Expressed in units of duration
      p essed    u ts o du at o
      • Person-Months




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations
Effort Estimation                                                 54

    McConnell shows schedule tables for conversion of size
    to effort
    As with parametric size estimation, these techniques
    perform better with historical data
    Again, not seen in ‘average’ projects
    Often the size and effort estimation steps are
                                            p
    combined (not that this is recommended, but is what
    often is done)
    “Commitment-Based” Scheduling is what is often done
      • Ask developer to ‘commit’ to an estimate (his or her
        own))




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations - Efforts
ECOCOMO                                                           55

    COnstructive COst MOdel
    Allows for the type of application, size, and “Cost
                                                   Cost
    Drivers”
    Outputs in Person Months
                e so   o t s
    Cost drivers using High/Med/Low & include
      • Motivation
      • Ability of team
      • Application experience
    Biggest weakness?
               k    ?
      • Requires input of a product size estimate in LOC




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations
Issues                                                            56

    Quality estimations needed early but information is
    limited
    Precise estimation data available at end but not
    needed
      • O is it? What about the next project?
        Or            abo t     ne t p oje t?
    Best estimates are based on past experience
    Politics of estimation:
      • You may anticipate a “cut” by upper management
    For many software projects there is little or none
      •     Technologies change
      •     Historical data unavailable
      •     Wide variance in project experiences/types
      •     Subjective nature of software estimation



 Planning and Managing Software Projects – Emanuele Della Valle
Estimations - Issues
Over and Under Estimation                                              57

    Over estimation issues
      • The project will not be funded
              – C
                Conservative estimates guaranteeing 100% success may
                        ti     ti  t           t i
                mean funding probability of zero.
      • Parkinson’s Law: Work expands to take the time allowed
      • D
        Danger of feature and scope creep
                 ff         d
      • Be aware of “double-padding”: team member +
        manager
    Under estimation issues
      • Quality issues (short changing key phases like testing)
      • Inability to meet deadlines
      • Morale and other team motivation issues




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations
Estimation Guidelines                                             58

    Estimate iteratively!
      •     Process of gradual refinement
      •     Make your best estimates at each planning stage
      •     Refine estimates and adjust plans iteratively
      •     Plans and decisions can be refined in response
      •     Balance: too many revisions vs. too f
               l                                 few




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations
Know Your Deadlines                                               59

    Are they ‘Real Deadlines’?
      • Tied to an external event
      • Have to be met for project to be a success
      • Ex: end of financial year, contractual deadline, Y2K
    Or ‘Artificial Deadlines’?
        Artificial Deadlines ?
      • Set by arbitrary authority
      • May have some flexibility (if pushed)




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations
“Presentation”                                                     60

    How you present the estimation can have huge impact
    Techniques
      • Plus-or-minus qualifiers
              – 6 months +/-1 month
      • Ranges
              – 6-8 months
      • Risk Quantification
              – +/- with added information
              – +1 month of new tools not working as expected
              – -2 weeks for less delay in hiring new developers
                 2
      • Cases
              – Best / Planned / Current / Worst cases
      • Coarse Dates
              – Q3 2009
      • Confidence Factors
              – April 1 – 10% probability, July 1 – 50%, etc.

 Planning and Managing Software Projects – Emanuele Della Valle
Estimations
Other Estimation Factors                                          61

    Account for resource experience or skill
      • Up to a point
      • Often needed more on the “low” end, such as for a new
                                       end
        or junior person
    Allow for “non-project” time & common tasks
               non project
      • Meetings, phone calls, web surfing, sick days
    There are commercial ‘estimation tools’ available
      • They typically require configuration based on past data




 Planning and Managing Software Projects – Emanuele Della Valle
Estimations
Other Estimation Notes                                            62

    Remember: “manage expectations”
    Parkinson s
    Parkinson’s Law
      • “Work expands to fill the time available”
    The Student Syndrome
                 y
      • Procrastination until the last minute (cram)




 Planning and Managing Software Projects – Emanuele Della Valle
Optional Reading                                                  63

    McConnell: 9, “Scheduling”
    Schwalbe: 5, “Project Time Management”
                  Project      Management
    URLs: See projectreference.com on “PERT/CPM”
      • http://www.projectreference.com/#PERT
           p //    p j                 /




 Planning and Managing Software Projects – Emanuele Della Valle
Homework – 2: WBS                                                         64

   Create a WBS for your project
     • Please think this through. You’re the PM now!
   Guidelines
     • Do it at managerial level (see slide 14)
             – 4 7 nodes at 1st level
               4-7
             – 2-5 nodes at 2nd level (per each node at 1st level)
             – You can go deeper at your discretion.
     • As we covered in class, you can use either a process,
       product or hybrid approach.
             – For most of your projects I suspect the process approach
               would work best at managerial level.
     • Follow the standard hierarchical numbering scheme for
       WBS structures.
     • Use the Word template of homework–1
             – Keep only the coversheet
             – Update the title to “homework – 2 : WBS“
                                    homework       WBS
     • Submit to mpsp2010@gmail.com as you did with
       homework-1
Planning and Managing Software Projects – Emanuele Della Valle
Questions?                                                       65




Planning and Managing Software Projects – Emanuele Della Valle

Weitere ähnliche Inhalte

Was ist angesagt?

Work breakdown structure
Work breakdown structureWork breakdown structure
Work breakdown structureCOEPD HR
 
Wbs, estimation and scheduling
Wbs, estimation and schedulingWbs, estimation and scheduling
Wbs, estimation and schedulingSulman Ahmed
 
Engineering Economics|Work Breakdown Structure
Engineering Economics|Work Breakdown StructureEngineering Economics|Work Breakdown Structure
Engineering Economics|Work Breakdown Structureumair khan
 
The Work Breakdown Structure: Lack Of A Good One Already Sets Your Project Up...
The Work Breakdown Structure: Lack Of A Good One Already Sets Your Project Up...The Work Breakdown Structure: Lack Of A Good One Already Sets Your Project Up...
The Work Breakdown Structure: Lack Of A Good One Already Sets Your Project Up...Ed Kozak
 
What is a Work Breakdown Structure?
What is a Work Breakdown Structure?What is a Work Breakdown Structure?
What is a Work Breakdown Structure?Kenny Hirschmann
 
Work Break Down Structure
Work Break Down StructureWork Break Down Structure
Work Break Down StructureSomtel
 
WBS presentation
WBS presentationWBS presentation
WBS presentationjpstewar
 
Work breakdown structures
Work breakdown structures Work breakdown structures
Work breakdown structures Ian Cammack
 
Work breakdown structure
Work breakdown structureWork breakdown structure
Work breakdown structureNicola2903
 
Work breakdownstructure
Work breakdownstructureWork breakdownstructure
Work breakdownstructureRahul Saini
 
Work breakdown structure in project management ppt by kiran j
Work breakdown structure in project management ppt by kiran jWork breakdown structure in project management ppt by kiran j
Work breakdown structure in project management ppt by kiran jIIT delhi
 
Information technology project management
Information technology project managementInformation technology project management
Information technology project managementSeredup Maya
 
K.chaitanya pm
K.chaitanya pmK.chaitanya pm
K.chaitanya pmkongara
 
Diploma in Project Management – How to Create a Work Breakdown Structure (WBS...
Diploma in Project Management – How to Create a Work Breakdown Structure (WBS...Diploma in Project Management – How to Create a Work Breakdown Structure (WBS...
Diploma in Project Management – How to Create a Work Breakdown Structure (WBS...danieljohn810
 
Using the work breakdown structure to plan a project
Using the work breakdown structure to plan a projectUsing the work breakdown structure to plan a project
Using the work breakdown structure to plan a projectMohieudeen Mohamed
 
Program Management 2.0: Work Breakdown Structure
Program Management 2.0: Work Breakdown StructureProgram Management 2.0: Work Breakdown Structure
Program Management 2.0: Work Breakdown StructureJohn Carter
 
Project scheduling and work break down structure(wbs) 12 cs18
Project scheduling and work break down structure(wbs) 12 cs18Project scheduling and work break down structure(wbs) 12 cs18
Project scheduling and work break down structure(wbs) 12 cs18Engr Imran Ashraf
 

Was ist angesagt? (20)

Wbs Building Use This
Wbs Building Use ThisWbs Building Use This
Wbs Building Use This
 
Work breakdown structure
Work breakdown structureWork breakdown structure
Work breakdown structure
 
Wbs, estimation and scheduling
Wbs, estimation and schedulingWbs, estimation and scheduling
Wbs, estimation and scheduling
 
Engineering Economics|Work Breakdown Structure
Engineering Economics|Work Breakdown StructureEngineering Economics|Work Breakdown Structure
Engineering Economics|Work Breakdown Structure
 
The Work Breakdown Structure: Lack Of A Good One Already Sets Your Project Up...
The Work Breakdown Structure: Lack Of A Good One Already Sets Your Project Up...The Work Breakdown Structure: Lack Of A Good One Already Sets Your Project Up...
The Work Breakdown Structure: Lack Of A Good One Already Sets Your Project Up...
 
Work breakdown structure
Work breakdown structureWork breakdown structure
Work breakdown structure
 
What is a Work Breakdown Structure?
What is a Work Breakdown Structure?What is a Work Breakdown Structure?
What is a Work Breakdown Structure?
 
Work Break Down Structure
Work Break Down StructureWork Break Down Structure
Work Break Down Structure
 
WBS presentation
WBS presentationWBS presentation
WBS presentation
 
Work Breakdown Structure
Work Breakdown StructureWork Breakdown Structure
Work Breakdown Structure
 
Work breakdown structures
Work breakdown structures Work breakdown structures
Work breakdown structures
 
Work breakdown structure
Work breakdown structureWork breakdown structure
Work breakdown structure
 
Work breakdownstructure
Work breakdownstructureWork breakdownstructure
Work breakdownstructure
 
Work breakdown structure in project management ppt by kiran j
Work breakdown structure in project management ppt by kiran jWork breakdown structure in project management ppt by kiran j
Work breakdown structure in project management ppt by kiran j
 
Information technology project management
Information technology project managementInformation technology project management
Information technology project management
 
K.chaitanya pm
K.chaitanya pmK.chaitanya pm
K.chaitanya pm
 
Diploma in Project Management – How to Create a Work Breakdown Structure (WBS...
Diploma in Project Management – How to Create a Work Breakdown Structure (WBS...Diploma in Project Management – How to Create a Work Breakdown Structure (WBS...
Diploma in Project Management – How to Create a Work Breakdown Structure (WBS...
 
Using the work breakdown structure to plan a project
Using the work breakdown structure to plan a projectUsing the work breakdown structure to plan a project
Using the work breakdown structure to plan a project
 
Program Management 2.0: Work Breakdown Structure
Program Management 2.0: Work Breakdown StructureProgram Management 2.0: Work Breakdown Structure
Program Management 2.0: Work Breakdown Structure
 
Project scheduling and work break down structure(wbs) 12 cs18
Project scheduling and work break down structure(wbs) 12 cs18Project scheduling and work break down structure(wbs) 12 cs18
Project scheduling and work break down structure(wbs) 12 cs18
 

Andere mochten auch

Software Project Management (lecture 4)
Software Project Management (lecture 4)Software Project Management (lecture 4)
Software Project Management (lecture 4)Syed Muhammad Hammad
 
Different types of wbs structures
Different types of wbs structuresDifferent types of wbs structures
Different types of wbs structuressanddrap
 
25 project management
25 project management 25 project management
25 project management osegura2475
 
WBS Refinery Overhauling
WBS Refinery OverhaulingWBS Refinery Overhauling
WBS Refinery OverhaulingAshar Ahmed
 
8 Essential Interpersonal Skills Project Manager Must Have!
8 Essential Interpersonal Skills Project Manager Must Have! 8 Essential Interpersonal Skills Project Manager Must Have!
8 Essential Interpersonal Skills Project Manager Must Have! PMExamSmartNotes
 
NCV 4 Project Management Hands-On Support Slide Show - Module 2
NCV 4 Project Management Hands-On Support Slide Show - Module 2NCV 4 Project Management Hands-On Support Slide Show - Module 2
NCV 4 Project Management Hands-On Support Slide Show - Module 2Future Managers
 
Intro to environmental site assessments (esa)
Intro to environmental site assessments  (esa)Intro to environmental site assessments  (esa)
Intro to environmental site assessments (esa)Gordon Onley
 
Phase I Environmental Site Assessment Training Seminar
Phase I Environmental Site Assessment Training SeminarPhase I Environmental Site Assessment Training Seminar
Phase I Environmental Site Assessment Training SeminarBrandon Trate
 
Project Management and Control
Project Management and ControlProject Management and Control
Project Management and Controleresource erp
 
Phase I ESA Site Reconnaissance
Phase I ESA Site ReconnaissancePhase I ESA Site Reconnaissance
Phase I ESA Site Reconnaissancegdmayo
 
WBS Structure –Essential Element In Project Management
WBS Structure –Essential Element In Project ManagementWBS Structure –Essential Element In Project Management
WBS Structure –Essential Element In Project ManagementAnjali Rao
 
New technologies in environmental cleaning
New technologies in environmental cleaningNew technologies in environmental cleaning
New technologies in environmental cleaningMoustapha Ramadan
 
Work breakdown structure by muhammad talha
Work breakdown structure by muhammad talhaWork breakdown structure by muhammad talha
Work breakdown structure by muhammad talhaMuhammad Talha
 
Project Management Body of Knowledge (Introduction)
Project Management Body of Knowledge (Introduction)Project Management Body of Knowledge (Introduction)
Project Management Body of Knowledge (Introduction)Jeffrey Cheah
 
Safe Drinking Water Act How Safe is My Drinking Water
Safe Drinking Water Act How Safe is My Drinking WaterSafe Drinking Water Act How Safe is My Drinking Water
Safe Drinking Water Act How Safe is My Drinking WaterMichael Klein
 
Work Breakdown Structures (WBS)
Work Breakdown Structures (WBS)Work Breakdown Structures (WBS)
Work Breakdown Structures (WBS)stakeholdermap
 

Andere mochten auch (20)

Software Project Management (lecture 4)
Software Project Management (lecture 4)Software Project Management (lecture 4)
Software Project Management (lecture 4)
 
Different types of wbs structures
Different types of wbs structuresDifferent types of wbs structures
Different types of wbs structures
 
25 project management
25 project management 25 project management
25 project management
 
WBS Refinery Overhauling
WBS Refinery OverhaulingWBS Refinery Overhauling
WBS Refinery Overhauling
 
8 Essential Interpersonal Skills Project Manager Must Have!
8 Essential Interpersonal Skills Project Manager Must Have! 8 Essential Interpersonal Skills Project Manager Must Have!
8 Essential Interpersonal Skills Project Manager Must Have!
 
NCV 4 Project Management Hands-On Support Slide Show - Module 2
NCV 4 Project Management Hands-On Support Slide Show - Module 2NCV 4 Project Management Hands-On Support Slide Show - Module 2
NCV 4 Project Management Hands-On Support Slide Show - Module 2
 
Sadchap03
Sadchap03Sadchap03
Sadchap03
 
Intro to environmental site assessments (esa)
Intro to environmental site assessments  (esa)Intro to environmental site assessments  (esa)
Intro to environmental site assessments (esa)
 
Phase I Environmental Site Assessment Training Seminar
Phase I Environmental Site Assessment Training SeminarPhase I Environmental Site Assessment Training Seminar
Phase I Environmental Site Assessment Training Seminar
 
Project Management and Control
Project Management and ControlProject Management and Control
Project Management and Control
 
Phase I ESA Site Reconnaissance
Phase I ESA Site ReconnaissancePhase I ESA Site Reconnaissance
Phase I ESA Site Reconnaissance
 
WBS Structure –Essential Element In Project Management
WBS Structure –Essential Element In Project ManagementWBS Structure –Essential Element In Project Management
WBS Structure –Essential Element In Project Management
 
New technologies in environmental cleaning
New technologies in environmental cleaningNew technologies in environmental cleaning
New technologies in environmental cleaning
 
Work breakdown structure by muhammad talha
Work breakdown structure by muhammad talhaWork breakdown structure by muhammad talha
Work breakdown structure by muhammad talha
 
Wbs For Building Project
Wbs For Building ProjectWbs For Building Project
Wbs For Building Project
 
PERT CPM Intro
PERT CPM IntroPERT CPM Intro
PERT CPM Intro
 
Project Management Body of Knowledge (Introduction)
Project Management Body of Knowledge (Introduction)Project Management Body of Knowledge (Introduction)
Project Management Body of Knowledge (Introduction)
 
Quality control methods
Quality control methodsQuality control methods
Quality control methods
 
Safe Drinking Water Act How Safe is My Drinking Water
Safe Drinking Water Act How Safe is My Drinking WaterSafe Drinking Water Act How Safe is My Drinking Water
Safe Drinking Water Act How Safe is My Drinking Water
 
Work Breakdown Structures (WBS)
Work Breakdown Structures (WBS)Work Breakdown Structures (WBS)
Work Breakdown Structures (WBS)
 

Ähnlich wie P&msp2010 04 wbs-and-estimation

Overview Of Project Management - P&MSP2010 (2/11)
Overview Of Project Management - P&MSP2010 (2/11)Overview Of Project Management - P&MSP2010 (2/11)
Overview Of Project Management - P&MSP2010 (2/11)Emanuele Della Valle
 
P&msp2010 08 development-management
P&msp2010 08 development-managementP&msp2010 08 development-management
P&msp2010 08 development-managementEmanuele Della Valle
 
Understanding Software Project Management
Understanding Software Project ManagementUnderstanding Software Project Management
Understanding Software Project ManagementEmanuele Della Valle
 
Planning Phase Part I - Project Phases and Lifecycle Planning
Planning Phase Part I - Project Phases and Lifecycle PlanningPlanning Phase Part I - Project Phases and Lifecycle Planning
Planning Phase Part I - Project Phases and Lifecycle PlanningEmanuele Della Valle
 
Software Project Management - Introduction and fundamentals
Software Project Management - Introduction and fundamentalsSoftware Project Management - Introduction and fundamentals
Software Project Management - Introduction and fundamentalsEmanuele Della Valle
 
More on Software Project Management
More on Software Project ManagementMore on Software Project Management
More on Software Project ManagementEmanuele Della Valle
 
People Dimension in Software Projects
People Dimension in Software ProjectsPeople Dimension in Software Projects
People Dimension in Software ProjectsEmanuele Della Valle
 
Software Project Fundamentals and Classic Mistakes - P&MSP2010 (1/11)
Software Project Fundamentals and Classic Mistakes - P&MSP2010 (1/11)Software Project Fundamentals and Classic Mistakes - P&MSP2010 (1/11)
Software Project Fundamentals and Classic Mistakes - P&MSP2010 (1/11)Emanuele Della Valle
 
software project management
software project managementsoftware project management
software project managementAnkit Gupta
 

Ähnlich wie P&msp2010 04 wbs-and-estimation (20)

Scheduling
SchedulingScheduling
Scheduling
 
Overview Of Project Management - P&MSP2010 (2/11)
Overview Of Project Management - P&MSP2010 (2/11)Overview Of Project Management - P&MSP2010 (2/11)
Overview Of Project Management - P&MSP2010 (2/11)
 
Estimation
EstimationEstimation
Estimation
 
P&msp2010 08 development-management
P&msp2010 08 development-managementP&msp2010 08 development-management
P&msp2010 08 development-management
 
Understanding Software Project Management
Understanding Software Project ManagementUnderstanding Software Project Management
Understanding Software Project Management
 
Planning Phase Part I - Project Phases and Lifecycle Planning
Planning Phase Part I - Project Phases and Lifecycle PlanningPlanning Phase Part I - Project Phases and Lifecycle Planning
Planning Phase Part I - Project Phases and Lifecycle Planning
 
Planning Phase - P&MSP2010 (3/11)
Planning Phase - P&MSP2010 (3/11)Planning Phase - P&MSP2010 (3/11)
Planning Phase - P&MSP2010 (3/11)
 
P&msp2010 10 project-control
P&msp2010 10 project-controlP&msp2010 10 project-control
P&msp2010 10 project-control
 
Software Project Management - Introduction and fundamentals
Software Project Management - Introduction and fundamentalsSoftware Project Management - Introduction and fundamentals
Software Project Management - Introduction and fundamentals
 
More on Software Project Management
More on Software Project ManagementMore on Software Project Management
More on Software Project Management
 
People Dimension in Software Projects
People Dimension in Software ProjectsPeople Dimension in Software Projects
People Dimension in Software Projects
 
Web Project Management
Web Project ManagementWeb Project Management
Web Project Management
 
Spm tutorials
Spm tutorialsSpm tutorials
Spm tutorials
 
P&msp2010 05 scheduling
P&msp2010 05 schedulingP&msp2010 05 scheduling
P&msp2010 05 scheduling
 
Software Project Fundamentals and Classic Mistakes - P&MSP2010 (1/11)
Software Project Fundamentals and Classic Mistakes - P&MSP2010 (1/11)Software Project Fundamentals and Classic Mistakes - P&MSP2010 (1/11)
Software Project Fundamentals and Classic Mistakes - P&MSP2010 (1/11)
 
P&msp2010 11 final-stages
P&msp2010 11 final-stagesP&msp2010 11 final-stages
P&msp2010 11 final-stages
 
Chap04 project integration management
Chap04 project integration managementChap04 project integration management
Chap04 project integration management
 
Tls
TlsTls
Tls
 
software project management
software project managementsoftware project management
software project management
 
Unit 1 spm
Unit 1  spmUnit 1  spm
Unit 1 spm
 

Mehr von Emanuele Della Valle

Taming velocity - a tale of four streams
Taming velocity - a tale of four streamsTaming velocity - a tale of four streams
Taming velocity - a tale of four streamsEmanuele Della Valle
 
Work in progress on Inductive Stream Reasoning
Work in progress on Inductive Stream ReasoningWork in progress on Inductive Stream Reasoning
Work in progress on Inductive Stream ReasoningEmanuele Della Valle
 
Knowledge graphs in search engines
Knowledge graphs in search enginesKnowledge graphs in search engines
Knowledge graphs in search enginesEmanuele Della Valle
 
La città dei balocchi 2017 in numeri - Fluxedo
La città dei balocchi 2017 in numeri - FluxedoLa città dei balocchi 2017 in numeri - Fluxedo
La città dei balocchi 2017 in numeri - FluxedoEmanuele Della Valle
 
Stream Reasoning: a summary of ten years of research and a vision for the nex...
Stream Reasoning: a summary of ten years of research and a vision for the nex...Stream Reasoning: a summary of ten years of research and a vision for the nex...
Stream Reasoning: a summary of ten years of research and a vision for the nex...Emanuele Della Valle
 
ACQUA: Approximate Continuous Query Answering over Streams and Dynamic Linked...
ACQUA: Approximate Continuous Query Answering over Streams and Dynamic Linked...ACQUA: Approximate Continuous Query Answering over Streams and Dynamic Linked...
ACQUA: Approximate Continuous Query Answering over Streams and Dynamic Linked...Emanuele Della Valle
 
Stream reasoning: an approach to tame the velocity and variety dimensions of ...
Stream reasoning: an approach to tame the velocity and variety dimensions of ...Stream reasoning: an approach to tame the velocity and variety dimensions of ...
Stream reasoning: an approach to tame the velocity and variety dimensions of ...Emanuele Della Valle
 
Big Data: how to use it to create value
Big Data: how to use it to create valueBig Data: how to use it to create value
Big Data: how to use it to create valueEmanuele Della Valle
 
Listening to the pulse of our cities with Stream Reasoning (and few more tech...
Listening to the pulse of our cities with Stream Reasoning (and few more tech...Listening to the pulse of our cities with Stream Reasoning (and few more tech...
Listening to the pulse of our cities with Stream Reasoning (and few more tech...Emanuele Della Valle
 
Ist16-03 An Introduction to the Semantic Web
Ist16-03 An Introduction to the Semantic Web Ist16-03 An Introduction to the Semantic Web
Ist16-03 An Introduction to the Semantic Web Emanuele Della Valle
 
Ist16-02 HL7 from v2 (syntax) to v3 (semantics)
Ist16-02 HL7 from v2 (syntax) to v3 (semantics)Ist16-02 HL7 from v2 (syntax) to v3 (semantics)
Ist16-02 HL7 from v2 (syntax) to v3 (semantics)Emanuele Della Valle
 
IST16-01 - Introduction to Interoperability and Semantic Technologies
IST16-01 - Introduction to Interoperability and Semantic TechnologiesIST16-01 - Introduction to Interoperability and Semantic Technologies
IST16-01 - Introduction to Interoperability and Semantic TechnologiesEmanuele Della Valle
 
Stream reasoning: mastering the velocity and the variety dimensions of Big Da...
Stream reasoning: mastering the velocity and the variety dimensions of Big Da...Stream reasoning: mastering the velocity and the variety dimensions of Big Da...
Stream reasoning: mastering the velocity and the variety dimensions of Big Da...Emanuele Della Valle
 
Listening to the pulse of our cities fusing Social Media Streams and Call Dat...
Listening to the pulse of our cities fusing Social Media Streams and Call Dat...Listening to the pulse of our cities fusing Social Media Streams and Call Dat...
Listening to the pulse of our cities fusing Social Media Streams and Call Dat...Emanuele Della Valle
 
Social listener-brera-design-district-2015-03
Social listener-brera-design-district-2015-03Social listener-brera-design-district-2015-03
Social listener-brera-design-district-2015-03Emanuele Della Valle
 
City Data Fusion for Event Management (in Italiano)
City Data Fusion for Event Management (in Italiano)City Data Fusion for Event Management (in Italiano)
City Data Fusion for Event Management (in Italiano)Emanuele Della Valle
 

Mehr von Emanuele Della Valle (20)

Taming velocity - a tale of four streams
Taming velocity - a tale of four streamsTaming velocity - a tale of four streams
Taming velocity - a tale of four streams
 
Stream reasoning
Stream reasoningStream reasoning
Stream reasoning
 
Work in progress on Inductive Stream Reasoning
Work in progress on Inductive Stream ReasoningWork in progress on Inductive Stream Reasoning
Work in progress on Inductive Stream Reasoning
 
Big Data and Data Science W's
Big Data and Data Science W'sBig Data and Data Science W's
Big Data and Data Science W's
 
Knowledge graphs in search engines
Knowledge graphs in search enginesKnowledge graphs in search engines
Knowledge graphs in search engines
 
La città dei balocchi 2017 in numeri - Fluxedo
La città dei balocchi 2017 in numeri - FluxedoLa città dei balocchi 2017 in numeri - Fluxedo
La città dei balocchi 2017 in numeri - Fluxedo
 
Stream Reasoning: a summary of ten years of research and a vision for the nex...
Stream Reasoning: a summary of ten years of research and a vision for the nex...Stream Reasoning: a summary of ten years of research and a vision for the nex...
Stream Reasoning: a summary of ten years of research and a vision for the nex...
 
ACQUA: Approximate Continuous Query Answering over Streams and Dynamic Linked...
ACQUA: Approximate Continuous Query Answering over Streams and Dynamic Linked...ACQUA: Approximate Continuous Query Answering over Streams and Dynamic Linked...
ACQUA: Approximate Continuous Query Answering over Streams and Dynamic Linked...
 
Stream reasoning: an approach to tame the velocity and variety dimensions of ...
Stream reasoning: an approach to tame the velocity and variety dimensions of ...Stream reasoning: an approach to tame the velocity and variety dimensions of ...
Stream reasoning: an approach to tame the velocity and variety dimensions of ...
 
Big Data: how to use it to create value
Big Data: how to use it to create valueBig Data: how to use it to create value
Big Data: how to use it to create value
 
Listening to the pulse of our cities with Stream Reasoning (and few more tech...
Listening to the pulse of our cities with Stream Reasoning (and few more tech...Listening to the pulse of our cities with Stream Reasoning (and few more tech...
Listening to the pulse of our cities with Stream Reasoning (and few more tech...
 
Ist16-04 An introduction to RDF
Ist16-04 An introduction to RDF Ist16-04 An introduction to RDF
Ist16-04 An introduction to RDF
 
Ist16-03 An Introduction to the Semantic Web
Ist16-03 An Introduction to the Semantic Web Ist16-03 An Introduction to the Semantic Web
Ist16-03 An Introduction to the Semantic Web
 
Ist16-02 HL7 from v2 (syntax) to v3 (semantics)
Ist16-02 HL7 from v2 (syntax) to v3 (semantics)Ist16-02 HL7 from v2 (syntax) to v3 (semantics)
Ist16-02 HL7 from v2 (syntax) to v3 (semantics)
 
IST16-01 - Introduction to Interoperability and Semantic Technologies
IST16-01 - Introduction to Interoperability and Semantic TechnologiesIST16-01 - Introduction to Interoperability and Semantic Technologies
IST16-01 - Introduction to Interoperability and Semantic Technologies
 
Stream reasoning: mastering the velocity and the variety dimensions of Big Da...
Stream reasoning: mastering the velocity and the variety dimensions of Big Da...Stream reasoning: mastering the velocity and the variety dimensions of Big Da...
Stream reasoning: mastering the velocity and the variety dimensions of Big Da...
 
On Stream Reasoning
On Stream ReasoningOn Stream Reasoning
On Stream Reasoning
 
Listening to the pulse of our cities fusing Social Media Streams and Call Dat...
Listening to the pulse of our cities fusing Social Media Streams and Call Dat...Listening to the pulse of our cities fusing Social Media Streams and Call Dat...
Listening to the pulse of our cities fusing Social Media Streams and Call Dat...
 
Social listener-brera-design-district-2015-03
Social listener-brera-design-district-2015-03Social listener-brera-design-district-2015-03
Social listener-brera-design-district-2015-03
 
City Data Fusion for Event Management (in Italiano)
City Data Fusion for Event Management (in Italiano)City Data Fusion for Event Management (in Italiano)
City Data Fusion for Event Management (in Italiano)
 

Kürzlich hochgeladen

Building Your Own AI Instance (TBLC AI )
Building Your Own AI Instance (TBLC AI )Building Your Own AI Instance (TBLC AI )
Building Your Own AI Instance (TBLC AI )Brian Pichman
 
UiPath Platform: The Backend Engine Powering Your Automation - Session 1
UiPath Platform: The Backend Engine Powering Your Automation - Session 1UiPath Platform: The Backend Engine Powering Your Automation - Session 1
UiPath Platform: The Backend Engine Powering Your Automation - Session 1DianaGray10
 
20230202 - Introduction to tis-py
20230202 - Introduction to tis-py20230202 - Introduction to tis-py
20230202 - Introduction to tis-pyJamie (Taka) Wang
 
Bird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemBird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemAsko Soukka
 
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationUsing IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationIES VE
 
How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?IES VE
 
UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6DianaGray10
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...Aggregage
 
Nanopower In Semiconductor Industry.pdf
Nanopower  In Semiconductor Industry.pdfNanopower  In Semiconductor Industry.pdf
Nanopower In Semiconductor Industry.pdfPedro Manuel
 
UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8DianaGray10
 
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...DianaGray10
 
COMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a WebsiteCOMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a Websitedgelyza
 
Empowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintEmpowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintMahmoud Rabie
 
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostKubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostMatt Ray
 
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfUiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfDianaGray10
 
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsIgniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsSafe Software
 
Computer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and HazardsComputer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and HazardsSeth Reyes
 
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDEADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDELiveplex
 
Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024D Cloud Solutions
 

Kürzlich hochgeladen (20)

Building Your Own AI Instance (TBLC AI )
Building Your Own AI Instance (TBLC AI )Building Your Own AI Instance (TBLC AI )
Building Your Own AI Instance (TBLC AI )
 
UiPath Platform: The Backend Engine Powering Your Automation - Session 1
UiPath Platform: The Backend Engine Powering Your Automation - Session 1UiPath Platform: The Backend Engine Powering Your Automation - Session 1
UiPath Platform: The Backend Engine Powering Your Automation - Session 1
 
20230202 - Introduction to tis-py
20230202 - Introduction to tis-py20230202 - Introduction to tis-py
20230202 - Introduction to tis-py
 
Bird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemBird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystem
 
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationUsing IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
 
How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?
 
UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
 
Nanopower In Semiconductor Industry.pdf
Nanopower  In Semiconductor Industry.pdfNanopower  In Semiconductor Industry.pdf
Nanopower In Semiconductor Industry.pdf
 
UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8
 
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
 
COMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a WebsiteCOMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a Website
 
201610817 - edge part1
201610817 - edge part1201610817 - edge part1
201610817 - edge part1
 
Empowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintEmpowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership Blueprint
 
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostKubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
 
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfUiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
 
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsIgniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
 
Computer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and HazardsComputer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and Hazards
 
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDEADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
 
Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024
 

P&msp2010 04 wbs-and-estimation

  • 1. Session 4 WBS, Estimation & Scheduling Emanuele Della Valle http://home.dei.polimi.it/dellavalle
  • 2. Credits 2 This slides are largely based on Prof. John Musser class notes on “Principles of Software Project Management” M t” Original slides are available at http://www.projectreference.com/ htt // j t f / Reuse and republish permission was granted Planning and Managing Software Projects – Emanuele Della Valle
  • 3. Today & Next Week 3 Review Session 3 Work Breakdown Structures (WBS) Estimation Network Fundamentals N t kF d t l PERT & CPM Techniques Gantt Charts This slide set will likely roll-over to next week y Planning and Managing Software Projects – Emanuele Della Valle
  • 4. Session 3 Review 4 Full Lifecycle • Know your pure waterfall, 7 phase model • Understand the steps in each phase • Know the primary issues and goals of each Methodologies • Know a representative sample • Waterfall and variation, 1-2 iterative ones • Learn a bit about XP and other Agile methods Planning (introduction) • Primary Planning Steps • Documents Planning and Managing Software Projects – Emanuele Della Valle
  • 5. Introduction to session 4 and 5 Estimation 5 “Predictions are hard, especially about the future”, Yogi Berra 2 Types: Lucky or Lousy? Planning and Managing Software Projects – Emanuele Della Valle
  • 6. Introduction to session 4 and 5 Planning, Estimating, Scheduling 6 What’s the difference? Plan: Identify activities. No specific start and end dates. Estimating: Determining the size & duration of st at g ete g t e s e du at o o activities. Schedule: Adds specific start and end dates, p , relationships, and resources. Planning and Managing Software Projects – Emanuele Della Valle
  • 7. Introduction to session 4 and 5 Project Planning: A 12 Step Program 7 Set goal and scope Identify tasks Select lifecycle Estimate size Set org./team form Estimate effort Start team selection Identify task dependencies Determine risks Assign resources Create WBS Schedule work Planning and Managing Software Projects – Emanuele Della Valle
  • 8. Introduction to session 4 and 5 How To Schedule 8 1. Identify “what” needs to be done • Work Breakdown Structure (WBS) 2. Identify “how much” (the size) • Size estimation techniques 3. Identify the dependency between tasks • Dependency graph, network diagram 4. Estimate total duration of the work to be done • The actual schedule Planning and Managing Software Projects – Emanuele Della Valle
  • 9. Introduction to session 4 and 5 WBS & Estimation 9 How did you feel when I asked • “How long will your project take?” Not an easy answer to give right? At least not if I were are real customer on a real project How can you manage that issue? y g Planning and Managing Software Projects – Emanuele Della Valle
  • 10. Introduction to session 4 and 5 Partitioning Your Project 10 You need to decompose your project into manageable chunks ALL projects need this step Divide & Co que de Conquer Two main causes of project failure • Forgetting something critical g g g • Ballpark estimates become targets How does partitioning help this? Planning and Managing Software Projects – Emanuele Della Valle
  • 11. Introduction to session 4 and 5 Project Elements 11 A Project: functions, activities, tasks Planning and Managing Software Projects – Emanuele Della Valle
  • 12. Work Breakdown Structure: WBS 12 Hierarchical list of project’s work activities 2 Formats • Outline (indented format) • Graphical Tree (Organizational Chart) Uses a decimal numbering system • Ex: 3.1.5 Includes • Development, Mgmt., and project support tasks Shows “i contained in” relationships Sh “is t i d i ” l ti hi Does not show dependencies or durations Planning and Managing Software Projects – Emanuele Della Valle
  • 13. WBS Contract vs. Project WBS 13 Contract WBS (CWBS) Project WBS (PWBS) • First 2 or 3 levels • Defined by PM and team • Hi h l High-level t l tracking ki members • Tasks tied to deliverables • Lowest level tracking Planning and Managing Software Projects – Emanuele Della Valle
  • 14. WBS A Full WBS Structure 14 Up to six levels (3-6 usually) such as Upper 3 can be used by customer for reporting (if part of RFP/RFQ) Different level can be applied to different uses • Ex: Level 1: authorizations; 2: budgets; 3: schedules Planning and Managing Software Projects – Emanuele Della Valle
  • 15. WBS Chart Example 15 Planning and Managing Software Projects – Emanuele Della Valle
  • 16. WBS Outline Example 16 Retail Web Site 1.0 Project Management 2.0 Requirements Gathering 3.0 Analysis & Design 4.0 4 0 Site Software Development 4.1 HTML Design and Creation 4.2 Backend Software 4.2.1 Database Implementation 4.2.2 Middleware Development 4.2.3 Security Subsystems 4.2.4 Catalog Engine 4.2.5 4 2 5 Transaction Processing 4.3 Graphics and Interface 4.4 Content Creation 5.0 Testing and Production Planning and Managing Software Projects – Emanuele Della Valle
  • 17. WBS Types 17 Process WBS • a.k.a Activity-oriented • Ex: Requirements Analysis Design Testing Requirements, Analysis, Design, • Typically used by PM Product WBS • a.k.a. Entity-oriented • Ex: Financial engine, Interface system, DB • Typically used by engineering manager Hybrid WBS: both above • This is not unusual • Ex: Lifecycle phases at high level with component or feature-specifics within phases • Rationale: processes produce products Planning and Managing Software Projects – Emanuele Della Valle
  • 18. WBS Product WBS 18 Planning and Managing Software Projects – Emanuele Della Valle
  • 19. WBS Process WBS 19 Planning and Managing Software Projects – Emanuele Della Valle
  • 20. WBS Outline WBS with Gantt Chart 20 Planning and Managing Software Projects – Emanuele Della Valle
  • 21. WBS WBS by PMI Process Groups 21 Planning and Managing Software Projects – Emanuele Della Valle
  • 22. WBS Less Frequently Used Alternatives 22 Organizational WBS • Research, Product Design, Engineering, Operations • Can be useful for highly cross functional projects cross-functional Geographical WBS • Can be useful with distributed teams • NYC team, San Jose team, Off-shore team Planning and Managing Software Projects – Emanuele Della Valle
  • 23. WBS Work Packages 23 Generic term for discrete tasks with definable end results Typically the “leaves” on the tree The “one-to-two” rule e o e to t o u e • Often at: 1 or 2 persons for 1 or 2 weeks Basis for monitoring and reporting p g g p g progress • Can be tied to budget items (charge numbers) • Resources (personnel) assigned Ideally shorter rather than l d ll h h h longer • Longer makes in-progress estimates needed • These are more subjective than “done” j • 2-3 weeks maximum for software projects • 1 day minimum (occasionally a half day) • Not so small as to micro-manage micro manage Planning and Managing Software Projects – Emanuele Della Valle
  • 24. WBS Wrap Up (so far) 24 List of Activities, not Things List of items can come from many sources • SOW, Proposal, brainstorming, stakeholders, team Describe activities using “bullet language” g g g • Meaningful but terse labels All WBS paths do not have to go to the same level Do not plan more detail than you can manage Planning and Managing Software Projects – Emanuele Della Valle
  • 25. WBS WBS & Chosen Lifecycle 25 PM must map activities to chosen lifecycle Each lifecycle has different sets of activities Integral process activities occur for all • Planning, configuration, testing g, g , g Operations and maintenance phases are not normally in plan ( p (considered p post-project) p j ) Some models are “straightened” for WBS • Spiral and other iterative models • Linear sequence several times Deliverables of tasks vary by chosen lifecycle Planning and Managing Software Projects – Emanuele Della Valle
  • 26. WBS Techniques 26 Top-Down Bottom Up Bottom-Up Analogy Brainstorming B i t i • Post-its on a wall Rolling Wave • 1st pass: go 1-3 levels deep • Gather more requirements or data • Add more detail l d il later Planning and Managing Software Projects – Emanuele Della Valle
  • 27. WBS -Techniques Top-down 27 Start at highest level Systematically develop increasing level of detail Best if • The problem is well understood p • Technology and methodology are not new • This is similar to an earlier project or problem But is also applied in majority of situations Planning and Managing Software Projects – Emanuele Della Valle
  • 28. WBS -Techniques Bottom-up 28 Start at lowest level tasks Aggregate into summaries and higher levels Cons • Time consuming g • Needs more requirements complete Pros • Detailed Planning and Managing Software Projects – Emanuele Della Valle
  • 29. WBS -Techniques Analogy 29 Base WBS upon that of a “similar” project Use a template Analogy also can be estimation basis Pros P • Based on past actual experience Cons • Needs comparable project Planning and Managing Software Projects – Emanuele Della Valle
  • 30. WBS -Techniques Brainstorming 30 Approach • Generate all activities you can think of that need to be done • Group them into categories Both Top-down and Brainstorming can be used on the Top down same WBS Remember to get the p p who will be doing the g people g work involved (buy-in matters!) Planning and Managing Software Projects – Emanuele Della Valle
  • 31. WBS WBS are Basis of Many Things 31 Network scheduling Costing Risk analysis Organizational structure O i ti l t t Control Measurement Planning and Managing Software Projects – Emanuele Della Valle
  • 32. WBS Guidelines Part 1 32 Should be easy to understand Some companies have corporate standards for these schemes So e top e e te s, e oject g t a e Some top-level items, like Project Mgmt. are in WBS S for each project • Others vary by project What often hurts most is what’s missing Break down until you can generate accurate time & cost estimates Ensure each element corresponds to a deliverable Planning and Managing Software Projects – Emanuele Della Valle
  • 33. WBS Guidelines Part 2 33 How detailed should it be? • Not as detailed as the final MS-Project plan • Each level should have no more than 7 items • It can evolve over time What tool should you use? • Excel, Word, Project • Org chart diagramming tool (Visio, etc) • Specialized commercial apps Re-use a “template” if you have one Planning and Managing Software Projects – Emanuele Della Valle
  • 34. Estimations Introduction 34 Very difficult to do, but needed often Created, used or refined during • Strategic planning • Feasibility study and/or SOW • Proposals • Vendor and sub-contractor evaluation • Project planning (iteratively) Basic process • Estimate the size of the product • Estimate the effort (man-months) • Estimate the schedule • NOTE: Not all of these steps are always explicitly performed Planning and Managing Software Projects – Emanuele Della Valle
  • 35. Estimations Introduction (cont.) 35 Remember, an “exact estimate” is an oxymoron Estimate how long will it take you to get home from class tonight • On what basis did you do that? • Experience right? • Likely as an “average” probability • For most software projects there is no such ‘average’ Most software estimations are off by 25-100% Planning and Managing Software Projects – Emanuele Della Valle
  • 36. Estimations Target vs. Committed Dates 36 Target: • Proposed by business or marketing • Do not commit to this too soon! Committed: • Team agrees to this • After you’ve developed a schedule Planning and Managing Software Projects – Emanuele Della Valle
  • 37. Estimations Cone of Uncertainty 37 Planning and Managing Software Projects – Emanuele Della Valle
  • 38. Estimations Size 38 Small projects (10-99 FPs), variance of 7% from post- requirements estimates Medium (100-999 FPs), 22% variance Large (1000-9999 FPs) 38% variance a ge ( 000 9999 s) a a ce Very large (> 10K FPs) 51% variance Planning and Managing Software Projects – Emanuele Della Valle
  • 39. Estimations - Size Methodologies 39 Top-down Bottom up Bottom-up Analogy Expert J d E t Judgment t Priced to Win Parametric or Algorithmic Method • Using formulas and equations Planning and Managing Software Projects – Emanuele Della Valle
  • 40. Estimations - Size Top-down Estimation 40 Based on overall characteristics of project • Some of the others can be “types” of top-down (Analogy, (Analogy Expert Judgment and Algorithmic methods) Judgment, Advantages • Easy to calculate • Effective early on (like initial cost estimates) Disadvantages g • Some models are questionable or may not fit • Less accurate because it doesn’t look at details Planning and Managing Software Projects – Emanuele Della Valle
  • 41. Estimations - Size Bottom-up Estimation 41 Create WBS Add from the bottom-up bottom up Advantages • Works well if activities well understood Disadvantages • Specific activities not always known • More time consuming Planning and Managing Software Projects – Emanuele Della Valle
  • 42. Estimations - Size Expert Judgment 42 Use somebody who has recent experience on a similar project You get a “guesstimate” Accuracy depends on their ‘real’ expertise ccu acy depe ds o t e ea e pe t se Comparable application(s) must be accurately chosen • Systematic y Can use a weighted-average of opinions Planning and Managing Software Projects – Emanuele Della Valle
  • 43. Estimations - Size Estimation by Analogy 43 Use past project • Must be sufficiently similar (technology, type, organization) • Find comparable attributes (ex: # of inputs/outputs) • Can create a function Advantages • Based on actual historical data Disadvantages • Difficulty ‘matching’ project types • Prior data may have been mis-measured mis measured • How to measure differences – no two exactly same Planning and Managing Software Projects – Emanuele Della Valle
  • 44. Estimations - Size Priced to Win 44 Just follow other estimates Save on doing full estimate Needs information on other estimates (or prices) Purchaser must closely watch trade-offs P h t l l t ht d ff Priced to lose? Planning and Managing Software Projects – Emanuele Della Valle
  • 45. Estimations - Size Algorithmic Measures 45 Lines of Code (LOC) Function points Feature points or object points Other Oth possible ibl • Number of bubbles on a DFD • Number of of ERD entities • Number of processes on a structure chart LOC and function points most common • ( f the algorithmic approaches) (of h l ih i h ) Majority of projects use none of the above Planning and Managing Software Projects – Emanuele Della Valle
  • 46. Estimations - Size Code-based Estimates 46 LOC Advantages • Commonly understood metric • Permits specific comparison • Actuals easily measured LOC Disadvantages • Difficult to estimate early in cycle • Counts vary by language • Many costs not considered (ex: requirements) • Programmers may be rewarded based on this – Can use: # defects/# LOC • Code generators produce excess code Planning and Managing Software Projects – Emanuele Della Valle
  • 47. Estimations - Size LOC Estimate Issues 47 How do you know how many in advance? What about different languages? What about programmer style? Stat: St t avg. programmer productivity: 3 000 LOC/yr d ti it 3,000 LOC/ Most algorithmic approaches are more effective after requirements (or have to be after) Planning and Managing Software Projects – Emanuele Della Valle
  • 48. Estimations - Size Function Points 48 Software size measured by number & complexity of functions it performs More methodical than LOC counts House analogy ouse a a ogy • House’s Square Feet ~= Software LOC • # Bedrooms & Baths ~= Function points • Former is size only, latter is size & function only Three basic steps Planning and Managing Software Projects – Emanuele Della Valle
  • 49. Estimations - Size Function Point Process 49 1. Count # of biz functions per category • Categories: outputs, inputs, db inquiries, files or data structures, structures and interfaces 2. Establish Complexity Factor for each and apply • Simple, Average, Complex • Set a weighting multiplier for each (0->15) • This results in the “unadjusted function-point total” 3. Compute an “influence multiplier” and apply • It ranges from 0.65 to 1.35; is based on 14 factors 4. Results in “function point total” • This can be used in comparative estimates Planning and Managing Software Projects – Emanuele Della Valle
  • 50. Estimations - Size Wideband Delphi 50 Group consensus approach Rand corp. (http://www.rand.org/) used orig. Delphi approach to predict future technologies Present experts with a problem and response form ese t e pe ts t p ob e a d espo se o Conduct group discussion, collect anonymous opinions, then feedback Conduct another discussion & iterate until consensus Advantages • Easy, inexpensive, utilizes expertise of several people • Does not require historical data Disadvantages • Difficult to repeat • Ma fail to reach consensus, reach wrong one, or all may May ea h onsens s ea h ong one o ma have same bias Planning and Managing Software Projects – Emanuele Della Valle
  • 51. Estimations - Size Parametric Method Issues 51 Remember: most projects you’ll run into don’t use these Which is ‘normal’, so don’t be surprised • Or come-in to new job and say “Hey, let’s use COCOMO” These are more effective on large projects • Where a past historical base exists Primary issue for most projects are • Lack of similar projects – Thus lack of comparable data Catch-22: how to get started • See http://en.wikipedia.org/wiki/Catch-22_( g ) p // p g/ / (logic) Planning and Managing Software Projects – Emanuele Della Valle
  • 52. Estimations - Size Code Reuse & Estimation 52 Does not come for free Code types: New, Modified, Reused If code is more than 50% modified, it’s “new” Reuse f t R factors have wide range h id • Reused code takes 30% effort of new • Modified is 60% of new Integration effort with reused code almost as expensive as with new code Planning and Managing Software Projects – Emanuele Della Valle
  • 53. Estimations Effort Estimation 53 Now that you know the “size”, determine the “effort” needed to build it Various models: empirical, mathematical, subjective Expressed in units of duration p essed u ts o du at o • Person-Months Planning and Managing Software Projects – Emanuele Della Valle
  • 54. Estimations Effort Estimation 54 McConnell shows schedule tables for conversion of size to effort As with parametric size estimation, these techniques perform better with historical data Again, not seen in ‘average’ projects Often the size and effort estimation steps are p combined (not that this is recommended, but is what often is done) “Commitment-Based” Scheduling is what is often done • Ask developer to ‘commit’ to an estimate (his or her own)) Planning and Managing Software Projects – Emanuele Della Valle
  • 55. Estimations - Efforts ECOCOMO 55 COnstructive COst MOdel Allows for the type of application, size, and “Cost Cost Drivers” Outputs in Person Months e so o t s Cost drivers using High/Med/Low & include • Motivation • Ability of team • Application experience Biggest weakness? k ? • Requires input of a product size estimate in LOC Planning and Managing Software Projects – Emanuele Della Valle
  • 56. Estimations Issues 56 Quality estimations needed early but information is limited Precise estimation data available at end but not needed • O is it? What about the next project? Or abo t ne t p oje t? Best estimates are based on past experience Politics of estimation: • You may anticipate a “cut” by upper management For many software projects there is little or none • Technologies change • Historical data unavailable • Wide variance in project experiences/types • Subjective nature of software estimation Planning and Managing Software Projects – Emanuele Della Valle
  • 57. Estimations - Issues Over and Under Estimation 57 Over estimation issues • The project will not be funded – C Conservative estimates guaranteeing 100% success may ti ti t t i mean funding probability of zero. • Parkinson’s Law: Work expands to take the time allowed • D Danger of feature and scope creep ff d • Be aware of “double-padding”: team member + manager Under estimation issues • Quality issues (short changing key phases like testing) • Inability to meet deadlines • Morale and other team motivation issues Planning and Managing Software Projects – Emanuele Della Valle
  • 58. Estimations Estimation Guidelines 58 Estimate iteratively! • Process of gradual refinement • Make your best estimates at each planning stage • Refine estimates and adjust plans iteratively • Plans and decisions can be refined in response • Balance: too many revisions vs. too f l few Planning and Managing Software Projects – Emanuele Della Valle
  • 59. Estimations Know Your Deadlines 59 Are they ‘Real Deadlines’? • Tied to an external event • Have to be met for project to be a success • Ex: end of financial year, contractual deadline, Y2K Or ‘Artificial Deadlines’? Artificial Deadlines ? • Set by arbitrary authority • May have some flexibility (if pushed) Planning and Managing Software Projects – Emanuele Della Valle
  • 60. Estimations “Presentation” 60 How you present the estimation can have huge impact Techniques • Plus-or-minus qualifiers – 6 months +/-1 month • Ranges – 6-8 months • Risk Quantification – +/- with added information – +1 month of new tools not working as expected – -2 weeks for less delay in hiring new developers 2 • Cases – Best / Planned / Current / Worst cases • Coarse Dates – Q3 2009 • Confidence Factors – April 1 – 10% probability, July 1 – 50%, etc. Planning and Managing Software Projects – Emanuele Della Valle
  • 61. Estimations Other Estimation Factors 61 Account for resource experience or skill • Up to a point • Often needed more on the “low” end, such as for a new end or junior person Allow for “non-project” time & common tasks non project • Meetings, phone calls, web surfing, sick days There are commercial ‘estimation tools’ available • They typically require configuration based on past data Planning and Managing Software Projects – Emanuele Della Valle
  • 62. Estimations Other Estimation Notes 62 Remember: “manage expectations” Parkinson s Parkinson’s Law • “Work expands to fill the time available” The Student Syndrome y • Procrastination until the last minute (cram) Planning and Managing Software Projects – Emanuele Della Valle
  • 63. Optional Reading 63 McConnell: 9, “Scheduling” Schwalbe: 5, “Project Time Management” Project Management URLs: See projectreference.com on “PERT/CPM” • http://www.projectreference.com/#PERT p // p j / Planning and Managing Software Projects – Emanuele Della Valle
  • 64. Homework – 2: WBS 64 Create a WBS for your project • Please think this through. You’re the PM now! Guidelines • Do it at managerial level (see slide 14) – 4 7 nodes at 1st level 4-7 – 2-5 nodes at 2nd level (per each node at 1st level) – You can go deeper at your discretion. • As we covered in class, you can use either a process, product or hybrid approach. – For most of your projects I suspect the process approach would work best at managerial level. • Follow the standard hierarchical numbering scheme for WBS structures. • Use the Word template of homework–1 – Keep only the coversheet – Update the title to “homework – 2 : WBS“ homework WBS • Submit to mpsp2010@gmail.com as you did with homework-1 Planning and Managing Software Projects – Emanuele Della Valle
  • 65. Questions? 65 Planning and Managing Software Projects – Emanuele Della Valle