Project Management with the IBM Rational Unified Process: Lessons From The Trenches

Index

[A] [B] [C] [D] [E] [F] [G] [H] [I] [J] [K] [L] [M] [N] [O] [P] [Q] [R] [S] [T] [U] [V] [W]

maintaining systems

    Help Desks

         best practices

         call management systems

         call tracking software

         equipping

         goals of

         license utilization software

         problem tracking software

         staffing

         Web sites

    maintenance support

         corrections in software

         maintenance contractors

managers

     IT managers

     project managers

managing software project teams

Managing Software Requirements

medium-sized projects, progressive acquisition model

meetings

     minutes

     proposal meetings and conferences

     technical interchange meetings

     with stakeholders

metrics data 2nd

migrating data

     analyzing cleansed data

     data cleansing

     extracting legacy data

     planning

     points to remember

     shutting down legacy systems

     testing migrated data

     transferring legacy data

milestones, Lifecycle Objectives Milestone

mistakes in RUP (Rational Unified Process) implementation

     assuming you can implement RUP perfectly the first time

     failing to integrate change requests into iterations

     failing to tailor RUP

     failing to test properly

     iterations of inappropriate length

     iterations with no clear goal

     poor project choice

modeling business processes

     definition of

     insufficient use cases

     supplementing with user interface prototypes

     transitioning to

     use cases

     user interface prototypes

     when to use

monitoring project performance

     Earned Value

     releases

multiple contractors