Please enable JavaScript.

Coggle requires JavaScript to display documents.

scheduling (Budget vis a vis schedule (During the project execution, the…

- - - - Individual components of a project
      - and their relationships with each other in a hierarchical manner, either graphically or in a table.
  - - - a work breakdown structure (WBS) is designed to structure all the tasks that are necessary to build up the elements of the OBS during the project.
    - - project sponsor,
      - project manager and
      - project team members.
    - - Each WP must have a distinct owner and a list of main objectives and may have a list of additional objectives and out-of-scope objectives
        
        WP specifications should include dependencies on other WPs and a definition of how to evaluate performance and goal achievement.
    - - • The top WBS level represents the final deliverable or project.
      - • Sub deliverables contain WPs that are assigned to an organization’s department or unit. #
      - • WPs are unique and should not be duplicated across the WBS.
      - • All elements of the WBS do not need to be defined to the same level.
      - • WPs define the work, duration and costs for the tasks required to produce the subdeliverable.
      - • WPs should not exceed a duration of 10 days.
      - • WPs need to be independent of each other in the WBS.
- - - - • Earliest start date, by considering the logical sequential relationship among tasks and attempting to perform tasks in parallel, wherever possible
      - • Latest expected finish date, by considering the estimate of hours per the budget and the expected availability of personnel or other resources, and allowing for known, elapsed-time considerations (e.g., holidays, recruitment time, full-time/part-time employees)
  - - - a project = network
        activities = branches connected at nodes immediately preceding and immediately following activities
        
        path through the network is any set of successive activities that go from the beginning to the end of the project.
        
        Critical
        
        is the sequence of activities that produces the longest path
        through a project.
        
        are important because, if everything goes according to schedule, they help estimate the shortest possible completion time for the overall project.
        
        do not have slck time
        
        non critical
        
        have slack time
        
        Activity associated with number which shows that
        best estimates the amount of time the activity will consume.
    - - PERT is a CPM-type technique that uses three different estimates of each activity duration
        
        best-case (optimistic) scenario
        
        worst-case (pessimistic) scenario
        
        most likely scenario
        
        three estimates are reduced to a single number (by applying a mathematical formula), and then the classic CPM algorithm is applied.a
      - When designing a PERT network for system development projects, the first step is to
        
        identify all the activities
        
        list of activities
        determines the detail of the PERT network
        
        related events/milestones of the project
        
        their relative sequence.
      - PERT is often used in system development projects with uncertainty about the duration (e.g., pharmaceutical research or complex software development)
      - advantage of PERT over CPM in the example provided is that the
        formula is based on the reasonable assumption
    - - charts show
        
        when an activity should begin and when
        it should end along a timeline.
        
        which activities can occur concurrently and which must be completed sequentially.
        
        resources assigned to each task and by what percent allocation,
      - Advantages
        
        aid in scheduling the activities (tasks) needed to
        complete a project.
        
        aid in identifying activities that have been completed early or late by comparison to a baseline.
        
        By comparing to base line, it is determined whether the project is behind, ahead or on schedule
        
        used to track the achievement of milestones or significant accomplishments for the project such as the end of a project phase or completion of a key deliverable
    - - used to accomplish prototyping or rapid application development-type approaches in which key features are to be delivered in a short time frame
      - project management technique for defining and deploying software deliverables within a relatively short and fixed period of time and with predetermined specific resources.
      - is a need to balance software quality and meet the delivery requirements within the timebox.
      - advantage
        
        prevents project
        cost overruns and delays from scheduled delivery.
      - Preparation of test cases and testing requirements are easily
        written down as a result of end-user participation.
        
        System test and user acceptance testing (UAT) are normally performed together.