1. SWEN 302: AGILE METHODS Roma Klapaukh & Alex Potanin

2. WELCOME TO SWEN 302 Course Outline

3. MARKING Weekly reports Final report Group work

4. MAKING GROUPS Pick the day when you have the most free time (6-8 hours free) Labs run from 9am – 5pm You will do ALL your programming on that day

5. SOFTWARE DEVELOPMENT What is the purpose of a software engineer? To create a program What should a program do? Can a program have bugs? Who will use the program? Where must the program be able to work? Who is paying for it?

6. SOFTWARE DEVELOPMENT There are a large number of conflicting factors when making software Does the program do what the developer intended? Does the program do what the client intended? Can the program be used for the task it was intended for? Clients can change their mind about what they want People can misunderstand each other Limited time and money

7. WHAT IS THE PRIORITY? To deliver something that the client is happy with within the budget (time / money) that you have.

8. WHAT TO KEEP IN MIND Aglie vs Waterfall? Is software flexible? It’s just text Standish group (Chaos Report 2013): 50% of features are hardly ever or never used

9. CHAOS REPORT 2013

10. BREAKING UP A JOB I want to build an online costume shop Recent natural phenomena have been behind a range of disasters, I want to create an app to help people find their friends and loved ones.

11. USER STORIES As a, I want [so that ]

12. ACCEPTANCE TESTS How do you know a user story is complete? It needs to be checked off by the client It needs to meet the set of requirements / tests set added by the client to the user story.

13. BACKLOG Your collection of stories is your backlog With your client, the backlog must be sorted Fine grained at the top Coarser near the end Users stories are then done in order As users stories are moved from the backlog they are broken up as much as possible

14. PLANNING Agile does not mean absence of planning Planning is critical Choose your technologies and platforms with care, thinking about the needs of the project

15. RESEARCH SPIKE These are essentially about testing out an idea They don’t directly deliver value to the client They should not be common Otherwise, they are a normal story like any other