By Cameron Watson, QAIassist
Context
I am hoping to spend
some time this week to discuss methodology structure. A multitude of
methodologies or lifecycles exist and are routinely applied by the IT resources
of most organizations. Just to name a few, here are the better known ones:
project management, software development, software testing, etc.
Commercially
purchased methodologies are similar in many ways.
- They establish a set of terms and vocabulary
that remains consistent throughout the methodology.
- They all rely on a phased naming structure,
for example : Initiate, Plan, Execute & Control, Closeout. This phase
terminology is used as the basis to guide a project through the methodology.
- They all have a pre-defined set of
deliverables and/or activities that must be addressed within each specific
phase.
- The pre-defined activities and deliverables
of each phase can be scaled to reflect the methodology needs of the project.
The following generic
example provides a description of a structure, naming conventions, and
terminology used to describe a project management methodology.
Project Management Methodology
A
project management (PM) methodology consists of four unique phases: Initiate,
Plan, Execute & Control, and Closeout. Within each
phase, PM deliverables are created and administered. Progression through the
following phases is dependent on obtaining the appropriate authorizations from
the designated project owners and stakeholders.
Initiate is
the first phase to be performed within a project management methodology. It is
the process of formally recognizing that a project exists and has obtained the
appropriate level of authority to continue. The purpose of this phase is
twofold.
- First, to assess and determine
a business need.
- Second, to translate high
level business requirements into a document so the project team can confirm if the
project requirements can be fulfilled.
This phase begins when a business case has
been prepared and approved and a project has been authorized to proceed. This
is traditionally an iterative process between the business stakeholders and the
designated project manager.
Plan
this is the second phase to be performed within a project management
methodology. It is the process of recognizing that a project has been
authorized and requires further resources to devise, maintain and execute a
workable plan to ensure the business solution is effectively implemented. The
workable plan must address matters associated with project scope, resource
requirements, project team roles, deliverables to be prepared throughout the
project, a schedule to define how and when the project will be completed, and
the activities to be applied to ensure "quality" is incorporated into
the solution.
Execute
& Control is the third phase to be performed
within a project management discipline. This process is three-fold:
- Coordinating the activities
of the project team resources to ensure the project can be completed according
to the project plan,
- Monitoring the progress of
the project activities against the project plan
- Taking the appropriate
corrective action when the project is deviating from project plan.
The
Project Manager prepares and uses a number of specific deliverables to ensure
project procedures are available to the project team, the project management
deliverables are maintained throughout the life of the project, deviations to
scope, schedule and resources are addressed in a timely fashion.
Closeout is the final project management phase. Its
purpose is to document a true reflection of how the project evolved from start
date through to its completion so that future organizational projects can
benefit from the knowledge and experience gained on the project. Future project
teams can then leverage this knowledge to increase the efficiencies on
delivering business solutions to their clients.
Wrap Up
Although Project
Management, Software Development and Software Testing methodologies and lifecycles
have been created and applied to address unique and specific needs, they are
similar in that they all rely on a phased structure, unique terminology,
pre-defined set of deliverables and/or activities that must be addressed within
each specific “phase”.
A methodology context
diagram illustrating these three methodologies, the phases applicable to each
and a list of specific deliverables can be viewed here. (LINK to PDF placemat
file – I can also add it as an image in the post)
About QAIassist
QAIassist helps organizations increase and
optimize their IT delivery and support efficiency. QAIassist's Integrated Methodology incorporates the disciplines and
deliverables required for organizations to consistently deliver quality
applications on time and within budget. Visit QAIassist's website or email Cameron for more information.