Please enable JavaScript.
Coggle requires JavaScript to display documents.
Initiate Information System Solutions ((Project Characteristics (Project…
Initiate Information System Solutions
Question 2: What are the reasons for so many roles and responsibilities in IT projects?
Identify priorities of stakeholders
limiting the risks that may occur in project
to ensure that work is completed on time, achieve specific objectives of the project and its goals.
rational use of resources
Overview of Information System
User Requirements
What users will be able to do?
Systems Requirements
What system need to be needed?
Business needs
Why the system is needed?
System Requirements
What software need to be developed?
Project Life Cycle
5 phases
Execution Phase
mitigate project risks
manage
project perfomance
project intergration
Control Phase
To track progress against the plan
take corrective action
Closure Phase
Planning Phase
Determine
Project Scope
Resources
How to control
Actions to achieve Project objectives
Initiation Phase
To gain understand and define important aspect of the project
Confirm project understanding
Takk backage
Determine stakeholder's expectations
Revew decision boards
Collect and review Project information
Prepare to start
Project Manager
Describe
the rationale
the vision of the information system
business needs
work with Business Manager
solve Business Problems for the users from the business point of view
define the sucess criteria
Question 1: What are the advantages of following the Information System phases? Why don‘t we just use the project management life cycle phases?
Why don‘t we just use the project management life cycle phases?
Project activities must be grouped into phases
=> Project managers to efficiently plan and
organize resources for each activity.
Project managers can objectively measure achievement
of goals and justify their decisions to proceed, correct, or
terminate.
A logical sequence of activities to accomplish the
project’s goals or objectives.
What are the advantages of following the Information System phases?
help management to make a decision whether
to initiate the project or to cancel it.
An evaluation of benefits, costs and risks, with a
recommendation for go/no-go decision.
Solution Recommendation Task Package.
Effective Communication Early
he timely generation and dissemination of project information
Communication provides the critical links
share information,and understand how the communications
Document The Task Package
project manager's understanding of the
project is accurate
could decide to launch the project
project manager's understanding of the project, requirement
Project manager write understanding of the project in “Project requirements Task package
Project Characteristics
Availability of users to participate in project.
Availability of users to participate in project
Project structure
Project team’s knowledge & skills –experience with method,
tools, domain, platform, development environment.
Technology –new or old
Priority of project
high, middle, low
Quality issues
security, severity
External drivers
Confirm Project Requirements
This activity occurs before any project planning is
started.
The key objective is to confirm project’s goals and
business needs to ensure that project managers
understand what must be done to implement project
successfully.
Project Requirements Document
The description of the goals and objectives of the
proposed solution that will be implemented as a project,
its high-level features, required efforts, and costs
The description of the overview of the project.
The business needs and the information system solution
The management & customers approval and
commitment.
Benefits
Scope, functionalities, issues, and risks will be managed
accordingly.
To review project requirements based on the project
manager’s view before approval of the project launch.
To document project manager's understanding of the
project’s requirements.
Why Requirements Document?
Allows project manager
Provides management an information system
Identifies approach
Requirements Document
The “task package” prepared by the project manager
Can be presented to stakeholders:)
• Business manager
• Customers
• Users
• External suppliers (if needed)
To gain mutual understanding on some important
aspects of the project.
Problem Recognition
A brief description of the problem.
A description of the available technologies and information system
Answer the question, "Does the system make business sense?
A preliminary proposal of benefits, costs.
Information Gathering & Analysis
A review of the information system
A definition of the information system solution the new system works
A review of the current information system.
Identification alternative solutions other off-the-shelf components
A proposal “Task Package” to management
An evaluation of benefits, costs and risks
Pre-Project Activities
Consider to the solution is technically feasible, management support
Gathering information to conduct a feasibility analysis
Project managers want to understand other factors effect the proposed project
Make a decision: initiate or cancel
Solution Recommendation
Overview
Problem Description
Business Goals & Objectives
Critical Aspect
Needs Description
Technology Solutions
Recommendation
Management Decision
Made
Initiate Project
No go
Not Approde
Buy
Purchase Solution from outside
The Approach
project manager can incrementally build the information
system according to a project plan
allows organizations to:
Validate results and make required adjustments
Easily refine and change according to user needs
Execute certain activities in parallel
Show “tangible results” earlier
Reduce risks
Requirements
A condition or capability needed
by a customer => to solve
a problem or achieve an objective.
by a system or system component => to satisfy a contract,
standard, specification, or other formally imposed
document.
Before starting, project managers must
confirm all the important information of the project
understand the context in which it will be implemented.
Understand The Requirements
Project objectives
Project background
Business information
People information
Technical information
Project conditions
Interface with other projects
Project characteristics
Major milestones and task packages
Allocated budget
Suppliers and subcontractors
Assumptions
is a situation that a project manager is
aware of
BUT Could not confirm
Some assumptions may turn into project risks
Limitations
are known situations to impact the
project team’s capacity of achieving the goals.
Some limits may turn into issues.
Known issues must be solved in the planning phase.
