Australian Electric Supply

This memo discusses Agile & Iterative Systems Development, Agile Scrum Methodology, Advantages and Discussion. It is relevant for students studying Agile Methods and related courses. Download now from Desklib!

qwertyuiopasdfghjklzxcvbnmqw
ertyuiopasdfghjklzxcvbnmqwert
yuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiop
asdfghjklzxcvbnmqwertyuiopasd
fghjklzxcvbnmqwertyuiopasdfgh
jklzxcvbnmqwertyuiopasdfghjkl
zxcvbnmqwertyuiopasdfghjklzxc
vbnmqwertyuiopasdfghjklzxcvb
nmqwertyuiopasdfghjklzxcvbnm
qwertyuiopasdfghjklzxcvbnmqw
ertyuiopasdfghjklzxcvbnmqwert
yuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiop
asdfghjklzxcvbnmqwertyuiopasd
fghjklzxcvbnmqwertyuiopasdfgh
jklzxcvbnmrtyuiopasdfghjklzxcv
Australian Electric Supply
Agile Methods and Memo
5/30/2019

Australian Electric Supply
Table of Contents
Agile & Iterative Systems Development....................................................................................2
Agile Scrum Methodology.....................................................................................................2
Discussion...........................................................................................................................2
Advantages..........................................................................................................................2
Disadvantages.....................................................................................................................2
Lean & Kanban Software Development.................................................................................3
Discussion...........................................................................................................................3
Advantages..........................................................................................................................3
Disadvantages.....................................................................................................................3
Extreme Programming (XP)...................................................................................................3
Discussion...........................................................................................................................3
Advantages..........................................................................................................................4
Disadvantages.....................................................................................................................4
Dynamic System Development Method (DSDM).................................................................4
Discussion...........................................................................................................................4
Advantages..........................................................................................................................4
Disadvantages.....................................................................................................................5
Recommended Methodology..................................................................................................5
References..................................................................................................................................6
Appendix....................................................................................................................................7
1

Australian Electric Supply
Agile & Iterative Systems Development
The methodology that OZES management team shall follow must be agile and iterative
system development. It comprises of the set of methods that follow ad-hoc method of system
development. The agile methods do not have a set of pre-defined methods or sequential steps;
rather, the steps and methods are determined as per the project conditions and project
environment. There are a number of different agile methods that have been defined which can
be used for the system.
Agile Scrum Methodology
Discussion
Scrum is the agile development methodology that will allow incremental and iterative
development of the system. There is a Product Backlog that comprises of the system
requirements. In this methodology, the project will be carried out in a series of sprints
(iterations) and each sprint will include a sub-set of the overall requirements. The
methodology will focus on the functional as well as the functional requirements. These
sprints will run for a period of two to four weeks and there will be customer collaboration
process conducted at the end of each sprint (Ashbacher, 2010).
Advantages
 There is specific amount of work that the team commits in a particular sprint and
therefore, the team has a vision and a goal in perspective.
 The team involved is cross-functional and self-directing.
 There are only three roles defined under scrum to avoid ambiguities. These include
Product Owner, Scrum Master, and Scrum Team
Disadvantages
 The lack of experienced professionals and members in the project team may lead to
significant issues and there may be problem of scope creep that may emerge.
 In case of poor definition of the tasks and activities, there are chances of inefficiencies
and operational failures that may come up (Rajasekaran, 2015).
2

Australian Electric Supply
Lean & Kanban Software Development
Discussion
Lean & Kanban software development will carry out the development processes on the basis
of the value streams. The primary aim in this methodology will be to deliver highest value to
the customers and the business organization. The primary principles on which the
methodology will be based upon will be elimination of the wastes, empowering the team,
amplification of the learning, and integrity development. Kanban is the development method
that is based of visual workflow management and keeps a limit on the work in progress. The
enhanced flow is one of the characteristics associated with the methodology (Ebert,
Abrahamsson & Oza, 2012).
Advantages
 Time-boxed iteration is optional in this case.
 The waste activities are eliminated and therefore, the effort of the resources is utilized
and directed in the correct direction.
 The board can be shared by multiple teams or individuals associated in the project
team.
Disadvantages
 There are situations wherein unwanted complexities get added to the project which
may appear as significant issue for the members of the project team.
 There are no defined timeframes associated with the project phases which may lead to
confusions among the project team members.
Extreme Programming (XP)
Discussion
Extreme Programming (XP) is the agile method that will provide high-quality software and
will provide continuous and quick deliveries. There may be changes in the software
requirements that may occur. These changes will be readily managed with the aid of this
methodology. There will be high customer involvement and continuous testing & planning
that will be made possible with the aid of the methodology. There are four basic principles
that the methodology relies upon. These include simplicity, communication, feedback, and
courage (Kunwar, 2018).
3

