知识管理-1.doc

UNIVERSITY OF SOUTH AUSTRALIAAssignment Cover Sheet - Group An Assignment cover sheet needs to be included with each assignment. Please complete all details clearly. If you are submitting the assignment on paper, please staple this sheet to the front of each assignment. If you are submitting the assignment online, please ensure this cover sheet is included at the start of your document. (This is preferable to a separate attachment.) Please check your Course Information Booklet or contact your School Office for assignment submission locations. Student Name (Print clearly)UniSA Email ID1. Nan Liu L.au2. Shaorong Lin L.au3. Lin Li Liyly036 .au4. .au5. .au6. .auCourse code and title: INFS 5057, Information Technology Project Management MProgram Code: LMCTSchool: School of Computer and Information Science Day, Time & Location of Tutorial/Practical: Tuesday, 2-4 pm, City WestCourse Coordinator: Jo HanischTutor: Tina DuExtension granted (Yes/No):Due Date: 18/10/2010Assignment number & topic: assignment 2We declare that the work contained in this assignment is our own, except where acknowledgement of sources is made.We authorise the University to test any work submitted by us, using text comparison software, for instances of plagiarism. We understand this will involve the University or its contractor copying our work and storing it on a database to be used in future to test work submitted by others.We understand that we can obtain further information on this matter at .au/ltu/students/study/integrity.asp Note: The attachment of this statement on any electronically submitted assignments will be deemed to have the same authority as a signed statement.Signed:Date:1. Liu Nan14/10/20102. Shaorong Lin 16/10/20103. Lin Li 16/10/20104.5.6.Date received from studentAssessment/gradeAssessed by:Recorded:Dispatched:Project Plan for the Local Archive SocietyThis report provides the project plan for the local archive to classify and track the records and artifacts. The traditional systems development lifecycle (SDLC) approach and the agile approach are applied to build two different type schedules for customer choice.1. Project Goals and ObjectivesThe overall purpose of this project is to develop plans for the classifying and tracking web-base system of Local Archive Societys records and artifacts using both waterfall and agile model. This system will be easy use and can be updated on line. Archivists can query format, location and relevant information of the records and artifacts.in addition, old materials such as newspaper can be facility scanned and recorded in digital type.The rationale of this project is to keep the budget competitive and finish work on time. An efficient project team will be developed considering the experience, available working time and pay rate. Other resources required such as hardware and software will refer to market price. The estimated cost is calculated involves all the relevant resources. The size, effort, duration will be evaluated by some estimate technique such as Function Point and COCOMO. Risk and quality are concerned to improve the success rate of this project and meet customer requirements.2. Deliverables of the Project and Billing Milestones2.1 Project key deliverablesThe system project schedules are designed based on the waterfall and agile system method. Whatever which system method is selected, there are still several common key deliverables to be delivered to customers:Customer requirements document: The purpose of this document is to track and record the process of customer requirement collection. This document focus on identifying customer needs through meeting, online discussing or e-mail. This document will refine as the project progresses.Work breakdown structure (WBS): WBS provides the framework of tasks for the project, helping customer to eliminate and control the cost by making the schedule. WBS can be revised and updated according to the necessary change.Product design and development report: according to customers expectation, project teams will design the database, user interface for the system and continuously optimize products refer to the feedback from customer.Operational manuals and user guide documents: documents including system setup description, hardware and software requirements function implemented, operating instruction and scenarios from implementation point of view.Final product: Final product will be delivered to customers who have already understood the operational process. Final product can be putted into use directly for classifying and tracking the records and artifacts of Local Archive Society.2.2 Billing milestones This part shows each step cost to clients by following different system methods. The billing cost information is showed as follow:MS project task IDDescription of Milestone EstimatedFinish dateStaged BillingAmount Percentage6Confirm the clients requirement1/Dec/2010$24004.53%22project analysis and planning established7/Jan/2011$1126021.24%31Finish the database and website design2/Mar/2011$1405026.5%38Purchased hardware and software and started implement the product31/Mar/2011$7462.5514.07%47Finished the testing and released the final product20/May/2011$39007.36%55Deliver the final product and finished the project2/Jun/2011$680012.82%Total cost$53022.55100%Table-1 Waterfall ApproachMS project task IDDescription of Milestone EstimatedFinish dateStaged BillingAmount Percentage6Confirm the clients requirement1/Dec/2010$24004.53%22project analysis and planning established7/Jan/2011$1126021.24%31Finish the database and website design8/Feb/2011$1240023.81%38Purchased hardware and software and started implement the product1/Mar/2011$6972.5513.39%47Finished the testing and released the final product9/May/2011$38407.37%55Deliver the final product and finished the project2/Jun/2011$680013.06%Total cost$52072.55100%Table-2 Agile Approach3. Risk managementHubbard (2009) showed that risk management is the identification, estimation, and optimization of risk followed by current environment and resources to plans control and reduces the probability potential events or problems happened. In the project, project managers should understand each facts of the whole development process, including schedules, costs, resources, human and strategies. Table 1 displays the possible risks when operating the project for Local Archive Society.RiskImpactLikelihoodResponsible officerStrategyCustomers do not understand the whole development process deeplyMediumMediumProject managerTo choose professional staffs to communicate with clients and provide documents and other media methods to explain more information about development processThere are not enough products testing before handling to clientsHighLowProject managerTo find out problems on schedules and arrange days to do products testing until there is no problemTo communicate with clients and explain why to delay time for testing productsBecause of healthy problems or urgent events to make some team members absent development processHighHigh Project manager and team leaderTo understand all staffs information and skills, then prepare second teams when happens urgent thingsBecause of lacking enough work experiences to make mistakes about time tables and requirements from clientsHighMediumProject manager and team leaderTo communicate with experienced experts and staffs for discussing how to solve problemsPoor relations between team members or teams with clientsHighLowProject manager, team leader and team memberTo increase communication by meetings, consultations by various approaches or mediasTable-3 Risk Register4. Comparison SDLC system method and Agile system method4.1 Resource and rational in development cycleDonaldson and Siegel (2007) stated that when the life cycle is selected, planners need to estimate required resources to accomplish the project in each stage. Due to one of the attribute of project is that uncertainties involved, it is very important promote optimal allocation of any available resources to minimize development uncertainties (Schwalbe 2007; Ramirez-Marquez & Sauser 2009). Ramirez-Marquez and Sauser (2009) described the purpose of resources allocation is to create individual tasks to maintain budget and schedule and ultimate develop a product to satisfy the customer. In order to keep the project budget competitive, for both SDLC approach and agile method schedules, budget allocation strategy are applied on the onset of the project, and resource allocation are concerned at key milestones throughout the life cycle.On the one hand, there are some similar resource assignments for both lifecycles: according to Seidman and Rappaport (1986) state that small-scale projects usually can be initiated small scale people. Then, firstly, each lifecycle has 4 team members including project manager, team leader, system analyst, programmer and website. Some of them undertake double roles. This project assumes that all the team member do not turnover until the work has been completely done. Secondly, the equipment such as computer, printer, scanner and software like MS Office are the same for both lifecycles. Thirdly, because of some traditional planning approach often ignore the risk factor on resource allocation (Donaldson & Siegel 2007), risk analysis are considered for both lifecycles to help to reduce risks for the project. Fourthly, public holidays are non-working.On the other hand, there are some different for approaches. Firstly, different team members are selected for both lifecycles. Sennikovski (2010) stated that there are typically more system analysts than programmer in SDLC lifecycle because the planning stage accounts for most time. For agile project, more programmers are required in order to maintain continual coding output within each iterative process. In terms of this, in each 4-person team, two people undertake system analysis work in SDLC lifecycle and two programmers in agile lifecycle. Secondly, customer participates in agile lifecycle. Agile is an iterative and incremental approach which requires continuous end user involvement (Ling at el. 2008). Customer feedbacks are obtained after each release to adjust the project meet the possible change requirement. Thirdly, the roles and responsibility of team members are different for both lifecycle. Sumrell (2007) insisted that the roles and responsibilities of team members should be redefine in the agile team. For example, programmers take charge of the testing work in waterfall lifecycle, however, the entire team needed to participate in the testing process in agile lifecycle. In view of this, the allocation of resources is more flexible and effective in agile lifecycle.4.2 BudgetAs mentioned before, relatively less experience team members are selected to maintain budget competitive. More time and cost are required when apply waterfall model to develop and implement system and the main features of agile model are fast development and cost saving (Qureshi & Hussain 2008). The cost relevant hardware and software such as computer, printer, scanner and MS office software are estimated according to market price, medium level PC is $ 800, one printer is $ 60, one scanner is $ 152.55 and MS Office software is $ 200. The human resource costs are calculated according to available working time, pay rate of team members. The project includes eight main tasks and there are fifty subtasks within. According to the tasks content, it will take approximately 5 months to finish the whole project. During the process, to exclude public holidays and the specific date is from 29 November 2010 to 11 June 2011. The project budget is controlled within $ 50,000 - $ 55,000. 4.3 Estimation techniquesThe accurate estimation of project lifecycle is one of the key elements for successful project management. Any software project desires accurate estimation to make the resources, schedule, budget and time properly and avoid overrun. Some techniques have been developed to estimate the cost, size, effort for project such as Function Points (FP), Constructive Cost Model (COCOMO) which are simple to understand, little effort and practice are required and it is easy to count (Nasir 2006). Pow-Sang and Jolay-Vasquez (2006) stated that traditional estimate techniques such as Function Point, COCOMO are not only can be used in waterfall lifecycle, but also adaptation for incremental and iteration software development project such as agile. Therefore, Function Point and COCOMO model are utilized in this project. Function Point which is a measure method considering external system parameters to verify and validate the content of specification document of system requirement (Pow-Sang & Jolay-Vasquez 2006). This technique is used to determine the tasks in each lifecycle. The difference is, in agile lifecycle, Function Points are determined per iteration.COCOMO model is used to the number of Person-Months and duration required to develop a project. There are three types of formula in COCOMO, among which basic mode is suitable for small development team (Nasir 2006). The equations of basic model are illustrated as follows:Effort=2.4* (size) 1.05, Time=2.5* (effort) 0.38, Number of team members=Effort/Time. Effort is presented in person months, size is estimated in KSLOC (thousand lines of code), and the time is estimated in months. As mention before, this project team involve 4 people, and according to their available working time and non-working time, In waterfall lifecycle, the Effort are approximately 21 person-month, the time will take around 5 months, the size of this project is around 7.8KLOC. 4.4 QualityCompared to waterfall lifecycle, agile approach can produce better quality of project. Each phase of waterfall model do not start when the previous phase is completed, which means there is no turning back even though the customer requirements have already changed(Qureshi & Hussain 2008).Schwalbe (2007) demonstrated that clients are responsible for defining quality. Therefore, projects which produce in SDLC lifecycle may dissatisfy customers due to the changing requirement so that lead to low quality. Project which adopt agile model can do it better. According to Highsmith and Cockburn (2001), all the agile software developments attach importance to quality in design. Agile development approaches can be adapted to ISO which is a set of international standards adopted by over 90 countries worldwide for both quality management and quality assurance. (Qureshi & Hussain 2008; Liberatore & Johnson 2009). Quality is a key factor in projects so that has to be taken into seriously consideration. As a project manager perspective, making quality planning and improving communication with customers to make sure the projects meet their expectation (Schwalbe 2007). Liberatore and Johnson (2009) also suggest that project manager and customers should jointly determine the rules and quality criteria to measure the quality of project. In addition, project manager should pay attention to quality assurance to evaluate whether the performance of project satisfy the customer. Some tools such as benchmarking can be use in quality assurance by comparing the current project with other projects (Schwalbe 2007). Moreover, quality control should be adopted throughout the project lifecycle. Paquin, Couillard and Ferrand (2000) stated that project manager need to identify individual responsible for each WBS work elements and estimate the contribution of each element to its quality criteria.5. Recommendations and suggestion This report assures that this project team can be a reliable recommendation of experts. For this project, agile approach is recommended for this project, the reasons are as follows:Firstly, agile development approach will be better when the customer requirements are vague. Waterfall model is only applicable when comprehensive requirements are clear available. However, it is impossible to collect complete requirements initially at the start of the project that is the fundamental requirement of this model (Qureshi & Hussain 2008). For this project, the user interface requirements are not clearly understood and will need to be progressively reviewed by the client. Therefore, agile approach is a wise choice.Secondly, lightweight life cycle models such as agile are better suited for small project teams. Agile process models are only proposed to develop small-scale software within couple of months (Qureshi & Hussain 2008). This project was firstly defined as a small system which separate from the enterprise-wide cataloguing systems and the client understands this project will take some months. Thus, agile model is appealed to this project.Thirdly, agile model can save cost and quickly respond to customer requirements. Waterfall model require more time and cost to develop and implement the system (Qureshi & Hussain 2008). The main benet of agile models are f