You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello everyone, we are Group 1, thank you for your time today. We're looking forward to getting started here, with our sprint review.
Slide 2
Our first plan of action was to delegate roles to each member in our group, and establish our development teams, including teams for Front-end, Back-end, and an API / DB team. I myself am the SCRUM master, and Alex is our Product owner.
Slide 3
Today we're showing off our web app, with a desktop and mobile view. We'll also show you our API, along with documentation for 3rd party developers. We'll also show our database, completed with the datasets provided. Our back end team have been working on tying all of these elements together, and we're really proud of what our teams have managed to get done in this Sprint.
Slide 4
We'll begin with our Front-end team (introduce Kyle & Alba).
Our primary goals for Sprint 1 revolved around setting the stage for future functionalities and enhancing the user experience. We knew we needed to implement a dynamic map which would clearly display all branches and ATMs. We knew we would need to begin development in preparation for future functionality, including features such as searching, filtering, and a list view for branches and ATMs. We also knew we had to ensure the website was fully compatible with mobile devices.
So what did we accomplish? Firstly we successfully implemented a dynamic map, leveraging LeafletJS and OpenStreetMap to accomplish this. By the end of the sprint, in collaboration with the Back-end Team, we managed to seamlessly integrate Branch/ATM data into the map allowing users to visualise all branches and ATMs in the country. Blue markers represent branches, and the grey markers represent ATMs. When clicked it will currently display very basic information about the name of the branch or ATM, and in sprint 2 we plan to flesh this out further to show more valuable information to the user. Geolocation is also used to automatically centre in on the user's location, improving their experience. Checkboxes have been added in preparation for filtering and a slider will be used to narrow or expand the user's search radius. We have also implemented the design for a list view that will display all the branches and ATMs, and sliding animations have been used to enhance the user experience and allow for a clean design of the website. We have also managed to make the website fully responsive for mobile and tablet devices, allowing the website to be used on any device.
Slide 5
[INSERT BACK-END STUFF]
Slide 6
[INSERT API / DB STUFF]
Slide 7
We inevitably ran into some issues during development, which we wanted to make you aware of. A big challenge we faced was that we didn't take enough time to plan our sprint before we began development. We should have done more planning about the work that we should have done during sprint 1. A big problem we ran into is that - "How do we know that we are done working during the sprint." Basically have a definition of done for our sprint 1 for each of our areas that we are working on so we know what we are doing.
Another big issue we faced was that a lot of our development team fell ill mid-sprint, which made it a lot harder to communicate, and work together in person. With half of us working in the QMB, and the other half working from home, Pair programming became more challenging and we relied on online communication between our SCRUM team.
We also ended up spending a lot time moving things from the product backlog to the sprint backlog, as we didn't separate these on GitHub. Originally we had both the Sprint backlog and Product backlog being handled in one Kanban board, which was proven to be insufficient.
Slide 8
Going into Sprint 2, we're going to take more time to plan our development beforehand, and make sure we estimate the time each task will take to complete. This will help us with time management, and give the development teams a clearer definition of what is expected to be complete by the end of the Sprint. We plan to use T-shirt sizing for our time estimates, as we have agreed that this is our preferred way to incorporate this into our Sprint plan
With our illness issues in this Sprint, we remedied this by having them work remotely, and used Discord, as well as GitHub features to be able to communicate with them. We adopted a 50:50 split between remote and in-person working, which worked very well for us, as we've all had previous experience using Discord and GitHub.
For our backlog issues, we have now separated these backlogs into their own respective Kanban boards, which has helped the workflow significantly. If we could have made these changes at the very start, we could have saved ourselves a lot of time, and had our development teams work more efficiently. We look forward to taking these changes into our second Sprint, and we believe we'll see a vast improvement
Slide 9
There are obviously some aspects of the project that we have not managed to complete this week, and we plan to have these finished for the end of the next Sprint. WCAG accessibility is something we want to look into in Sprint 2, including text alternatives for images, and ensuring that the on-screen text is big enough for users with vision problems
We also want to implement the bank branch admin login system that you mentioned in our previous meeting, where administrators can log into the web app, and make changes to their branches and ATM's
We also look to include analytics into our project, where bank executives are able to view statistics around the searches for branches and ATM's
Filtering searches is also something we didn't manage to complete in this Sprint, but we plan to complete before our next meeting. At the moment, user's can view the different types of search criteria, but these check-boxes are unfortunately not functional as of today. We're confident we can have this completed by next week, and are eager to start working on it.
[INSERT something about street names]
Slide 10
To wrap things up for today's meeting, we're very happy with what we've been able to show you, and are very confident in our progress this week. We've made steady, consistent progress with all aspects of development. Our documentation has also been very thorough, and we've become very comfortable using GitHub discussions and Projects. One of the highlights of our group work has been our use of GitHub, we think we used it very effectively to keep track of our use of the agile methodology, as well as to gain understanding of the project. We also were very happy with how our pair programming went, splitting into groups based on expertise and past experiences has proven to be very useful for us, and we have no complaints regarding anyone's contributions.
Slide 11
To improve in Sprint 2, we're going to spend more time planning the Sprint out before development starts, especially using the T-shirt size method to establish time-estimates for each issue. [INSERT something about priority of user stories, Alex was saying]. We also found code reviews to be really helpful during our Sprint, and so we plan to have more of these during our second Sprint.
Slide 12
For our next Sprint, we plan to work on WCAG accessibility for the web app, as well as admin login, with the ability to edit their branches and view analytics. We also are looking to complete the filtering of search criteria, as well as allowing the user to search via street names.
Slide 13
Thank you very much for your time today guys, we've really enjoyed working with you, and we're very confident in our first Sprint. We really look forward to continuing to work with you, and are open to any criticisms or suggestions of things we could change or improve. Any questions or feedback would be greatly appreciated, as we want to make this project as good as it can be, and to match your requirements effectively. Thanks again for meeting with us today, we really appreciate it
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Slide 1
Hello everyone, we are Group 1, thank you for your time today. We're looking forward to getting started here, with our sprint review.
Slide 2
Our first plan of action was to delegate roles to each member in our group, and establish our development teams, including teams for Front-end, Back-end, and an API / DB team. I myself am the SCRUM master, and Alex is our Product owner.
Slide 3
Today we're showing off our web app, with a desktop and mobile view. We'll also show you our API, along with documentation for 3rd party developers. We'll also show our database, completed with the datasets provided. Our back end team have been working on tying all of these elements together, and we're really proud of what our teams have managed to get done in this Sprint.
Slide 4
We'll begin with our Front-end team (introduce Kyle & Alba).
Our primary goals for Sprint 1 revolved around setting the stage for future functionalities and enhancing the user experience. We knew we needed to implement a dynamic map which would clearly display all branches and ATMs. We knew we would need to begin development in preparation for future functionality, including features such as searching, filtering, and a list view for branches and ATMs. We also knew we had to ensure the website was fully compatible with mobile devices.
So what did we accomplish? Firstly we successfully implemented a dynamic map, leveraging LeafletJS and OpenStreetMap to accomplish this. By the end of the sprint, in collaboration with the Back-end Team, we managed to seamlessly integrate Branch/ATM data into the map allowing users to visualise all branches and ATMs in the country. Blue markers represent branches, and the grey markers represent ATMs. When clicked it will currently display very basic information about the name of the branch or ATM, and in sprint 2 we plan to flesh this out further to show more valuable information to the user. Geolocation is also used to automatically centre in on the user's location, improving their experience. Checkboxes have been added in preparation for filtering and a slider will be used to narrow or expand the user's search radius. We have also implemented the design for a list view that will display all the branches and ATMs, and sliding animations have been used to enhance the user experience and allow for a clean design of the website. We have also managed to make the website fully responsive for mobile and tablet devices, allowing the website to be used on any device.
Slide 5
[INSERT BACK-END STUFF]
Slide 6
[INSERT API / DB STUFF]
Slide 7
We inevitably ran into some issues during development, which we wanted to make you aware of. A big challenge we faced was that we didn't take enough time to plan our sprint before we began development. We should have done more planning about the work that we should have done during sprint 1. A big problem we ran into is that - "How do we know that we are done working during the sprint." Basically have a definition of done for our sprint 1 for each of our areas that we are working on so we know what we are doing.
Another big issue we faced was that a lot of our development team fell ill mid-sprint, which made it a lot harder to communicate, and work together in person. With half of us working in the QMB, and the other half working from home, Pair programming became more challenging and we relied on online communication between our SCRUM team.
We also ended up spending a lot time moving things from the product backlog to the sprint backlog, as we didn't separate these on GitHub. Originally we had both the Sprint backlog and Product backlog being handled in one Kanban board, which was proven to be insufficient.
Slide 8
Going into Sprint 2, we're going to take more time to plan our development beforehand, and make sure we estimate the time each task will take to complete. This will help us with time management, and give the development teams a clearer definition of what is expected to be complete by the end of the Sprint. We plan to use T-shirt sizing for our time estimates, as we have agreed that this is our preferred way to incorporate this into our Sprint plan
With our illness issues in this Sprint, we remedied this by having them work remotely, and used Discord, as well as GitHub features to be able to communicate with them. We adopted a 50:50 split between remote and in-person working, which worked very well for us, as we've all had previous experience using Discord and GitHub.
For our backlog issues, we have now separated these backlogs into their own respective Kanban boards, which has helped the workflow significantly. If we could have made these changes at the very start, we could have saved ourselves a lot of time, and had our development teams work more efficiently. We look forward to taking these changes into our second Sprint, and we believe we'll see a vast improvement
Slide 9
There are obviously some aspects of the project that we have not managed to complete this week, and we plan to have these finished for the end of the next Sprint. WCAG accessibility is something we want to look into in Sprint 2, including text alternatives for images, and ensuring that the on-screen text is big enough for users with vision problems
We also want to implement the bank branch admin login system that you mentioned in our previous meeting, where administrators can log into the web app, and make changes to their branches and ATM's
We also look to include analytics into our project, where bank executives are able to view statistics around the searches for branches and ATM's
Filtering searches is also something we didn't manage to complete in this Sprint, but we plan to complete before our next meeting. At the moment, user's can view the different types of search criteria, but these check-boxes are unfortunately not functional as of today. We're confident we can have this completed by next week, and are eager to start working on it.
[INSERT something about street names]
Slide 10
To wrap things up for today's meeting, we're very happy with what we've been able to show you, and are very confident in our progress this week. We've made steady, consistent progress with all aspects of development. Our documentation has also been very thorough, and we've become very comfortable using GitHub discussions and Projects. One of the highlights of our group work has been our use of GitHub, we think we used it very effectively to keep track of our use of the agile methodology, as well as to gain understanding of the project. We also were very happy with how our pair programming went, splitting into groups based on expertise and past experiences has proven to be very useful for us, and we have no complaints regarding anyone's contributions.
Slide 11
To improve in Sprint 2, we're going to spend more time planning the Sprint out before development starts, especially using the T-shirt size method to establish time-estimates for each issue. [INSERT something about priority of user stories, Alex was saying]. We also found code reviews to be really helpful during our Sprint, and so we plan to have more of these during our second Sprint.
Slide 12
For our next Sprint, we plan to work on WCAG accessibility for the web app, as well as admin login, with the ability to edit their branches and view analytics. We also are looking to complete the filtering of search criteria, as well as allowing the user to search via street names.
Slide 13
Thank you very much for your time today guys, we've really enjoyed working with you, and we're very confident in our first Sprint. We really look forward to continuing to work with you, and are open to any criticisms or suggestions of things we could change or improve. Any questions or feedback would be greatly appreciated, as we want to make this project as good as it can be, and to match your requirements effectively. Thanks again for meeting with us today, we really appreciate it
Beta Was this translation helpful? Give feedback.
All reactions