Curtin Business School School of Information Systems

Unit Outline

11739 Information Systems Development Methodologies 601 Semester 2, 2013

Unit study package number: Mode of study: Tuition pattern summary: Credit Value: Pre-requisite units: Co-requisite units: Anti-requisite units: Result type: Approved incidental fees: Unit coordinator: 11739 Internal Seminar: 1 x 3 Hours Weekly This unit does not have a fieldwork component. 25.0 307777 (v.0) Systems Analysis 501 or any previous version Nil 11734 (v.0) Systems Development 503 or any previous version Grade/Mark Information about approved incidental fees can be obtained from our website. Visit f ees.curtin.edu.au/incidental_fees.cfm for details. Name: Phone: Email: Building: Room: Jules De Souza +618 9266 7139 Jules.DeSouza@cbs.curtin.edu.au 402 710

Teaching Staff:

Administrative contact:

Name: Phone: Email: Building: Room:

Julie Kivuyo 08 9266 7056 Julie.Kivuyo@curtin.edu.au 402 Reception

Learning Management System:

Blackboard (lms.curtin.edu.au)

11739 Information Systems Development Methodologies 601 Bentley Campus 26 Jul 2013 School of Information Systems, Curtin Business School

Page: 1 of 8 CRICOS Provider Code WA 00301J, NSW 02637B

Curtin Business School School of Information Systems

Acknowledgement of Country
We respectfully acknowledge the Indigenous Elders, custodians, their descendants and kin of this land past and present.

Syllabus
The systems development process; frameworks and methodologies, methods and techniques. Contemporary systems development approaches and methods. In-depth study of a contemporary system development methodology.

Introduction
This unit will address what agile methods are, and the theory, practice and implementation of agile methods.

Unit Learning Outcomes

On successful completion of this unit students can: 1 Explain the fundamental aspects of major contemporary system development approaches along with their advantages and disadvantages 2 Apply practices used in contemporary systems development methodologies 3 Select and evaluate appropriate Information Systems development methods in complex environments 4 Communicate appropriate arguments for the use of an approach in the development of information systems Graduate Attributes addressed

Curtin's Graduate Attributes

Apply discipline knowledge Communication skills International perspective
(value the perspectives of others)

Thinking skills
(use analytical skills to solve problems)

Information skills
(confidence to investigate new ideas)

Technology skills Cultural understanding

(value the perspectives of others)

Learning how to learn

(apply principles learnt to new situations) (confidence to tackle unfamiliar problems)

Professional Skills
(work independently and as a team) (plan own work)

Find out more about Curtin's Graduate attributes at the Office of Teaching & Learning website: ctl.curtin.edu.au

Learning Activities
The seminars are used to introduce the concepts, provide examples, raise questions and discuss assessments.

11739 Information Systems Development Methodologies 601 Bentley Campus 26 Jul 2013 School of Information Systems, Curtin Business School

Page: 2 of 8 CRICOS Provider Code WA 00301J, NSW 02637B

Curtin Business School School of Information Systems

Learning Resources
Essential texts
The required textbook(s) for this unit are: Smith, G. and Sidky A. (2009). Becoming agile in an imperfect world, Manning Publications Co.

Recommended texts
You do not have to purchase the following textbooks but you may like to refer to them. Cohn, M (2004). User Stories Applied, Addison Wesley/Pearson Education. Highsmith, J (2002). Agile Software Development Ecosystems, Addison Wesley/Pearson Education.

Other resources
All lecture slides, exercises, assignment cover sheets, marking guides, and general announcements about the unit are available from the ISDM 601Blackboard site. Please access the units Blackboard regularly to check for updates about the unit.

Assessment
Assessment schedule
Task Journal Article Critique 1 Mid Semester Test 2 Information Systems Development Assignment 3 30 percent 10 percent Value % 10 percent Date Due Unit Learning Outcome(s) Assessed 1,3,4

Final Exam 4

50 percent

Week: TBA Day: During seminar Time: During seminar Week: See Program 1,2 calendar Day: During seminar Time: During seminar Week: See Program 2,3,4 calendar Day: See Program calendar Time: See Program calendar Week: Exam weeks 1,3,4 Day: TBA Time: TBA

11739 Information Systems Development Methodologies 601 Bentley Campus 26 Jul 2013 School of Information Systems, Curtin Business School

Page: 3 of 8 CRICOS Provider Code WA 00301J, NSW 02637B

Curtin Business School School of Information Systems

