chapter 17

9
Chapter 17 Building Software to Support an Agile Organization

Upload: tadita

Post on 06-Jan-2016

23 views

Category:

Documents


0 download

DESCRIPTION

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 - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Chapter 17

Chapter 17

Building Software to Support an Agile Organization

Page 2: Chapter 17

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

Page 3: Chapter 17

Concepts

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

Page 4: Chapter 17

THE SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)

Other cycles include:1.Current State analysis2.Requirements Definition3.Design4.Build or Buy5.Testing/Maintenance

Page 5: Chapter 17

Waterfall Methodology

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

Page 6: Chapter 17

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

Page 7: Chapter 17

Why Software Projects Fail

1. Unclear or missing business requirements2. Skipping SDLC phases3. Failure to manage project scope• Scope creep – occurs when the scope increases• Feature creep – occurs when extra features are added

4. Failure to manage project plan5. Changing technology

Page 8: Chapter 17

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

Page 9: Chapter 17

In What Phase Should You Fix Software Problems