|
EMAPS™ Engagement Management And Performance
System
The engagement approach that underlies PWI
software development solutions was developed to add
capabilities and leverage to a client's existing IT team
through capable and scaleable software programming and
engineering. In this approach the client plays a key role
and together with PWI executives helps to form an integrated
high-performance solution team.
The PWI approach, Engagement Management and
Performance System (EMAPS™), combines traditional project
management and software development methods with proprietary
tools and techniques specifically designed to ensure
efficient product delivery and high quality standards for
the management of outsourced technical resources. EMAPS™
complies with common industry standards such as ISO 900X and
SEI CMM.
The EMAPS™ approach is comprised of four
phases: Consultation, Determination, Execution & Validation
and Deployment & Maintenance. When applying the approach,
PWI works closely with its clients to streamline the process
and adapt EMAPS™ to fit the client's current circumstances
and business needs. This eliminates unnecessary process
steps and speeds the process forward toward the development
and deployment of a solution that's still relevant and
appropriate.
Four common-sense guiding principles
influence how PWI engages with its clients:
· Make the process un-burdensome for clients
· Seek first to understand and validate, then deliver ·
Ensure that quality and speed drive all our activities ·
Implement advanced solutions that work
PWI makes these four principles
common-practice in all its client engagements. This is
evident from the first interaction with the client and it is
demonstrated by the commitment and drive that PWI teams
bring to helping its clients achieve their stated business
objectives.
|
Phase Name |
Descriptions & Outputs |
Notes |
|
Consultation |
In the Consultation phase, PWI and the client work
closely to convert the client’s expression of its
business needs and requirements into a System
Requirement Specification (SRS).
The SRS is a high-level technology design of the
solution |
Depending upon how much clarity and understanding exists
regarding the business needs and requirements, PWI
endeavors to condense the Consultation phase into as
short a time period as possible.
The tools and techniques PWI employs in this phase are
adapted to fit the preferences and working style of the
client.
These include practices such as workshops, interviews
and questionnaires.
Before moving to the Determination phase, both the
client and PWI will “sign-off” on the content of the
SRS.
|
|
Determination |
In the Determination phase PWI’s focus is to drive the
higher-level SRS to a more exacting level of detail that
can be acted upon.
The System Design Specification (SDS) is the
primary deliverable in this phase.
It is the technical companion document to the
SRS. The
SDS typically includes the following elements:
-
project timetable
- project
deliverables
- representative
screen shots
- workflow diagram
- MDBs and IDLs
- list of third party tools, libraries
and packages
- overview of the technical environment
- staffing model
At the conclusion of Determination, the cost and
resource estimates are finalized and agreement to
proceed has been established between PWI and the client. |
PWI
employs standard tools to help visualize the
complexities and intricacies of the solution model.
These include Microsoft / Corba interfaces, Rational
Rose and Visual Studio.
PWI determines the project management tool set after
receiving input from the client and in consideration of
their preferences.
Standard packages supported include Microsoft
Project and Source Safe.
Measurable progress toward the final deliverable is made
in this phase as key technology issues are resolved and
working prototypes and solution components are developed
and presented to the client.
|
|
Phase Name |
Descriptions & Outputs |
Notes |
|
Execution and Validation |
The
Execution and Validation phase is designed to help
ensure that the client achieves its business objectives
as early and as quickly as possible.
The development and delivery process is highly iterative
and is highlighted by the release of solution phases --
the schedule and functionality of which are established
and agreed to in the project plan.
The cumulative result of the release phases is
the delivery of the application. |
In
the phased releases fully functional solution components
are developed and released to the client who performs
Validation and QA as the components are field tested.
A
Modification Request (MR) list is developed and
co-managed with the client to ensure that the project
remains on target in terms of functionality and delivery
dates.
In this way the MR list informs the scope management
process by keeping the priorities set and in focus at
all times. |
|
Deployment and Maintenance |
In
the Deployment and Maintenance phase the application has
been delivered and the project has come to its natural
ending point.
Documentation and maintenance training are delivered.
In instances where PWI is to perform ongoing
maintenance, that period formally begins at this point. |
The
focus in this phase is to transition responsibility and
ownership of the application to the client in an orderly
fashion.
Knowledge transfer is completed with the delivery of the
system documentation and training of the client’s
application support staff.
As called for in the business agreement, PWI works with
the client to ensure that the application is properly
deployed to the designated user community.
However, in many instances this will already have
been accomplished as the application is deployed in
parallel fashion with the delivery of the phased
releases. |
|
