Abstract ITWeb organization is a small scale web development firm that belongs to the IT industry. It provides web solutions and services to its clients and primarily deals in the domains of commercial solutions, finance, marketing and healthcare. ITWeb comprises of a small group of resources with varying set of skills and has been able to establish itself as a reputed IT firm in the market. However, with increase in competition, the organization was facing trouble with the requirement of maintaining a competitive edge in the market. It came up with a plan to develop a smart web application for tele-health monitoring. The document covers the organization background along with time management plan, fact finding plan, AS-IS diagram along with the report to the top management. Introduction ITWeb organization is a small scale web development firm that belongs to the IT industry. It provides web solutions and services to its clients and primarily deals in the domains of commercial solutions, finance, marketing and healthcare. There are a number of web development organizations all around the globe and it has become difficult for the organizations to develop a competitive edge above the rest of the firms. Organization Background ITWeb comprises of a small group of resources with varying set of skills and has been able to establish itself as a reputed IT firm in the market. However, with increase in competition, the organization was facing trouble with the requirement of maintaining a competitive edge in the market. It later came up with a plan to develop a smart web application for tele-health monitoring. Report Overview The document is a report that covers the various details of the ITWeb organization along with it smart tele-health web application project. It covers the time management plan, fact finding plan, organization chart and other relevant details of the organization (Chang, 2013). Time Management Plan Work Breakdown Structure Task Name Duration Start Finish Predecessors ITWeb Smart Tele-Health Web Application 119 days Thu 3/2/17 Tue 8/15/17 Phase 1 - Initiation 15 days Thu 3/2/17 Wed 3/22/17 Technical feasibility analysis and evaluation of results 3 days Thu 3/2/17 Mon 3/6/17 Operational feasibility analysis and evaluation of results 3 days Tue 3/7/17 Thu 3/9/17 3 Economical feasibility analysis and evaluation of results 3 days Fri 3/10/17 Tue 3/14/17 4 Chartering of the Project 5 days Wed 3/15/17 Tue 3/21/17 5 Submission of Project Charter 1 day Wed 3/22/17 Wed 3/22/17 6 Milestone 1: Project Charter Document 0 days Wed 3/22/17 Wed 3/22/17 7 Phase 2 - Planning 25 days Thu 3/23/17 Wed 4/26/17 Requirements Analysis and Scope Finalization 6 days Thu 3/23/17 Thu 3/30/17 8 Assessment and Analysis of Project Risks 4 days Fri 3/31/17 Wed 4/5/17 10 Scheduling tasks 3 days Thu 4/6/17 Mon 4/10/17 11 Budgeting tasks 3 days Tue 4/11/17 Thu 4/13/17 12 Fact finding and Communication plan 4 days Fri 4/14/17 Wed 4/19/17 13 Project Plan Development and Submission 5 days Thu 4/20/17 Wed 4/26/17 14 Milestone 2: Project Plan 0 days Wed 4/26/17 Wed 4/26/17 15 Phase 3 - Execution 48 days Thu 4/27/17 Mon 7/3/17 Designing of the smart tele-health web app 6 days Thu 4/27/17 Thu 5/4/17 15 UI/UX design and wireframes 10 days Fri 5/5/17 Thu 5/18/17 18 Design review and change implementation 3 days Fri 5/19/17 Tue 5/23/17 19 Creation of source code 20 days Wed 5/24/17 Tue 6/20/17 20 Unit testing of the source code 4 days Wed 6/21/17 Mon 6/26/17 21 Review of the source code 5 days Tue 6/27/17 Mon 7/3/17 22 Milestone 3: Source Code 0 days Mon 7/3/17 Mon 7/3/17 23 Phase 4 - Control 23 days Tue 7/4/17 Thu 8/3/17 Implementation of the Application 7 days Tue 7/4/17 Wed 7/12/17 23 Security features 6 days Thu 7/13/17 Thu 7/20/17 26 Testing of the application 5 days Fri 7/21/17 Thu 7/27/17 27 UI and performance testing 5 days Fri 7/28/17 Thu 8/3/17 28 Mielstone 4: Implementation and Test Plan 0 days Thu 8/3/17 Thu 8/3/17 29 Phase 5 - Closure 8 days Fri 8/4/17 Tue 8/15/17 Project Deliverables Acceptance 3 days Fri 8/4/17 Tue 8/8/17 29 Sign offs 2 days Wed 8/9/17 Thu 8/10/17 32 Lessons Acquired 2 days Fri 8/11/17 Mon 8/14/17 33 Closure Report Development and Submission 1 day Tue 8/15/17 Tue 8/15/17 34 Milestone 5: Closure Report 0 days Tue 8/15/17 Tue 8/15/17 35 Gantt chart Fact Finding Plan It is essential to collect relevant information regarding the project from the stakeholders and associated entities to ensure that the project is developed as per the requirements and specifications. There are various fact finding techniques that will be used in the project that have been summarized below. Interviews Interviews are the fact finding techniques in which there are entities that are enquired about the project and its requirements. There are various steps that are included in the process of carrying out the interviews. ⦁ Step 1: Short-listing the people for interviews ⦁ In order to get relevant information about the requirements of smart tele-health app, it would be necessary to select the right set of people. ⦁ The project will have five phases as described in the time management plan above. In the initial phases such as initiation and planning, interviews shall be carried out with the middle level managers and heads of the departments. In further phases, it would be required to carry out the interviews for all people. ⦁ Group interviews shall also be carried out with correct sets of people for saving the time (Lind and Culler, 2011). ⦁ Step 2: Establishment of the objectives ⦁ Once the selection of people will be made, the points of discussion and the questions that would be covered in the interviews shall be decided. It shall cover the various areas of the smart tele-health application such as functional requirements, non-functional requirements, design constraints and likewise. ⦁ Step 3: Development of Interview Questions ⦁ A standard list of interview questions must be formed at beginning covering the general know-how regarding the application. ⦁ The interview questions must be a mix of various types of questions such as open ended questions, close ended questions and likewise (Badiru, 2010). ⦁ Step 4: Preparation for the Interview ⦁ Once the selection of people, objectives for the interview sessions and set of questions are done, preparation for the interview shall be carried out. ⦁ The interviewer must circulate the details of the interview session such as location, duration, and agenda and likewise. ⦁ A reminder shall also be placed in order to create alerts for the parties. ⦁ The list of topics associated with the smart tele-health application such as functional and non-functional requirements, design constraints, dependencies and likewise shall be circulated well in advance (Parry and Lind, 2016). ⦁ If any particular document would be necessary as references and it is available with the interviewee then it shall be asked to be carried along at the time of the interview. ⦁ Step 5: Conduction of Interview ⦁ The questions shall be asked in a particular order during the interview. ⦁ The interviewee must be made comfortable in order to gain maximum information. ⦁ The focus shall be on listening to the response that is provided for each of the questions and also a record of the same shall be maintained. ⦁ The interviewer must maintain a polite tone with the interviewee at all times. ⦁ Step 6: Document the Interview ⦁ It is essential to record the responses that are provided by the interviewee during the interview session. However, it is considered as an incorrect practice to note down everything that is responded by the interviewee. Some of the key points shall therefore be noted down. ⦁ Once the interview session is completed, a quick note down of the entire discussion shall be made to have an account of the information that is shared during the interview. ⦁ Minutes of meeting or the interview may also be circulated to have an account of the discussion that took place between the interviewer and the interviewee. ⦁ Step 7: Evaluation of the Interview ⦁ The relevant information shall then be retrieved from the interview in terms of the details of the smart tele-health application, requirements of the application and likewise. Document Review ⦁ It is a fact finding technique that would allow the system experts and project resources to understand the details of the application. ⦁ There are often scenarios wherein several drafts of the documents are made and are then modified later on. A track of all of these changes shall therefore be made. ⦁ Original copies of the forms and the documents shall be referred during the project activities. Observation ⦁ Observation is also one of the relevant fact finding techniques that is available. ⦁ It is a technique in which the practical components of the smart tele-health app will be observed and the demonstrations will be provided for the observation of the same. ⦁ With this technique the drawbacks that are associated with the interviews and the document review techniques will be overcome (Peslak, 2012). Questionnaires and Surveys ⦁ There will be various entities that will be involved with the smart tele-health application in terms of the stakeholders and project resources. It would therefore be beneficial to use Questionnaires as the fact finding technique. ⦁ Questionnaire is a document that comprises of the set of questions regarding the topic which would be smart tele-health application in this case. ⦁ There are certain guidelines regarding the smart tele-health application that would be required to be followed during the design of the questionnaire such as ease of understanding, clarity of questions and likewise (Goodwin, 2014). Research ⦁ Another important fact finding technique that will be useful in the collection of information in case of the smart tele-health application is research. ⦁ The research would include the various sources such as online magazines, articles, journals, internal and external documentation and many more. The above fact finding techniques will be used in the smart tele-health application for understanding the details of the application. The order of carrying out these techniques would be the same as listed above as there would be maximum information that will be obtained from the above techniques in the same order. Organization Chart ⦁ ITWeb Owner ⦁ President of the Company ⦁ Vice President - Systems ⦁ Project Managers ⦁ Development Team ⦁ System Developers ⦁ System Engineers ⦁ Technical Experts ⦁ Design Team ⦁ UI/UX Experts ⦁ System Designers ⦁ Testing Team ⦁ Testing Analyst ⦁ Test Associate ⦁ Implementation Team ⦁ Implementation Head ⦁ Implementation Engineer ⦁ Vice President - Sales ⦁ Sales Manager ⦁ Sales Experts ⦁ Sales Analysts ⦁ Sales Associates ⦁ Vice President - Marketing ⦁ Marketing Manager ⦁ Marketing Experts ⦁ Marketing Analysts ⦁ Marketing Associates ⦁ Vice President - Human Resources ⦁ HR Manager ⦁ HR Experts ⦁ HR Analysts ⦁ HR Associates The following list of people will be interviewed from the organization and the set of their objectives has also been explained in the list below. ⦁ System Developers ⦁ The development methodology that is commonly followed in the projects of ITWeb. ⦁ The development tools those are available with the organization in terms of the software and hardware tools. ⦁ The development framework and the languages that are normally used in the organization. ⦁ System Engineers ⦁ The development methodology that is commonly followed in the projects of ITWeb. ⦁ The development tools those are available with the organization in terms of the software and hardware tools. ⦁ The development framework and the languages that are normally used in the organization. ⦁ Technical Experts ⦁ Technical skills those are available with the resources at the organization. ⦁ The development methodology that is commonly followed in the projects of ITWeb. ⦁ The development tools those are available with the organization in terms of the software and hardware tools. ⦁ The development framework and the languages that are normally used in the organization. ⦁ UI/UX Experts ⦁ The UI/UX tools that are used by the resources for completion of the UI/UX design of the project. ⦁ The skill sets of the resources that are present in the organization ⦁ System Designers ⦁ The design tools that are used by the resources for completion of the UI/UX design of the project. ⦁ The skill sets of the resources that are present in the organization ⦁ Testing Analyst ⦁ Testing types that shall be executed on the smart tele-health application ⦁ Testing tools that are used by the resources at the organization ⦁ Implementation Engineer ⦁ Implementation methodology that is used at the organization AS-IS Diagram AS-IS ITWeb Diagram The processes that are followed in the ITWeb organization are as described above. The one process that would require improvements is the testing phase which shall come early in the lifecycle. The testing activities shall be included in every phase and process in order to validate and verify the processes and activities in each step (Rozenes, 2011). Report to Top Management Objectives ⦁ The objective of the smart tele-health application is to provide the users with the ability to record and monitor their health conditions in a remote manner. ⦁ The project shall be completed in the estimated project duration. ⦁ The project shall be completed in the estimated project costs. Process Undertaken The project will be completed in five phases in a time period of 119 days. The initial phase of the project has begun and the project activities that will be covered are specified below with their respective statuses. Task Name Duration Start Finish Status ITWeb Smart Tele-Health Web Application 119 days Thu 3/2/17 Tue 8/15/17 Phase 1 - Initiation 15 days Thu 3/2/17 Wed 3/22/17 Completed Technical feasibility analysis and evaluation of results 3 days Thu 3/2/17 Mon 3/6/17 Completed Operational feasibility analysis and evaluation of results 3 days Tue 3/7/17 Thu 3/9/17 Completed Economical feasibility analysis and evaluation of results 3 days Fri 3/10/17 Tue 3/14/17 Completed Chartering of the Project 5 days Wed 3/15/17 Tue 3/21/17 Completed Submission of Project Charter 1 day Wed 3/22/17 Wed 3/22/17 Completed Milestone 1: Project Charter Document 0 days Wed 3/22/17 Wed 3/22/17 Completed Phase 2 - Planning 25 days Thu 3/23/17 Wed 4/26/17 Requirements Analysis and Scope Finalization 6 days Thu 3/23/17 Thu 3/30/17 Completed Assessment and Analysis of Project Risks 4 days Fri 3/31/17 Wed 4/5/17 Completed Scheduling tasks 3 days Thu 4/6/17 Mon 4/10/17 In-process Budgeting tasks 3 days Tue 4/11/17 Thu 4/13/17 Pending Fact finding and Communication plan 4 days Fri 4/14/17 Wed 4/19/17 Pending Project Plan Development and Submission 5 days Thu 4/20/17 Wed 4/26/17 Pending Milestone 2: Project Plan 0 days Wed 4/26/17 Wed 4/26/17 Pending Phase 3 - Execution 48 days Thu 4/27/17 Mon 7/3/17 Pending Designing of the smart tele-health web app 6 days Thu 4/27/17 Thu 5/4/17 Pending UI/UX design and wireframes 10 days Fri 5/5/17 Thu 5/18/17 Pending Design review and change implementation 3 days Fri 5/19/17 Tue 5/23/17 Pending Creation of source code 20 days Wed 5/24/17 Tue 6/20/17 Pending Unit testing of the source code 4 days Wed 6/21/17 Mon 6/26/17 Pending Review of the source code 5 days Tue 6/27/17 Mon 7/3/17 Pending Milestone 3: Source Code 0 days Mon 7/3/17 Mon 7/3/17 Pending Phase 4 - Control 23 days Tue 7/4/17 Thu 8/3/17 Pending Implementation of the Application 7 days Tue 7/4/17 Wed 7/12/17 Pending Security features 6 days Thu 7/13/17 Thu 7/20/17 Pending Testing of the application 5 days Fri 7/21/17 Thu 7/27/17 Pending UI and performance testing 5 days Fri 7/28/17 Thu 8/3/17 Pending Milestone 4: Implementation and Test Plan 0 days Thu 8/3/17 Thu 8/3/17 Pending Phase 5 - Closure 8 days Fri 8/4/17 Tue 8/15/17 Pending Project Deliverables Acceptance 3 days Fri 8/4/17 Tue 8/8/17 Pending Sign offs 2 days Wed 8/9/17 Thu 8/10/17 Pending Lessons Acquired 2 days Fri 8/11/17 Mon 8/14/17 Pending Closure Report Development and Submission 1 day Tue 8/15/17 Tue 8/15/17 Pending Milestone 5: Closure Report 0 days Tue 8/15/17 Tue 8/15/17 Pending Project Scope In-Scope ⦁ Ability to allow the users to log in to the smart tele-health application ⦁ Ability to allow the users to record their health conditions (Mallery, 2011) ⦁ Ability to allow the users to view and download their medical reports ⦁ Ability to allow the doctors and medical professionals to provide feedback on the health condition of the patient ⦁ Ability to allow the doctors and medical professionals to download the patient information ⦁ Ability to provide feedback on the application ⦁ Ability to log-out from the application ⦁ The following non-functional requirements will also be fulfilled in the project ⦁ The project should be developed and implemented in such a manner that it reflects the system quality of reliability in all of its components ⦁ The project should be developed and implemented in such a manner that it reflects the system quality of supportability in all of its components ⦁ The project should be developed and implemented in such a manner that it reflects the system quality of scalability in all of its components ⦁ The project should be developed and implemented in such a manner that it reflects the system quality of performance in all of its components ⦁ The project should be developed and implemented in such a manner that it reflects the system quality of usability in all of its components ⦁ The project should be developed and implemented in such a manner that it reflects the system quality of adaptability in all of its components ⦁ The project should be developed and implemented in such a manner that it reflects the system quality of inter-operatibility in all of its components ⦁ The project should be developed and implemented in such a manner that it reflects the system quality of maintainability in all of its components Recommendations The one process that shall be paid due attention is the testing phase which shall come early in the lifecycle. The testing activities shall be included in every phase and process in order to validate and verify the processes and activities in each step. The project management and development methodology that would be carried out on the project shall be in accordance with the project specifications and requirements. Conclusion ITWeb comprises of a small group of resources with varying set of skills and has been able to establish itself as a reputed IT firm in the market. However, with increase in competition, the organization was facing trouble with the requirement of maintaining a competitive edge in the market. It came up with a plan to develop a smart web application for tele-health monitoring. The project shall be completed in five phases as initiation, planning, execution, control and closure. There are numerous fact finding techniques that shall be applied in the project as interviews, document reviews, observations, questionnaires and research. References Badiru, A. (2010). Half-Life of Learning Curves for Information Technology Project Management. International Journal of Information Technology Project Management, 1(3), pp.28-45. Chang, J. (2013). Perceived Required Skills and Abilities in Information Systems Project Management. International Journal of Information Technology Project Management, 4(1), pp.1-12. Goodwin, S. (2014). Changing communication on researchgate through interface updates. Proceedings of the American Society for Information Science and Technology, 51(1), pp.1-4. Lind, M. and Culler, E. (2011). Information Technology Project Performance. International Journal of Information Technology Project Management, 2(4), pp.14-25. Mallery, M. (2011). Project Management Portal (PMP) from the University of Washington Information Technology Wiki - https://wiki.cac.washington.edu/display/pmportal/Project+Management+Portal. Technical Services Quarterly, 28(3), pp.365-367. Parry, V. and Lind, M. (2016). Alignment of Business Strategy and Information Technology Considering Information Technology Governance, Project Portfolio Control, and Risk Management. International Journal of Information Technology Project Management, 7(4), pp.21-37. Peslak, A. (2012). Information Technology Project Management and Project Success. International Journal of Information Technology Project Management, 3(3), pp.31-44. Rozenes, S. (2011). The Impact of Project Management Methodologies on Project Performance. International Journal of Information Technology Project Management, 2(2), pp.64-73.