Three- Reflective Journal

8/6/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89880_1&content_id=_8975603_1&mode=reset 1/5

MODULE 5.2MODULE 5.2

Requirements for speci�c project classes

Source: https://www.nimble.com/blog/why-outsourcing-is-a-good-thing-for-

your-business/

Introduction:

Requirements practices may need to be adapted in di�erent types of

projects. Business analysts should have the �exibility to tailor requirement

practices to �t di�erent types of project. The requirement practices in a

outsourced project may not be the same as those in a packaged solution

project. Module 5.2 looks at a particular class of project – Agile project.

8/6/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89880_1&content_id=_8975603_1&mode=reset 2/5

The traditional waterfall development method is a sequential model, that is,

project moves through a number of pre-de�ned stages. It is very expensive,

though possible, to move backwards in the project lifecycle, hence the name

“waterfall”. Customers are engaged upfront in the requirement elicitation

phase of a project. After requirement analysis, speci�cation, validation,

customers are required to sign o� a software requirement speci�cation. The

speci�cation will then be fed into design, development, testing phase.

Customers will then be engaged in the �nal delivery stage of the project.

However, the waterfall development model has a number of limitations and

has led to a very high failure rate among the software development

projects. For example, di�erent from a construction project where customer

can visualise the progress of the product, customers in software

development projects have a tendency to change requirement as they

cannot see the architecture and the development of software. The

in�exibility of waterfall development model requires the requirements to be

frozen before they are passed to the software designer and developers and

therefore incapable of coping with requirement changes.

Agile development method seeks to address the limitations of waterfall

model. Both methods handle requirements di�erently in various aspects.

You will read about the agile development method �rst, e.g. its manifesto,

and learn how requirement practices can be tailored in an agile project.

Essential Resources:

Manifesto for Agile Software Development

Read the manifesto for Agile Software Development at

https://agilemanifesto.org and the 12 principles behind the Agile

Manifesto at: https://agilemanifesto.org/principles.html

The values and principles in the Agile Software Development

Manifesto are discussed in the next Essential Resource.

8/6/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89880_1&content_id=_8975603_1&mode=reset 3/5

Selected videos from the Agile Foundations Course on

Linda.com.

View the following videos from the Agile Foundations Course on

Linda.com.

The agile manifesto: Values (3m 20s): https://www.lynda.com/Project-Management-tutorials/agile- manifesto-Values/761929/5011070-4.html?org=think.edu.au

The agile manifesto: Principles (3m 20s): https://www.lynda.com/Project-Management-tutorials/agile- manifesto-Principles/761929/5011071-4.html?org=think.edu.au

User stories (3m 5s): https://www.lynda.com/Project- Management-tutorials/User-stories/761929/5011078-4.html? org=think.edu.au

User stories: Common challenges (2m 3s): https://www.lynda.com/Project-Management-tutorials/User- stories-Common-challenges/761929/5011079-4.html? org=think.edu.au

These four videos contain an introduction to the values and principles

of the agile manifesto as well as the user stories, an approach

commonly adopted in agile project. 

Schön, E., Thomaschewski, J., & Escalona, M. (2017). Agile

requirements engineering: A systematic literature review.

Computer Standards & Interfaces, 49, 79-91.

doi:10.1016/j.csi.2016.08.011

This article is a recent literature review on Agile requirement

engineering – the state-of-the-art requirement practices in agile

project. This article is available from Torrens library at:

https://lesa.on.worldcat.org/oclc/6812611139

Learning Activity:

8/6/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89880_1&content_id=_8975603_1&mode=reset 4/5

Learning Activity: Discussion forum post

In this Module, you learnt requirement practices in agile

development project. In this learning activity, you are required to

research characteristics of requirements or customisation of

requirement practices for speci�c project classes, for example,

Enhancement and replacement projects;

Packaged solution projects;

Outsourced projects;

Business process automation projects;

Business analytics projects;

Embedded and other real-time systems projects;

Or any other types of project you would like to research. Post on

Module 5 discussion forum your �ndings.

Read other students’ post and provide constructive comments to at

least two students’ posts.

To participate in the Discussion Forum, click here to scroll to the

bottom of this page then click on the "Module 5 - Discussion

Forum" link.

Note: The Learning activities above are not part of summative/graded

assessment; however they are designed to prepare you for incremental

graded assessment and expand your learning.

These activities encourage a community learning experience between peers,

and provide opportunities for facilitators to o�er formative feedback,

throughout a module, to the student cohort.

8/6/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89880_1&content_id=_8975603_1&mode=reset 5/5