In Part 2, Randy spoke of the process to identify ECM CC services packages and tiers. During that exercise the services were prioritized based on the project pipe line when the services will be needed. In this part, I will focus on developing a staffing plan to deliver and support the planned services and projects. There are a number of activities that must be understood to develop a well thought out staffing plan. First the organization needs to establish a project concurrency capacity objective. The number of concurrent projects will determine the number of resources and skills mix needed to deploy solution leveraging the ECM CC Community services.
Once the number of concurrent projects is determined, then the information gathered in the Evaluate Current State step of the roadmap can be used to define an organization leveraging many of the ECM skills that currently exist in the organization. A plan is defined to address the skill gaps and take into account the prioritization of the projects in the pipeline, as well as the concurrency objectives when determining a timeline and the immediacy of filling the gaps. Once the timeline and immediacy is understood, the plan would outline the approach to fill both short term and long term gaps. For some skills it may involve contract resources to address immediate needs while leveraging those resources in a mentoring capacity.
Here is an example of the impact of the number of concurrent ECM enabled projects on the staffing of an ECM CC.
In this example, an IBM ECM CC modeled customer looked back at the projects they deployed over a year and determined the average number of hours by role. They also determined an average elapse time of the projects, which was 3½ months for an ECM engagement for the given year. With that information they determined that if they started 1 new project per month that it should average 3½ projects being managed in a given month. In the above chart you can see the impact this organization saw when managing 3½ projects concurrently and the impact if more projects are introduced on a monthly bases. This analysis helps them to determine staffing needs given the amount of work that the steering committee had established as guidelines.
The next part in this series will discuss developing an ECM CC Engagement Process. This is one of the Best Practices and Standards that needs to be developed to guide ECM Solution delivery and helps the organization to take full advantage of the benefits of having an ECM CC.
In the meantime, please feel free to leave feedback or suggest topics that you'd like me to explore. Love to hear from you!
the last post (Part 1) I indicated that we were going to talk about the first
steps of the establishment of an ECM Center of Excellence organization. But
before we go there we have a few other things that need to fall in place.
Establish a ECM Program and Program Manager
ECM to be successful at a enterprise level, it must be treated as a program. A
program with a Steering Committee that is representative of the whole
enterprise and leverage it to provide guidance, impetus, and a high-level
sign-off for company-wide issues such as the corporate taxonomy, key metadata,
and security models as well as critical SLA and Disaster Recovery/Business
Continuity requirements. The ECM Steering Committee is responsible for the
establishment of a ECM Center of Excellence, first by assigning a ECM Program
Manager that is responsible:
program services are visible, planned and managed to the client’s goals and
the development of ECM vision and strategy
development, promotion and management of ECM services
creation and adherence of best practices, proven methodologies and processes
continuously refine COE metrics and management reporting
Develop an ECM Program Roadmap
of the first item of the ECM Steering Committee is to assign resources to work
with the ECM Program Manager to develop an ECM
Program Roadmap. First step of the ECM Program Roadmap is to evaluate
current state followed by gathering current and future business and IT needs.
Once the current state and needs are determined then the high-level future
architecture is defined. A gap analysis from current to future is performed
which drives the rest of the ECM roadmap. The roadmap needs to address both the
ECM COE development/implementation, ECM technology planning/design/deployment
tasks and the establishment of measurements/system validation tasks.
ECM COE Foundation Development group of tasks in the ECM Program Roadmap,
includes the identification of needed services, and a development plan for the
COE resources. The development of key ECM COE processes to run the COE as well
as develop and deliver the needed services.
ECM Technology Planning & Design group of task focuses on the development
of the ECM Technical architecture and produce the architecture artifacts to
integrate into your Enterprise Architecture. On of the important artifacts that
I want to point out is the concept of Solution Patterns. Later I will discuss
packaged (tiered services) and these solution patterns provide governance when
to use particular packages and provides guidelines around the extension
(customization) of these packages. The other activity of this grouping is the
development of an ECM Technology Deployment Plan which will be a detailed plan
and timeline of the deployment of all the ECM underpinning as well as the
services provided to the organization
Identify ECM COE Offered Services
evaluate the current state (first swim lane) of the ECM Program roadmap,
information was gathered to define a high-level architecture to meet the
business/IT needs. Now the ECM COE resources look at the business
challenges/objectives and the future architecture and define appropriate levels
of functionality for various segments of the potential user base.
COE and business units work together to define various packages or tiers of ECM
functionality (for example: ranging from packages with basic store-and-retrieve
capabilities, to more advance packages offering revision-control and automated
workflow capabilities). Other tiers may take into account the acceptance of
change in the business units. Some business units may desire mature services
and avoid change while others may require more leading edge technology which
typically involves introduction of technology on a more frequent basis.
leveraging package solutions is the desired for fast deployment and cost
containment of ECM to the business, it may not meet all the requirement of the
business. In that case the package can be used as the base and custom
components augment the package to meet the business needs. All custom
components will be design with reuse in mind and could be considered ECM COE
services as well.
the Current/Planned ECM technology and the project pipeline, a prioritized
delivery plan of packages and custom components can be developed. The Industry
ECM Direction can be used to determine other services/packages that might need
to be developed that are not currently needed by projects in the pipeline.
Services that have no immediate need but need is expected in the near term,
should be noted and once the ECM COE has needed services implemented, these
will be areas of research focus (Research is a key recommended process that
will not be discussed in this presentation).
far we have been talking about technology services but the ECM COE also
provides Advise & Consult Role based services to the enterprise. Services
Solution Design Services – ECM COE Architect Role provides the knowledge to
develop business solutions leveraging the ECM technologies. These solutions can
be either: Content Storage and Retrieval Solutions: These solutions are
primarily focused on centrally managing content (paper and electronic) as well
as content retrieval. Typically a generic client is provided for retrieval.
Document Centric Workflow Solutions: These solutions not only focus on
centrally managing the content but managing the business process that leverages
the content. Typically this will be a BPM application with a customized user
Solution Requirement Gathering Services - ECM COE Process Designer/Business
Analyst provides the skills to help the business gather and understand their
requirement and translate them into ECM solution requirements. This information
is then used by ECM COE Architect to more efficiently and accurately design a
Modeling Services - ECM COE Process Designer/Business Analyst is
knowledgeable in principles of process modeling as well as the tools to assist
the business with documenting their current and future process with ECM
technology enablement. The ECM enable process models then can be used by the
technical designer to automate the model with the BPM tool
Technology Research Services - ECM COE provides the skills to evaluate and
research new ECM technologies and help the business in the selection of
technologies to meet their requirements
ECM COE role services should be indentified during this exercise so that it can
be communicated to the customers resulting in strengthen ECM solution provided
by the ECM COE
time flies when having fun. I am out of time and my daughter is waiting for me
to tuck her in so on the next post we’ll pick up with a discussion of the next
step of a ECM COE Foundation Development.
let me know what you think. All feedback is greatly appreciated.