Beruflich Dokumente
Kultur Dokumente
cordin8 is a collaborative business platform that transforms how knowledge work is managed. It
centralizes the data, but using distributed management techniques, so that business units can organize
and manage their work independently with the ability to link into enterprise-wide work. It provides
managers with visibility into the work process that is far superior to managing through email and file
attachments.
There are three cornerstone solutions that comprise our Management of Knowledge Work Framework:
These three solutions will be described in our Transform the Management of Knowledge Work Series.
This paper details how the Enterprise P/PMO Solution supports the idea lifecycle from idea generation,
selection, execution to archival. The solutions depicted within this paper are based upon project and
portfolio management methodologies from TenStep, Inc. (www.tenstep.com). As with all of our
solutions, they may be customized to meet your business requirements.
Idea Workflow
The major stages for managing an idea from cradle to grave are shown in Figure 1: Idea; Business Case;
Project; Post-Project Review; and Archive.
When the
user submits the idea form, a new entry is created in the portfolio that contains the user submitted
data. The portfolio page (see Figure 3) contains fields that will be used to manage the idea through
all of the stages of the idea lifecycle. At the top of the portfolio page, there are a set of six tabs:
Users who are assigned as SMEs access the portfolio item through their my cordin8s. They can
review all of the information related to the idea—description, documents (files) – as well as post
questions and comments in the Replies, a threaded-discussion style section. Then, they use the
Before the portfolio review meeting, portfolio team members review each idea that has been
assessed by reading through the comments and ratings. At the monthly portfolio review meetings,
they review the list of evaluated ideas to determine the fate of each idea. At this stage, the
portfolio team is deciding whether the idea is worth further investigation. If it is, then a team will be
formed to develop a business case, which will be used to decide whether or not it becomes a
project. The decision for each idea, whether approved to move forward or rejected, is documented
with the idea (see Figure 5). The team also documents the discussion and decisions in the Portfolio
Review Meeting minutes form (see Figure 6).
The Business Case Notebook (see Figures 7-10) consists of sections to manage the team’s work, such as
schedule, meetings, action items, issues, as well as forms to use to create the deliverables for the
business case stage, including the business case document, SWOT analysis, risks, and overall evaluation.
Before the Portfolio Review meeting, the portfolio team can use the portfolio analyzer (see Figure 11) to
perform ‘what if’ scenarios with the set of ideas that have business case data. At the meeting, the team
documents the outcomes for each idea that has business case data. Ideas that are approved to proceed
move to the Project stage.
Stage: Project
The portfolio team determines whether the effort will be organized as a project or a program, a
collection of multiple projects. If different disciplines or functions or departments will be involved, it will
likely be setup as a program with each discipline or function assigning a project manager to their portion
of the work. Requests are made to the appropriate departments or functions, e.g., IT, Engineering,
where they will setup a project that will be visible in individual department’s portfolio, e.g., IT’s
portfolio, as well as visible to the program (See Figure 12). An example program notebook is shown in
Figure 13.
The project notebooks are used to manage and organize the work of the project, such as creating and
approving the project charter, assessing and managing project risks, issues, and scope changes and so
forth. Team members use the notebooks to receive work assignments (e.g., tasks, issues, action items).
Requirements, designs, test cases and so forth are also maintained within the notebook. (See Figure 14)
At the Gate Review meeting, the portfolio team will review the deliverables for the current phase and
approve or suggest changes that need to be made in order to be accepted. (See Figure 17)
While the status of the portfolio can be reviewed at anytime through the PPMO Portal, the portfolio
team can also run reports for monthly review meetings with the leadership team (See Figures 18-22 for
sample reports).
The Project Knowledge Base is a community-based portal for project managers within a business unit as
well as across the enterprise. Within each item of the Portal is a voting tab, so project managers can
provide feedback (comments and a rating) of how well a particular piece of information in the
knowledge base helped them (See Figure 23). So, the organization is capturing not only what the
original team learned in the executing the project, but how other teams used what they learned within
their own projects.
Stage: Archive
Since the portfolio form has been used throughout the life of the idea, it can be searched in the archive.
Detailed information can be accessed via that program and project notebooks.
Conclusion
The Enterprise P/PMO Solution is one of three solutions from cordin8 to transform how companies
manage the knowledge work portion of their business. It facilitates the Idea Lifecycle, which is the
fundamental business process of creating new products and services. By embedding best practice
portfolio and project management methodologies as well as employing a central data store with
distributed management capabilities, the organization can achieve both consistent practices and data
which lead to increased maturity and improved performance.