1. Creator: ACSession No: 19 Slide No: 1Reviewer: - CSE300Advanced Software EngineeringMarch 2007 ‘Agile Methods’ (part 2) CSE300 Advanced Software Engineering University of Sunderland © 2006 Anne Comer anne.comer@sunderland.ac.uk

2. CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 2Reviewer: - Agile Development – the Difference All software development methods, including the Agile ones, have some sort of underlying project life cycle. The key elements are a Project Initiation and Project Plan followed by one or more Releases made up of timeboxes. Optional phases of Elaborate Requirements, & Architecture. The generic ‘Agile Life Cycle’

3. CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 3Reviewer: - Is Agile Good Project Management? Aspects of project management (Watson (1998)) Project Initiation Project Planning, Estimating and Budgeting Roles and Responsibilities Controlling the Project Managing Change Managing Quality Managing Risk Reviewing the Project

4. CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 4Reviewer: - Project Initiation Scope Project Choose the right method Choose your formality Define a vision to point the way High Level Requirements - Fast

5. CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 5Reviewer: - Project Planning, Estimating and Budgeting Planning based on Timeboxes Developers do initial project estimates No contingency in developer estimates Project Plan = Requirements in Timeboxes Timebox Plan built by team

6. CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 6Reviewer: - Roles and Responsibilities Small Cross-functional teams Agile Developer – generalist User/Customer – An Active Role Project Manager as Shepherd

7. CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 7Reviewer: - Controlling the Project Produce Product quality releases Simple and direct communication is key –Intra-team communication –Inter-team communication –Management reporting

8. CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 8Reviewer: - Managing Change Time is more important than functionality Minor changes accepted in a timebox Big changes outside a timebox customer can add/change any requirement developers re-estimate customer trades off requirements Big changes inside a timebox either isn’t allowed at all or customer trades functionality in/out of timebox.

9. CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 9Reviewer: - Managing Quality Stated ‘Quality Goals’ / addressed continuously Peer Review (mandatory XP (pair programming) / common in DSDM) XP – must have tests before code Integration Testing continuous & automatic, daily build & smoke test. (XP, Scrum) User Acceptance Testing –UAT during development (XP, DSDM) –formal reviews during timebox (DSDM) and at end (XP, Scrum, DSDM) Extra testing activities (e.g., performance testing) - - scheduled in the same way as requirements

10. CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 10Reviewer: - Risk Management (RM) DSDM explicitly demands RM procedure Agile process reduces level of 5 of top 10 risks –Feature creep –Gold plating –Short changed quality –Overly optimistic estimates –Friction between developers and customers Technical risk addressed by –“prototypes” (DSDM) –“spike solutions” (XP)

11. CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 11Reviewer: - Project Review Inside the project (self adapting) –1or2 hours reflection each Iteration (timebox) XP The next project –Story Pile (XP) –Product Backlog (Scrum) –Project Review Document (DSDM).

12. CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 12Reviewer: - Review Mainly design for today and ‘refactor’ tomorrow Only DSDM makes an architecture phase compulsory Agile Development is a set of practices and guidelines Agility can be good Project Management