Detailed information on assessment tasks
1. Students are required to form a group of two or three students. Students are required to work as a team with shared accountability and leadership. The group is required to critically analyse the assigned journal article, conduct additional research and make a formal presentation. Journal articles will be assigned to student groups in the first class. The student group presentation should include the following THREE (3) components: 1) a concise summary of key ideas/arguments in the assigned journal article (approx. 10 minutes); 2) critical thoughts on some of the key issues together with findings from the teams additional literature search and analysis on the issues (approx. 15 minutes); and 3) class discussion on those issues addressed (approx. 15 minutes). Please note that this assessment is designed to promote first independent and then collective critical thinking in a group. The student is required to question and challenge implicit assumptions and logic/reasoning explicit in the journal article as well as any discernable shortcomings of the study reported in the article while acknowledging the papers contribution. As a group, the students are also encouraged to engage in a series of debate-like discussions where each wears different thinking hats (e.g., Support, Neutral and Refute). 2. The semester test is intended to test your knowledge of whats been covered in the unit up to the week before the test. The questions will be from material covered in the seminar and the textbooks. The emphasis of the test will be on interpretation and application of material covered in the unit. The questions are designed to make you think, prove your understanding of the material covered in the unit. 3. The major assignment will be a research assignment on a topic related to agile development. Students will be assigned a topic. This assignment requires the student to review literature relevant to his/her own research topic and produce an essay/report around 3,000 words. Note that this involves the following tasks: 1) searching relevant literature on the subject matter widely, 2) analysing and systematically evaluating the body of knowledge, and 3) synthesising pieces of literature information/knowledge with your own critical thoughts and reasoning. 4. The final examination will be comprehensive in nature (covering all areas of the unit) and will be two hours in duration. The exam will have a mixture of theoretical questions (which ask about the concepts, processes, rules, philosophy, etc.) and practical questions (which ask you to apply the techniques and reason about a scenario of a particular situation).

Fair assessment through moderation

Moderation describes a quality assurance process to ensure that assessments are appropriate to the learning outcomes, and that student work is evaluated consistently by assessors. Minimum standards for the moderation of assessment are described in the Assessment Manual, available from policies.curtin.edu.au/policies/teachingandlearning.cfm

Late assessment policy

This ensures that the requirements for submission of assignments and other work to be assessed are fair, transparent, equitable, and that penalties are consistently applied. 1. All assessments which students are required to submit will have a due date and time specified on the Unit Outline. 2. Accepting late submission of assignments or other work will be determined by the unit coordinator or Head of School and will be specified on the Unit Outline. 3. If late submission of assignments or other work is not accepted, students will receive a penalty of 100% after the due date and time ie a zero mark for the late assessment. 4. If late submission of assignments or other work is accepted, students will be penalised by ten percent per calendar day for a late assessment submission (eg a mark equivalent to 10% of the total allocated for the assessment will be deducted from the marked value for every day that the assessment is late). This means that an assignment worth 20 will have two marks deducted per calendar day late. Hence if it was handed in three calendar days late and marked as 12/20, the student would receive 6/20. An assessment more than seven calendar days overdue will not be marked. Work submitted after this time (due date plus seven days) may result in a Fail - Incomplete (F-IN) grade being awarded for the unit.

11739 Information Systems Development Methodologies 601 Bentley Campus 26 Jul 2013 School of Information Systems, Curtin Business School

Page: 4 of 8 CRICOS Provider Code WA 00301J, NSW 02637B

Curtin Business School School of Information Systems

Assessment extension
A student must apply for an assessment extension on the Assessment Extension Form, as prescribed by the Academic Registrar. The form is available on the Forms page at http://students.curtin.edu.au/administration. The student will be expected to lodge the form and supporting documentation with the unit coordinator before the assessment date/time or due date/time. An application may be accepted up to five working days after the date or due date of the assessment task where the student is able to provide an acceptable explanation as to why he or she was not able to submit the application prior to the assessment date. An application for an assessment extension will not be accepted after the date of the Board of Examiners' meeting.

Additional assessment information Pass requirements

To pass this unit you must: a. Receive a mark greater than or equal to 50, AND b. Attempt all assessment activities

Referencing style
The referencing style for this unit is Chicago. More information can be found on this style from the Library web site: library.curtin.edu.au.

Plagiarism
Plagiarism occurs when work or property of another person is presented as one's own, without appropriate acknowledgement or referencing. Plagiarism is a serious offence. For more information refer to academicintegrity.curtin.edu.au.

Plagiarism monitoring
Work submitted may be subjected to a plagiarism detection process, which may include the use of systems such as 'Turnitin'. For further information, see academicintegrity.curtin.edu.au/students/turnitin.cfm.

Additional information Deferral of semester test

You may request a deferment of the semester test, but you must provide documentation to substantiate your request for a deferment as soon as possible (no later than one week from the date of the test). A deferment longer than one week will only be granted for exceptional circumstances. Acceptable reasons for deferment are sickness and personal trauma but these must be substantiated. Any request for deferment and accompanying documentation must be given to me and not your tutor. If, due to emergency or illness, you know you will miss a test, it is your responsibility to let me know ahead of time.

