s/socialmedia/youtube.jpg" alt="Youtube" width="25" height="25" border="0">
|
|
|
|
|
Quality Process >> Project Management Practices |
| |
| Project Management Practices |
Project Management is the art of balancing competing objectives, managing risk, and overcoming constraints to deliver, successfully, a product, which meets the needs of both clients and the users.
This workflow focuses mainly on the specific aspect of an iterative development process. Our goal with this section is to make the task easier by providing:
|
|
 |
| |
|
|
A
framework for managing software-intensive
projects. |
|
Practical guidelines
for planning, staffing, executing, and
monitoring projects. |
|
A framework for
managing risk. |
|
|
 |
| |
|
| At
Gateway we have developed our own standards, which
are commensurate with IT industry standards. We
make sure that the entire team at Gateway follows
the standards to deliver quality software
products. By adopting and following these
standards we have been successful in performing
on-time delivery of products that are bug free and
robust |
| |
| |
| * |
In case,
if the Client has long-term requirements for
project development, which needs estimation ,
assessment and approval from Client side, we
interact with Client through Project Outsourcing
Methodology. |
*
|
In case of any
alterations in the project already implemented,
we deal with the Client through Project
Alteration methodology. |
| * |
In case of short term
projects, which do not require process of
estimation, approval for implementation or
having fixed cost for development, we interact
with Client through Fixed Cost Project
methodology. |
|
| |
|
Project Outsourcing
Form |
| |
The Project Outsourcing Form includes
the details about project implementation
methodologies and responsibilities on both the
sides. To ensure the clarity for change requests
during execution and after implementation of the
project, POF also defines the process for Change
Request and Approval for the same. |
|
Project
Estimation |
| |
We do project estimation based on the
requirements. For estimation we use either
Microsoft Excel or Microsoft Project. Various
methods like Functional point etc, are used to
make an estimation. We also draw information
from past project experiences in the estimation
of new projects. |
|
Risk management
Plan |
| |
We prepare detailed document listing
the risk envisaged in the project implementation
and the mitigation strategy for the
same. |
|
System Quality Assurance
Plan |
| |
The Software Quality Assurance (SQA)
Plan describes the role and allocation of the
SQA member. Purpose of the SQA Plan is to
establish a uniform software development
process, which is applicable through out the
software development life cycle. It also covers
the processes defined in the process
guidelines. |
|
Test Plan |
| |
Contains the detailed testing plans
for the project along with the type of testing
to be done. This include the module level test
plan as well as the over all project test
plan. |
|
Training Plan |
| |
Contains the detailed training plans
for the project team for the tools and
technologies used in the design specification
document. |
|
|
Minutes of meeting -
Client |
| |
Contains details of the client meeting
and the agenda for next meeting. We follow this
standard to keep track of and follow each
interaction during project
development. |
|
Minutes of meeting -
Internal |
| |
Contains details of the internal
meeting stating observations and task list for
various team members. We follow this standard to
keep track of and follow each interaction during
project development. |
|
|
Change Request
Template |
| |
Contains request changes to be
incorporated. This also include the nature of
change, whether it is internal or from client,
scope and reason of the change. |
|
Impact Analysis
Template |
| |
Contains the details about the impact
of the change requested on the entire product
and individual module. This is very important
document, as it helps keep track of changes and
eliminate unusual bugs in the code. |
|
|
Requirement trace
ability Matrix |
| |
Contains tracking of requirements in
various stages of project, this helps make sure
that all the changes requested are incorporated
and also track change in the code. |
|
Peer Review
Form |
| |
Contains details about findings and
closure of peer review, also the details of
which document was reviewed along with defects
found and remedy for the same. |
|
Project Status
Report |
| |
Contains details of project execution
and implementation, one of the most important
activities is to track the project. We ensure
this efficiently by following our process for
project monitoring. PSR includes the details
about the status of the project as of
now. |
|
|
| |
|
| |
|
|
|
|
|
