The First Sprint of the

Student Productivity Tool

By Morgan, Aidan, Lukas, George and Paddy
The Product Brief

- To produce a Student Productivity Tool

- For managing time throughout a semester/course

- Setting tasks, goals and assignments

How will it be developed

The program will be developed using the Agile method

- The specification production

- Designing the GUI

- The implementation of the product

- The testing of the product

- The review

- Improvements
First Sprint Planning

For the first sprint, we planned on focusing on

- Producing the basic and initial version of the tool

- Focusing on the basic main functions of the tool

- Tasks allocated to different members of the team, based from the Agile methodology
Initial Product Backlog
Sprint 1 Backlog
Priority Item Description Points Estimated
Duration

1 Data Sequence The diagram will show how the 5 3 days

Diagram user will interact with the GUI
and show how the input will be
passed on to a text file

2 GUI Design The design will give use a basic 3 2 days

idea of how the software will be
displayed on screen.

3 The first version of The product will be the first 13 6 days

the program version of the program, reflecting
on what has been required in the
specification agreed by the team

4 Testing The produced program will be 5 3 days

tested to ensure that all the
functions specified in the
specification do follow
Paddy - The data sequence diagram

The diagram shows the flow of the program

How the program flows with 2 GUIs

- How the tasks & goals are added

- How they are displayed on the program

- How they are saved and load from a text

file
Aidan - The GUI design

The GUI Design is that of a calendar, where each

individual day on the calendar is a button that
allows you to select that date. You can then use
buttons at the bottom of the window to add and
delete any events to that date, as well as being
shown a list of deadlines already set.
Lukas - The implementation of the code

Python and TKinter is used ((Screenshots of the program))

2 GUIs are produced

- 1 for Calendar (for display)

- Options to add, load, save and edit

- 1 for Input (to add goals)

- Adding information of assignment

- Adding module information

Morgan - The Test Case and testing

The test cases focuses on the main functions

The results of the tests are positive

Improvements have been discussed

George - The testing and review
The tests are carried out with the test cases
Testing the whole basic program
Noting what can be improved
The program does perform the basic and
important functions
Validations needs to be included in the program
Options could be included to indicate a type
- Task, Sub-goal etc
Review of the first sprint

- The first version of the product met the basic requirements

- Additional features have been discussed

- More information of inputs could be included

- Testing would have to be specific

Second Sprint Summary

The second sprint focuses on

- The calendar GUI improvements

- Including additional features to taskbar menu

- Adding navigation of calendar

Third Sprint Summary

The third sprint focuses on

- Adding more input boxes on options

- Include validations of inputs

- Saving and loading goals, tasks etc.

Fourth Sprint Summary

The fourth sprint focuses

- Implementing features to the final program

- Including reminders

- Final test plan set up and conducted

What went well? Any improvements?

What went well: What could go better:

- We have followed the agile methodology - We could hold more frequent meetings
during term holidays
- We collaborated in sharing ideas and
review progress - Arrange emergency plans for absentees

- We kept track of previous sprints and - Include more frequent code reviews
reflect on them