IT 3700, Section 9 – Information Technology Management
right952500BANKT & Co Team Name and Members:Annika Navac- Project ManagerTerria Byrdsong- Presentation CoordinatorKortney Campbell-Research CoordinatorBen DeJarnett- Formal Report CoordinatorNick Haun-WebmasterTeam Mission Statement:Our mission is to provide exceptional insight in information systems, and top quality service to any of our clients’ business endeavors. Team Objective:Our team’s objective is to provide quality information that will lead to the success of our clients. In doing so, we will have a fully functional website that will make it easy for our clients to access any source of research material that will be included in the formal report. While preparing the report and the presentation, we will make sure to provide correct information and submit our findings in a timely manner to our clients. All of this will be accomplished due to our great teamwork and motivation to outperform the completion. Our research topic will explore the way information systems plays a role in the sporting industry, and how they successfully implement the use of mobile apps. The purpose of this assignment is to grasp a deeper understanding of the way information systems works in the real world, which is important for us at BANKT & Company, because it allows us to use that information to bring a better understanding to our clients. We interpret the instructions in a way that everyone will have an equal amount of work, while also having a leading role within the team.We will research how the sporting industry applies information systems to its daily routine, and how the industry successfully uses mobile apps.We will present our findings using a written formal report and Microsoft PowerPoint. We will need computers with Microsoft Office to present our report, and about twenty online resources to validate our claims. Preparation and Quality:Concerning the quality of our work as BANKT & Co, we only provide the best as it comes to our research and website which will be both easily accessible to the client. We as a company define quality as a group of people who has years of experience leading up to the best possible options given to our clients whether that be more research done, different ideas for clients, trustworthy work, and whatever else need be. Quality work, to us, looks like an organized proposal that is easy to read, entertaining, knowledgeable, all which is backed up by appropriate research for clients as needed. The client comes first and we will not be satisfied until our clients are satisfied. As a team we work together to have everything done two weeks ahead of time so as a whole we can review and give our diverse input on any proposal before deliverance. We not only work together but celebrate together once we get our job done.Team Decision Making:Team decision-making is more effective when each member takes on his or hers preferred role, such as having a project manager, research coordinator, etc. Members can concentrate on their own role without the problem of everyone not agreeing on something. When there is one decision to be made, each team member should think about the decision individually and at one at a time, introducing new ideas. All members can then discuss alternatives until everyone can agree on a solution. To handle conflict, everyone should state how he or she feels about a situation while everyone else listens, so that no one is left without saying what he or she is bothered by. Next, find out what everyone needs to feel comfortable working. Then make a plan and apply it to future problems to make sure conflict does not resurface. Work Breakdown and Structure: Five team members that include the roles of Research Coordinator, Formal Report Coordinator, Website Coordinator, Presentation Coordinator and Project Manager will complete the project. The project will require three major deliverables: the team’s website, the team’s formal report, and the team’s presentation.The Research Coordinator (RC) will assign each member to find four sources, two Internet and two traditional, regarding the research topic. The deadline to have all sources turned into the RC will be on October 18th, 2015. Once the formal report is done, the RC will be in charge of checking for its authenticity, such as the citations and references. The Formal Report Coordinator (FRC) will be in charge of structuring the formal report together, and creating an outline from the resources that the Research Coordinator will provide. The FRC will assign each member of the group a section from the outline to write about in the formal report. Each member of the group will be required to write a minimum of four pages for the report, with an internal due date of November 2nd, 2015 for the rough draft, two weeks before the actual due date of November 19th, 2015. The FRC will then integrate the work done by the other group members, while working closely with the Research Coordinator and Project Manager to make sure that all of the information is relevant to the research topic. The Website Coordinator (WM) is in charge of the overall look, integration of the team’s website, and assigning the group members a page for website. While every member of the group is required to post the website on the studentweb.kennesaw.edu server, the WM will make sure that the format and layout of each team members page is the same. The WM will be the key to the website looking professional, and will help other team members if they are having trouble with anything. The team’s website has the earliest due date, October 23rd, 2015, and is therefore one of the team’s first priorities, and will be submitted internally by October 21st, 2015. The Project Coordinator (PC) will be in charge of leading the team in the team’s group presentation, and will work closely with the Formal Report Coordinator (FRC) in assigning each group member an area of expertise to present. The PC and FRC will assume that each member will present whatever topic they wrote about in the formal report. Another area the PC will be in charge of is setting the organizational pattern of the presentation, and creating the introduction and the conclusion of the presentation. Each group member will meet with the PC no later than November 19th, 2015, two weeks before the due date of the presentation on December 4th, 2015, to discuss presentation techniques. Finally, the Project Manager will be involved in all aspects of the project, working with the Formal Report Coordinator, Website Coordinator and the Presentation Coordinator. They will act as an enforcer for each member’s requirements, and be the main communicator between all the team members and coordinate the whole project, making sure that every deliverable due is complete on time. The PM will also be the lead member in completing the team’s operating agreement.Team Meetings:As it comes to attendance to team meetings attendance is mandatory on a normal circumstance, holidays and team members being out of town are marked as exceptions. The Project Manager is required to show up to every meeting but not all team meetings require every team member to be present; every team meeting must have a minimum of four team members. There are exceptions as it comes to missing a team meetings last minute when to comes to family or personal emergencies, we have a trust policy where no proof is needed for reason of absence. During team meetings phones must be turned onto silent mode so that we are focused and able to put 100% into our work and discussions. The Project Manager will take notes during the team meetings for review purposes and to send to those who could not make the meeting. Meetings will take place on campus at Kennesaw State University, team members should have material to show and discuss at each meeting which should last about an hour but no longer than three. Below is a tentative meeting schedule and is subject to change in case there is an emergency and only three members can be present.Operating Agreement ScheduleDue: 10-16-2015Meeting: 10-12-2015Review Meeting: 10-14-2015Submit by: 10-15-2015Topic on 10-12-2015: General discussion on what all team members agree on, coming up with terms and agreements, discussing the general idea of entire project, coming up with research topic. Leader of meeting: Project Manager.Team Website ScheduleDue: 10-23-2015Meeting: 10-15-2015Review Meeting: 10-20-2015Submit by: 10-21-2015Topic on 10-15-2015: Cohesiveness of team website, color schemes, finalizing team logo, overall design and function of website, tentative discussion about team paper including possibility of making skeleton for paper. Leader of meeting: Webmaster.Team Paper ScheduleDue: 11-19-2015Meeting: 10-29-2015Review Meeting: 11-02-2015Submit by: 11-16-2015Topic on 10-29-2015: Finalization of research links, finalization of skeleton for paper, discussion of overall paper, team research of topic, discussion of structure, possible proof read of each others work, tentative discussion of team presentation project. Leaders of meeting: Research Coordinator and Formal Report Coordinator.Team Presentation ScheduleDue: 12-04-2015Meeting: 11-19-2015Review Meeting: 11-30-2015Submit by: 12-02-2015Topic on 11-19-2015: Review of finished paper, discussion of PowerPoint, possible write up a draft for audio content, assign number of slides to each team member, discussion of theme and color scheme of presentation, tentative skeleton for PowerPoint presentation. Leaders of meeting: Presentation Coordinator and Project Manager.Non-Performance:If a team member misses a meeting they shall be required to bring fresh doughnuts to the next team meeting for all members and will receive point deduction from team member evaluation. If a team member fails to communicate with the other team members once they will receive a warning and be reminded they need to communicate thoroughly with the team. If a team member misses a deadline set by the group they will have one day, twenty four hours, to complete and send whatever they missed to the group. If a team member stops contributing to the team they will be warned that they are not contributing enough to the team and will be advised to improve. Any repetition of these action or not improving will result in the following actions:When a team member stops communicating or misses an internal deadline, the project manager will document attempts to communicate with the team member by phone, email and/or social media. This documentation will be copied by email to the professor. Failure to answer the team’s attempt to contact will constitute a written warning by email copied to the professor. The professor will then attempt to contact the team member by email. If the team member then does not respond to the team and professor, then the professor has the option to allow the team to fire the member. If a member is fired, he or she will be placed in the ghost group and expected to complete all project components individually.Signature: Benjamin DeJarnettDate: 10/16/2015Signature:Annika Navac_____________________________ Date: 10/16/2015___Signature:Terria Byrdsong____________________________ Date: 10/16/2015___Signature:Nick Haun____________________ ___________ Date: 10/16/2015___Signature:Kortney Campbell_________ _________________ Date: 10/16/2015___ ................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.