WHO SHOULD ATTEND
Individuals attending this facilitated session are involved in one or more of the areas below:
-
System development staff.
-
Project managers.
-
Business clients.
-
Business and IT managers.
WHAT THE SESSION PROVIDES
By not
having a methodology, system development and project
management jump into implementation, which does not
encourage alignment to the business. Use of a methodology
encourages application of technology, client involvement and
strategic planning.
WHAT PARTICIPANTS LEARN
After attending this session, the participants will be able to:
-
Identify
the reasons for a methodology.
-
Define the phases of the methodology.
-
Associate each phase with a deliverable built by tools
and techniques.
-
Define the purpose behind deliverables.
-
Explain the difference between system development and
project management.
- List
the resources available to help with development and
documentation.
|
|
Why a Methodology?
•
Problems With Traditional
Approach
•
Components that Make It Work
Building a New System
•
Planning
•
Analysis
•
Design
•
Development
•
Installation
•
Maintenance
•
Tools and Techniques
Project Management
•
Distinct from System Development
•
Responsibilities
•
Roles
Tools and
Techniques
•
Planning
•
Analysis
•
Design
•
Project Management
Exercises
|
|
