Project Management Methodology
Project Initiation
Project Outsourcing Form
The Project Outsourcing Form includes the details about project implementation methodologies and responsibilities on both sides. To ensure the clarity of change requests during execution and after implementation of the project, the POF also defines the process for Change Request and Approval.
Project Planning
Project Estimation
We do project estimation based on the requirements. For this we typically use tools like Microsoft Project. Various methods like Functional point, etc. are used as well. We also draw information from past project experiences in the estimation of new projects.
Risk management Plan
Modern software development methodologies reduce risk by developing and delivering software incrementally. Early methodologies suffered from the fact that they only delivered software in the final phase of development; any problems encountered in earlier phases meant costly rework and often jeopardized the whole project. By developing in iterations, software projects can limit effort wasted to a single iteration.
Software Quality Assurance Plan
The Software Quality Assurance (SQA) Plan describes the role and allocation of the SQA member. The purpose of the SQA Plan is to establish a uniform software development process, which is applicable throughout 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 includes the module level test plan as well as the overall project test plan.
Training Plan
Contains the detailed training plans for the project team on the tools and technologies used in the design specification document.
Interaction Management
Minutes of meeting - Client
Contains details of the client meeting and the agenda for the 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 Management
Change Request Template
Contains change requests to be incorporated. This also includes the nature of the change, whether it is internal or from the client, as well as the 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 a very important document, as it helps keep track of changes and eliminates unusual bugs in the code.
Requirement Management
Requirement traceability Matrix
Contains the tracking of requirements in various stages of the project. This helps make sure that all the changes requested are incorporated and also tracks changes in the code.
Reviews Management
Peer Review Form
Contains details about findings and closure of the peer review, which document was reviewed, defects found, and remedies for the defects.
Project Status Report
Contains details of project execution and implementation. One of the most important activities of any project is to track the project. We ensure this is done efficiently by following our process for project monitoring. The Project Status Report (PSR) includes the details about the current status of the project.