News
October 6th, 2008
This year again, IT Six is a co-exhibitor on the Romanian booth at SYSTEMS, the biggest regional IT event in Germany, the leading B-2-B trade show for IT, Media and Communications. read more
May 20th, 2008
IT Six Global Services was selected to take part in a live TV show being recognized by the Romanian National Television as one of the most successful companies in Romania. read more
May 10th, 2008
IT Six Global Services will be exhibiting at the Gaylord National Resort & Convention Center, Washington DC, as part of the Romanian delegation at the " Gartner Outsourcing & Vendor Management Summit 2008", between May 19th and 21st, 2008. read more
|
 |
|
 |
|
|
Software Development
Project Analysis
Project Execution Methodology
1. Service Level Agreements
1.1 Scope of work
1.2 Deliverables
1.3 Milestones
1.4 Response time
1.5 List of responsibilities
2. Process Management
2.1 Estimations
2.2 Detailed planning (use an hours/man estimate + percentage of completed work)
2.3 Specific tools used for development (from development tools to plug-ins and so on)
2.4 Document source code by developers
2.5 Unit testing
3. Project Monitoring
3.1 Communication with clients
3.2 Conferences, meetings, reports, e-mails, weekly reviews
4. Skills Management
4.1 Identify skill needs
4.2 Arrange training as required
Stages in developing a project
- Requirement Study Phase: develop the business case and the requirements specifications documents;
- Architectural Design Phase: evaluate certain architectural designs, choose the best one and plan a staged delivery process for the selected one (basically, create the main milestones);
- High Level Design Phase: high level design document, database design document, integration test cases
- Low Level Design Phase: detailed design document for all modules (basically, this document will be very technical so that the developers would use it in the implementation of the requirements as easily as possible)
- Development Phase: source code, document source code and unit testing
- Testing & Deployment Phase: testing execution reports, user guide, deploy the application, organize trainings for usage of the developed product.
Project Execution
Creation of various plans - project plan, quality plan, configuration management plan, risk management plan
Creating the development environment
Complete briefing at the start of a project. The entire team is apprised of the project definitions, customer's objectives and policies, project goals, process to be followed, standards, risks, delivery, quality commitments and project plan
Task allocation - weekly basis
Status reporting of assigned tasks - weekly basis
Daily team meetings - to address status of the project, task execution, issues found/resolved, resources (hardware, software) problems, project changes, team recommendations, managing slippages, motivational aspects, etc.
Change Control & Risk Management
Change Control
During the lifecycle of the project, all changes are carried out through the change control procedure. Changes are defined as those activities not included in the scope of work or which alters the scope of work. The change control procedure is initiated by the client and is recorded by the Project manager and analysed for implications on functionality, design, schedule, resources, etc. Once the impact on the project has been evaluated, the change request and the impact analysis are presented to the customer for approval.
Risk Management
Risks are identified at various stages: contract review, project planning and project execution. Both internal and external risks and probable time and impact are identified and tracked on a regular basis. This enables the project team to ensure that all risks affecting the course of the project are known and managed. Mitigation strategies are identified for each risk and a contingency plan is defined to handle them.
|
