Background to the Project Overview
Project name: I-Crop Project Management
Team details:
Team Name: SmartTech IT Group
There is a rapid change in business activities, for instance, most companies have upgraded their systems from standalone to internet based, therefore; enhancing communication between management and their customers (Paterno, 2012). Internet-based applications are vital, for instance, a company can automate its activities, therefore; enhancing easy management of operations (Ra et al., 2011). Besides, it can also enable a company management to communicate effectively to its customers through recent technologies such as Customer Relationship Management (CRM), therefore, maintaining its customers and increasing sales (Ernst, Hoyer, Krafft & Krieger, 2011). However, there are some factors that should be considered prior to incorporating IT solutions, for instance, choosing best vendors is one of the factors that need to be considered as there are several vendors such as IBM (Watson, 2014). A company can evaluate different vendors depending on its previous experience more so focusing on how its solutions were implemented and whether a given company can develop a quality application. Regarding Globex company, which is found in Riverina Region of NSW, has contracted most of its application development projects to Virtucon. Currently, Virtucon has been contracted to develop an internet-based application referred to as I-Crop. My team, which has four members, has been assigned to develop proposed application. Hence, this paper has described entire processes that we followed while developing proposed application.
Project description is vital as it forms a basis for developing specification. It consists of detailed description on how proposed system should work, including transactions that can be supported. Therefore, any company must come up with preliminary description in respect to proposed application. The first step of writing project description is defining problems encountered and consequently, explaining explicitly how proposed application can solve situation at hand. Regarding Globex Corporation, there are some reasons for developing proposed system, for instance, there is a need of connecting growers with buyers through proposed application, easing management of operations and selling warehoused grains. Apart from selling warehoused grains, Globex also buys grains.
Other than describing problems that need to be solved, Globex has also defined transactions regarding proposed application and ways on which it can solve problems as it is a new application rather than replacing existing application. I-crop application consists of several features such as offer and bid transactions. Concerning offers, I-crop will allow sellers to set their cash price, and afterwards, potential customers can accept offers that have been placed. Similarly, buyers can list their preferred cash prize, and afterwards, growers or sellers can view and sell their grains. Listing of cash price is called as bids. Therefore, offers and bids cannot be separated, thus working hand in hand.
Apart from offers, I-crop will also enable sellers and growers to list their preferred buyers, therefore; selling grains to trusted buyers. Besides, I-crop will not support both bids and offers that were placed for previous seasons, thus supporting seasonal sales. Furthermore, it will enhance availability of information such as contact details about grain silo sites though only limited for those ones that are registered. Moreover, I-crop will be implemented as both a mobile application and website, therefore; supporting a range of users. Although clients are not supposed to pay any subscription fee to download the application, but normal network charges will apply. In addition, a client will be informed incase high internet connectivity may be required for updating information on a certain page because businesses are dynamic, thus offers and bids are likely to change from time to time. Regarding miscellaneous features, user’s interphase will enable a client to download summaries of a given page using ‘printing option’ button. Besides, any client can be a seller or a buyer concurrently, which will be made possible using one login system.
Skills & knowledge inventory |
Member 1 |
|
Member 2 |
||
Member3 |
||
Member4 |
||
Roles and Responsibilities |
Member 1 |
|
Member 2 |
||
Member 3 |
||
Member 4 |
||
Team communications |
Week-5 |
9am-6pm. Motel 24. |
Week-6 |
3pm-10pm. Globe Apartments. |
|
Week-7 |
8am-4pm. Albury Manor House. |
|
Communication and sharing methods; google hangouts and skype (Tang, Wei & Kawal, 2012). |
||
Team rules & expectations (team values, code of ethics, rules & expectations) |
Team values |
<Commitment, dependability, reliability, respect, positivity, teamwork (Warren & Lucas, 2016)> |
Code of ethics |
||
Rules and expectations |
||
previous experience as team |
Member1 |
I’ve identified some positive and negative impacts of working as a team member such as enhancing collaboration and resulting in conflicts respectively. Teamwork aims at development of new ideas as well as sharing of information, thus increasing productivity. |
member |
||
Member 2 |
I’ve worked previously as a team member, and afterwards, identified some of its positive and negative impacts such as enhancing collective ownership and encouraging laziness respectively. |
|
Member 3 |
From my experience, I’ve identified some of the positive and negative impacts associated with working as a team member such as development of a quality application and time consuming respectively. |
|
Member 4 |
I’ve worked previously as a team member, and afterwards, identified some of its positive and negative impacts such as enhancing innovation and communication breakdowns respectively. |
|
Signatures |
Member1 |
<> |
Member2 |
<> |
|
Member3 |
<> |
|
Member4 |
<> |
Week-5 |
Organiser |
Scribe |
What should be done? Determining total costs that will be incurred for developing i-Crop application, identify and analyze requirements collected through Requirement Engineering. (RE) (Abrahamsson, Salo, Ronkainen & Warsta, 2017). |
What was done? We estimated costs that will be incurred by Globex company for development of i-Crop application to 2000 U.S dollars. However, an addition of 1000 U.S. will be required to purchase necessary infrastructure. Thus, we approximated total costs for development and implementation of i–Crop to 3000 U.S. dollars. Also, we interacted with relevant stakeholders and afterwards, developed specification. Diagrammatic representation of requirements collected by UML diagrams using software such as ArgoUML. |
|
Week-6 |
Organiser |
Scribe |
What should be done? Designing application using project management methodologies such as agile and waterfall. Choosing best programming language that can be used to develop a quality software. (Abrahamsson et al., 2017). |
What was done? We developed i-Crop using both agile and waterfall methodologies. Besides, we written codes using C# and android programming language alongside other languages. Moreover, we executed codes using android studio alongside other software. |
|
Week-7 |
Organiser |
Scribe |
What should be done? Configuration of all individual components, selecting best platform for creating database, testing application that was developed; both users and release testing (Bhuvaneswari & Prabaharan, 2013). |
What was done? We integrated individual components to form i-Crop application, developed MySQL database, and afterwards, connected with i-Crop application. We tested i-Crop properly through generation of test cases from data that was entered by customers. |
Project Description
Communication Plan
Stakeholder name |
Information to be shared |
Frequency of information exchange |
Location of information exchange |
Purpose of communication |
Mechanism (hard copy, PDF, PPT, DOC) |
Who |
what |
when |
Where |
Why |
How |
Business analyst (Eva, Hindle, Paul, Rollaston & Tudor, 2014). |
Software requirements |
Held meetings weekly. |
Motel 24 |
To understand real needs of Globex; including ways on which it carries on its day-to-day business operations, learning much on business models that are currently used in Globex company and understanding how proposed application can improve ways on which operations are carried out. |
DOC |
System designers (Abelein, Sharp & Paech, 2013). |
System designs |
Held meetings after every two weeks |
The Houston Wagga |
Understanding information related to a plan that shows guidelines, which should be followed while developing i-Crop, ensuring that application has been developed in accordance with specification and understanding recent technologies that should be incorporated. |
PPT |
Security administrators (Thomas, Gorman, Beal & Wilson, 2011). |
Security of i-Crop |
Held meetings monthly |
Globe Apartments |
Understanding security mechanisms that should be incorporated into developed application, ensuring that database and servers are working correctly, ensuring that i-Crop is secured against attacks and ensuring that proper measures have been undertaken aiming at preventing anticipated risks from occurring. |
|
Operational team (Wallach & Scholz, 2012). |
Configuration of individual components and overall functionality details |
Held a meeting after two months |
Victoria hotel |
Ensuring that developed application is functioning properly, ascertaining that different information systems have been integrated correctly such as ERP and CRM systems, evaluating performance of i-Crop by measuring its response time as well as time taken before server has replied to different requests and loading pages. |
PPT |
Reflection
Leadership Qualities to Successfully Lead a Project
I’ve lead some teams and realized that a project manager should be equipped with some leadership skills to make the entire development process a success (Keil, Lee & Deng, 2013). For instance, communication skill is very important as it can enable a project manager to describe explicitly project objectives. Therefore, a project manager is required to master different communication forms, for example, full-staff and phone calls respectively. Also, a project manager should also be equipped with motivation skills, which can enable him/her to inspire other team members (Sunindijo, 2015). There exist several methods that can be used to motivate team members such as providing rewards and mentoring. Besides, leaders should also have delegating skills, for instance, most leaders fear to assign duties to their employers and keeps on working on them. Delegating tasks can enable a project manager to identify strengths and weaknesses of other members. Furthermore, positivity is an important leadership skill that can enable a project manager to have hopes that everything will go on well despite some challenges encountered. Moreover, accountability skills can enhance trustworthiness, therefore; encouraging team members to ask for clarification when the need arises (Sunindijo, 2015).
Other than leadership skills, I’ve also identified different techniques, methods and skills, which can be used in leading ICT projects, therefore, knowledge of methods cannot be an option to a project manager rather a necessity. For instance, agile methodology can assist project manage to plan activities properly (Balaji & Murugaiyan, 2012). It enhances involvement of stakeholders in the entire process involved for development of a system. Therefore, incorporation of ideas of stakeholders results in development of a high-quality system. It’s used widely because of sprint principle, which facilitates accommodation of necessary changes at any stages of system development life cycle. Also, waterfall methodology can be used to lead a project (Balaji & Murugaiyan, 2012). It’s convenient for leading larger and complex projects rather than small projects. Activities are carried out sequentially. All tasks required for developing an application are listed ranging from requirements collection to maintenance. The main disadvantage of waterfall methodology is that changes cannot be made at any stage till completion. Apart from waterfall and agile methodologies, there are other methodologies though rarely used, for example, scrum, which is made up of different values such as respect and lean methodology, which minimizes waste (Balaji & Murugaiyan, 2012).
Conclusion
In conclusion, SDLC consists of four main stages; specification, development, validation and evolution, therefore; understanding all processes involved is much important as it provides guidance while developing any application. Regarding development of i-Crop application, I ensured that all processes were followed strictly. For instance, we collected requirements from relevant stakeholders such as business analyst and system administrator of Globex Corporation. Apart from requirements collection, we developed i-Crop application in accordance with specification using programming languages such as C# and android programming for website and mobile application respectively, and afterwards, several stakeholders participated in testing i-Crop, for example, operational team and security administrator of Globex Corp.
Team charter
The entire process was completed successfully as we specified some code of ethics, rules and values that each member was to adhere strictly. For instance, the following are some of the values that we specified; commitment, dependability and reliability, while code of ethics included the following; understanding requirements of proposed application, use of appropriate methodology, ensure that application is tested properly and informing Globex management concerning any dangers associated with developed application. On the other hand, all team members were required to respect others including stakeholders and being transparent were some of the specified rules. However, few problems encountered include; time consuming and communication breakages.
References
Abelein, U., Sharp, H., & Paech, B. (2013). Does involving users in software development really influence system success? IEEE software, 30(6), 17-23.
Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017).
Agile software development methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Balaji, S., & Murugaiyan, M. S. (2012). Waterfall vs. V-Model vs. Agile: A comparative study on SDLC.
International Journal of Information Technology and Business Management, 2(1), 26-30.
Bhuvaneswari, T., & Prabaharan, S. (2013). A survey on software development life cycle models. Journal of Computer Science and Information Technology, Vol2 (5), 263-265.
Carsten B.S. (2011). IT for a better future: how to integrate ethics, politics and innovation. Journal of Information, Communication and Ethics in Society, 9(3), 140-156.
Claro, M., Preiss, D. D., San MartíN, E., Jara, I., Hinostroza, J. E., Valenzuela, S., & Nussbaum, M. (2012).
Assessment of 21st century ICT skills in Chile: Test design and results from high school level students. Computers & Education, 59(3), 1042-1053.
Devolder, A., Vanderlinde, R., Braak, J., & Tondeur, J. (2010). Identifying multiple roles of ICT coordinators. Computers & Education, 55(4), 1651-1655.
Ernst, H., Hoyer, W. D., Krafft, M., & Krieger, K. (2011). Customer relationship management and company performance—the mediating role of new product performance. Journal of the academy of marketing science, 39(2), 290-306.
Eva, M., Hindle, K., Paul, D., Rollaston, C., & Tudor, D. (2014). Business analysis. D. Paul, Yeates, & J. Cadle (Eds.). British Computer Society.
Keil, M., Lee, H. K., & Deng, T. (2013). Understanding the most critical skills for managing IT projects: A Delphi study of IT project managers. Information & management, 50(7), 398-414.
McDermid, D. (2015). Ethics in ICT: an Australian perspective. Pearson Higher Education AU.
Paterno, F. (2012). Model-based design and evaluation of interactive applications. Springer Science & Business Media.
Ra, M. R., Sheth, A., Mummert, L., Pillai, P., Wetherall, D., & Govindan, R. (2011, June).
Odessa: enabling interactive perception applications on mobile devices. In Proceedings of the 9th international conference on Mobile systems, applications, and services (pp. 43-56). ACM.
Sunindijo, R. Y. (2015). Project manager skills for improving project management. International Journal of Business Performance Management, 16(1), 67-83.
Tang, J. C., Wei, C., & Kawal, R. (2012, February). Social telepresence bakeoff: Skype group video calling, google+ hangouts, and microsoft avatar kinect.
In Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work Companion (pp. 37-40). ACM.
Thomas, O. M., Gorman, R. F., Beal, S. K., & Wilson, S. (2011). U.S. Patent No. 7,958,234.
Washington, DC: U.S. Patent and Trademark Office.
Watson, H. J. (2014). Tutorial: Big data analytics: Concepts, technologies, and applications. CAIS, 34, 65.
Wallach, D., & Scholz, S. C. (2012). User-centered design: why and how to put users first in software development. In Software for people (pp. 11-38). Springer, Berlin, Heidelberg.
Warren, M., & Lucas, R. (2016). Ethics and ICT: Why all the fuss? Journal of Information, Communication and Ethics in Society, 14(2), 167-169.
Whatley, J. (2012). Evaluation of a team project-based learning module for developing.