Howdy there and welcome to week 6!
This weeks task was to get familiar with Scrum. To put it short, Scrum is a way to manage agile projects, mostly, but not only used in software engineering. In Scrum, at the beginning of a project, all work packages are documented and put in the so-called “backlog”. Then, for the development, there are “Sprints”. Every sprint is one or two weeks long and at the start of each sprint, the exact scope of the sprint is defined, so the work packages that are going to be done in this sprint are taken out of the project backlog and into the sprint baclog. During the sprint, every developer takes tickets out of the backlog and finishes them. The scope of the sprint does not change during the sprint itself, if there are any impediments that come up during the spint, they are planned into the next sprint. This way, it’s easier to get all work packages done by the end of the sprint.
As we already mentioned, we’re going to use YouTrack as project management tool. Luckily, YouTrack also has Scrum support, so we’re good to go right away. We already created the Sprint (Name is Elab#1) and added some Stories and Tasks to it. In theory, you should be able to have a look at our progress in this sprint via the Scrum Board, Burndown Diagram and the Cumulative Flow Chart, although we had some problems with the sharing of those reports so feel free to contact us if it doesn’t work properly. Also, in our case, the tasks for this sprint are not all created yet as we don’t know Angular and Node too well yet and first have to get an impression on what exactly has to be done in order to complete the goal for this sprint, so please don’t be too harsh with us 😀
As we are using IntelliJ IDEA, support for YouTrack is pretty good, so it was quite easy to get the task list and time tracking to work in the IDE as you can see in the following screenshots.
In our case, for the first sprint, Elab#1, contains the work packages for the most important use case, “Search for Product”. This is also the base for the other use cases, which is why we decided to work on this use case first. As our other main component, the Web Crawler, is not yet available, we’re going to create some demo Data in our Database so we can already work on the frontend without having to guess how it’s going to look like.
Alright, that’s it for this week! We hope it was interesting for you to read and we’ll see you again next week! Have a nice one 🙂
Your Betterzon Team
Dear Betterzon Team,
first we want to say it’s very nice that you explained the agile manage system SCRUM. So everbody can follow you if you explain how you managed that with your project.
We think that you organized your project very good, but maybe it would be easilier to understand what you explain with the sprints, board… if you would share a screen to visualize.
Just a little thing, the sprint should called “Elaboration#1” instead of “Elab#1”, but we think alos that you have the freedom to change that <3
We are very interested in your blog post next week and what you will implement this week.
Your friend from TaskHub
Dear Betterzon Team,
thanks for sharing this week’s progress with us. I really liked it that you explained everything about Scrum and gave sort of a “reminder” so other people can follow along.
About the actual stuff I couldn’t find something inheridently wrong with it….
But I agree with the commenter before that a screen shot of the scrum board would be nice since the access to the YouTrack page is not allowed. (I don’t know how to fix that one too but yeah xD).
Other than that. Great work. Keep it up. 🙂
Best regards
Team Futurum