Lulit Asfaw - Scrum Master and Developer
Saipavanlumar Muppalaneni - Product Owner and Developer
Melkyas Eshetu- Developer\Tester
To efficiently order our backlog we started out with writing out a foundation of user stories that we believed accurately covered the primary functionality of the application, TradeTalk. Based on their similarities, the user stories were grouped into three main epics. The epics are user registration, stock search & display, and automatic buy and sell signal. The three epics were prioritized based on the logical ordering of how they will be delivered. We believe this backlog ordering rationale will help us develop the primary functionalities of TradeTalk and continue to add/change features with each iteration.
- Update - Once we completed our sprint on Jira, the backlog and kanban board for Sprint 1 were no longer available and Jira didn't allow access to backlogs and boards of previous sprints. However, the Roadmap shows the completed stories and tasks within each epic for Sprint 1.
Our team used Kanban Board in Jira to assign, prioritize, and update tasks. It helped us to organize our work and focus on our workflow.
When the sprint 1 was completed, the Kanban Board was automatically cleared, so we recreated an image of the Kanban Board.
The sprint burndown chart in Jira provided a graphic representation of the rate at which our tasks are completed and the amount of work that remains to be done. As we complete our story points, our chart slopes downward until there are 0 story points left on the last day of the sprint.
Daily scrum meetings helped us improve our communication and identify impediments early on and work to resolve it. Below is a recording of one of scrum meetings.
Scrum.Meeting.Recording.mp4
By mobbing on our code, we improved communication and visibility within the team. It was also a great way to help eachother and resolve issues. Below is a video of the team mobbing on running the testing cases.
Code.Mobbing.Compressed.mp4
As per the requirement, we included 10 unit tests in our test suite. Below is a screenshot showing that the tests pass.
To inspect the outcome of Sprint 1 and determine features for our next iteration, we held a Sprint Review at the end of Sprint 1. Below is a video of our sprint review.
Sprint.Review.Meeting.mp4
Hosting URL:http://web-service-project.tunecareer.com/#/
Forecast: Our forecast for the work to be completed in Sprint 2 is 17 Story Points. This forecast contains seven individual stories, and their subtasks ranging from an estimated 2 story points up to 5 story points using the Fibonacci Scale.
Rationale: Sprint 1 gave us a working history as a team, which helped us understand our velocity and therefore, we didn't have to rely on collaborative guesses to determine our story points for Sprint 2. Once our product backlog was created, we grouped stories based on their relationship to specific functions and/or features of the TradeTalk Application to create three epics. After logically vieweing the epics, we assigned an order for completion.
Daily scrum meetings helped us improve our communication and identify impediments early on and work to resolve it. Below is a recording of one of the scrum meetings we held for Sprint 2.
Scrum.Meeting.Sprint.2.mp4
By mobbing on our code, we improved communication and visibility within the team. It was also a great way to help eachother and resolve issues. Below is a video of the team mobbing on running the testing cases.
Code.Mobbing.Sprint.2.compressed.mp4
As per the requirement, we included 20 unit tests in our test suite. Below is a screenshot showing that the tests pass.
Our team conducted a sprint review on 04/03 after the end of Sprint 2 were we addressed both positive and negative takeaways. Below is a video of our sprint review.
Sprint.2.Review.mp4
We have integrated Continuous Integration (CI) and Continuous Delivery (CD) pipelines with Bitbucket Cloud to automate our code from test to production. Continuous integration is an integral part of Scrum as it helps reduce risk and improve quality. With CD integrated, the code that is stored in our repository can be continuously delivered to production.
Hosting URL: http://web-service-project.tunecareer.com/#/
Forecast: Our forecast for the work to be completed in Sprint 3 is 25 Story Points. There are eight stories in this Sprint including subtasks; the stories range from an estimated 2 story points to 8 story points using the Fibonacci Scale. The story points estimated for this sprint are a lot higher from the previous sprints because we are also picking up the slack remaining after closing Sprint 3. With this being our final sprint, we wanted to ensure that our near and far vision for the application were fulfilled.
Rationale: In sprint 2, there was quite a bit of work to be done outside of the functional requirements to set up the project, and the team decided the importance of documenting those tasks and issues as stories and/or tasks in the future in order to get a more accurate depiction of the effort applied and the work completed. Which leads to our rationale for Sprint 3: We now have a working history as a team and we have two sprints to reference from (Yesterday’s Weather), so we were equipped to handle the 25 story points for Sprint 3.
To see subtask on the board find "GROUP BY" in the top right corner and select "Subtask." Note: Board only shows cards while sprint is active. Depending on the timing it may be empty. Please refer to the image below.
Burndown Report
Note: Ensure Sprint 3 is selected from the dropdown.
Daily scrum meetings helped us improve our communication and identify impediments early on and work to resolve it. Below is a recording of one of the scrum meetings we held for Sprint 3.
Sprint.3.Scrum.mp4
By mobbing on our code, we improved communication and visibility within the team. It was also a great way to help eachother and resolve issues. Below is a video of the team mobbing on running the testing cases.
Sprint.3.Code.Mobbing.mp4
Below are screenshots showing that we have at least 30 unit tests in our test suite that all pass; including the new tests we have added for Sprint 3.
Our team conducted a sprint review on 04/25 after the end of Sprint 3 were we addressed both positive and negative takeaways. Since we didn't have another sprint to look forward to, we addressed what we have learned from our project overall and expressed what we can take forward. Below is a video of our sprint review.
Sprint.Review.mp4
For the project we are utilizing Bitbucket to build and deploy our applications on each merge.
The primary motivation for using Bitbucket as the CI/CD tool was that it is a Git-based source code repository hosting service owned by Atlassian. Bitbucket also offers a free cloud plan. Another benefit of using the Bitbucket pipeline was the numerous common workflows and prebuit templates that were available for us to use as a starting point. We found many helpful documentation that helped us piece together any challenges we were facing.
Both the backend and frontend of TradeTalk are deployed to a production like environment upon each merge. In order to get the TradeTalk application up and running, we used Digital ocean: a reliable and easy-to-use cloud hosting solution.
Hosting URL: http://web-service-project.tunecareer.com/#/