Course Introduction Agile Methods

Transcription

1 Course Introduction Agile Methods Jonas Sjöström, Ph.D.

2 Objective Introduction Course aims and topics to cover Examination Preparations for seminar 1 and 2

3 Learning Outcomes After the course, the student should be able to: Explain the philosophy and historical context of agile methods Explain and critique common agile practices and principles based on the contemporary scientific discourse Analyse the strengths and weaknesses of an agile approach given a particular development context Plan an agile project Apply agile principles and practices in an actual project Demonstrate the strengths and weaknesses of an agile approach given a particular development context Document and assess an agile project Explain and critique selected agile practices and principles based on own experience from project

4 Content History of agile methods Philosophy of agile methods Agile method enactment Overview of contemporary agile methods, including XP and Scrum Agile management practices and principles Agile developer practices and principles Agile software development project work using XP and Scrum Project evaluation and reporting

5 Beyond Agile The concept of method in ISD The use and non-use of ISD methods Method-ism Methodology

6 Developers & Information Systems

7 Lecturers Ruth Lochan Jonas Sjöström E332 (Ekonomikum) Pär Ågerfalk Guest lecturer(s)

8 Anything you can do, I can do meta ISD Methododology Meta-Method Method Development ISD Method Systems Development (ISD)

9 Why Agile Software Development? No matter how well you are doing the plans there are always unexpected changes during the course of the project.

10 Examination Written exam Individual exam Accounts for ~ 40 % of the credits Research paper Individual work Accounts for ~ 40 % of the credits Agile development project Groups of ~ 6 students Accounts for ~ 20 % of the credits

11 Literature Beck, K. (2004) Extreme Programming Explained, 2nd Edition. Addison-Wesley. ISBN Larman, C. (2004). Agile and Iterative Development: A Manager s Guide. Addison-Wesley. ISBN Schwaber, K. & Beedle, M. (2001) Agile Software Development with Scrum. ISBN Articles (listed in seminar instructions)

12 General comments Lecturing style As above But, active student participation envisaged Handouts Articles Studentportalen

13 Now, what about you? ISD background Programming experience Research interest Expectations on this course

14 Methods & IS Development

15 What is an Information System? Information System in a broader sense The totality of all formal and informal data representation and processing activities within an organisation including the associated communication, both internally and with the outside world Information systems in the narrower sense Computer based sub-systems, intended to provide recording and supporting services for organisational operation and management

16 An Information System is A [software intensive] system which assembles, stores, processes, and delivers information relevant to an organisation (or to society), in such a way that the information is accessible and useful to those who wish to use it.

17 Or, more concisely Information Technology in Use

18 What is ISD? Designing a technical solution Designing a social action space Solving an organizational problem Programming Modelling and drawing diagrams Politics None of the above/all of the above

19 Information Systems Development A process of applying information technology to a specific purpose in a particular context

20 Different Forms of ISD Building from scratch Buying off the shelf New Information System Configuring components Using High level tools Some combination

21 Who is the Developer? Specialised professionals Analysts Designers Programmers Technical specialist Other stakeholders System users Clients Problem owners Decision makers

22 The Notion of Perspective A perspective is a mental representation of the world in terms of interesting/ purposeful things and a selection of interesting/purposeful properties of those things A perspective is subjective and different people might see different things when looking at the same piece of reality

23 Who are You? My focus is on Design processes and product design, in a human-centered sense. Software Engineering and Software Design

24 ISD Traditions Information Systems Human-Computer Interaction Software Engineering

25 ISD Method A coherent and systematic approach, based on a particular philosophy of systems development, which will guide developers on what steps to take, how these steps should be performed and why these steps are important in the development of an information system Concepts, notations and a process We may be doing wrong, but we re doing so in the proper and customary manner

26 Techniques and Tools Techniques Data Flow Diagram Entity Relationship Diagram State Transition Diagram Decision Tree Structured English Prototyping Tools CASE Tool Diagramming Tool Req mgt tool Data Dictionary Test Tools

27 Method v. Methodology Ronald Stamper: I use the term methodology under protest bowing only to customary usage. It would be better, as in philosophy of science, to speak of methods when referring to specific ways of approaching and solving problems, and to reserve methodology for comparative and critical study of methods in general; otherwise this vital field of study is nameless

28 Systems Development Life Cycle Planning Analysis Design Implementation

29 The RUP Process Model

30 The Importance of Context Integration Complex web of relationships Developer-method interaction Context-method interaction è method-in-action

31 Developer experience and method usage + Educational exposure to methods Method Use - Realisation of futility of blind adherence to lowlevel formalised method prescriptions touted as universally applicable Derivation of sensible method practice at an appropriate level of granularity & tailored to profile of development environment - Developer Experience +

32 FRS s Framework Influence/shapes Development Context Analyse Formalised Method May be basis of Method-in-Action Enact Developers Justify Influence Develop Roles of Method Information Processing System

33 Seminars 1 & 2 Students read articles on ISDM and write a reflection memo (~2 pages) Hand-in memo one hour before seminar starts (via ) Active participation in seminar discussions, based on your reflection memos Moderated by me