Railway Timetable Application: Scope, Team Effectiveness, and Project Management
Added on 2019-10-18
6 Pages1158 Words229 Views
Meeting Report 1: Initial AnalysisScope of the systemScope 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 startand 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 stationTeam effectivenessIt 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 wellversed 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 duringthe 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 usedas 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 effectivenessSprint PlanningFor railway timetable application development we use agile software development methodology, during a real time project the product manager and customer change their mindabout 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.
End of preview
Want to access all the pages? Upload your documents or become a member.
Related Documents
Railway Timetable: Scope, Team Effectiveness, SDLC, Use Cases, UI Design, Reflectionlg...
|12
|2225
|458
Railway Timetable Application Assignmentlg...
|14
|2261
|283
Three Musketeers: Group Report for Software Engineering Workshoplg...
|24
|5307
|445