Information System Project Management

1
Information System Project Management

• Ayssar Midani
• Consultant strategy organization
• of information systems

2


Information System Project Management

• Phases of an IS project
• Preliminary study
• General Design
• Detailed design
• Implementation
• Acceptance and launch
• Pilote experience
• Production
• Maintenance evolution

3

IS Project management Preliminary study

• Define the scope and the goals of the IS project
• Define the requierement for Proposal
• Choose subcontractor
• Software Package selection
• Define methodological basis of the project
• New process new organization

4

• Functional study
• Architecture definition modeling (database,
  distributed system, internet, servers,
  communication )
• Organization data model

5
IS Project management General Design

• Implementation of chosen methodology
• Detailed analysis of needs
• Data process definition modeling
• Data dictionary (conceptual models)

6
IS Project management General Design

• Collaborative work functional experts software
  designer
• Design Tools requierd
• Extreme consistency requiered (Data
  administration )
• Expert validation requierd

7
IS Project management Software Detailed design

• Data logical Model (database schema, constraints
  )
• Data processing logical model and time
  constraints
• Implementation constraints (progiciel or database)

8
IS Project management Software Detailed design

• Description of historization (archives )
• Data Volume study (database, network, archives)
• Software specifications

9
IS Project management Software Detailed design

• Communication model
• Interface definition
• Whith other systems, applications
• Data flow
• Data processing
• Timing scheduling

10
IS Project management Software Detailed design

• System initiatialization specifications
• How? When? which tools?
• From where ?
• which correction rules ?
• Constraints

11
IS Project management Software Detailed design

• Organization questions (who recycles functional
  errors,system errors? Functional help desk?
  Technical help desk? )
• Program scheduling
• Definition of back up periodicity and objects
  (tools)

12
IS Project management Software Detailed design

• Rights and confidentiality definition
• Who owns the data
• Who creates, modify, suppress it in the IS?
• Users groups definition
• Implementation in DD(tools?)
• in each phase

13
IS Project management Software Detailed design

• Last step of analysis
• Validation of the sponsor and the deciders is
  requiered ?important steering committe
• Last possibility for modification ?versioning

14
IS Project management Software Detailed design

• Integration of new rules is already expensiv, but
  later it is much more (X10)

15
IS Project management Software Detailed design

• See whats missing? Have we forgot any process?
  Any data for Working process, reports, editions,
  data for decision making?

16
IS Project management New organization
preparation

• The end of software detailed design phase is the
  beginning of many other sub-projects in parallel
• System initialization operations or/and tools
  development (different scenarii)

17
IS Project management New organization
preparation

• Users education (new management rules and
  software)
• Network building
• Organization representation and coding
• Ergonomy studies

18
IS Project management New organization
preparation

• Technical performance benchmarking
• Physical work position preparation (desks, lamps,
  computers, )
• System security studies
• help-desk job definition recruetement education

19
IS Project management New organization
preparation

• Futur Information system manager team job
  definition, recruitement education
• Communication about the project
• To the direction
• To the pilote experience sites
• To futur users
• To other teams for interface

20
IS Project management New organization
preparation

• Tools to follow up the pilot experience
  deployment
• Communication education to pilote sites
• Training organization plan
• Training Database deployment
• Documents for users

21
IS Project management New organization
preparation

• Documentation sub-project(on line or on paper
• Users manual, at each level
• Education cases
• Functional new rules
• For IS managers
• For maintenance

22
IS Project management New organization
preparation

• Testing sub-project
• Protocoles and scenarii for testing (functional)
• Testing tools setting
• Testers education
• Tools for the testing, follow up
• Follow up of anomlies
• Software Quality evaluation
• Technical performance

23
IS Project managementRealization phase

• Active phase for software engineers
• Specs realizations
• Database setting (or ERP software)
• Transactions development
• Unitary tests
• Integration and system management
• Different parts of the software
• Integration test
• ? Software delivery

24
IS Project management Acceptance phase

• Who accepts
• Key users
• Functionnal experts
• According to protocoles and scenarii already
  written respecting testing method
• Testing tools
• Testing follow up
• Everyday or 2 days meeting with realizer

25
IS Project management Acceptance phase

• Who accepts
• Conflict for acceptance
• Old system does not give the same results
• Which is right? Wrong ?
• .
• old system have some errors but peoples lived
  with
• Continue or no?

26
IS Project management Acceptance phase

• Preparation for users training
• key users are the system ambassadors
• Instruction cases design implementation
• Functionnal experts for futur help desk
• Instructors to other experts and users

27
IS Project management Acceptance phase

• Critical very important phase
• Tests must be very complete for all business
  processes
• Test general and exceptionnal cases
• Verify calculation rules
• Errors processing recyclingretesting
• ? Software acceptance

28
IS Project management Launch pilote experience

• What is pilote experience?
• GO live on One or several sites for limited time
  3 or 6 months
• New process
• New organization
• Managers
• Users
• Assistance
• Information system Managers

29
IS Project management Launch pilote experience

• Normal size
• Data and volume
• Data recycling
• Initialisation process
• Interface
• Education
• Documentation

30
IS Project management Launch pilote experience

• Users verify data results
• Work in double old and new system
• Follow up of anomalies
• Immediat correction for blocking anomalies
• Later for the others (version to be generalized)

31
IS Project management Launch pilote experience
results

• Recommandation for generalization
• New process
• Organization
• Education training

32
IS Project management Launch pilote experience
results

• Communication
• Documentation
• Software quality at work
• Software performance
• Network quality
• .

33
IS Project management Launch pilote experience
results

• Precise results presentation
• Software quality
• Software appropriation
• Data quality
• Interface
• Users satisfaction

34
IS Project management Launch pilote experience

• Finishing phase
• Last errors corrections optimization
• New version for generalization
• Testing Acceptance
• Documentation Packaging
• New organization adjustment
• Education training adjustment

35
IS Project management Go live

• Big bang
• All the sites at a time
• via internet
• Attention to data
• Progressive go live
• 1,2,3 sites at a time

36
IS Project management Go live

• Follow up
• Quality indicators
• End users satisfaction inquiry every 2,3 months

37
1IS Project managementEnding the project

• Human ressource deployment
• Propose an alternative for each of the team
  members
• Give the new managers and users the opportunity
  to take their new situation in hand
• Inquire about their satisfaction regularly

38
(No Transcript)
39
IS Project managementmaintenance and upgrade

• The new team will take in hand the aspects of
  maintenance
• New versions
• New legistlations
• New rules
• . Are diffrent little/or big projects
• Diffrent budget
• Different contract mostly

40
IS Project management Key points Conclusions

• Change management is an important part of IS
  projects
• Conflict solutions
• Risk management minimize risks
• Anticipation of phases
• Regular follow up tools care
• Clear expression of difficulties solutions

41
IS Project management Key points Conclusions

• Information management
• Deliveries identification and schedulling
• Configuration management and methodology
• Synchronisation points
• Workflow, documentation,information consistency

42
IS Project management Key points Conclusions

• De cisions making
• Steering committe or project committee
• Strategic tactic decisions
• Decision process identify decision point,
  prepare information for decision, decide and
  follow application

43
Questions ?