4.2.1. Planning
·  Development of a comprehensive backlog list.
·  Definition of the delivery date and functionality of one or more releases.
·  Selection of the release most appropriate for immediate development.
·  Mapping of product packets (objects) for backlog items in the selected release.
·  Definition of project team(s) for the building of the new release.
·  Assessment of risk and appropriate risk controls.
·  Review and possible adjustment of backlog items and packets.
·  Validation or reselection of development tools and infrastructure.
·  Estimation of release cost, including development, collateral material, marketing,
training, and rollout.
·  Verification of management approval and funding.
4.2.2. Architecture/High Level Design
·  Review assigned backlog items.
·  Identify changes necessary to implement backlog items.
·  Perform domain analysis to the extent required to build, enhance, or update the
domain models to reflect the new system context and requirements.
·  Refine the system architecture to support the new context and requirements.
·  Identify any problems or issues in developing or implementing the changes
·  Design review meeting, each team presenting approach and changes to implement
each backlog item.  Reassign changes as required.