Project Description

The following assignment is a project charter document that analyses the documentation of the specific measurable value, identification of the project scope, scope management plan, project scheduling, WBS structure, Cost-resource analysis, verification and validation activities, and the annotated bibliography. The completion of the operations can be affectively managed for making sure that the operations can be listed successfully.

I-Crop project would be developed for aligning with the management of the activities and defining the successful alignment of the proper and effective integration development. The listing of the probable integration and development is implied for listing the alignment and development. It has been developed for analysing the integration and management. The alignment would be implied for the execution of the mobile application development and website integration has been implied for taking implied management.

• Accounts department – The feasibility of the project needs to be analysed for the management of the needs and management of the costs of project development.
• Area of usability – The user needs to be involved in the development process of the project and its priority should be managed.
• Operation management – The different areas of operation should be managed for the management of the project and it implementation should be managed by involving different group of users.
• Area of strategy – Selection of a strategy is important for successfully implementing the project and respond on the appropriate activity.
• Social Responsibility – the project should not have an impact on the social environment and the ethical issues should be identified fir the development of the project.
• Better-

The choosing of the measurable organizational values helps in improving the customer experience and reduce the errors in the final build project.

• Faster-

The operation speed for the development of the project should be faster it should have a support for the development of the project.

• Cheaper-

A flow of the expense and the cost for the project development should be analysed and a control should be made for increasing the profit percentage.

• Do more-

Analyse the scope of the project and identification of the constraints in the project.

Rank	Impact	Metrics	Timeframe
1	Accounts	Calculation of NPV and Profit	1 month
2	Customer	Suggestions and customer feedback	3 months
3	Operational	Management Plan	4 months
4	Strategic	Strategic analysis matrix	5 months
5	Social	Review of Social Sites	1 months

Scope – It is important to define the scope of the project and identify the list of deliverables of the mobile application and the website for the i-crop

Project requirements – The main requirement of i-crop is to identify the needs of the website and management of the functionality for the management of the different activity of the project.

In scope-out scope items: 

In-scope – It should consist of project initiation document, application design for the mobile and the web platform, project closure report and proper planning of the project.

Out-Scope  – It should have a transportation requirement and the communication plan that should be used for the improvement of the different project activity.

Project Deliverables: 

It consists of the initiation documents, application design for the mobile and the web platform, project closure report and proper planning of the project.

Acceptance Criteria: The acceptance criteria for the project of website and mobile application formation project of I-Crop is,

• Development of project plan
• Management of the resource allocation plan
• Project documentation
• Development of the system design
• Testing the errors

Provide a list of Resources:

The main resource identified for the project development are given below:

• System analyst
• Planner
• Project manager
• Web designer
• Application designer
• Coder
• Unit tester
• Database administrator

The following are the technology that is used for the project development such as:

• Mobile application design
• Development and website designing tool
• Database management tool

Part One: MOV – Measurable Organisational Value

Workplace

• Testing room
• Meeting and conference rooms

Milestones

WBS	Task Name	Duration	Start	Finish
0	Development of Mobile and web application for i-corp	127 days	Thu 27-09-18	Fri 22-03-19
1	Project Initiation and Planning Phase	7 days	Thu 27-09-18	Fri 05-10-18
2	Board Meeting	29 days	Mon 08-10-18	Thu 15-11-18
3	Recruitment of System Experts for Project Execution	22 days	Fri 09-11-18	Mon 10-12-18
4	Project Execution	22 days	Tue 11-12-18	Wed 09-01-19
5	Implementation Phase	25 days	Thu 10-01-19	Wed 13-02-19
6	Closing Phase	27 days	Thu 14-02-19	Fri 22-03-19

WBS	Task Name
0	Development of Mobile and web application for i-corp
1	Project Initiation and Planning Phase
1.1	Analysis of Requirements set by Company CEO
1.2	Estimation of Materials and Gadgets
1.3	Estimation of Budget and Necessary Resources
2	Board Meeting
2.1	Stakeholder Meeting for Scope Analysis
2.2	Verification of the Project Scope
2.3	Additional Inputs and Scope Modification
2.4	Approval of the Project Plan
2.5	Procurement of Budget Funds
2.6	Risk Analysis
2.7	Risk Mitigation
2.8	Final Preparations
3	Recruitment of System Experts for Project Execution
3.1	Analysis of Project Requirements by System Experts
3.2	Suggestions of Modifications by System Experts
3.3	Procurement of Resources
3.4	Initiation of the Project
4	Project Execution
4.1	Testing of Procured Hardware Devices
4.2	Payment of the Required Prices
4.3	Purchase of Software
4.4	Testing the Software Licenses
4.5	Trail of Software
4.6	Setting Up the Site for Installation
4.7	Installation Requirement Analysis
4.8	Installation of Hardware and Software
5	Implementation Phase
5.1	Implementation of All Necessary Software
5.2	Purchase of Security Software
5.3	Installation of Security Software
5.4	Testing of the Security Software
5.5	Subscription to Cloud Server
6	Closing Phase
6.1	Connection of Data Entry Devices with Main Server
6.2	Testing of the Implemented System
6.3	Testing of Installed Hardware
6.4	Testing of Software
6.5	Testing of the Benefits of the New System
6.6	Employee Training and Signoff

Resource Assignment Project Budget

The following table is created for the demonstration of the cost of the project