Enrolment:
It is your responsibility to ensure that your enrolment is correct - you can check your enrolment through the eStudent option on OASIS, where you can also print an Enrolment Advice.

Supplementary/Deferred exams:
Supplementary and deferred examinations will be held at a date to be advised. Notification to students will be made after the Board of Examiners meeting via the Official Communications Channel (OCC) in OASIS. It is the student's responsibility to check their OASIS account on a weekly basis for official Curtin correspondence. If your results show that you have been awarded a supplementary or deferred exam you should immediately check your OASIS email for details.

11739 Information Systems Development Methodologies 601 Bentley Campus 26 Jul 2013 School of Information Systems, Curtin Business School

Page: 5 of 8 CRICOS Provider Code WA 00301J, NSW 02637B

Curtin Business School School of Information Systems

Student Rights and Responsibilities

It is the responsibility of every student to be aware of all relevant legislation, policies and procedures relating to their rights and responsibilities as a student. These include: the Student Charter the University's Guiding Ethical Principles the University's policy and statements on plagiarism and academic integrity copyright principles and responsibilities the University's policies on appropriate use of software and computer facilities Information on all these things is available through the University's "Student Rights and Responsibilities website at: students.curtin.edu.au/rights.

Disability
Students with a disability or medical condition (e.g. mental health condition, chronic illness, physical or sensory disability, learning disability) are encouraged to seek advice from Disability Services www.disability.curtin.edu.au. A Disability Advisor will work with you and liaise with staff to identify strategies to assist you to meet unit (including fieldwork education) and course requirements, where possible. It is important to note that the staff of the university may not be able to meet your needs if they are not informed of your individual circumstances.

Recent unit changes

We welcome feedback as one way to keep improving this unit. Students are encouraged to provide unit feedback through eVALUate, Curtin's online student feedback system (see evaluate.curtin.edu.au/info/). Recent changes to this unit include: Due to the positive feedback from students in Evaluate, no major changes were made to the unit.

See evaluate.curtin.edu.au to find out when you can eVALUate this unit.

Program calendar
Program Calendar Semester 2 2013

Week
1.

Begin Date
5 August

Lecture/ Seminar
Approaches to systems development Moving to agile

Pre-readings

Assessment Due

Chapter 1 Chapter 2

2.

12 August

The story of Acme Media Aligning the pilot team with the project

Feasibility: is this project viable? Chapter 10 Chapter 11 Chapter 12

3.

19 August

Feature cards: a tool for just enough planning Prioritizing the backlog

Chapter 13 Estimating at the right level with Chapter 14 the right people

11739 Information Systems Development Methodologies 601 Bentley Campus 26 Jul 2013 School of Information Systems, Curtin Business School

Page: 6 of 8 CRICOS Provider Code WA 00301J, NSW 02637B

Curtin Business School School of Information Systems

4. 26 August Overview of user stories Writing user stories Why user stories? Chapter 1 (MC) Chapter 2 (MC) Chapter 13 (MC)

5. 6.

2 September 9 September

Tuition Free Week Release planning: envisioning the overall schedule Chapter 15

Iteration planning: the nitty-gritty Chapter 16 details 7. 16 September Start your engines: iteration 0 Delivering working software Adapting: reacting positively to change Chapter 18 Chapter 20 8. 23 September Delivering working software (contd) Adapting: reacting positively to change (contd) Delivery: bringing it all together The retrospective: working together to improve 9. 10. 11. 30 September 7 October 14 October Tuition Free Week Planning game Scrum Extreme Programming 12. 21 October Are you ready for agile? The fitness test: all about readiness assessments The mindset of an agile leader 13. 28 October Chapter 17 (JH), Chapter 15 (MC) Chapter 22 (JH), Appendix A (MC) Chapter 3 Chapter 4 Chapter 7 Chapter 21 Chapter 22 Chapter 18 Chapter 20 Semester test during seminar Chapter 17

Injecting agility into your current Chapter 8 process Articulating your ecosystem Agile metamorphosis Chapter 24 (JH)\ Chapter 26 (JH) Chapter 25 (JH) Appendix C Chapter 3 Appendix A Assignment due Monday 6pm

14.

4 November

Customising an agile process Agile Overview Agile goals Agile Practices

15. 16. 17

11 November 18 November 25 November

Study Week Examinations Examinations

Page: 7 of 8 CRICOS Provider Code WA 00301J, NSW 02637B

11739 Information Systems Development Methodologies 601 Bentley Campus 26 Jul 2013 School of Information Systems, Curtin Business School

Curtin Business School School of Information Systems

11739 Information Systems Development Methodologies 601 Bentley Campus 26 Jul 2013 School of Information Systems, Curtin Business School

Page: 8 of 8 CRICOS Provider Code WA 00301J, NSW 02637B