Agile Software Development

Size: px

Start display at page:

Download "Agile Software Development"

Bethanie Reeves
6 years ago
Views:

1 Agile Software Development S. Adams. Dilbert. Available: Hans-Petter Halvorsen

2 Agile? I ll go up and find out what they need and the rest of you start coding!

3 3

4 Typical Job Ad Agile methods have become very popular these days!! 4

The Development Process The Development Process involves different phases, e.

the overall Requirements are given by the Teacher in the Assignment.

Design Implementation The Design phase is important, but make sure you have

Improve your code and fix the bugs Testing Make sure everything work as

5 The Development Process The Development Process involves different phases, e.g.: The Requirements may be given by the Customer Requirements In this case the overall Requirements are given by the Teacher in the Assignment. The details are written by you! Are the Design wrong? Go back and correct it! Design Implementation The Design phase is important, but make sure you have time left for all the other tasks as well) Errors? Improve your code and fix the bugs Testing Make sure everything work as expected When you are finished, you deploy and test the solution on the Customer Site Deployment & Maintenance 5

6 Agile methods Scrum XP (extreme Programming) Lean Software Development Feature Driven Development (FDD) Test Driven Development (TDD) etc. 6

7 Software Development Methods Traditional Plan-driven Methods Agile Methods Waterfall Method extreme Programming (XP) Scrum V-Model Feature Driven Development (FDD) Spiral model Lean Software Development Test Driven Development (TDD) Even if we use different software development methods, we deal with the same phases like Requirements, Design, Coding, Testing and Deployment but they may have different priority and may be done in different manners and order, etc. 7

8 Teams and Roles Customer/Stakeholders Project Manager Software Architect UX Designer Developer Tester etc. Software Architect Collaboration! Project Manager Customer/Stakeholders Software Tester UX Designer Programmer 8

9 Plan-based development Plan-driven vs. Agile Requirements engineering Requirements specification Design and implementation Requirements change requests Agile development Requirements engineering Design and implementation I. Sommerville, Software Engineering: Pearson,

10 Agile vs. Traditional Development Wikipedia. (2013). Agile Software Development. Available: 10

11 Agile vs. Traditional Essentials of Software Engineering, Frank Tsui; Orlando Karam; Barbara Bernal, 3 ed., Jones & Bartlett Learning. 11

12 Agile Software Development O. Widder. (2013). geek&poke. Available: 12

13 Manifesto for Agile Software Development O. Widder. (2013). geek&poke. Available: We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Agile Alliance. (2013). Agile Manifesto. Available: 13

14 Wikipedia. (2013). Agile Software Development. Available: 14

15 Agile Development O. Widder. (2013). geek&poke. Available: 15

every 2-4 weeks Self-organizing and cross-functional

16 Agile A group of software development methods Iterative approach Incremental: Software available to Customers every 2-4 weeks Self-organizing and cross-functional Teams Refactoring Examples: Scrum extreme Programming (XP) 16

17 O. Widder. (2013). geek&poke. Available: 17

18 Burn Down Chart A burn down chart is a graphical representation of work left to do versus time. The outstanding work (or backlog) is often on the vertical axis, with time along the horizontal. That is, it is a run chart of outstanding work. It is useful for predicting when all of the work will be completed. It is often used in agile software development methodologies such as Scrum. However, burn down charts can be applied to any project containing measurable progress over time. 18

19 Code Review & Refactoring O. Widder. (2013). geek&poke. Available: 19

20 extreme Programming Hans-Petter Halvorsen, M.Sc. O. Widder. (2013). geek&poke. Available:

21 exreme Programming (XP) 21

22 exreme Programming (XP) An Agile method Pair Programming Code Reviews Refactoring Unit Testing Standup Meetings 22

Pair Programming O. Widder. (2013). geek&poke. Available: http://geek-and-poke.com Is Pair Programming Good or Bad?

23 Pair Programming O. Widder. (2013). geek&poke. Available: Is Pair Programming Good or Bad? Various Studies of the Productivity of Pair Programming Study 1: Comparable with that of 2 developers work independtly Study 2: A significant loss in productivity compared with 2 developers wprking alone Should the 2 developers have the same skills or not? Newerless, there are benefits: Collective Ownership Continuous informal Review process because each codeline is looked at by at least 2 people It supports Refactoring, which is a proces of software improvement Less time is spent on repairing bugs. Improved Code Quality It reduced the overall risks I. Sommerville, Software Engineering: Pearson,

24 24

25 Refactoring 25

26 26

27 Scrum Hans-Petter Halvorsen, M.Sc.

28 Scrum Daily Scrum Meetings Sprint Sprint Review Product Owner Sprint Backlog Product Backlog Stakeholders Scrum Master Development Team 3-9 persons

29 Scrum Daily Scrum Meetings Sprint Review 29

30 Scrum A Framework for Software Development Agile Software Development method Simple to understand Flexible Exremely difficult to master! Self-organizing Teams (3-9 persons) Scrum Team: Product Owner Scrum Master Development Team 30

31 Lean Software Development Hans-Petter Halvorsen, M.Sc.

32 Lean Software Development Based on the Toyota Production System and Lean manufacuring 32

33 Summary You should always Refactor your Code even if you don t do Agile! Pair Programming could be useful in some situations Scrum is probably the most popular Agile method Agile means less documentation Agile is more flexible than traditional methods (like the waterfall) 33

References I. Sommerville, Software Engineering: Pearson, 2010. E. J. Braude and M. E.Bernstein, Software Engineering. Modern Approaches, 2 ed.: Wiley, 2011. Wikipedia. (2013). Scrum Development.

Available: http://www.coretrek.no/scrum-i-etnoetteskall/category642.html S. Adams. Dilbert. Available: http://dilbert.com O. Widder. (2013). geek&poke. Available: http://geek-and-poke.

34 References I. Sommerville, Software Engineering: Pearson, E. J. Braude and M. E.Bernstein, Software Engineering. Modern Approaches, 2 ed.: Wiley, Wikipedia. (2013). Scrum Development. Available: Wikipedia. (2013). Agile Software Development. Available: CoreTrek. (2013). Scrum i et nøtteskall. Available: S. Adams. Dilbert. Available: O. Widder. (2013). geek&poke. Available: Agile Alliance. (2013). Agile Manifesto. Available: Essentials of Software Engineering, Frank Tsui; Orlando Karam; Barbara Bernal, 3 ed., Jones & Bartlett Learning. 34

Hans-Petter Halvorsen, M.Sc. University College of Southeast Norway www.

35 Hans-Petter Halvorsen, M.Sc. University College of Southeast Norway Blog:

The Software Development Process (SDLC)

http://home.hit.no/~hansha/?page=software_development O. Widder. (2013). geek&poke. Available: http://geek-and-poke.com The Software Development Process (SDLC) Hans-Petter Halvorsen IT System B. Lund.