Managing Software Development Assignment 2022

Managing Software Development i
SOUTHERN CROSS UNIVERSITY
ASSIGNMENT COVER SHEET
For use with online submission of assignments
Please complete all of the following details and then make this sheet the first page of each file
of your assignment – do not send it as a separate document.
Your assignments must be submitted as either Word documents, text documents with .rtf
extension or as .pdf documents. If you wish to submit in any other file format please discuss
this with your lecturer well before the assignment submission date.
Student Name:
Student ID No.:
Unit Name: Managing Software Development
Unit Code: CMP73010
Tutor’s name:
Assignment No.:
Assignment Title:
Due date:
Date submitted:
Declaration:
I have read and understand the Rules Relating to Awards (Rule 3 Section 18 –
Academic Misconduct Including Plagiarism) as contained in the SCU Policy
Library. I understand the penalties that apply for plagiarism and agree to be bound
by these rules. The work I am submitting electronically is entirely my own work.
Signed:
(please type
your name)

Managing Software Development ii
Table of Contents
1. Part 1: The Agile Process...................................................................................... 1The Values of the agile process...............................................................................1General principles of Agile process.........................................................................1
2. Explanation of the possible Agile methodologies that could be used...................2Scrum...................................................................................................................... 2
How does scrum work?........................................................................................ 2
Framework for Scrum........................................................................................... 3Extreme Programming (XP)..................................................................................... 3
Practices of XP..................................................................................................... 3
Roles in XP........................................................................................................... 4
3. Arguments for and against the adoption of agile development method..............5Arguments for the adoption of Scrum agile development method..........................5Arguments against adoption of XP agile development method...............................5
4. Projects that can benefit from Scrum...................................................................6
Projects that may not benefit from Scrum..................................................................6Why using SCRUM is a good method for two clients?.................................................6
Part 2: Automatic Document Generation....................................................................7
Refences..................................................................................................................... 9

Managing Software Development 1
1. Part 1: The Agile Process
Agile process of software development is a method of the project management process,
principally used for software /system development, where requests, product demands and
solutions passes through the cooperation of self-organized team and cross-working groups and
their clients. (Muslihat, 2019, 7)
Starting from the values and standards of Agile principles and values, it was made as a
solution option to the insufficiencies of traditional methods of software development, for
example, the Waterfall technique. Software industry is profoundly a competitive market because
software product has to be updated continuously. This implies software engineers have to always
improve and upgrade their software to keep up the game — and the straight, consecutive
approach of the Waterfall technique simply was not sufficient and may not guaranteed quality
work. (Muslihat, 2019, 7)
The Values of the agile process
 People and interaction over procedures and devices
 Working software over exhaustive documentation
 Client cooperation over contract arrangements
 Reacting to change over the accompanying plan
General principles of Agile process
 Consumer fulfilment through on schedule and nonstop deliverables i.e software
 Accommodate the changing software requirements during the improvement process
 Working software is delivered often, it can be weekly as opposed to monthly
 Close working cooperation between business delegate and the engineers
 A working product is the measure of the product improvement process

Managing Software Development 2
 The Agile process supports a constant development pace
 face-to-face discussion is the best kind of communication because of the fact that the
designers are in the same area. (Muslihat, 2019)
 Continuous attention regarding technical excellence and great product design plan
Individuals who apply any kind of Agile method cling to these values and principles. The
principles offer a decent overview of what is required in regards to the Agile development life
cycle practices. (Muslihat, 2019, 11). The main agile methodologies are Kanban, SCRUM, Lean
Development, Extreme Programming (XP) and Crystal.
2. Explanation of the possible Agile methodologies that could be used
The methods that can be used for the two clients are Scrum and XP.
Scrum
This is the most used method in the Agile process development cycle. It has stages of
development called sprints. Scrum stresses on the maximization of the development time of a
product, characterized by day to day meetings to design the most ideal direction for the workday.
Work the matters more than others are given a priority and is broken into manageable loads.
(Pawar and Mahajan, 2017)
Scrum is about cooperation from both the development team and the owners of the
business or software project. It is about getting responses and giving a feedback to ensure that
the software developed is the best. (Pawar and Mahajan, 2017, 2)
How does scrum work?
 Scrum main activity is the sprint, an iteration of 1-4 weeks.
 Sprint planning is done to determine and define goals that the upcoming sprint is
supposed to achieve