|
|
|
|||||
|
| Home | | | About Us | | |
Products |
| |
Consulting |
| |
Training |
| | Careers | | | Partners | | | Contact Us | | |
CMD Project Management MethodologyThe challenge that organizations face is integrating Project Management tasks with the development or technical tasks of a project. Project Management seems to be a continuous stream of tasks that must be performed from concept through delivery. So should these tasks be separate from the project as an oversight set of tasks? Should these be integrated with the development tasks? If so, how? What are the roles and responsibilities of the development team? What are the interfaces to PM team? After working on many projects we have defined a practical set of PM tasks that conform to the industry standards but are designed to be “actionable” within the project framework. Merging the PM tasks with development tasks is made easy with our Synergy and CMD Symphony products.
|
Often organizations buy large methodologies from vendors with the expectation that since these are “industry best practices” they will be accepted by their organization. This is followed by a “cultural” change expectation. What is wrong with these expectations? They don’t address two factors we have learned over 15 years:
Benefits CMD Products Bring
CMD Products based Methodologies actually get used!!
|
|
Standard Development Baseline
This development path supports the creation of large applications. It is a complete, concise methodology - containing all of the definitions, topics, roles and responsibilities and deliverables needed for success. The Strategic Visioning phase creates key architectures that are used in the succeeding Analysis and Architecture, Design and Construction phases - and are implemented in the Transition and Production Phases. |
|
|
Client Server Design
Client/Server
architectures require special considerations for proper distribution of
data and processes. This
path utilizes event based modeling techniques and covers
distributed architecture considerations.
|
|
|
|
Client Server Development (Object Oriented)
This full-life-cycle
methodology utilizes object-oriented development methods and techniques
and is target at distributed applications development.
|
|
Component Based Development
This
development path utilizes staged analysis/design/construction techniques
to deliver incremental system functionality. Each stage delivers usable
application components. Early stages are used to resolve technical issues
and refine architectures to ensure success and reusability
in remaining phases.
|
|
|
Rapid Application Development
This
development path applies proven group facilitation and prototyping
techniques to gather requirements and produce a high quality system in a
fast development environment. RAD
is extremely useful in situations where project scope is well known and
tight deadlines must be met. RAD
is delivered as a full methodology - complete with all information about
each technique utilized.
|
|
|
Internet Applications Design
Web-enabled
architectures involve careful attention to architecture, deployment and
security implications. This
path utilizes UML modeling techniques and covers web architecture
considerations.
|
|
|
Purchased Package Acquisition and Adaptation
This path
covers all aspects of Acquisition and Adaptation of a Commercial
Off-the-Shelf (COTS) package. It includes considerations for integrating
data and process models of COTS with existing application models.
|
|
|
Small Systems Development
Every
organization is faced with dozens of small, short-cycle application
development projects. The Small Systems path contains tasks to manage the
issues inherent in these projects and integrate the new system into an
overall architecture.
|
|
|
Decision Support Systems Development
Decision
support systems and data warehousing frameworks supply businesses with
consistent historical information for strategic and long-term business
planning. This path includes
datamart, data warehouse, operational data store, and metadata repository
architectures.
|
|
Legacy Systems Enhancement
The decision
to enhance, rebuild or refurbish existing application systems requires
thorough analysis and planning - and Legacy Systems Enhancement solves
this problem. These methods
develop a broad view of an enterprise’s enhancement requirements in
light of its information processing position,
and then prescribe a disciplined approach for the prioritization,
consolidation, development, testing and deployment of legacy systems
enhancements.
As these
methods are applied, a systematic set of documentation and models is
produced to provide a valuable on-going documentation library describing
an organization’s information technology framework.
|
|
|
Systems Maintenance
This lifecycle deals primarily with the identification and resolution of routine change requests and identified errors
in legacy information systems, but has processes that allow for proper prioritizing, testing and putting the software
in production.
Emphasis is placed on the often-overlooked tasks to justify, plan, and coordinate the activities of a maintenance organization. |
|
Microsoft Project 2003 EPM Deployment
This is a customizable framework designed to help organizations install, test, and gradually rollout Microsoft Project
2003 EPM in their environment. The methodology has built in accelerated approaches to installing and getting past the
“proof of concept” stage for the EPM technologies. We have included processes from our Core PM Lifecycle to ensure
that the deployment project is treated in the same manner as any other project. For organizations that want to also
include the process management component, we have added the processes from our Process Implementation Planning
methods. The deployment of an enterprise solution like the Microsoft Project EPM requires not only technical
implementation but also aspects of cultural change, establishment of policies and procedures and management of
expectations. CMD brings all these into a concise methodology and plan supported by our full education and training
curriculum for Microsoft Project 2003. This methodology is designed for our consulting staff to follow during an
implementation. Once the pilot projects have completed and roll-out process has started, organizations can continue to
use this methodology with only spot assistance from CMD. In addition to standard PM deliverables, many specific
documents are produced to assist the organization in maintaining their Project EPM environment. These include EPM
Requirements document and Project Server Configuration document.
|
|
|
Process Implementation Planning
This is a customizable framework that is designed to help organizations set up a process and program management
environment in your organization that leverages the use of Synergy or CMD Symphony products. It is designed to ensure
that management expectations and plans for roll-out including institutionalization of process management are properly
managed. Its step by step processes include creation of an internal communications plan, an organization skills
development plan, and setting up of standards, policies and procedures. It also includes tasks for customization and
building of methodology libraries that are important to your organization. Methodologies, policies and procedures are
tested through a few initial projects before a full roll-out. This methodology the need of organizations that have
already set up a project management environment and are now looking at adding methods and a process management
environment.
|
|
|
Process Implementation Planning for CMM Level 2
This methodology is a implementation
plan specifically targeted to implementing the processes and policies
associated with the key process areas prescribed for SW-CMM Level 2
certification.
|
|
|
Process Implementation Planning for CMM Level 3
This methodology is a implementation
plan specifically targeted to implementing the processes and policies
associated with the key process areas prescribed for SW-CMM Level 3
certification.
|
There are many viable approaches to introducing methodology usage in an organization. Many times it is necessary to focus on a specific area of improvement or a “pain point” first. CMD recognizes this reality and has designed a number of “Practice Area” processes that cover many Management and Control processes. Each Practice Area represents a workflow of activities associated with that practice. For example, the Risk Assessment and Management practice area is a control practice area that participates in all development phases. It describes the actual workflow involved in the identification, quantification and management of risks associated with the development process.
|
Management practices are those practices necessary for the orchestration of the entire product line effort.
|
|
|
Control practices are those management practices necessary to engineer the creation and evolution of the core assets and the products.
|
For more information, please contact us.
Copyright © CMD Corporation 2005. All rights reserved Terms of Use