in many instances is designated to refer to an actionable plan or multiple
actionable plans. Although strategy originates for military usage which is distinct
yet connected to tactics to determine how different engagements are linked,
this actionable plan is intended to achieve a particular goal which should be
properly selected, controlled and evaluated. In addition, a collection of plans
create the opportunity or need for better project portfolio management
capabilities for PMOs (program or project management offices), project
managers, product line engineer managers, system engineering managers and
leadership executives. The goal is to have standard methods and governance for
selecting, controlling and evaluating investment candidates (projects or
overall fundamental goal for project portfolio management is to have the
optimal program, capability, project and/or product distribution mix and
priority sequence based on measurable defined criteria such as strategic
objectives. This also includes additional weighted criteria constraints or
barriers such as budgets (cost), time/schedules, resources, risks,
feasibilities, significance and other pre-defined agency criteria applicable to
your department or bureau. In addition to optimal decision reliability for
quantifiable decision support, the goal is also to determine right decisions in
a way that is systematic, audit-able and repeatable.
Rational Focal Point and Rational Team Concert give agencies
offers a strategy determination, innovation, and portfolio management decision
support system that is completely based on web services: Rational Focal Point
software. Rational Focal Point helps companies collaborate globally at all
levels of the organization. This collaboration can help ensure that their
innovation, technology, and product and service portfolios:
Improved decision reliability based on a quantifiable consistent methodology using Analytic Hierarch Process
Supports the distinct 3 phases of smarter investment lifecycle of the
Clinger-Cohen Act for Capital Planning & Investment Control (CPIC)
Supports process governance such as the Defense Acquisition Guide
Lifecycle Materiel stage gate workflow
Represent the best possible mix of innovative and sustaining offerings
Deliver the appropriate blend of risk and return, cost, and benefit
Consistently yield the best trade-offs between agency demand, strategic
objectives, and response
Rational Focal Point is a configurable 100% web-based software portfolio management platform that allows agencies to capture, classify, govern, align, decide, control and evaluate portfolio artifacts such as investment candidate proposals. Let's look at a typical portfolio artifacts lifecycle, where an agency is able to manage portfolio artifacts such as investment candidate proposals and portfolio artifacts portfolios with standards, governance, key performance indicators, traceability, decision support and assessments such as even performing portfolio artifacts Maturity Model Integration task if necessary. Although this is one example of a portfolio artifacts lifecycle and portfolio support, an agency has the ability to easily configure the Rational Focal Point software platform to fit it's taxonomy classification, process and leverage existing IT investments.
Agencies are able to import portfolio artifacts information via spreadsheet and other integration means; nonetheless, users need standard template forms to submit portfolio artifacts proposals, work on portfolio artifacts, view portfolio artifacts analytics and decision support trade-off exercises. The following figure is a Rational Focal Point screenshot capturing a portfolio artifacts proposal based on a standard template specific to your taxonomy (Please click the image to enlarge).
Rational is a leader at providing prioritization management solutions with our
IBM Rational Focal Point tool. Rational Focal Point delivers agency-driven program,
capability, project, system, product and portfolio management to help
executives and teams make the right decisions to deliver agency and stakeholder
value. This example will be using Department of Defense Lifecycle Guide Materiel framework; however, agencies can implement current processes or implement other frameworks, such as the Balanced Scorecard (BSC), or the US Department of Defense Architecture Framework (DoDAF), The Ministry of Defence Architecture Framework (MODAF), The Open Group Architecture Framework (TOGAF), Zachman's Framework for Enterprise Architecture, Feature Driven Development (FDD), Scrum & other Agile methods and Quality Function Deployment (QFD) House of Quality as examples. After using the Defense Acquisition Guide Lifecycle, the investment candidate gets deployed from the project proposal stage to the execution stage by creating the project plan which will be managed in Rational Team Concert with a work breakdown structure. By using Rational Focal Point, the agencies can:
Make faster, better-informed strategic and tactical decisions
Prioritize IT investments candidates to support agency goals
Improve risk management of organizational transformation
Turn strategy into execution and measure the results
As investment candidates go through decision support trade-off analysis and stage gate approval process such as the following figure below which is an example screenshot of Rational Focal Point using the Defense Acquisition Guide Lifecycle Materiel phase (Please click the image to enlarge), project proposals become project plans with a manageable work breakdown structure.
The following figure is an example of a stage gate decision support process using the Analytic Hierarchy Process (AHP) with configurable weighted criteria (Please click the image to enlarge).
Once the agency approves the investment candidate, the integration between Rational Focal Point and Rational Team Concert allow for effective Portfolio and Project Management.
Focus on what matters most in driving business
Organize work around value
Gather all inputs into one place with consistency in
Analyze stakeholder needs to drive scope and
Reduce delays and mistakes
with real-time, “in-context” collaboration
Any plan, any process: Support traditional and agile
Continually validate cost and scope
Investment candidates & projects have gone through a workflow stage governance process and trade off justification to validate the project to be executed as part of the portfolio. The project within this view for execution and the associated business needs will be integrated to the Team Concert plan. This screen shows us the Project “Identity Protection” after it has been approved for execution. As members of the portfolio team, our interest lies in knowing that the project will be delivered on time and on budget.
The agency has identified 7 Business Needs or High level Project Requirements. We want the project execution to focus on this delivering these needs so it is important to the business that work being performed traces directly to them. As we can see from the project implementation page, the development has started for this project. It is 47% complete and overall it is reporting healthy metrics by the look on the green traffic lights. The Completeness and health metrics are being derived directly from the execution data entered by the project development organization. Point out that the Project Execution Area can be opened by clicking on the “Link to Implementation Project”.
IBM Rational Team Concert (RTC) is a lean
collaborative lifecycle management solution that helps companies builds better
projects, software, products and programs. Rational Team Concert, based on the
Jazz platform, supports the agencies plan, process, and platform. New formal
planning templates support traditional project phases, while risk management
capabilities can be used by any traditional, agile, or hybrid team.With a single release for the agencies platforms,
simple role-based user licensing, no charge for the server software, and new
flexible pricing models, agencies will be able to freely mix and match
deployments to suit their particular environments. Its distributed version
control support improves collaboration with other lines of the agency, and
outside suppliers, who need to share document repositories. Rational Team
Concert provides the following elements of value:
Accelerating complete agile, formal ,and hybrid
planning coverage from work item inception through planning, development, and tracking
Supports geographically distributed teams with
features, such as communication in context, event feeds, integrated chat, and
automated traceability, all beyond simple email
Lowers Total Cost of Ownership (TCO) for agency by
exploiting a common scalable infrastructure that provides common processes,
common security, with open integrations and services for project support
Can be easily adopted by component, as a
unified solution, or surrounding existing tooling
Comes with simple, role-based user licensing
Includes Collaborative Lifecycle Management (CLM)
support for improving productivity plus built-in integration with IBM
Connections social software
With the integration to Rational Focal Point, agencies have increased decision reliability with project plans and work items. The agency can show the Work Breakdown and Schedule created by the Project Manager. The Agency Business Needs that were defined in the project definition are part of this view such as Authentication. In a conventional project management practice, you can decompose these business needs/requirements into lower level work items. Each work item is managed independently. The lower level decomposed work items drive the schedule of the agency business need. The following figure is an example screenshot of Rational Team Concert project plan work breakdown structure (Please click the image to enlarge).
There work items show here have dependencies amongst themselves. Some of the dependencies shown here include: Finish to Start (Finish to Start) and Finish no later than (FNLT). The agency can click on Authentication Database Changes Work Item to drill into the work item and enter data such as effort and other activities.
Select the Type drop down boxes and explain how this Work Item has been flagged as a task but that it could be change to other work item types. The Work Item was estimated to be completed in 1 Week. The Time Spend displays the time spend on this task. Click on the Time Tracking Tab and show how we have captured the time spend on this task. 40 hours in total. Use the work breakdown structure (WBS) to show the Authentication Business Need for The Progress attribute's estimates and completion times of all the Tasks associated to this agency business need. From here we can see that a 100% of the tasks have been estimated: The estimate comes up to: 240 hrs & 56 Hrs have been completed .
This view displays the resources associated to this project. We can see the resource load for each person. In the case of Miguel, it is obvious that we are over allocating tasks to him. The Tasks display a warning icon next to them warning that they are being assigned to an over allocated person.
The information is integrated back into Rational Focal Point for additional portfolio management capabilities and decision reliability trade-off analysis. This allows the agency to look at the execution actual(s) from a portfolio management perspective. In the scope section, open the Authentication business need. Expand the Effort and Links section. As an agency business department or bureau owner of the project, you can instantly see the hour estimates and actual effort which drive project health indicators such as the Actual vs Planned traffic light. The estimates and actual hour efforts come from the WBS that we just reviewed. Hover over the Authentication Link to display the interoperability information access of Rational Team Concert.
Organizations need to flexibly assemble their software
delivery environment, using their preferred tools and vendors. As this
environment is not static, organizations need to evolve their environment as
their needs change at their own pace. The Jazz platform provides the technical
foundation for several types of lifecycle tool integration. This platform
consists of architecture and a set of application frameworks and toolkits. The
following figure is IBM’s Jazz foundation is an open platform that supports any
industry participant with the goal of improving the software lifecycle and
breaking down walls between tools. The figure to the left is an example Jazz Platform Architecture and Open Services Lifecycle Collaboration using web services for integrations and interoperability of information.
is built on architectural principles that represent a key departure from
approaches taken in the past. Together, these approaches allow teams to “surf
the collaborative Web” to seamlessly access teams, processes, and artifacts.
The following figure is an example of an integrated best practices process
based on IBM Rational Jazz Architecture.
architecture includes the following features:
Jazz separates the implementation of tools from the definition of and
access to the data. Data semantics do not rely on “secret knowledge” embedded
in product code.
Jazz federates data across independent databases using Internet
protocols. Jazz does not assume all data is in a single database.
Jazz can access and integrate data where it resides, that is, Jazz does
not need to import and export data between tools or repositories.
Jazz assumes an open, flexible, distributed data model. Jazz does not
assume there is a single data model that is centrally managed, or that each
tool needs to understand the entire data model to participate.
Jazz allows tools to be implemented in any Internet-aware programming
language or platform. Jazz does not impose an implementation framework tied to
a particular language or technology platform.
Jazz supports multiple client technologies. While Web user interfaces are the choice for
many Jazz tools, Jazz also supports Eclipse-based clients and Microsoft Visual
Studio-based clients, and other client platforms could easily be implemented
based on demand.
are two principal facets of the Jazz architecture, described below:
Linked Lifecycle Data, applying the W3C “Linked Data” standards to the
realm of lifecycle data (for example, requirements, change requests, test
Integration services, providing cross-cutting capability for any
lifecycle tool (for example, user admin,
project admin, lifecycle query) to
enable the system of tools to work well together
first principal facet of the Jazz architecture is Linked Lifecycle Data. Customers
use tools from multiple vendors to capture and manage data across the software
lifecycle. These data are typically accessed by using the tool that created the
data or by accessing a database used for storage by the tool. The lack of
common protocols across resources makes it difficult for other tools to gain
such access. The
Jazz architecture addresses this problem by providing standard interfaces and
methods for tools to establish links to data housed and managed by other tools,
possibly those built on widely varying technologies. Jazz embraces the linked
data approach as implemented in the Open Services for Lifecycle Collaboration
(OSLC) initiative. Linked data is the fundamental architectural principle of
OSLC, making it "the community and specifications for Linked Lifecycle
supports the notions of Providers and Consumers. An OSLC Provider is a tool
that "owns" lifecycle data and exposes those data to other tools as
described in corresponding OSLC specifications. And OSLC Consumer is a tool
that accesses another tool's data through its corresponding OSLC specified
interface. Architecting lifecycle tools to interact in this manner enables
interoperability between tools and resources spanning across vendors. OSLC
shifts the emphasis from tools and their widely varying APIs to the lifecycle
resources (the data) and the relationships between resources. By doing so, one
tool can access and link to another tool's resources where the data live, as
opposed to a more classical copy and synchronize approach. By exposing data
through OSLC-defined RESTful interfaces, tools contribute to a web of data that
can be traced, indexed, and analyzed from a cross-lifecycle perspective.