Chapter 12 Development Processes "We Think We Can Open the Doors to an Entirely New Market" • Example of decision making in small company – Zev owner and source of investment funds – Team presents idea, he listens and makes a decision • Team doesn’t really know what’s involved • Building a prototype a good, low cost way to learn • Situation similar with a professional IS department Copyright © 2016 Pearson Education, Inc 12-2 Bottom Line • Startups can be fun and interesting places to work • Time and budgets limited • Decisions usually made more quickly, but risky if not well managed • Prototypes used to reduce front-end risk • Scrum ideal development process for creating prototypes Copyright © 2016 Pearson Education, Inc 12-3 Study Questions Q1: How are business processes, IS, and applications developed? Q2: How organizations use business process management (BPM)? Q3: How is business process modeling notation (BPMN) used to model processes? Q4: What are the phases in the systems development life cycle (SDLC)? Q5: What are the keys for successful SDLC projects? Q6: How can scrum overcome the problems of the SDLC? Q7: 2025 Copyright © 2016 Pearson Education, Inc 12-4 Q1: How Are Business Processes, IS, and Applications Developed? Application: combination of hardware, software, data components that accomplish a set of requirements Copyright © 2016 Pearson Education, Inc 12-5 Relationship of Business Processes and Information Systems Every information system has at least one application Copyright © 2016 Pearson Education, Inc 12-6 How Do Business Processes, Information Systems, and Applications Differ and Relate? Business processes, information systems, applications have different characteristics and components Relationship of business processes to information systems is many-to-many, or N:M Business process need not relate to any information system, but an information system relates to at least one business process Every IS has at least one application because every IS has a software component Copyright © 2016 Pearson Education, Inc 12-7 Which Development Processes Are Used for Which? Copyright © 2016 Pearson Education, Inc 12-8 Role of Development Personnel Copyright © 2016 Pearson Education, Inc 12-9 Q2: How Do Organizations Use Business Process Management (BPM)? • Business process • Activities • Repository • Inventory • Database Copyright © 2016 Pearson Education, Inc 12-10 Q6: How Can Scrum Overcome the Problems of the SDL • Alternatives to SDLC – Rapid application development – Unified process – Extreme programming – Scrum – Others Copyright © 2016 Pearson Education, Inc 12-37 Principles of Agile (Scrum) Development Copyright © 2016 Pearson Education, Inc 12-38 Scrum Essentials Copyright © 2016 Pearson Education, Inc 12-39 Scrum Process Copyright © 2016 Pearson Education, Inc 12-40 When Are We Done? • Customer is satisfied with product created and accepts it • Project runs out of time • Project runs out of money Copyright © 2016 Pearson Education, Inc 12-41 How Do Requirements Drive the Scrum Process? Copyright © 2016 Pearson Education, Inc 12-42 Summary of Scrum Estimation Techniques Copyright © 2016 Pearson Education, Inc 12-43 Q7: 2025? Continuing focus on aligning business processes and information systems with business strategy, goals, objectives Applications built faster, more easily changed and adapted Applications develop other applications (singularity) – The cloud lead to substantially more innovation Very small hardware budgets – Emergence of new software vendor business models Copyright © 2016 Pearson Education, Inc 12-44 Security Guide: Psst There’s Another Way, You Know • Do you think servers in China were actually shut down? • Large organizations with good IS departments with port 24 set to only allow traffic to go to IP address of ISP did not lose any designs • What about smaller organizations with minimal IS Department, or supported by small, unsophisticated VAR? Copyright © 2016 Pearson Education, Inc 12-45 Guide: Final, Final Word • Learn to find, create, and manage innovative applications of IS technology • Two important takeaways: – – – Software developers are optimists Be aware of consequences of negotiating a schedule Large projects much harder to schedule than small ones If project lasts longer than a year, watch out! o Longer projects mean more chance for technology change, requirements change, employee turnover Copyright © 2016 Pearson Education, Inc 12-46 Guide: The Final, Final Word (cont'd ) • Use what you’ve learned in this class to obtain the job you really want! • Do the exercises at the end of this guide, and use the answers in your job interviews! Copyright © 2016 Pearson Education, Inc 12-47 Active Review Q1: How are business processes, IS, and applications developed? Q2: How organizations use business process management (BPM)? Q3: How is business process modeling notation (BPMN) used to model processes? Q4: What are the phases in the systems development life cycle (SDLC)? Q5: What are the keys for successful SDLC projects? Q6: How can scrum overcome the problems of the SDLC? Q7: 2025 Copyright © 2016 Pearson Education, Inc 12-48 Case Study 12: When Will We Learn? • 1974 - Number one reason for failure was a lack of user involvement in creating and managing system requirements • Access CT project (2013) successful – If schedule is fixed, and funding nearly fixed, what factor can be traded-off to reduce project difficulty and risk? – Requirements Reduce to bare minimum and get system running Then, after some success, add to it Copyright © 2016 Pearson Education, Inc 12-49 Case Study 12: When Will We Learn? (cont'd) • State of Oregon wasted more than $248 million attempting to develop an information system to support its healthcare exchange • Very early in project, Maximus Company, consulting firm hired to provide quality assurance, warned that requirements were vague, changing, and inconsistent • Those warnings made no difference Why? • Software and systems are made of pure thought-stuff – Easy to imagine a glorious future of amazing capability, but subject to human frailties Copyright © 2016 Pearson Education, Inc 12-50 Copyright © 2016 Pearson Education, Inc 12-51 ... time • Project runs out of money Copyright © 2016 Pearson Education, Inc 12- 41 How Do Requirements Drive the Scrum Process? Copyright © 2016 Pearson Education, Inc 12- 42 Summary of Scrum Estimation... Relationship of business processes to information systems is many-to-many, or N :M Business process need not relate to any information system, but an information system relates to at least one business... Education, Inc 12- 12 Examples of Change in Business Fundamentals • Market (new customer category, change in customer characteristics) • Product lines • Supply chain • Company policy • Company organization