1 / 9

Chapter 17

Chapter 17. Building Software to Support an Agile Organization. Building Software to Support an Agile Organization. Learning Objectives Identify business benefits associated with successful software development Describe the phases of the SDLC Characterize Agile methodology

tadita
Download Presentation

Chapter 17

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chapter 17 Building Software to Support an Agile Organization

  2. Building Software to Support an Agile Organization Learning Objectives • Identify business benefits associated with successful software development • Describe the phases of the SDLC • Characterize Agile methodology • Team Assignment 1: use video • Summarize different software development methodologies • Team Assignment 2: use textbook

  3. Concepts • SDLC • Prototype • Methodology • Agile • Waterfall • Scrum • Extreme programming • Rational unified process (RUP) • Rapid application development (RAD)

  4. THE SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC) Other cycles include: • Current State analysis • Requirements Definition • Design • Build or Buy • Testing/Maintenance

  5. Waterfall Methodology An activity-based process in which each phase in the SDLC is performed sequentially from planning through implementation and maintenance

  6. Implementing Agile Methodologies • The Agile Alliance Manifesto • Early and continuous delivery of valuable software will satisfy the customer • Changing requirements are welcome • Business people and developers work together • Projects need motivated individuals • Use self-organizing teams • Reflect on how to become more effective

  7. Why Software Projects Fail • Unclear or missing business requirements • Skipping SDLC phases • Failure to manage project scope • Scope creep – occurs when the scope increases • Feature creep – occurs when extra features are added • Failure to manage project plan • Changing technology

  8. How To Not Let Projects Fail • Primary principles for successful agile software development include: • Slash the budget • If it doesn’t work, kill it • Keep requirements to a minimum • Test and deliver frequently • Assign non-IT executives to software projects 17-9

  9. In What Phase Should You Fix Software Problems

More Related