Project: Agile Development of HolidayTreats Web Application System

This document outlines the development of the HolidayTreats web application system using the Agile methodology. It begins with an introduction to Agile, highlighting its advantages such as customer satisfaction, adaptability to change, and stakeholder engagement. The document then details the tools and techniques used, including the project charter, stand-up meetings, retrospective meetings, product backlog, and sprints. A scenario is presented with a stakeholder identification table and user stories for various roles. Furthermore, it includes a use case diagram, activity diagram, and class diagram to illustrate the system's design. The conclusion emphasizes the importance of effective communication within the development team for the project's success, and references are provided. The Agile approach ensures iterative development, customer involvement, and adaptability throughout the project lifecycle. The document provides a comprehensive overview of the project's planning, design, and implementation using Agile principles.

COVER PAGE
COURSE:
MODULE NAME:
DATA NUMBER:
TUTOR NAME

Contents
1 Introduction..............................................................................................................................................4
1.1 Advantages of Agile Approach...............................................................................................................4
2 Tools/Techniques.....................................................................................................................................4
2.1 Project charter...................................................................................................................................4
2.2 Stand-up meetings.............................................................................................................................4
2.3 Retrospective meetings.....................................................................................................................5
2.4 product backlog.................................................................................................................................5
2.4 Sprint.................................................................................................................................................5
3 scenario....................................................................................................................................................5
3.2 Stakeholders identification table.......................................................................................................5
3.2 User story..........................................................................................................................................5
Property owners..................................................................................................................................5
Short-term tenants..............................................................................................................................6
Site staff...............................................................................................................................................6
Site manager........................................................................................................................................6
Manager..............................................................................................................................................6
3.3 Use case diagram...............................................................................................................................7
3.4 Activity diagram.................................................................................................................................8
3.5 class diagram.....................................................................................................................................9
5 Conclusion..............................................................................................................................................10
6 References..............................................................................................................................................10

Table of figures
Figure 1: Use case diagram..........................................................................................................................6
Figure 2: class diagram................................................................................................................................8

1 Introduction
This document discusses the development of HolidayTreats web application system by discussing
various concepts and techniques that will be used during the project period.
1.1 Advantages of Agile Approach
Agile methodology is a software engineering process where the proposed software system is delivered
in increments to the customer. Agile embraces the concept of customer inclusion in the development
process by delivering the software in increments or deliverables as specified in the project plan.
The following are the main advantages of the agile approach;
 Agile approach ensures customer satisfaction as the software is delivered in increments thus the
customer is able to get what they want at the end of the whole project (Dawson, 2015).
 Agile is able to incorporate changes in requirements easily as compared to other methods. This
is because the software is delivered in increments and if a change occurs then the development
team can integrate it easily into the project plan.
 Agile approach enhances interactions between the stake holder as compared to process and the
tools used.
 Agile approach ensures stakeholder engagement in the whole project development plan.
 Agile approach provides a degree of predictability of the final outcome to all stakeholders as
they are able to see the system as each increment or deliverable is completed.
 Agile ensures payments are done as the software is delivered in increments so typically the
customer pays for every increment delivered (Segue, 2015).
2 Tools/Techniques
2.1 Project charter
A project charter is a document containing the scope of the proposed project, objectives of the project
and the stakeholders involved in a project. The project charter acts as preliminary guide with roles and
responsibilities of all the stakeholders involved and the objectives of the project. The project charter has
the following components;
 Scope of the project
 Justification
 Objectives of the project
 Stakeholders
 Risks
 Benefits that is the cost benefit analysis of the project
 The general budget of the project.
2.2 Stand-up meetings
A stand-up-meeting is a meeting where those who have attended participate in the meeting while
standing. The main aspect of having a meeting while standing is to make the meeting brief and
comprehensive as possible. Stand up meeting s are typically embraced in agile approach where the main
development method is scrum.

2.3 Retrospective meetings
A retrospective meeting is a meeting done while using Agile approach where a project development
team holds a meeting to reflect and analyze on the way they are working so as to improve the working
process. The team inspects how a sprint has been done and then processes to improve are decided in
(Linders, 2013).
2.4 product backlog
A product backlog is a list used in agile where scrum is the main approach. The list contains short and
precise descriptions of every functionality of the proposed product. A product backlog typically consists
of the following items.
 Features of the proposed system
 Bugs
 Technical work
 How knowledge will be acquired.
2.4 Sprint
In agile development approach a sprint can also be referred to as an iteration and is considered to be
the basic unit of development while using the scrum approach. So a deliverable is divided into iterations
or sprints and then the sprints are allocated a timeframe usually one week to one month depending on
the complexity and scope of the sprint.
3 scenario
3.2 Stakeholders identification table
Stakeholder Description
Property owners Owns property to be rented
Short term tenants Rents property for a short term
Site staff Manage property posts
Site manager Receives property listing applications
Manager Oversees the website
3.2 User story
The following are the user stories for different users involved with the system.
Property owners
 As a property owner I want to be able to register in the website
 As a property owner I want to be able to add my properties in the website.
 As a property manager I should be able to view the contract sent by the site manager and
upload it
 As a property owner I want to be able to advertise the properties I have added
 As a property owner I want to see who has booked any of my properties
 As a property owner I want to get payments for my booking.

Short-term tenants
 As a short term tenants I want to be able t register in the website.
 As a short term tenant I want to be able to view all available properties in a certain area.
 As a short term tenant I want to be able to book a property
 As a short term tenant I want to be able to pay for a booked property.
Site staff
 As a site staff I want to be able to see all posts advertised by property owners
 As a site staff I should be able to see details of a specific property post to verify if it’s standard.
 As a site staff I should be able to edit a property post
 As a site staff I should be able to remove a property post
Site manager
 As a site manager I should be able to view all new properties added.
 As a site manager I should be able to view a property so as to review it
 As a site manager I should able to send a contract to the owner of the new listed property
 As a site manager I should be able to approve a post.
Manager
 As a manager I want to see a report of all registered property owners
 As a manager I want to be able to see a report of all property posted.
 As a manager I want to be able to see a report of all bookings

3.3 Use case diagram
Figure 1: Use case diagram

3.4 Activity diagram
The following diagram shows the activity diagram for the activity of booking a property by a short term
tenant.

3.5 class diagram
Figure 2: class diagram

5 Conclusion
The paper discusses the development of HolidayRetreats Web Application System which will be
developed using agile methodology. Use of Agile will ensure that the software system is delivered in
increments to the customer. The development team will use scrum where by sprints will be
allocated to every developer. For the project to be a success, the development team has to ensure
there is effective communication.
6 References
Dawson, C., 2015. The Pros and Cons of Utilizing Agile Methodologies. Nearshore Americas. Available
at: http://www.nearshoreamericas.com/agile-methodology-advantages-disadvantages/ [Accessed
August 16, 2017].
Linders, B., 2013. What’s an Agile Retrospective and Why Would You Do It? Ben Linders Sharing my
experience. Available at: https://www.benlinders.com/2013/whats-an-agile-retrospective-and-why-
would-you-do-it/ [Accessed August 16, 2017].
Segue, 2015. 8 Benefits of Agile Software Development. Segue Technologies. Available at:
http://www.seguetech.com/8-benefits-of-agile-software-development/ [Accessed August 16, 2017].