Nearly all systems development projects require input from users of different types (subject matter experts, sponsors, general users). When, how, and how much they are involved in the development process is a critical success factor for a project. However, it is not always clear what the correct amount of this involvement should be. Below is a spreadsheet that contains a detailed breakdown of tasks for a development process used to develop and implement web-based applications (and a sample of the IS personnel and user personnel normally involved).
1. Use the spreadsheet given, for each task indicate the percent of the time that the IS personnel should spend on that task and the percent of the time that the user personnel should spend. For example, for the first task "Determine project scope" I think should mostly be done by users with some input from the IS specialists, so I would say this is 10% ISP 90% UP.
2. Analyze your results. If a project was expected to take 10,000 hours (a team of five working for 1 year), how many hours would be dedicated to ISP? to UP?
3. Discuss your estimates and your analysis. Why did you make the decisions you did? Are any tasks 100% ISP or UP? Given your results, how would you answer the question: How important is user involvement in the systems development process?
UPLOAD:
L28 1 STAGE OF LIFE CYCLE PERSONNEL INVOLVED 2 Scope 3 4 6 10 11 8 Analysis Software Requirements 9 17 18 Design 19 20 21 22 23 24 AutoSaveo) H SDLC v Human Resources.xlsx Protected View File Home Insert Page Layout Formulas Data Review View Help JMP PROTECTED VIEW Be careful-files from the Internet can contain viruses. Unless you need to edit, it's safer to stay in Protected View. ix fx Develop preliminary budget 12 13 Review sofware specifications/budget with team Incorporale leedback on software specifications Develop delivery imeing 14 15 Obtain approvals to proceed (concept, timeline, budget 16 29 25 28 Development 27 20 31 33 Testing 30 37 38 39 40 41 42 44 45 46 4/ 4 Determine project scope Secure project sponsorship Define preliminary resources Ready Secure core resources Scopa completa Condunda analysis Draft preliminary software specifications 91F Sunny Develop prototype based on functional specifications Review funcional spacifications Incorporate feedback into functional specifications Obtain approval to proosad Design complete Secure required resources Analysis complete Review preliminary software specifications Develop functional specifications Review functional specifications Identify modulatiered design parameters Develop unit test plans using product spectications Develop integration test plans using product specifications Line Testing Sheet1 Assign development stan Cevelop code Developer testing (primary debugging) Development complete i completa Review modular code Test component modules to product specifications Identity anomalies to product specifications Modity code Re-test moded code Une testing complete Test module integration Identity anomalies to specifications Modify code Remoded code Sheet2 Sheet3 (+) B ISP C UP D IS PERSONNEL CodeBuilder Designer Project Manager Archited C System Programmer Database Analyst Sotware Integrator USER PERSONNEL Operations Stat Department Manage Executive Management Champion Owner Customer Business Analyst H O Search (Alt+Q) F H 1 Enable Editing J K 0 I H N 0 P A Abrams, Austin Jeffrey AA R S TEI E Comments V X Share x 'A 72% 2:58 PM 6/30/2022 C35 42 43 tonledny 44 40 46 47 48 W 49 Training 50 54 55 58 Develop training specifications for and use 51 Develop training specifications for helpdesk support staff 50 Identify training delivery methodology (CBT, classroom, etc 53 Develop training materiale AutoSave Of H SDLC v Human Resources.xlsx Protected View File Home Insert Page Layout Formulas Data Review View Help PROTECTED VIEW Be careful-files from the Internet can contain viruses. Unless you need to edit, it's safer to stay in Protected View. X fx 58 Documentation 50 51 23 54 86 50 87 58 Plot 89 70 71 72 74 70 Deployment 76 77 78 79 80 81 87 88 4 Unitesting complete Test module integration Identity anomalies to spectications Mody code By Bide Re-test mocted code Imagration tasting completa Ready 82 Post Implementation Review 83 84 85 85 88 91F Sunny Conduct kaining usstilly study Final ze training materiale Develop trening delivery mechanism Training materials complete Develop Hep spectication Develop Help System Review Help documentation Incorporate Help documentation feedback Develop user manuala specifications Develop user manuals Review all user documentation Incorporate user documentation feedback Documentation complete Identify teal group] Develop software delivery mechanism Installideploy otware Obtain userfeedback Evaluale leating information Flict complete Determine final deployment stranagy Develop deployment methodology Secure deployment resourcAR Train support stan Deploy software Deployment complete Documentlessons Isamed Distribute to team members Create software maintenance team Postimplementation review complele Software development template complets Sheet1 Sheet2 Sheet3 | (+) B C H a JMP Search (Alt+Q) E F H 1 Enable Editing K 0 L H N 0 P A Abrams, Austin Jeffrey AA R S TEI E Comments V X Share x 72% 3:15 PM 6/30/2022 L28 1 STAGE OF LIFE CYCLE PERSONNEL INVOLVED 2 Scope 3 4 6 10 11 8 Analysis Software Requirements 9 17 18 Design 19 20 21 22 23 24 AutoSaveo) H SDLC v Human Resources.xlsx Protected View File Home Insert Page Layout Formulas Data Review View Help JMP PROTECTED VIEW Be careful-files from the Internet can contain viruses. Unless you need to edit, it's safer to stay in Protected View. ix fx Develop preliminary budget 12 13 Review sofware specifications/budget with team Incorporale leedback on software specifications Develop delivery imeing 14 15 Obtain approvals to proceed (concept, timeline, budget 16 29 25 28 Development 27 20 31 33 Testing 30 37 38 39 40 41 42 44 45 46 4/ 4 Determine project scope Secure project sponsorship Define preliminary resources Ready Secure core resources Scopa completa Condunda analysis Draft preliminary software specifications 91F Sunny Develop prototype based on functional specifications Review funcional spacifications Incorporate feedback into functional specifications Obtain approval to proosad Design complete Secure required resources Analysis complete Review preliminary software specifications Develop functional specifications Review functional specifications Identify modulatiered design parameters Develop unit test plans using product spectications Develop integration test plans using product specifications Line Testing Sheet1 Assign development stan Cevelop code Developer testing (primary debugging) Development complete i completa Review modular code Test component modules to product specifications Identity anomalies to product specifications Modity code Re-test moded code Une testing complete Test module integration Identity anomalies to specifications Modify code Remoded code Sheet2 Sheet3 (+) B ISP C UP D IS PERSONNEL CodeBuilder Designer Project Manager Archited C System Programmer Database Analyst Sotware Integrator USER PERSONNEL Operations Stat Department Manage Executive Management Champion Owner Customer Business Analyst H O Search (Alt+Q) F H 1 Enable Editing J K 0 I H N 0 P A Abrams, Austin Jeffrey AA R S TEI E Comments V X Share x 'A 72% 2:58 PM 6/30/2022 C35 42 43 tonledny 44 40 46 47 48 W 49 Training 50 54 55 58 Develop training specifications for and use 51 Develop training specifications for helpdesk support staff 50 Identify training delivery methodology (CBT, classroom, etc 53 Develop training materiale AutoSave Of H SDLC v Human Resources.xlsx Protected View File Home Insert Page Layout Formulas Data Review View Help PROTECTED VIEW Be careful-files from the Internet can contain viruses. Unless you need to edit, it's safer to stay in Protected View. X fx 58 Documentation 50 51 23 54 86 50 87 58 Plot 89 70 71 72 74 70 Deployment 76 77 78 79 80 81 87 88 4 Unitesting complete Test module integration Identity anomalies to spectications Mody code By Bide Re-test mocted code Imagration tasting completa Ready 82 Post Implementation Review 83 84 85 85 88 91F Sunny Conduct kaining usstilly study Final ze training materiale Develop trening delivery mechanism Training materials complete Develop Hep spectication Develop Help System Review Help documentation Incorporate Help documentation feedback Develop user manuala specifications Develop user manuals Review all user documentation Incorporate user documentation feedback Documentation complete Identify teal group] Develop software delivery mechanism Installideploy otware Obtain userfeedback Evaluale leating information Flict complete Determine final deployment stranagy Develop deployment methodology Secure deployment resourcAR Train support stan Deploy software Deployment complete Documentlessons Isamed Distribute to team members Create software maintenance team Postimplementation review complele Software development template complets Sheet1 Sheet2 Sheet3 | (+) B C H a JMP Search (Alt+Q) E F H 1 Enable Editing K 0 L H N 0 P A Abrams, Austin Jeffrey AA R S TEI E Comments V X Share x 72% 3:15 PM 6/30/2022
