Computer Information System

Questions: 1. How well did your project meet its initial aims? Discuss what modifications were made to the initial aims and why? 2.How well did the estimated schedule correspond with the actual implementation times? Discuss any differences. Where there are any tasks that took a significant amount of time that did not appear in the work item list? Discuss these tasks in terms of project scheduling and budget. 3.What went right? Discuss those aspects of the project that you think went well. 4. What went wrong? Discuss those aspects of the project that you think went badly. 5. What would you do differently next time? Discuss those aspects you would change in undertaking another project and why? Answers: (1). When the project was initiated, the entire team of the project had evaluated the requirements in detail that helped to come out with a good website and there are no major modifications done to the project that was developed initially. However, small adjustments are performed in terms of navigation of the website, so that code can be simpler, for faster execution of the code to make the website run faster. During the development phase, there were small modifications implemented so that smaller and minor functionalities can be included to the system. The minor modifications made with the intent of enriching the presentation and user interface, but the code is not made heavier. The objectives of these minor modifications are to improve the existing performance of the functionalities, which were realized and identified, after the website is navigated through, after the development of the website. For example, when the user gives the basic details of the journey, such as the from location to the destination location, travel date and return date and clicks on the button, search flights, there used to be a second window displaying directly the details of the flights that match the input criteria of the details entered. However, this experience is further enhanced, by displaying a dialog box in the second window saying, This is your flight. After the user enters OK, the list of the flights are displayed. And some more similar minor modifications are made. (2). Initially, the deadline is considered and the team has set the own deadline, before 1 week from the given deadline, anticipating possible delays of the completion of the project. The overall schedule is compressed within the deadline set by the team. The work item list created by the team consists of all the tasks in a logical sequence. The tasks of design the website layout, developing the code, testing and final quality enhancements are distributed and allocated to each of the team member. Every team member has done ones best to complete their tasks. However, when the code is integrated with the database, there were certain issues raised and the code used to show many errors and took considerably longer time to come to a stable state, where the code started executing without the errors and expected outputs started displaying. The coding issue was major, while the owner dashboard was developed. It demanded several accesses to the databases and also the functions for insertion, deletion and update. The issue with the coding was resolved, after going through the basics of the database as well as Java, regarding how to connect and operate the database, when the user information is entered as part of filling the forms. (3). The entire project has moved smoothly, except minor deviations and obstructions. Facilitator and lecturer were helpful enough in guiding and showing the ways to move ahead with the project. Initially, a complete structure is prepared by the team and discussed with the lecturer for enhancements and the enhancement done by the lecturer has made the structure to be completely logical and effective. The tasks are performed as they are ordered and allocated to the members of the team. Whenever the team is stuck, especially, while the errors were problematic, lecturer has given all the necessary inputs, in such a way that the team gets to know, where can and how can the solutions can be found, rather than directly correcting the mistake then and there. It helped us to develop problem solving skills, which are vital for implementation of any project. Another important aspect that needs to be addressed in this context is the opportunity to learn a vital and significant project management technique called, OpenUp. The technique helped us to develop the project simple through iterative processes and it is definitely going to be helpful in our professional careers going forward. (4). There were hardly any aspects that were wrong, rather being complex. The structure of the project and the support of the lecturer for the sake of the team of the project have been significant support to the team and success of the project. However, it is important to address that there were certain things that were not moving as smoother as the team expected. For example, the coding has taken tremendously a lot many efforts and time, both for developing as well as for testing and correction. It was because of the lack of the experience in the programming languages, Java and SQL. However, the basic knowledge that the team has gained as part of the academics and also online tutorials and more than everything, the guidance and support of the lecturer helped to finally stabilize the code and yield the expected results. Since the deadline set by the team is shorter than the deadline given by the authorities, there were certain pressure created within the team members, especially, while coding, testing and corrections. However, the team retained the spirit for the entire project and spend tremendously great efforts, working even during the holidays and weekends. Overall, except these two lighter concerns, things went on well and the project was successful. (5). Having completed this project successfully, the team shows enough confidence to develop further projects, especially, similar projects. Having known the fact that every project is unique, the team is aware of the possibilities of new challenges that would be associated with any project. However, the team believes to have certain pre-requisites for the success of any projects, as common elements. For example, OpenUp technique or framework can make the processes and structure of the structure projects simpler. Having gained good degree of familiarity with the OpenUp framework, the future projects are expected to be easier to develop. Another pre-requisite needed for any project, according to the team is, the familiarly, exposure and experience in the respective subject. The subject knowledge help the project to be developed smoother, without serious obstructions and without any serious mistakes. The team has experienced pressure of developing the code, as the team members lack enough familiarity and experience in the programming languages, like Java, SQL, etc., as the learning of these languages is at the student level, rather than with practical learning experience. References Paul C. Dinsmore et al (2005)The right projects done right!John Wiley and Sons, Cattani, G., Ferriani, S., Frederiksen, L. and Florian, T. (2011) Project-Based Organizing and Strategic Management, Advances in Strategic Management, Vol 28, Emerald, oseph Phillips (2003).PMP Project Management Professional Study Guide. McGraw-Hill Professional, Peter Nathan, Gerald Everett Jones (2003).PMP certification for dummies. Harold Kerzner(2003).Project Management: A Systems Approach to Planning, Scheduling, and Controlling(8th ed.). Wiley PMI(2010).A Guide to the Project Management Body of Knowledge Dennis Lock (2007)Project Management(9th ed.) Gower Publishing, Ltd., 2007 James P. Lewis (2000).The project manager's desk reference:: a comprehensive guide to project planning, scheduling, evaluation, and systems Jrg Becker, Martin Kugeler, Michael Rosemann (2003). Process management: a guide for the design of business processes. David I. Cleland, Roland Gareis (2006).Global Project Management Handbook. "Chapter 1: "The evolution of project management". McGraw-Hill Professional, 2006 Martin Stevens (2002).Project Management Pathways. Association for Project Management. APM Publishing Limited Steinle, Bruch, Lawa (1995). Projektmanagement. FAZ Verlagsbereich Wirtschaftsbcher Morgen Witzel(2003).Fifty key figures in management. Routledge Cynthia Snyder, Frank Parth (2006).Introduction to IT Project Management David I. Cleland, Roland Gareis (2006).Global Project Management Handbook. McGraw-Hill Professional Ralph Stauber, H. M. Douty, Willard Fazar, Richard H. Jordan, William Weinfeld and Allen D. Manvel.