Overview

Activities and Artifacts

Project Management(PM)

To control a project management, planning process is very critical. During planning process, we may find that the communication is very important and may directly influence the execution of the project and also the final result, especially in the software development outsourcing environment. So at the beginning of the project we should make the communication plan which approved by the clients in order to organize and simplify this process.

• Project Schedule
• Software Development Plan
• Iteration Plan
• Communication Plan
• Project Team Structure
• Project Review Plans
• Risk Mitigation, Monitoring and Management Plan (RMMM Plan)


A transparent communication on the status may help to monitor and manage the project. In this case, IMON has customized the Project management solution to fit the needs of our client. Some clients may want to view the current status of the project anytime from anywhere, that's why now we used the online project management tool and the whole project team and some related person could update the current project status. During this process, we may create and use some documents which list below:

• Project Status Reports
• Meeting-Minutes, Communication Log
• RevIMONons of Software Development Plan
• Requirement Change Impact Document
• Project Coding Standards and Code Repository
• Daily Meeting & Report
• Nightly Build
• Team Member Weekly Report
• Exception Report

Software Quality Assurance(SQA)

To well manage the execution of the project at IMON, a set of documentation, project development methodology and testing techniques should be followed, some of those are:

• Software Quality Assurance Plan
• Policy for Implementation of SQA
• Deviations in Software Activities and Software Work Products Procedure
• SQA Participation Procedure
• SQA Reports
• SQA Reviews Procedure

Software Configuration Management (SCM)

To guarantee the configuration management of the project specific documentation and code, an identified project team member is responsible for the planning and execution at IMON. Some documents generated and used by the project team are written down:

• SCM Activities Plan
• SCM Policy
• Changes to Baselines Procedure
• Software Baseline Library Product Creation and Release Control Procedure
• Configuration Items/Units Status Review Procedure
• Standard Software Configuration Management Reports

Channels for communication

• Bridge SE & Clients - talk face to face in working language
• Web Conference - via MS NetMeeting, MSN or other facilities
• Weekly Report - via email or fax
• CVS - access all documents in repositories via Internet
• Daily Log - via email
• Weekly Conference, onsite, in the development team
• Emergency Call System will be setup
• Telephony Conference between Clients and Team when necessary
• SQA Weekly Reports - via email
• Tracing System will be setup by PM. Trace Table will be sent to clients when necessary

Suite of Tools

• Project Management Tools: Projekt or eGroupWare, MS Project
• SCM Tools: CVS or MS SourceSafe
• Analysis & Design Tools: Rational Rose or MS VIMONo
• Document Tools: MS Office
• IDE Tools: Eclipse, MS Visual Stuio, UltraEdit etc
• Test Tools: Loadrunner, Rational Robot etc
• Bug Management Tools: Bugzilla, BugFree
• Deploy Tools: Jakarta Ant, InstallShield etc
• Communication Tools: MSN, MS NetMeeting, Skype etc
• Other Tools: Acrobat Reader, ftp tools, MS outlook etc

• Prototype and High Level Diagrams - In a well defined process, we may usually generate some   documents. But most customers perhaps don't know whether these are what they want for their   payment. Prototype and High level diagrams could help the clients to have a clue of what will be   delivered after coding.
• Iterative and Incremental Development - Our process is an iterative process. As soon as an   iteration is completed we release a milestone version and send it to the customer. This enables   customers to track progress and notify us with any changes in flow.
• Periodic review and update to the client - The project leader may review the project every week   and provide client the update about the schedule, completed targets and planned targets for   the next week.
• Checklist method - In order to dramatically reduce the commonly made mistakes made by the   developers while designing, coding, releasing and deploying, IMON follow checklist method from   planning to deployment.
• Well defined architecture - In order to train newly recruited developers quickly, a well-defined   architecture was made by IMON. What's more, this architecture should be known well by every   project member and is also followed in all the projects. We could control manpower resources   efficiently every developer can be deployed on any project in no time.
• Common Libraries - Because these are common functions required while coding of any project,   we have coded a set of libraries which the developers uses while coding the application, which   helps expediting the development and virtually eliminating bugs as these libraries are well   tested and optimized.
• Knowledge management - In order to reduce the development time, we added common   functions and solutions to challenges and issues to our Knowledge management application.
• Task and bug tracking system - We have a project management application to manage/track   both bugs and tasks with advanced reporting, tracking and auditing features, for it is usually   very difficult to manage bugs where multiple Quality Engineers and developers are working on   an application. That would also help to improve the quality of each project.
• Source code and version control system - We use Concurrent Version System (CVS) for   source code and version control to avoid related risk during developing an application.