Ref no.	RF000701	RF000702	RF000703	RF000704	RF000705
Name of Risk	Issues in web and application development	Error in design	Cost overrun	Human Errors	Completion delay
Description	The website may not function according to the user needs and return the user to the appropriate page.	Feasibility and usability of the design is important for the analysis of the feasibility	The overrun of the budget can cause exhausting of the resource and create a plan for its management.	The human errors and the other activity can include another risk in the project	It cause missing the deadline for the completion of the final build of the website or the mobile application
Category	Technical	Technical	Financial	Human	Operational
Triggers	Failure of device or equipment	Missing of design principle	Resource shortage	Resource in manual process.	Minor issues
Potential Response	Testing the project and evaluation of the feasibility	Using of software development lifecycle model.	Development of provisional budget	Providing training to the team members	Development of contingency plan.
Risk Owner	Developer	Designer	Cost analysis	Project Manager	Planner
Probability	Likely	Possible	Possible	Unlikely	Likely
Impact	Very High	High	Medium	High	Low
Ranking	1	2	3	4	5

For the development of the quality management plan it is important to analyse on the factor that can generate errors while commencing the project. The output of the project should be acceptable such that it meeds the needs of the user. Testing should be done on the different factors following the project requirement plan and deployed in the real life scenario for its completion.  

There are different testing methodology applied for verification of the set of activities like black box testing, white box testing, alpha testing, simulation of the prototype and testing the performance.

The activity of the project should be validated and the project manager should have a control on the development of the project. Different document like checklist, risk matrix can be used for the management of the activity.

Annotated Bibliography: 

First Artcile: Managing project risks Project Skills. – Paul Newton

According to the author Paul there are some risk in each of the activity of the business and it is important to analyse the risk for analysis of the consequence of the risks. The success of the project is dependent on the right choice of the risk and avoidance of the risk. There are a certain risk level and it is important to deal with the different activities and the potential risk should be identified for the management of the development process. The project manager is responsible to manage the different activity of the project with the analysis of the requirement, assumptions, conditions and barriers. Each of the risk should be analysed according to the threats and opportunity. The identification of the risk is important for the management of the different strategy and it is important to analyse the past experiences and a risk register should be created for listing the risk and identification their root cause. The evaluation of the risk should e done before starting the development phase and different types of analysis such as qualitative and quantitative analysis should be done for the management of a variety of tool and assist for the project development.

Second Article: Project Risk Management Handbook: A Scalable Approach

According to the author identifying and managing project risk: essential tools for failure-proofing your project Bob Pieplow the objectives and benefits of the project management are analysed and the handbook is designed for increasing the simplicity of project management. There are different risk management values of the project that are needed for taking right decision and balancing the schedule, quality and cost of the project. The different factors that is important for the development of a risk management culture is defined in the report. The definition of risk and analysis of the project planning and design is important for the management of the basic process of risk management process. The three tier scalability of the project is defined and it is defined factors such as: political sensitivity, project duration, project types and sensitivity of the sponsors. The roles and responsibility of the project management team is also given in the report that helps in creating the risk register, communication plan, etc. At last the author concluded that for the success of a project the identification and the management of the risk is the most important factor.

Third Article:

The author Kendrick (2015), states that for the proper execution of a project a risk management strategy should be developed and the project should be aligned with the requirement for reducing the errors in the final developed system. A communication plan should be developed such that the team member should be involved in the project development should communicate according to the hierarchy. The possible factor of risk should be discussed with the team  members such that its solution can be identified. The priority of the risk and planning of the project is important for the execution of the different methods and analysis of the cost and budget for the development of the project. A risk management structure should be followed defining the risk management planning, risk identification, qualitative analysis of risk, risk response and monitoring the risk.

Checklist for the project

Items	Status (Running /Completed)
Development of project plan
Management of the resource allocation plan
Project documentation
Development of the system design
Testing the errors

Evaluation Criteria

The following are the criteria of evaluation that defines the success of the project such as:

• Completion of the documentation of the project
• Planning and designing approval
• Positive result and expectation
• Cost analysis

References

Bob Pieplow (2018). Dot.ca.gov. Retrieved 27 September 2018, from https://www.dot.ca.gov/projmgmt/documents/Project_Risk_Management_Handbook.pdf

Braglia, M., &Frosolini, M. (2014).An integrated approach to implement project management information systems within the extended enterprise.International Journal of Project Management, 32(1), 18-29.

Coronel, C., & Morris, S. (2016). Database systems: design, implementation, & management. Cengage Learning.

Goetsch, D. L., & Davis, S. B. (2014). Quality management for organizational excellence.pearson.

Kendrick, T. (2015). Identifying and managing project risk: essential tools for failure-proofing your project. AMACOM Div American Mgmt Assn.

Nanda, V. (2016). Quality management system handbook for product development companies.CRC Press.

Paul Newton (2018). Free-management-ebooks.com. Retrieved 27 September 2018, from https://www.free-management-ebooks.com/dldebk-pdf/fme-project-risk.pdf

Pritchard, C. L., & PMP, P. R. (2014). Risk management: concepts and guidance. CRC Press.

Schwalbe, K. (2015). Information technology project management.Cengage Learning.

Stark, J. (2015). Product lifecycle management.In Product Lifecycle Management (pp. 1-29).Springer International Publishing.

Verburg, R. M., Bosch-Sijtsema, P., &Vartiainen, M. (2013).Getting it done: Critical success factors for project managers in virtual work settings.International Journal of Project Management, 31(1), 68-79.

Verzuh, E. (2015). The fast forward MBA in project management.John Wiley & Sons.