Tag Archives: Product Backlog

The First Artifact

Entry 9, Day 16

     “The product backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product.”

– Scrum Guide

Being recently in the tools department, let’s continue the topic and look for something to manage The Product Backlog.  But wait, what’s that?

As I’ve said, I’m not going to do full fledged Scrum here, because there is no point in that. However I will keep some of Scrum elements. For example, Scrum defines so called Artifacts. There is the Product Backlog, there is a Sprint Backlog and there is an Increment. I’ll keep the Product Backlog. I will probably not need Sprint Backlog. And we will see about Increments later.

So, the Product Backlog (or simply the Backlog from now henceforth) is where the idea of the product is kept. The idea might be more or less clearly and precisely defined, usually the higher the priority, the better the definition. The Backlog is composed of Items. Single Item might be a requirement, feature, enhancement, bugfix or anything that is going to change the product. Changes may be indirect and be without immediate value, say “Setup Tomcat” is actually an internal task, but it is required to proceed for me.

My needs are simple. I need a tool where I can add items in at least three categories – to do, ongoing and done. I need to be able to easily change priority (distance from top of the list), move between categories (say it’s ongoing / done) and edit Items. The tool should be cloud based (fancy term recently), free and publicly accessible.

In my work, we have mostly used Excel with quite advanced scripting (hi Kamil ;)) to help with moving, changing and calculating stuff. Sometimes we would just take a pin board and stick notes to it (It is common with Sprint Backlog, but not really with Product Backlog). Or simply there was no public Backlog whatsoever (well…).

But Excel has drawbacks. First, it is a desktop tool, and I want to share stuff in the blink of an eye. So, I could go for Google Spreadsheets, but still manipulating Items would require some effort. Let’s look for something more dedicated then. Quick research convinced me that there is an overwhelming number of tools to choose from. You can check out Wikipedia’s comparison of project management tools, You can then narrow the criteria to Agile tools. I’ve taken a look here and there. I’ve decided to give some of them a try.

So first, there is Jira. It was used by some teams around me. But apparently, it is not free, and is too big for my needs. We need simplicity. Out.

Someone mentioned when I was sniffing around. Unfortunately, while it’s simple, it’s also more of a calendar tool, not really good for me. Out.

Then, there are quite a few tools (I’ve checked iceScrum), that are open source, but there is no free hosting. Either you download and host by yourself or you pay. I want it quick, I want it now, I want it free. And I don’t have a hosting department operational yet. Out.

There are also promising tools closed source, but they are paid (e.g. Agilo for Scrum). Well, out.

There was one tool that was free and looked nice. The AgileFant.  I’ve played with it a bit, but it turns out to be too cumbersome for me. There were some UI glitches and manipulating items was not that simple as I wanted. Still it might be a valid option for fully Scrum team.

And finally there was Trello. Few friends actually recommended me this and it turns out to be perfect for my needs. It’s simple, intuitive, adorable and it is flying free above the clouds. As a welcome, you get three boards: to do, doing and done. You can quickly add Items, move vertically and horizontally, edit, add categories and make the board public. I’m not going to give you full review, that’s not what I’m here for. But you may want to check article here. The Wired had an article about coolest 7 startups you haven’t heard of, and Trello was one of them.

So, I have a lingering Product Backlog. You may check it out here. The link will be always available from the BookSentry, the main project page.

Huh, that was a long one. In the next episode, I’m going to talk about the environment. Namely the Server and the Database.

p.s. I’m using Wikipedia links a lot. It’s not because I’m a noob. My intent is to give you some quick and neutral overview of the subject at hand. You can get easily to subject’s home page (if it has any) from Wikipedia page for further, official details.


1 Comment

Posted by on August 17, 2014 in Agile, BookSentry


Tags: , , ,

Ideas are bulletproof

Entry 2, Day 2

“Behind this mask there is more than just flesh. Beneath this mask there is an idea… and ideas are bulletproof.”



From the environment setup point of view, I’ve just done the following things:

  • Downloaded Eclipse Luna (cutting edge, you know…)
  • Downloaded JDK 8, try to run Eclipse…
  • …since it did not work, update Path variable
  • …since it still did not work add -vm to eclipse.ini
  • …since well… throw out JDK and get new one, now 64 bits to match Eclipse (every single time…)
  • Aaand it worked


I’ve managed to do some workspace setup, get back to classic UI, and write my first program in Java 8 utilizing Lambdas. Lets call it a day in this scope.

From the Idea point of view…

Ok, lets start from the beginning. At the beginning there was a Client who had some money, wanted some software written for him to do some stuff that will bring more money. Since I’m now my own client, I don’t want any money (at least not with this project), lets skip to the point to what I’m trying to achieve here. To the Idea.

BookSentry is going to have the following base features:

  • User can register
  • User can view, add, remove? and modify? books
  • User can view their own private list of books they have finished (or claim to have finished), view and modify this list

That is the initial idea. Some further features might be:

  • Registration process involves an email
  • User can search books using filters and paging
  • User can get more details about the book via some integration with Amazon
  • User can see some statistics, monthly/yearly reads, favourite genres etc
  • User can add other Users to his friends group.
  • User has a public profile
  • User can somewhat communicate with each other, send messages, leave comments
  • User can somewhat compare themselves with others
  • There are some kind of notifications about ongoing events
  • User can rate books
  • User can change password, remove account
  • Application doesn’t look like 1998 crap (ekhm… I was going to say “Application is aesthetically pleasant”)
  • Application is responsive and gentle with bandwidth (ajax)
  • Admin can manage Users
  • Logging
  • more…

Let’s stop here. In the next episode, we are going to talk about the roles in the project even though there is only one person to assume them.

And maybe more.

Here is your picture of Toothless:



Leave a comment

Posted by on August 3, 2014 in BookSentry