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



Index


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

background section (implementation plans)
backup software and media
BAFO (Best and Final Offer)
balancing competing stakeholder priorities
baselines
BCWS (Budgeted Cost of Work Scheduled)
Best and Final Offer (BAFO)
best practices (RUP)
     adapting the process
     balancing competing stakeholder priorities
     collaborating across teams
     demonstrating value iteratively
     elevating level of abstraction
    focusing continually on quality
         analysis and design
         Project Management
         requirements
         testing
beta releases 2nd
bidders, questions from
bids, second phase
Booch, Grady 2nd
Budgeted Cost of Work Scheduled (BCWS)
Business Analysis Models
Business Cases
business modeling
     definition of
    use cases
         insufficient use cases
         supplementing with user interface prototypes
         transitioning to
     user interface prototypes
     when to use
business process, lack of agreement on
business risks




Index


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

call management systems
call tracking software
Carmel, Erran 2nd
case studies, NOAA Grants Online project
CCBs (Change Control Boards)
certifications
challenges of outsourcing
     colocated contractors
         communication mechanisms
         hours of operation
         IT problems in new environments
         IT resources
         overtime issues
         quality of facilities
         work space considerations
     distant contractors, same country
     multiple contractors
     offshore projects 2nd
         communication 2nd
         cultural differences
         differences in cultures, work practices, and laws
         when to use
     RUP and
Change Control Boards (CCBs)
change management, testing
change request management tools
     customizable behavior
     customizable change request lifecycle process
     customizable e-mail notification
     integration with other tools
     metrics collection
     querying and reporting
     Web-based interfaces
change requests
     ClearQuest
     construction delays
     discussing
     integrating into iterations
    management tools
         customizable behavior
         customizable change request lifecycle process
         customizable data fields
         customizable e-mail notification
         integration with other tools
         metrics collection
         querying and reporting
         Web-based interfaces
     requirements changes, tracking
classes
ClearCase
ClearQuest 2nd
client PCs
CM (configuration management) role
collaboration across teams
collecting project data
    information from stakeholders
         essential information
         non-essential information
     metrics data
     project postmortems
colocated contractors
     communication mechanisms
     hours of operation
     IT problems in new environments
     IT resources
     overtime issues
     quality of facilities
     work space considerations
Commercial Off-The-Shelf (COTS)
commercial tools
     advantages of
     disadvantages of
common code, developing
communication
     colocated contractors
     cultural differences
     offshore and long-distance projects 2nd
     status meeting minutes
     status reports
     technical interchange meetings
component-based architectures
components
Concept of Operations (CONOPS)
configuration management
     CM (configuration management) role
     project postmortems
     testing
     tools
         features and capabilities
         parallel development management
         workspace management
configuration management (CM) role
CONOPS (Concept of Operations)
Construction phase
     change requests, discussing
    common mistakes
         beginning construction too soon
         change request delays
         iterations of inappropriate length
         iterations with no stated purpose
         overly detailed plans
     contractual issues
     goals of 2nd 3rd
    iteration planning
         baselines
         content
         goals 2nd
         length 2nd
         releases
         staff considerations
         testing
         time considerations
    iteration results
         assessing
         demonstrating
     iterative versus Waterfall techniques
     readiness for construction, assessing
         checklist for customers
         checklist for products in development
         checklist for project environment and staffing
consultants
     expert consultants from vendors
     pricing
    process consultants
         choosing projects suitable for
         definition of
         implementation plans
         organizational assessments
         task schedules
         working with
     staff augmentation
consulting firms [See process consultants.]
content of iterations
Contract Work Orders (CWOs)
contracting officers
contractor's checklist
     outsourcing organization's checklist
contractors
     acceptance testing checklist
     access to stakeholders
    artifacts for
         executables produced by iterations
         list of risks and risk history
         other information
         project glossaries
         Software Architecture Document
         supplementary requirements
         UML models
         use cases
         Vision Statements
     best practices
     colocated contractors
         communication mechanisms
         hours of operation
         IT problems in new environments
         IT resources
         overtime issues
         quality of facilities
         work space considerations
     dependency on
     distant contractors, same country
     IBM Rational partnerships
     maintenance contractors
     multiple contractors
     offshore projects 2nd 3rd
         communication 2nd
         cultural differences
         differences in cultures, work practices, and laws
         when to use
     requirements management tasks
     selecting
     software project teams
         architects
         CM (configuration management) role
         developers
         managing
         project managers
         quality assurance personnel
         requirements analysts
         staffing principles
         technical leads
         testers
         toolsmiths
     working relationships with stakeholders
contracts
     Construction phase and
     Contract Work Orders (CWOs)
     cultural differences
     Firm Fixed Price (FFP) 2nd
     Head Contracts
     System Realization Contracts
     System Specification Contracts
         business and system use cases
         executables produced by iterations
         list of risks and risk history
         other information
         project glossaries
         Software Architecture Document
         supplementary requirements
         UML models
         Vision Statements
     two-stage procurement process implementation
copy-based models (workspace management)
corrections in software
cost of consultants
Cost Xpert
COTS (Commercial Off-The-Shelf)
cultural changes, two-stage procurement process implementation
cultural differences, offshore projects and 2nd
custom "in-house" tools
     advantages of
     disadvantages of
CWOs (Contract Work Orders)