Australian Electric Supply
Advantages
 The risks associated with the programming and technical failures are reduced and the
customers are collaborated at every step of the project making sure that they are
provided with the required set of deliveries.
 The entire process is visible and accountable.
 The overall timeframe that will be involved in this case will be lesser as compared to
the rest of the methods.
Disadvantages
 It has been witnessed that the methodology puts more focus on the code rather than
the design which may come up as an issue.
 There may be defects in the initial code that may be witnessed as the methodology
does not measure quality assurance.
Dynamic System Development Method (DSDM)
Discussion
It is an agile software development method that relies on the timely delivery of the project
and within the defined budget. There are certain principles on which the methodology is
based upon. These eight principles form the guidelines for the members of the project team
and the development project is carried out accordingly. The primary principle is to maintain
the focus on the business needs. The deliveries shall be made on time and there shall be no
compromise on the quality (Sharma, 2019). The iterative development is promoted as part of
this methodology with special focus on the communication mechanisms.
Advantages
 The risks associated with the schedule and budget, such as schedule overrun and
budget overrun are usually avoided in the projects that are carried out using this
methodology.
 The team members have the guidelines on the methods to follow and there is no
transparency issues observed.
 The communication process involved in this methodology is better than the other
methods.
4

Australian Electric Supply
Disadvantages
 The overall timeframe taken by the project under this methodology may be higher
than the others.
 The skills of the resources play a very important role in the project. The involvement
of the resources with poor skills may lead to significant issues in the project.
Recommended Methodology
The methodology that is recommended for the project is Extreme Programming (XP). The
methodology is recommended for this case because the timeframe that will be taken by the
XP methodology will be the least and the quality that will be provided by this method will be
better than the rest of the agile development methods. Another reason that is involved in the
selection of this methodology is the enhanced level of customer collaboration that is involved
in the method. The customers will be collaborated with at regular intervals and their
expectations from the project will be met.
Event table
Event Event
Type
Trigger Source Activity/
Use Case
System
Response/
Output
Destinatio
n
OZES
wants to add
new broker
Interna
l
Recruit
broker
Broker Create
broker
Associate or
Full-time
broker is to
be added
OZES,
New broker
OZES
wants to add
new
product/ite
m
Interna
l
New
item/produc
t
OZES Add
product/item
New
product/Ite
m added
successfully
OZES ,
warehouse
employee
OZES
wants sell
second-
handed item
Interna
l
New sale OZES Second-
handed item
is to be sold
New sale
has been
recorded
successfully
OZES,
Broker
Customer
wants to
place new
order
Interna
l
Purchase an
item/produc
t
Custome
r
Create order New order
added
successfully
OZES,
order
OZES
wants to
create a sale
order
Interna
l
Create sales
record
OZES Sale
calculation
New sale
record has
been added
successfully
OZES
5

Australian Electric Supply
Use case diagram
6

Australian Electric Supply
Use case description
7
Use Case Sell second-handed item
Scenario Associate broker has sent a second-handed item for
sale to OZES.
Triggering Event OZES checked the second-handed item and approve
it for sale.
Description Allows broker and OZES to put up a second-handed
item for sale.
Actors Staff, associate broker
Related Use Case N/A
Stakeholders 1. Staff
2. Associate broker
Pre-Condition Customer is able to view all items
Post-Condition Second-Handed item has been sold successfully.
Flow of activities
Actor System
1) Customer clicks on “View Second-
Handed items”,
3) Customer selects an item and
clicks submit button.
5) Customer enters payment details
and submit the form.
2) System displays list of all items with “buy” button
besides each of them.
4) System displays payment page.
6) System creates unique identification number.
Alternate Course of Action 4.1 If customer enters incorrect details then system
generates an error message.

Australian Electric Supply
Domain model class diagram
Design class diagram
8

