Search Home   |   Sitemap
 
IKF : project development methodology, website development methodology, software project documentation, software development methodology
project development methodology Introduction
website development methodology, Methodology
software project documentation Tools and Technologies
software development methodology Web based Services
website development services Application Testing
application testing services Ecommerce Solutions
ecommerce solutions SQL Injection Prevention
prevent SQL injection Academic Web Application
academic web application ERP Systems
ERP solutions india CMS Tools
CMS development services SMS Gateway Integration
SMS gateway integration Community Forum
database migration solution Data Migration & Mining
 
offshore software solutions Methodology
 
The objective is to provide common standards to ensure that projects are conducted in a disciplined, well-managed, and consistent manner to projects completed on time and within budget.

Large, complex projects require a more rigorous application of management processes than small, well-defined projects with readily achievable goals. The methodology supports this need for flexibility.
 
software project documentation
 
Analysis Phase
This section describes the activities and tasks required during the concept phase of the project lifecycle.

The concept phase is a three-stage project management process for investigating and satisfying a customer's need to achieve a business outcome. It can be a very short, simple process completed by a single person in a matter of days or it can be a major exercise in its own right taking years to complete and requiring a significant commitment of resources.

The first stage of this phase is the development and consideration of the proposal, a document that outlines the need and presents a plan for conducting the next two stages.

The second stage is to conduct an options analysis to identify and evaluate all plausible options for satisfying the customer's need.

The final stage is the preparation and submission of the project business case, a cost benefit analysis developed around the preferred option.

Between each stage is a formal decision point where the project can be terminated if it becomes apparent that the project is not viable. This minimizes the cost to the organisation.

Purpose :
»
Develop and document a thorough understanding of the customer's needs (problem or opportunity)
»
Identify and evaluate the range of possible solutions and select a preferred solution
»
Present an unbiased business case that details the costs, benefits and risks of the preferred solution against the organization's strategic objectives and priorities.
»
The objective is to provide sufficient detail and rigor in the options analysis and business case documents to enable the decision maker to make an informed decision.
»
Accept and initiate the project
»
Understand and articulate the requirements
»
Provide a plan for the conduct of the options analysis and the submission of the business case & outline the risks.
»
Seek the release of the required resources.
»
Obtain approval to proceed with the development of the business case.

Responsibility :
The customer is responsible for initiating the concept phase. A concept phase project manager will be appointed to manage the activities, and a project team will be implemented if the size and complexity of the task warrants it.
project development methodology
Launching Phase
The development phase commences following the approval of the business case and the allocation of organizational resources. For some projects, the approval of the business case and the allocation of resources occur simultaneously. For many projects however, the allocation of resources occurs as an independent process some time after the approval of the business case. It is not uncommon for there to be a time delay of many months or even years between the concept phase and the development phase.

This phase covers the project organizational structure, detailed project planning and design, contract establishment and detailed design. The major project management outputs are the completed project plan and establishment of any contract arrangements.

The purpose of this phase is to establish arrangements for effective implementation of the project.

Purpose :
»
To establish the arrangements and the staff necessary to manage the project. This activity follows approval of the business case.
»
Preliminary work, such as identification of skills and personnel, and the need for an advisory group, should have been commenced in parallel with development of the business case and included in the draft project plan that accompanies the business case.
»
Articulates the aim and objectives of the project.
»
Documents the initial baseline position and desired end state.
»
Details the implementation strategy.
»
Guides and controls project execution.
»
Documents planning assumptions and constraints.
»
Allocates project resources and assigns responsibilities.
»
To develop equitable, legally binding contracts, agreements and arrangements. This activity is to ensure that value for money is achieved in the acquisition of the required products and services and that the processes utilized are in accordance with organizational policies and standards.
»
Confirm the project team/contractors understand their roles and responsibilities and are prepared and ready to proceed to the implementation phase.
»
Confirm that the project plan meets the customer's requirements.
»
Confirm budget and schedule.

Responsibility :
The project manager is responsible for this phase. Responsibilities will be assigned to component managers, team leaders and others.

Implementation Phase
This section describes the activities and tasks required in the implementation phase.

This phase covers the activities necessary to produce, test and commission project deliverables in accordance with the project plan. The scope may also include the decommissioning of any existing or legacy systems and the migration to the new system if included in as part of the project.

The purpose of this phase is to ensure that: project implementation occurs in accordance with the project plan project progress is monitored and tracked against the planned schedule unacceptable variance is identified early and action taken to bring the project back on track the products and deliverables are produced to the required standard and specification the product or service is commissioned and brought into operation.

This activity covers all tasks associated with implementing the plan, tracking progress, managing issues and controlling change. This activity produces several outputs:
»
Regular project update reports.
»
Updated issues, risk and learning registers.
»
Approved change requests.
»
Records of meetings.

Purpose :
»
Control the project so it is completed on time and within budget.
»
Control changes.
»
Manage risk and issues.
»
Keep stakeholders informed.
»
Capture learning.

Responsibility :

The customer and project manager have responsibilities in this phase.
website development methodology
Finalization Phase
This section describes the tasks required in the finalization phase of the project lifecycle. These activities are necessary to conclude a project that has reached its planned end, or because a decision has been taken to abort or cease work on the project. For the latter case, not all activities and tasks in this phase will be applicable and the project manager will need to exercise discretion and judgment. During this phase the project team must maintain their vigilance to ensure that all the work is completed in a timely and efficient manner.

This phase covers the activities needed to transition control of the product to the customer, closing down the project and undertaking performance review and evaluation. Finalization follows the successful commissioning of the product.

Purpose :
»
The objective of this activity is to determine whether the customer's need has been satisfied and incorporate lessons learnt back into the strategic and business planning processes.
»
To ensure customer satisfaction with and acceptance of the project deliverables and handover package, including the handover report.
»
Identify and document how the project performed in terms of the success criteria and key.
»
Performance indicators established in the concept phase.
»
Evaluate the organizational processes and procedures used throughout the project.
»
Identify where problems occurred, and recommend improvements identify and explain any variance between the initial baseline plan, contract and schedule and their final versions.
»
Assess how well the individual management plans performed (risk, safety environment, and so on) and identify procedural modifications that would improve their performance.
»
Document the evaluation in a project completion report.
»
Project information is stored and archived appropriately.
»
All applicable financial and administrative legislation, regulations and instructions are complied with.
»
Raise a review team and conduct the review.
»
Determine the final cost of the project.
»
Evaluate the outcomes in terms of the original need.
»
Identify lessons learnt in terms of organizational processes and procedures.
»
Document the review.

Responsibility :
The project manager is responsible for this phase. The customer is responsible for the conduct of the post implementation review and incorporation of lessons learnt.

 
software project documentation
 
 
 
 
 
Disclaimer | Privacy Policy | Terms of Use | Resources | Copyright © I Knowledge Factory Pvt. Ltd. | All rights reserved.