This is the third part in continuation to my earlier post Goal
Management -
Goal Management - Goal partitioning for Elaboration phase
The goals that are set in the construction pahse is looking at the business goal of delivering some usable system to the end user or consumer. The goals in this phase are broadly:
* To describe the remaining requirements
* To flesh out the design of your system
* To ensure that your system meets the needs of its users and fits into your organization's overall system portfolio
* To complete component development and testing, including both the software product and its documentation
* To minimize development costs by optimizing resources
* To achieve adequate quality as rapidly as possible
* To develop useful versions of your system (alpha, beta, …)
During the Construction phase, your project team will focus on evolving the technical prototype that you developed during the Elaboration phase into the full fledged system. As a result, your team will:
* Achieve and maintain adequate quality in your work as early as possible
* Develop software models that are sufficient to guide the implementation of your system
* Work closely with your user community to validate that your work meets their needs
* Implement and test the various components of your system
* Develop useful versions of your system as early as is practical
* Baseline the validated components and
* Manage the risks, people, and other project resources effectively.
As you work towards your goals, you will create and/or evolve a wide variety of artifacts:
* Revised requirements model (use cases, supplementary specifications) describing what you intend to build
* Revised project−level software architecture documents (SAD)
* Detailed software design models showing how your system is built
* Executable system ready for beta release to your user community
* Revised project schedule, estimate, and risk list from which to manage your project
* Revised team environment definition (tools, processes, guidelines, standards, etc.) indicating the tools and techniques that your team will use
* User, support, and operations documentation that is ready to be beta tested.
Many enterprise IT organizations are tackling large, complex efforts that combine the delivery of software elements, new and changed business models, and overall changes to organizational structure and capabilities. Typically these efforts involve several parallel projects, and managers are finding that "traditional" project management approaches fall short for such undertakings. Consequently, many IT professionals are turning to the substantial body of experience, and the smaller body of documentation, that supports the discipline of program management. This discipline describes principles, strategies, and desirable results for managing large-scale efforts comprising parallel projects.
This article considers five major aspects of program management:
Governance: Defining roles and responsibilities, and providing oversight
Management: Planning and administering both projects and the overall program
Financial management: Implementation of specific fiscal practices and controls
Infrastructure: The program office, technology, and other factors in the work environment supporting the program effort
Planning: Activities that take place at multiple levels, with different goals. The program plan is not a traditional plan
Have a detailed and interesting view available on the following URL:
[
http://www.ibm.com/developerworks/rational/library/4751.html]