Page 105 - DCAP304_DCAP515_SOFTWARE_PROJECT_MANAGEMENT
P. 105

Unit 5: Project Approach




          chosen  according to  environment and  the type of  project  being undertaken.  Approaches  Notes
          should be chosen according to:

              How well understood the objectives are (by the client and the team)
              How stable the technology is (well proven or need testing and adaptation)
              How experienced the team is (in the technology, in development and in understanding
               the objectives set by the organizations management)

              How much control management want.
          Generic Project Phases
          1.   Initiation/Analysis
          2.   Design

          3.   Construction/Implementation/Execution/Coding
          4.   Testing/Pilot/Debugging/Verification)
          5.   Deployment
          6.   Review & Maintenance

          Approach Overviews
              Waterfall: Waterfall has extremely strict separate stages, with no overlap, and high levels
               of planning and process control. This is suitable for projects with a well understood scope
               that can be built using proven technology, before it goes out of date. For example, this is
               the favored approach in the construction industry.

              Iterative: In iterative the team produces succeeding releases that eventually evolve into a
               complete product. This is a good approach when there  are many unknowns, or when
               speed is of the essence. This might be a good approach to implementing a leading edge
               product or developing for a user who is not sure what they want.

              Agile: Agile is the same as Iterative but with particularly small/fast releases in a high
               performance  environment  with  low  levels  of  process  control.  Good for  motivated
               experienced teams with strict deadlines and  good understanding of the organisation’s
               strategy.
          The project approach should also list exact tools or techniques that are not part of the project
          management framework or not included in the approved information management technology list.
          The approach should be based on the decided information management project methodology.




             Notes  Managed exceptions to the approved methodology should be documented in the
             project management approach.

          The project management approach should comprise the following key tasks or phases:

          Business Case Analysis

          The objective of the business case analysis phase is to determine the business case for investing
          in a  data warehouse or business intelligence solution.   It identifies the  projected return  on
          investment.





                                           LOVELY PROFESSIONAL UNIVERSITY                                   99
   100   101   102   103   104   105   106   107   108   109   110