Project Management Approach
- Objectives and Goal
Identification of main objectives and set up a goal is very important before commencing any project. Our goal is to understand specific objectives of project, achieve with speed and quality in specified time frame.
Determine main objectives and final result of project
Identification of specific objectives
Make specific objective measurable with estimated timeline and cost
Define action steps to achieve specific objective with high level timeline and milestones
Evaluate objectives and plan resources
We create document of the project goal and objectives in a vision statement that is clear, articulated, and agreed upon so that during the development process, the whole team should be focused on the right objectives, so that decisions can be made in the correct context.
- Scope and Expectations
A well written scope of work can do more for the success of a contract than any other part of the contracting process.We understand that the scope of the work directly affects the number and quality of proposal submitted. It is very important for both the parties that scope of the work must be clear, precise and complete. The scope document will cover objective of project, technical consideration, tasks and sub tasks, define milestones for tasks with schedule, responsibilities of both the parties, deliverables, data requirements, information requirements, reference material and estimation for professional and technical person hours.
Before commencing project, our project manager and system analyst interact with client personal, who shall have complete business domain knowledge to understand main objectives of project
We create SRS document based on the system feature and functionalities, task and subtask, and information gathered from client
The SRS document consists:
Goal and objectives of application
Features and functionalities
Process flow and data flow diagram
Dependencies and assumptions
Wireframe / screenshot of forms & report
Use cases OR user stories with acceptance criteria
Case study and examples
Non-data specifications such as user access performance, quality assurance requirements, business rules, security requirement and user documentation
Module wise milestone
Installation and deployment criteria
Plan of implementation,training, operation, support & maintenance
Necessary authority of both the parties should review and make necessary changes before commencing development
Sign off SRS document from both the parties
After finalizing SRS document, any minor or major change shall pass through change management process
Project Risk Assessment
Based on our past experience, the following are the perceived risks along with the proposed measures to minimize the impact. The probability and impact/severity has been classified as low, medium and high.
RISK PROBABILITY IMPACT MEASURES Unclear roles & responsibilities and availability of client's resources as agreed Low High During the first week of the project, identify specific personnel and assign roles and responsibilities Unclear expectations Low High Take time to define clear objectives, and attach a timeline for realization of benefits. Communicate regularly to manage expectations Changes in requirement during UAT period Medium High Proper review of system requirement specification document by client before development commence Unclear prioritization of product features, especially in compressed Schedule Low High Decide on the functionalities, their priorities in context of deliverability in the given schedule Lack of involvement or signoff by senior management of key strategies, plans, and issue resolutions Low High Weekly status report. Monthly project status review by the project steering committee. Call for extraordinary meeting to resolve any critical issues. Limited access to information about: business areas, their processes, information generation and usage Medium Medium Conduct management review to verify that consultant engaged in analysis activities is not being blocked from gathering information Delays in receiving: Information, Clarification Low High Give adequate notice to client for supplying requested information. Normally, client will be expected to furnish the requested information within TWO working days. Disruptions to design activities due to frequent changes in requirements design and assumptions Low High Signoffs at each stage. After signoffs, requirement changes will undergo change management process. The development environment is not available when configuration activities are scheduled to begin. Low Medium Provide adequate lead-time for hardware and software procurement and environment preparation at client's premises Errors / bugs in initial stages Medium Medium Certain level of errors and bugs are expected in the pre go live stages. We have included the concept of acceptance to reduce the risks. Exception case business requirements are discovered as users perform job duties Low Medium Will undergo regular change management process
The information systems for any business are very difficult to envisage in its completeness at the outset. The IT needs for any business evolve as the business users' work with the IT systems for a period of time and new opportunities are spotted. By this time perhaps the architecture for the system has been more or less standardized and the system development would be in advanced stages. Adding more functionality at this point results into a substantial rework and results in the budget and schedule going haywire.
This is the classic area of contention amongst the development team and the user community. We would like to follow a process based approach, wherein we can gather as many requirements as we can identify in the requirements gathering and analysis phase and implement it as per the schedule outlined above. Requirement gathering can be carried out phase wise.
While this is in progress, there will be many more ideas that can come up. All these requirements/ideas will undergo the change management process.
We advocate a strict approach to change management. Each new change is formally reviewed, estimated and approved prior to being implemented
There are several consecutive steps in a change control procedure:
Change request comes from client or project team
Project manager, with the help of system analyst and project team, analyzes the impact. The impact is estimated in staff-hours cost and business days schedule
Client approves or rejects the estimation
New Specification is developed by the project team
Changes to schedule, risk, and budget and are estimated and presented
Client approves or rejects the changes
When the above procedure is finished, the changes become effective and the project team works with the new schedule, budget and risks
Timeline and Milestone
Milestones are deliverables or major events to be achieved on a specified date. Milestones can be viewed as "how are we doing" thresholds indicating whether a project is on track to finish as expected. Milestones helps you track: projects, milestones, tasks, blocked tasks, overdue tasks, time and expense budgets and a whole lot more.
Define different phases of project and expected target date
Break apart individual phase in multiple task and define target date of individual task
Set priority of task and identify task can be executed simultaneously
Mobilize enough quality manpower and resources as per task schedule
Review status of individual task and phases as per timeline define
Push more resources and make best effort if the object is not getting achieved in provided time line
Involve third party or specialize individual in case of major technical issues
- Project Quality Management
Project quality management simply stated comprises of processes that ensure that the software project would reach its goals. In other words the software project would meet the client's expectations.
Objective: Project should be delivered as per requirements and expectations define.
Software Quality Management Key Processes
Project quality management comprises of quality planning, quality assurance and quality control processes.
Quality planning is the most important step of project quality management. We believe that proper planning ensures that the remaining quality processes make sense and achieve the desired results. We document quality planning document which includes project objective, scope of the work, project technical requirements,testcases, use cases, case studies and any predefined standards of organization or industries. Project quality head make plan for resources (testing team) as per quality plan considering project completion timeline.
Quality audit is used to evaluate the performance of the project. This helps us to ensure that the project is following the Quality Management Plan accurately at every stage of project management.
The Quality control process uses various tools to study on the work done. If the work done is found unsatisfactory it may be sent back to the development team for fixes. Changes to the development process may be done if necessary. Our quality control process make sure that project meets the standards defined and as per quality planning then the work done is accepted and released to the clients.
In all quality management processes special emphasis is put on documentation. Documentation is the key for future analysis and all quality management efforts. Following documents shall be maintained by our quality department;
Document the requirements
Scope of work
Integration and dependencies
Quality management plan
Execute test cases and (log) document the results
Fix defects and document the fixes
Quality assurance audits the documents and test logs
We maintain consistent high quality level at every aspect of business. Our quality policy is to deliver excellence in all our services to enable our esteemed customers to excel in their own business.
- Roles and Responsibilities
Projects of different sizes have different needs for how the people are organized. In a small project, little organization structure is needed. There might be a primary sponsor, project manager and a project team. However, for large projects, there are more and more people involved, and it is important that people understand what they are expected to do, and what role people are expected to fill. This section identifies some of the common (and not so common) project roles that may be required for your project.
If the project is large enough, the client shall depute primary contact that is designated as a comparable project manager for work on the client side. E-Square project manager would have overall responsibility for the IT solution. The IT project manager and the client project manager would be peers who work together to build and implement the complete solution.
One point contact and bridge between E-Square and client
Define objectives and exact requirement (scope of the work)
Should have the necessary domain expertise
Co-ordinate with different division or application user for requirement gathering
Review SRS document and give acceptance on behalf of all concern department
Shall be accessible on immediate basis to clarify project team queries.
Take training from E-Square for efficient usage of the system
Organize environment for deployment, installation, implementation & training
The person with authority to manage a project. This includes leading the planning and development of all project deliverables. The project manager is responsible for managing the budget and schedule and all project management procedures (scope management, issues management, risk management, quality planning etc.).
Understand and define main objectives and goal of the project
Communicate with client to gather all required information for project
Scope of the work
Collect reference documents
Obligation and dependencies
Features and functionalities
Understand client architecture
Understand system flow and data flow
Installation and implementation criteria
Define project milestone in coordination with client
Continuous coordination with client
Manage project milestone timeline
Help system analyst during requirement gathering
Co-ordinate and work with quality head for quality planning to achieve quality standard
Weekly status report preparation & meeting with client
Manage module wise status of development tasks, change requests, bugs and testing
Manage resources and timesheet
Do team building exercise to make best internal co-ordination while actual development
The analyst is responsible for ensuring that the requirements of the business clients are captured and documented correctly before a solution is developed and implemented.
Requirement gathering and analysis
Create system requirement specification (SRS) document and take approval from project manager of both parties.
Prepare wireframe to be reviewed by client
Responsible for the architecture design of the system/application
Discussion with developers on daily basis
Discussion with client for bugs/technical clarification on issues/limitation of technologies
Project team leader manage the day-to-day operations that lead to project completion. The leader follows a strategic vision to keep the project uniform, oversees the daily development of individual components and coordinate deadlines and leading to a successful final project.
Create project plan as per timeline
Break down project scope in multiple phases and define milestones
Create an environment oriented to trust, open communication, creative thinking, and cohesive team effort
Provide the team with a vision of the project objectives and goal
Motivate and inspire team members
Lead by setting a good example (role model) - behavior consistent with words
Coach and help develop team members; help resolve dysfunctional behavior
Facilitate problem solving and collaboration
Ensure discussions and decisions lead toward closure
Intervene when necessary to aid the group in resolving issues
Assure that the team members have the necessary technical qualification and training to effectively participate on the team
Encourage creativity, risk-taking, and constant improvement
Enforce team to implement quality plan and standards
Keep the project manager and product committee informed of task accomplishment, issues and status
Immediate decisions to troubleshoot issues that arise as the project progresses
Review the work and progress of component development frequently
Reduce rework as much as possible to comply project timeline and cost
Provide guidance to the team based on management direction
Prepare project deployment and implementation plan
Maintain project technical documentation
The developer is responsible for the actual building of the solution.
Coordination with system analyst to understand requirement
Responsible for the design and development of builds, scripts, installation procedures, and systems including source code control and issue tracking
Interface with other systems
Reporting configuration and deployment
Contributing to technical strategy, policy and procedure
Reporting on progress/issues to management and users
Responsible for software builds and release
Maintain timeline and achieve milestone
Works closely with a quality assurance team to ensure final version is up to organizational standards
Put remarks in coding at every stage of application
Working with project manager, system analyst, project leader, quality head
The designer shall be responsible for understanding the business requirements and designing a solution that will meet the business needs. The designer determines the best approach for all potential solutions as per client requirements.
Understanding project requirement
Understand how the project can be use, accordingly create optimum solution as per project
Understand data, data flow and accordingly design best model to come out user friendly interface
Design overall model, framework, screen, reports and other components
The project team consists of the full-time and part-time resources assigned to work on the deliverables of the project. This includes the analysts, designers, developers, etc. They are responsible for:
Understanding the work to be completed
Planning the assigned activities in more detail if needed
Completing assigned work within the budget, timeline and quality expectations
Informing the project manager of issues, scope changes, risk and quality concerns
Proactively communicating status and managing expectations
A quality assurance manager, also commonly known as the quality manager or quality control manager, is responsible for the development and implementation of quality management systems and procedures.
Establish and formulate quality procedures and ensure that it should be followed by team
Develop quality planning document for individual project
Make audit in regular interval for quality assurance
Ensure that mobilize testing resources as per project need
Make case studies and test cases with the help of system analyst
Write and execute test plans to comprehensively examine the software development life cycle
Review error log and do meeting with developers and testers to reduce rework
Make sure what we promised; we deliver as per expectation of client
A software tester participates in an initial consultation with client, for the purpose of understanding the scope of a project. Either independently or in a group setting, tester creates a testing plan based on the parameters outlined during the client meeting. The tester shall be responsible for performance, reliability, bugs and any other failures.
Analyzing client requirement
Coordination with system analyst to understand requirement
Prepare test strategy
Participate in test plan preparation;
Prepare test cases (for module, integration and system testing)
Create test data, test scenarios (use for test cases)
Write necessary test script
Unit testing & integration testing
Defect tracking and perform necessary retesting
Report bugs in centralized location
Coordination with system analyst & developers to clarify the bugs scenarios
Basic verification testing after application deployed on stage / production server
- Data Security
Our data protection policy sets out our commitment to protecting client data and we implement that commitment with regards to the collection, use of client data and storage of data with following principles;
Ensuring that data is collected and used fairly and lawfully
Processing client data only in order to meet our operational needs or fulfill legal and contractual requirements
Establishing appropriate retention periods for client data
Providing adequate security & backup measures to protect client data against unauthorized access,accidental loss, destruction, or damage to client data
Ensuring that all staff is made aware of standard practice for data protection
Ensuring that queries about data protection, internal and external to the organization, is dealt with effectively and promptly
Regularly reviewing data protection procedures and guidelines within the organization
Another mirror of an organization designed mainly for Domestic clients.
Environment, Health and Safety Consultancy services
Certified Training Provider
Job portal for EHS personnel
Indian Outsourcing Company