Corporate project management model

Distributed Project Delivery Model based on Rational Unified Process Introductory Presentation © Soft Format, 2006

Introduction ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],Plan of the workshop

Explanation to Diagrams The provided schemes are the generalized representation of the project delivery model within the complex Relationship Management Model and due to their flexibility are subject to every Customer 's needs and requirements. The diagrams are developed using the Business Processes modeling suite of Rational Rose and applying the UML notation rules for business processes modeling. For easier understanding of the diagrams please consider the following legend: Business Activity - an activity performed by one of the parties within the business process Business Transaction - an activity jointly performed by both parties within the business process and results in a certain decision made or validated Business Entity - represents a significant and persistent piece of information that is manipulated by business actors and business workers. Artifact - a physical piece of information that is used or produced by a software development process. Milestone - a decision-making event in the project Shows a sequence of activities in the process Associates certain artifacts or business entities with certain activities

Relationship Management Diagram

Relationship Soliciting Diagram

Relationship Soliciting Diagram Continued

Project In accordance with PMBOK, project can be defined in terms of its distinctive characteristics: “ project is a temporary endeavour, undertaken to create a unique product or service” Temporary means that each project has its start and its end. Unique means that the product or service is different in some distinguishing way from the other product or service. Because the product of each project is unique, each project involve a degree of uncertainty and should be progressively elaborated . Iteration incorporates a loosely sequential set of activities in different disciplines and business processes, in various proportions depending on where in the development cycle the iteration is located. Organizations performing projects will usually divide each project into several project phases and iterations to improve each management control and provide for links to the ongoing operations of the performing organizations. Collectively, the project phases are known as the project life cycle .

Iteration Iteration incorporates a loosely sequential set of activities in business modelling, requirements, analysis and design, implementation, test, and deployment, in various proportions depending on where in the development cycle the iteration is located. All projects have a set of risks involved. The earlier in the lifecycle you can verify that you've avoided a risk, the more accurate you can make your plans. Many risks are not even discovered until you've attempted to integrate the system. You will never be able to predict all risks regardless of how experienced the development team is. In the Rational Unified Process, the interactive approach is very controlled; iterations are planned in number, duration, and objective. The tasks and responsibilities of the participants are defined. Objective measures of progress are captured. Some rework does take place from one iteration to the next, but this, too, is carefully controlled. ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Project Cycle As you see from the diagram, project life cycle encompasses 4 phases, such as inception phase, Elaboration Phase, Construction Phase and Transition phase. Each project phase is marked by completion of one or more deliverables. A deliverable is a tangible, verifiable work product (artefact) such as, e.g. Software Architecture, Software Prototype, Software Release. ,[object Object],[object Object],[object Object]

Inception Phase Inception Phase Objectives: ,[object Object],[object Object],[object Object],[object Object],Inception Phase Essential Activities: ,[object Object],[object Object],[object Object],[object Object],Inception Phase Essential Artifacts: ,[object Object],[object Object],[object Object],The overriding goal of the inception phase is to achieve concurrence among all stakeholders on the lifecycle objectives for the project. The inception phase is of significance primarily for new development efforts, in which there are significant business and requirements risks which must be addressed before the project can proceed. For projects focused on enhancements to an existing system, the inception phase is more brief, but is still focused on ensuring that the project is both worth doing and possible to do.

Elaboration Phase ,[object Object],[object Object],[object Object],[object Object],[object Object],Elaboration Phase Objectives: Elaboration Phase Essential Activities: Elaboration Phase Essential Artifacts: ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],The goal of the elaboration phase is to baseline the architecture of the system to provide a stable basis for the bulk of the design and implementation effort in the construction phase. The architecture evolves out of a consideration of the most significant requirements (those that have a great impact on the architecture of the system) and an assessment of risk. The stability of the architecture is evaluated through one or more architectural prototypes.

Construction Phase Construction Phase Objectives: ,[object Object],[object Object],[object Object],[object Object],[object Object],Construction Phase Essential Activities: Construction Phase Essential Artifacts: ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],The goal of the construction phase is clarifying the remaining requirements and completing the development of the system based upon the baseline architecture. The construction phase is in some sense a manufacturing process, where emphasis is placed on managing resources and controlling operations to optimize costs, schedules, and quality. In this sense the management mindset undergoes a transition from the development of intellectual property during inception and elaboration, to the development of deployable products during construction and transition.

Transition Phase Transition Phase Objectives: By the end of the Transition Phase lifecycle objectives should have been met and the project should be in a position to be closed out. In some cases, the end of the current life cycle may coincide with the start of another lifecycle on the same product, leading to the next generation or version of the product. For other projects, the end of Transition may coincide with a complete delivery of the artifacts to a third party who may be responsible for operations, maintenance and enhancements of the delivered system. This Transition Phase ranges from being very straightforward to extremely complex, depending on the kind of product. A new release of an existing desktop product may be very simple, whereas the replacement of a nation's air-traffic control system may be exceedingly complex. Transition Phase Essential Activities: Transition Phase Essential Artifacts: ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],The focus of the Transition Phase is to ensure that software is available for its end users. The Transition Phase can span several iterations, and includes testing the product in preparation for release, and making minor adjustments based on user feedback. At this point in the lifecycle, user feedback should focus mainly on fine tuning the product, configuring, installing and usability issues, all the major structural issues should have been worked out much earlier in the project lifecycle. The end of the transition phase should have met the objectives and the project should be in a position to be closed out unless the contract defines other terms of the project close-out.

Inception Phase: Customer -Related View

Elaboration Phase: Customer -Related View

Inception Phase: Customer -Related View Continued

Construction Phase: Customer -Related View

Project Close-Out: Customer -Related View

Next Steps ,[object Object],[object Object],[object Object],[object Object]

Corporate project management model

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (20)

Similaire à Corporate project management model

Similaire à Corporate project management model (20)

Plus de Latte Media

Plus de Latte Media (20)

Dernier

Dernier (20)

Corporate project management model