Australian Electric Supply
References
Ashbacher, C. (2010). Succeeding With Agile: Software Development Using Scrum, by Mike
Cohn. The Journal Of Object Technology, 9(4). doi: 10.5381/jot.2010.9.4.r1
Bijl-Brouwer, M., & Dorst, K. (2017). Advancing the strategic impact of human-centred
design. Design Studies, 53, 1-23. doi: 10.1016/j.destud.2017.06.003
Bullinger, H., Bauer, W., Wenzel, G., & Blach, R. (2010). Towards user centred design
(UCD) in architecture based on immersive virtual environments. Computers In
Industry, 61(4), 372-379. doi: 10.1016/j.compind.2009.12.003
Ebert, C., Abrahamsson, P., & Oza, N. (2012). Lean Software Development. IEEE Software,
29(5), 22-25. doi: 10.1109/ms.2012.116
Javaid, M. (2013). Review and Analysis of Human Computer Interaction (HCI) Principles.
SSRN Electronic Journal. doi: 10.2139/ssrn.2333608
Kunwar, S. (2018). Scenario Based Requirement Engineering (SBRE) in eXtreme
Programming (XP) through Agile Modelling (AM). SCITECH Nepal, 13(1), 9-15.
doi: 10.3126/scitech.v13i1.23496
Natda, K. (2013). Responsive Web Design. Eduvantage, 1(1). doi: 10.11635/2319-
9954/1/1/18
Rajasekaran, V. (2015). Issues in Scrum Agile Development Principles and Practices in
software development. Indian Journal Of Science And Technology, 8(35). doi:
10.17485/ijst/2015/v8i35/79037
Sharma, A. (2019). A Comparative Analysis of Agile Methods for Core Banking Software,
XP Versus DSDM. International Journal Of Communication And Media Studies,
9(3), 85-90. doi: 10.24247/ijcmsjun20199
Terblanche, J. (2014). Using HCI Principles to Design Interactive Learning Material.
Mediterranean Journal Of Social Sciences. doi: 10.5901/mjss.2014.v5n21p377
9

Australian Electric Supply
Appendix
To: The Executive Business People
From: Project Manager
Date: 30th May 2019
Subject: User Centred Design (UCD) and Human Computer Interaction (HCI) Design
Principles
The memo provides the information on the User Centred Design (UCD) and Human
Computer Interaction (HCI) Design Principles for the system. The relevance of these design
methods and elements along with the specific methods that shall be used in this case are
highlighted.
User Centred Design (UCD) is the design approach in which the designers make sure that the
system design is in accordance with the needs and expectations of the end-users (Bullinger,
Bauer, Wenzel & Blach, 2010). Human Computer Interaction (HCI) design principles are the
ones in which the focus is on the enhanced communication and collaboration between the
end-user and the system for enhanced user experience and engagement levels (Bijl-Brouwer
& Dorst, 2017).
These design approaches and principles will be necessary to be integrated in this system
because it is first of such systems that are being implemented in the organization. The
primary users of the system will be the employees of the organization that have little or no
experience with such a system in the past. It will be necessary that the end-users gain an
understanding of each of the system features so that the system goals and objectives are
achieved. There will be some of the HCI design principles and UCD norms that will be
integrated and followed in this case.
The first and the foremost principle that will be followed will be consistency in terms of the
design. There will be a number of user interface (UI) elements that will be integrated in the
system. It will be necessary that these elements do not vary from one screen to the other in
terms of the layout, color, placement, or size. This is because increased variance leads to the
deterioration of the customer engagement levels (Javaid, 2013). Therefore, consistency shall
be included as one of the primary design elements and principles and shall be followed for all
10

Australian Electric Supply
the system screens. Another principle that must be followed in the system shall be
customization and personalization. There will be multiple users that will have the access on
the system. These users may have different expectations from the system in terms of visual
appeal and look & feel of the system. These users shall be provided with the ability to adjust
the screen resolution along with the customization of the color scheme and color tone. Also,
the font face shall be customized as per the user requirements along with the change in the
font size. The other screen elements must automatically adjust as per the font size selected by
the user. Navigation and scrolling is another HCI design principle that must be followed and
maintained. The users will not want to keep on scrolling on a particular screen. Also, they
will want to have smooth navigation on the screens. Therefore, over-scrolling shall be
avoided on every screen of the system. The navigation on one screen and from one screen to
the other screen shall be kept smooth (Terblanche, 2014). The users will be utilizing such a
system for the first time. It is certain that the users will perform some of the operational errors
and mistakes during the utilization of the system. Therefore, the users shall be provided with
the opportunity to roll back their actions and the error resolution schemes must be integrated
in the system. The users shall also be notified about their mistakes so that they get to know
about the same and do not repeat the action in the future. The users shall also be provided
with the ability to make changes in the language of the system.
The responsive web design methodology shall be used in order to incorporate the user centred
design and HCI design principles. This is because the system will be accessed by the
employees in different modes and devices (Natda, 2013). There may be some users that may
access the system on their desktops while there may be certain users that may access the
system on the mobile devices. In the case of the mobile devices, the mode may vary as
portrait or landscape mode. The system shall automatically adjust as per the mode selected by
the user and the screen resolution and elements shall accordingly adjust.
These design approaches and principles will ensure that the system provides enhanced user
experience to all the end-users of the system.
Please review these design principles and provide your comments. Please feel free to suggest
the modifications and recommendations to improve the overall system design.
Best Regards,
Project Manager
11