Project i-Crop
This a new add-on service for the Globex corporation which seek to provide an online platform that shall link the grain growers to the potential buyers who may then repackage for export and sell to the local market, enabling both brain growers and buyers transact conveniently and efficiently by removing the geographical barrier which has made the business susceptible to unscrupulous middlemen.
Team Lion is tasked with the delivery of all the user requirements for the project i-Crop. The team member and their contact details are as shown below,
Team: LION Project: i-Crop
Name |
|
Phone |
Mathew Fitzsimmons |
0712521222 |
|
Rufaro Mafuta |
0712556222 |
|
Aaron Thomas |
0714856254 |
|
Vipulkumar Vaishnav |
0718252355 |
|
0712568785 |
Team lion has a battery of specialist geared towards the success of the project, the following table details the various specialists and their core functions in the i-Crop project,
Role |
Name |
Responsibilities |
System Analyst |
Mathew Fitzsimmons |
Will be lead in the whole project and acts as a link between the team and the clients |
Databases Administrator |
Rufaro Mafuta |
Is concerned with the proper creation of entities models, designing and creating tables to be used by the application |
Software Architecture |
Aaron Thomas |
Will use his long experiences to come up with software design and new requirements into the design. |
Developers |
Vipulkumar Vaishnav |
Will be involved in the actual coding and building of the i-crop app, perform various tests and document the various functionality. |
Baddege Wijesinghe |
The team has identified the email as the primary mode of communication for official communication between the peers and the client.
The team shall meet on second Friday of the month at the Head Office in Adelaide, South Australia for a standing meeting to establish the progress of the project. All meeting shall begin from exactly 08:00 am with a quorum of 3 members. (Kerzner & Kerzner, 2017)
The agenda of the meeting shall be emailed three days prior to the meeting by the secretary, who doubles as the software architecture. All the proceeding of every meeting will be documented and filed in the team’s cabinet at the headquarter, this includes the minutes and the attendance list. A copy of the minutes must be emailed to all team members for their review and reference (Murad & Cavana, 2012).
From our last project which was marred with a lot of controversies due to non-commitment on part of some members, it was deemed important that the team establish strategic goals, code of ethics and some ground rules earlier before problems escalate in the future (Gasik, 2011)
Our overall goal is to deliver i-crop application service on time and high quality within a maximum scope. The achievement of this goal shall be a matrix of delivery of the agreed scope, stretch goals and the product meeting the exit criteria (Bygstad & Lanestedt, 2009).
The following list is our established team values that all members shall identify with,
- Faster Feedback
- Clean code
- Repeatability
- Simplicity
- Team collaboration
- Respect
- Agile
Team Lion believe in the values of integrity in the software development lifecycle and every member must put on integrity while making decisions that affect the other team members and the project at large.
- All members must be punctual in meetings
- Agenda must be disseminated to all members a day to the meetings
- Minutes must be disseminated to all member immediately after the meeting concludes
- Absenteeism is highly discouraged unless in emergency situations
- Respect each other’s opinion
- Meeting time is from 08:00 am on the second Friday of the month
- Key decisions require 2/3 member’s approval
- Keep the team leader updated on the task assigned to a member
Learning cycle is important in the agile development as they give the team member a chance to learn from the experiences of another member in the course of the project (Larson & Gray, 2015). The learning cycles will coincide without sprints which are every two weeks with the first cycle being led by Mathew Fitzsimmons as the organizer and Rufaro Mafuta as the scriber (Berggren & Söderlund, 2008). This arrangement shall be changed on a rotational basis for every sprint with the next learning cycle lead by Aaron Thomas as the organizer and Vipulkumar Vaishnav as the scribe.
The table below shows the teams view the status of the i-Crop project as it stands now. Every member was given the chance to make the high-level view of the project in terms of feasibility of requirements.
Name |
Question |
Mathew Fitzsimmons |
We seem not to have a dedicated software tester |
Rufaro Mafuta |
The user account requirement seems unclear |
Aaron Thomas |
The team seems to be geographically dispersed |
Vipulkumar Vaishnav |
The MVC framework is new to some developers |
Baddege Wijesinghe |
We need to decide on whether to start with the web app or the mobile app version |
Team Lion
Effective communication is key to the success of any software project since it always about people. The team brainstormed on some of the key stakeholders for the success of the project and each requires a different approach to communication to effectively (Ahuja, Yang, & Shankar, 2009)
Stakeholder |
Means Of Communication |
Clients |
|
Team |
Email, Whatsapp, |
Clients |
|
Partners |
Email, Whatsapp, Memo |
End Users |
Email, Face To Face |
The software projects have been faced with a lot of challenges than most engineering fields due to the overwhelming number of failed software projects (Silvius & Schipper, 2014). This is mostly due to the limited professional in the software project management. The Team Lion has been engaged in several successful software development fields in the recent years. Such projects range from web portals, standalone desktop application, and web services all geared to increase the level of automation in the business domain. The team is experienced and with their level of organization, can successfully deliver a product within the required timeline not forgetting meeting the project scope. The system analyst being the most experienced in the team has led the team Lion combat some of the very challenging, for example, the Australian National Health portal was developed under the supervisor of the system analyst. He used his long working knowledge of software development to deliver a product to the Health ministry that has revolutionized the Australian Health sector. Our able two programmers who are much experienced in the web technologies have also led some successful projects where they were the lead programmers. Vipulkumar Vaishnav was involved in programming MyTaxi, a kind of drop in for the uber mobile app. The project exposed the member to new technologies in the mobile application development. Aaron Thomas who specialized in system architecture has great analytical skills which he has employed in the development of the MyTaxi app, making the uber redesign their business in Australia to remain relevant (Lindner & Wald, 2011). The general experience from each team member is their application of their skills both technical and soft to lead various projects and agrees that qualities such as integrity, greater interpersonal skills, high level of competence, team building spirit and being able to work under pressure are some of the key qualities in leading a team of software developers. It is therefore clear that Team Lion has the skill set needed to complete the i-crop application which if implemented shall revolutionize the entire grain buying and selling business model (Froese, 2010).
References
Ahuja, V., Yang, J., & Shankar, R. (2009). Benefits of collaborative ICT adoption for building project management. Construction Innovation, 9(3), 323–340.
Berggren, C., & Söderlund, J. (2008). Rethinking project management education: Social twists and knowledge co-production. International Journal of Project Management, 26(3), 286–296.
Bygstad, B., & Lanestedt, G. (2009). ICT based service innovation–A challenge for project management. International Journal of Project Management, 27(3), 234–242.
Froese, T. M. (2010). The impact of emerging information technology on project management for construction. Automation in Construction, 19(5), 531–538.
Gasik, S. (2011). A model of project knowledge management. Project Management Journal, 42(3), 23–44.
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.
Larson, E. W., & Gray, C. F. (2015). A Guide to the Project Management Body of Knowledge: PMBOK (®) Guide. Project Management Institute.
Lindner, F., & Wald, A. (2011). Success factors of knowledge management in temporary organizations. International Journal of Project Management, 29(7), 877–888.
Murad, R. S., & Cavana, R. Y. (2012). Applying the viable system model to ICT project management. International Journal of Applied Systemic Studies, 4(3), 186–205.
Silvius, A. J., & Schipper, R. P. (2014). Sustainability in project management: A literature review and impact analysis. Social Business, 4(1), 63–96.