|
A
A successful development initiative is dependent upon a Project Management Plan, which deploys the basic tenets of management and control of structured application development.
We offer software development tailored to your specific requirements and suited for your business needs. Any development initiative is thoroughly analyzed, ensuring a Project Management Plan that addresses every minute detail of that initiative.
Our project management methodology encompasses:
Requirement and Scope
Analysis
Input: The key components in this phase are user requirements, existing documentation, and acceptance criteria. Project scoping, problem definition, and problem decomposition are also included.
Process: At this stage, the requirements obtained from the client are analyzed and broken down into clear, functional feature units. This step is an interactive and iterative process, culminating in an identified high-level final software architecture model.
Output: This activity results in approved/base-lined Software Requirements Specification (SRS). Test plans and test cases creation are also started at this stage.
Design
Input: SRS forms key input. Design phase involves identifying methodologies and frameworks for project implementation.
Process: This process includes developing low-level design artifacts, data model, object model, test plans, test cases, and implantation plans. This step also includes building class diagrams, sequence diagrams, and collaboration diagrams. An effective use of established framework models and design patterns ensures a robust and scalable implementation of high-level architecture. The design specifications are documented, reviewed, and revised.
Output: Consists of
approved Design Specification Document, test plans, and test cases.
Development
Development infrastructure and communications are an essential part of any off-shore delivery.
Our hybrid model and project management approach ensures a strong synergy between the stakeholders, On-site Team (OT), and Off-shore Development Center (ODC). The success of any off-shore development initiative depends on development infrastructure and its accessibility, as well as effective communication between all on-site and off-shore team components.
-
Remote access to the customer’s environment through a secure, high-speed connection to the customer’s gateway and
VPN..
-
Isolation of modular systems for off-shore development. These systems are independent of other subsystems and can be programmed independently.
-
Replicated or mirrored environments wherever possible.
NOTE: This alternative may not be viable for highly distributed component architecture applications that involve intense information exchange with other systems.
-
Remote component testing.
-
Performance testing.
-
Onsite deployment, integration, and testing.
Quality Management
Quality control is an important part of our development philosophy. Our Quality Management Plan defines the quality control mechanisms that protect our development processes. Our Quality Management Methodology provides guidelines that assure the quality of procedures, work instructions, standards, testing, review, and development.
These guidelines also ensure compliance as per ISO 9001/CMM 5 guidelines. Our Quality Management Methodology covers personnel involved in the administration, development, implementation, and execution of the developing product or application.
Project Status
Management
Project Status will be monitored during each phase of development. Status managing activities include:
-
Tracking And Monitoring
Both the OT and ODC track and maintain records of problems and technical issues related to any stage of application development. Our experienced project teams ensure that these issues are evaluated, remedied, and closed within an appropriate timeframe.
Joint Reviews
Joint reviews will be conducted according to schedules listed in both the chart of events and the Project Management Plan. These reviews discuss project schedules, deadlines, constraints, risks, change requests, or introductions of any new functionality and its impact together with any other project aspects warranting intervention. Such joint reviews will be scheduled at the onset of the project. JSIMPLE wants participants to be informed of any reviews meetings in advance, ensuring availability for specified meeting dates.
Status Reports
JSIMPLE uses a reporting mechanism to effectively communicate project status to all participating teams, namely the CIT, OT, ODC, and the steering committee. The reports include summary information on:
~ Project Schedule, i.e. – milestones and deliverables
~ Constraints and risks
~ Minutes of previous meetings
~ Change-in-management issues
~ Overall summary of tasks completed during the reporting period
-
Escalation process
Identification: Issues can be identified by any member of the project team. The initiator should document the issue and inform the project manager in writing.
Logging
Issues:
All issues will need to be logged into the JSIMPLE support website. Issues not attended to for two days will be automatically escalated to Level 2; after five days issues will escalate to Level 3.
Incidents
–
High Priority Issues: All high priority issues are considered incidents and are reviewed at regularly scheduled project team meetings. All incidents are reported to in the Project Status Report provided on a weekly basis to the client by the JSIMPLE project manager.
Project report Data
Throughout the project schedule, JSIMPLE will maintain the project summary data and log the minutes of each meeting or joint review held both on-site and off-shore for each project. A project log includes plans, architecture, minutes of meetings, defects identified,
“risks and their
mitigation,” timelines, and delivery.
This summary data will help us analyze project monitoring and execution, allowing us to refine our processes. The project summary data will be reviewed at various phases throughout each project to evaluate performance and established benchmarks for all projects.
Contact
US
|