Railway Timetable Application Project

The assignment content discusses a group project to develop a Railway Timetable application, with a focus on team effectiveness, project management using Agile software development methodology, and Scrum framework. The scope of the system is to provide rail time table data, allowing users to filter the timetable by origin-destination pair, showing available trains for that route and their respective arrival times. The project involved regular stand-up meetings (Scrum) every Tuesday, Wednesday, Thursday, with notes recorded in a log. The team also held Sprint Review and Retrospective meetings to gather feedback from stakeholders and review previous sprints.

Meeting Report 1: Initial Analysis
Scope of the system
Scope of the system is to provide rail time table data
Following are the scope of Railway Timetable application:
I. The system provide the rail time table data, the application display the data for given
route in a tabular format, the layout of column shows the time of day, and rows
indicate station or spot name, (if the entire time table is not fit on the screen,
application allow scrolling for time and destination).
II. The application also allows filtering the timetable such as it shows only rows for a
specified origin and destination station.
III. The application can calculate the journey destination, when user given the known start
and end times, when filtered timetable is shown, application calculate the and display
the journey time.
IV. The application is able to present a Live departure Board for the selected departure
station
Team effectiveness
It is a group project and to work effectively in the group, we need to develop strategies and
tactics to efficiently complete this project. And for this we creating the Group Working
Agreement and follow the rules we set in this agreement.
Furthermore, we have made use of the online collaboration service JIRA for assignment
management.
For the development of railway timetable application we used systemic software
development practices, and worked to keep as much communication as we could.

Followings steps for effectiveness of team:
Identify the team:
The composition of team may vary on the basis of size; the team must include a member well
versed in console java programming, a member well versed in functionality testing, a
member well versed in software engineering principle.
Meet regularly and “on the clock”:
We set the time for meeting or “on-the-clock” we all team member meet for one hour twice a
week. In the meeting we talk about the progress of our application, difficulties we face during
the development, and how to tackle the problem.
Group Working Agreement:
We establish some ground rule for the application development from beginning the project;
we set the ground rule together and also all members agreeing on the ground rule.
Followings are some ground rule for our team:
Be present:
Each team member will be available on schedule meetings and all group sessions, if they are
absent due to any reason the team member should inform the other member and plan to
reschedule the meeting.
Agenda:
All the details of to be discussed in each meeting is recorded into the document, and it is used
as referred document on start of the meeting.
Ad-hoc:
Team member will use the collaboration tools (JIRA and google drive).

Stay on topic:
Always stay on topic in the meeting, if the discussion wanders, the other member should say
“Let’s take that offline”.
Focus on the issue:
Always focus on issue, not blame the other team member.
Project management / SDLC effectiveness
Sprint Planning
For railway timetable application development we use agile software development
methodology, during a real time project the product manager and customer change their mind
about what they need, and it the unpredicted challenges for the team member, for this reason
scrum uses the flexible approach (define scrum role).
Scrum roles:
Team member will take on the following defined role:
Product Owner:
A product owner is the person who clearly defined the product, they translate the customer
requirement into the user stories, prioritise the backlogs etc.
Scrum master:
We can say the mentor of all team, its scrum master duties to remove all the roadblock of the
projects, scrum master is very well versed in the scrum practice.
Team Member:
A team member is cross functional, with full of required technical skillset.
Our team is not fully structure as much because the capabilities difference in some aspect of
the project.

It is the scrum fundamental to work in the cycle, the team member needs to complete the
assigned work in a time bound cycle which is called sprint cycle. Followings are the sprint
cycle format:
Sprint Meeting:
In the sprint meeting the team member commits to set of deliverables and also identifies the
tasks that must be completed.
Followings are our sprint Meeting log for Railway Timetable application:
Sprint Meeting Log
Numbe
r
Location Date Start
Time
End
Time
Members
Present
1 Meeting place1 06/08/18 10:30 am 12:30 pm All
2 Meeting place1 13/08/18 10:30 am 12:30 pm All
3 Meeting place2 20/08/18 11:00 am 12:00 pm All
4 Meeting place2 27/08/18 11:00 am 12:00 pm All
5 Meeting place2 03/09/18 11:30 am 12:30 pm All
Scrum or Stand-up Meeting:
It is a short stand up meeting here all team member share the task has been completed, the
task they work next, discuss about the issue they face and also how they come up of these
issues.
We plan the scrum meeting on every Tuesday, Wednesday, Thursday of every week,
Followings are our scrum Meeting log for Railway Timetable application:

Scrum Meeting Log
Number Location Date Start
Time
End
Time
Members
Present
Notes
1 Meeting place1 07/08/2018 12:15 12:30 All members
2 Meeting place1 08/08/2018 3:30 3:45 All members
3 Meeting place1 09/08/2018 12:30 12:40 All members
4 Meeting place1 14/08/2018 11:30 11:45 All members
5 Meeting place1 15/08/2018 11:45 12:00 All members
6 Meeting place1 16/08/2018 11:45 12:00 All members
7 Meeting place1 21/08/2018 11:15 11:35 All members
8 Meeting place1 22/08/208 3:30 3:50 All members
9 Meeting place1 23/08/2018 11:40 12:00 All members
10 Meeting place1 28/08/2018 12:15 12:35 All members
11 Meeting place1 29/08/2018 2:20 2:40 All members
12 Meeting place1 30/08/2018 11:10 11:25 All members
13 Meeting place1 04/09/2018 3:40 3:55 All members
14 Meeting place1 05/09/2018 12:25 12:40 All members
15 Meeting place1 06/09/2018 11:20 11:40 All members
16 Meeting place1 11/09/2018 12:40 1:00 All members
17 Meeting place1 12/09/2018 3:40 3:55 All members
18 Meeting place1 13/09/2018 12:10 12:30 All members
19 Meeting place1 18/09/2018 11:45 12:00 All members
20 Meeting place1 19/09/2018 3:30 3:50 All members
22 Meeting place1
23 Meeting place1
24 Meeting place1
25

Sprint Review:
After completed the stories, the team member share the stories and feedback is gathered from
the stockholders which is very useful for the next iteration.
Retrospective:
In the retrospective meeting we review the previously completed sprint and share the
experience which could make the coming sprint more efficient.
Product Backlog:
Assumptions