Please enable JavaScript.

Coggle requires JavaScript to display documents.

Lecture 3 ((29-35) (Project Characteristics (Relationship between project…

- - - - Review with decision board
      - Deliver project requirements “Task package”
      - Confirm project understanding
      - Determine stakeholders’ expectations
      - Collect & review project information
      - Prepare to start project
- - - - A review of the current information system.
      - Identification alternative solutions and other off-the-shelf components (Made/Buy decision).
      - A definition of the information system solution and how the new system works with the current system.
      - A proposal “Task Package” to management for approval to proceed to the next phase.
      - An evaluation of benefits, costs and risks, with a
        recommendation for go/no-go decision.
    - - A description of the available technologies and information system that could solve the needs
      - A vision of the new system that can answer the question, "Does the system make business sense?”
      - A brief description of the problem
      - A preliminary proposal of benefits and costs.
- - - - A brief description of the problem.
        A description of the available technologies and information
        system that could solve the needs.
        A vision of the new system.
        A preliminary proposal of benefits and costs.
    - - A review of the current information system.
        A definition of the information system solution and how the new
        system works with the current system.
        Identification alternative solutions and other off-the-shelf
        components
        A proposal “Task Package” to management for approval to
        proceed to the next phase.
        An evaluation of benefits, costs and risks, with a
        recommendation for go/no-go decision
    - - A description of critical features of the new system.
        An initial architecture of the new system.
        An assessment of the feasibility of the solution.
        An estimate of the costs and benefits of the new system.
    - - Provide overview architecture for the system.
        Prototype some key components.
        Select off-the-shelf software components (if needed).
        Identify and design system components.
        Revise strategies and plans for design, construction and
        implementation.
        Confirm the feasibility of the solution.
    - - Construct system components for each release.
      - Test and verify each system component.
      - Update system architecture and integrate with previously released components.
      - Complete integration and verification.
      - Revise & update implementation plan.
      - Training users.
      - Convert data and install new release system.
      - Release in production.
    - - Production environment
      - Production release
      - Inform and train users
- - - - What criteria will be used to measure success ?
      - How they will be measure ?
    - - Rationale
      - Business needs
    - - Participants
      - Subject area, coverage, boundaries
      - Goals and expectations
    - - Costs
      - Schedule
      - Benefits
      - Budget
- - - - Development & maintenance to meet the stakeholders’ requirements
    - - Application of knowledge, skills, tools, and techniques to manage the software process to meet stakeholders’ expectations.
  - - - Executing
        
        Manage the process defined to deliver the product
        
        Effectively mitigate project risk
        
        Measure project performance
        
        Manage project performance
        
        Manage project integration with others
      - Controlling
        
        Track progress against the plan
        
        Take corrective actions when there are deviations from the plan
      - Planning
        
        Actions required to achieve project objectives
        
        Resources needed
        
        Means to control the execute project
        
        Project scope
      - Initiating
        
        Gain an understanding of all important aspects
        
        Define high level structure & roles and responsibilities
      - Closing
        
        Conclude the business relationship in the context of the project
      - PM Body of Knowledge is a framework describing PM in terms of knowledge and practice according to processes.