OFBiz Scrum, one year experience

This blog is a follow up of the earlier blog I wrote introducing the OFBiz scrum component we use in our Scrum projects we do for customers all over the world. This blog assumes you have the knowledge explained there.

We are now using the Scrum methodology (framework) for almost one year and it improved our development process considerable. We did however add a number of extra function to the Scrum framework like QA an unplanned backlog items.

What did improve?

  1. The development process is now completely transparent to the customer/product owner.
  2. All software updates are recorded in svn and are visible in the scrum component for team members and QA (Quality Assurance).
  3. Much more formal and documented way of implementation with allows top level specifications to be estimated.
  4. We use Chat for the scrum meetings in the morning which show to the customer what is happening on a daily basis.
  5. We can invoice on a backlog item level to which a customer can relate.

We think that using scrum in a outsourcing environment needs a supporting system. We used it for a number of customers and the OFBiz scrum component works very well here.

However we made a number of extensions to the Scrum framework:

  1. Next to the planned backlog we now also allow for unplanned, urgent backlog items which can be added to a 'unplanned' sprint which is running continuously. These unplanned items always take priority above the planned items.
  2. We introduced a QA function where backlog items are tested by a separate QA group who are able to add 'error' tasks and can approve the completion of a backlogitem. A function has been added which enables the listing of completed backlogitems which are not tested yet.
  3. In order to track the time spend in meetings, for every sprint, backlogitems for this purpose are automatically added.
  4. We now achieved a full integration with SVN where SVN updates are listed on a task, backlog, product, system and committer level with the possibility to show the actual changes made on a source line level.
  5. We now also have a link to the HR component for people to register the vacation/sick days in the scrum time sheet.
  6. It is now also possible to send and receive email on a product and backlog level to enable the communication between the product owner and scrum team.
  7. We added the role of stakeholder who has read access to the products of his company.

What is planned for the future?

  1. create an internal chat system to have daily scrum meetings directly integrated with a sprint
  2. Allow a customer to enter error reports against existing backlog items./li>

So in general this is an excellent experience using this Scrum framework, it will need some extensions like QA and urgent unplanned backlog items but is a sound basis for software development.



We have a demo of our current system available at http://scrum.antwebsystems.com

Let us know you are interested at support@antwebsystems.com